PCAnywhere Locking Registry?

[Patrick]

There has been persistent Userenv error as listed below on a Win2K Server
SP4 with the latest Service Pack, IIS5.0, SQL Server 2000 SP3, Symanctec PC
Anywhere 10.5, Terminal Services, Domain Controller, McAfee Virus Scan
Enterprise 7.1.0.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 11/05/2004
Time: 08:44:41
User: NT AUTHORITY\SYSTEM
Computer: COMPUTER-NAME
Description:
Windows cannot unload your registry file. If you have a roaming profile,
your settings are not replicated. Contact your administrator.

DETAIL - Access is denied. , Build number ((2195)).

I have now installed Microsoft User Profile Hive Cleanup Utilities from
http://www.microsoft.com/downloads/...6D-8912-4E18-B570-42470E2F3582&displaylang=en

And it is persistently logging the following on user log off-
Event Type: Information
Event Source: UPHClean
Event Category: None
Event ID: 1201
Date: 24/05/2004
Time: 17:33:08
User: Domain\DomainAdminUser
Computer: COMPUTER-NAME
Description:
The following handles in user profile hive Domain\DomainAdminUser
(S-1-5-21-484763869-1175051733-239522315-500) have been closed because they
were preventing the profile from unloading successfully:

awhost32.exe (1064)
HKCU (0xb7c)

awhost32.exe is the service for Symantec PC Anywhere. However, very
strangely, this error is logged on user log off even when only Microsoft
Terminal Service is used to log on to and log from the server in question!
Any remedies other than not to use PC Anywhere? We are using PC Anywhere
because it allow access to the "console" itself, which is useful for
applicaitons like Bullet Proof FTP Server because the only way to "access"
the server is to open up the icon from the task tray, which would not be
possible from the Terminal Services!

 

[Jason Hall [MSFT]]

--------------------

From: "Patrick" <[email protected]>
Subject: PCAnywhere Locking Registry?
Date: Tue, 25 May 2004 10:42:35 +0100
Lines: 49
..........

And it is persistently logging the following on user log off-
Event Type: Information
Event Source: UPHClean
Event Category: None
Event ID: 1201
Date: 24/05/2004
Time: 17:33:08
User: Domain\DomainAdminUser
Computer: COMPUTER-NAME
Description:
The following handles in user profile hive Domain\DomainAdminUser
(S-1-5-21-484763869-1175051733-239522315-500) have been closed because they
were preventing the profile from unloading successfully:

awhost32.exe (1064)
HKCU (0xb7c)

awhost32.exe is the service for Symantec PC Anywhere. However, very
strangely, this error is logged on user log off even when only Microsoft
Terminal Service is used to log on to and log from the server in question!
Any remedies other than not to use PC Anywhere? We are using PC Anywhere
because it allow access to the "console" itself, which is useful for
applicaitons like Bullet Proof FTP Server because the only way to "access"
the server is to open up the icon from the task tray, which would not be
possible from the Terminal Services!

--------------

Well, on Windows Server 2003 you can connect to the console through TS.
That would definitely get around your problem.

I know that there are Event ID 1000 problems that can occur when pcAnywhere
is used and the "pcAnywhere logoff" feature is not used to log off.

You might be able to get around this if you change TS to use the default
GINA to logon RDP sessions (pcAnywhere installs it's own GINA, which is
essentially just the logon box that you see).
To use the default Gina for Terminal Server clients, use the
following steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate the fUseDefaultGina value under the following key in
the registry:
3.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp
4. On the Edit menu, click REG_DWORD, type 0x1, and then click
OK.
5. Quit Registry Editor.
( this is from Q214488 )
---- I'm not sure what effect this will have on your environment, so PLEASE
test !!

Let me know if any of this helps, thanks.


--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Patrick]

After I used this settings, at first I thought the problem is sorted (i.e.
log off are still really quick and no UPHClean event logged to indicate
registry handle be locked). However, after I have uninstalled UPHClean
(UPHClean.exe -remove), the original problem (Userenv error) returned and I
had to resolve to installing UPHClean (which now log that AWHost32.exe is
locking on registry)

Weird!

 

[Jason Hall [MSFT]]

--------------------

From: "Patrick" <[email protected]>
References: <#[email protected]>

Subject: Re: PCAnywhere Locking Registry?
Date: Wed, 26 May 2004 09:44:02 +0100

After I used this settings, at first I thought the problem is sorted (i.e.
log off are still really quick and no UPHClean event logged to indicate
registry handle be locked). However, after I have uninstalled UPHClean
(UPHClean.exe -remove), the original problem (Userenv error) returned and I
had to resolve to installing UPHClean (which now log that AWHost32.exe is
locking on registry)

Weird!

--------------------

Looks like you should take the issue up with pcAnywhere support

--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.