Discussion Locked

Roaming Profiles and Metaframe 1.8

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are experiencing a problem with roaming Roaming Profiles not loading on the users systems. It does not happen all the time and the systems we use are 95/98/2000. The main error messages we get are ---user desktop can not be loaded or cannot locate profile contact your system administrator. Sometime when a user waits about an hour and than tries to log in s/he will be able to get their roaming profile. Any help be wonderful. Ask questions if need be and will get back to you with the answers as soon as I can since I am interning and not at the office everyday.
some information i hope will help.
Using terminal services/metaframe/citrix 1.8
No Novell,
Using Windows NT servers,Service Pack 4
No Active directory,

Robin

10 replies

by luv2bike2

Added information: There IS a profile server that takes care of all profiles (Metaframe).

by graham.hilton920

firstly make sure you are running the latest server pack for metaframe and certainly think abouk upgrading your NT service packs, we run on NT sp5 just fine.....

by graham.hilton920

Have you tried this? If not have ago while i did out my old notes..

"User Environment: Windows cannot log you on because the profile cannot be loaded. Contact your network administrator.
DETAIL - The system cannot find the file specified."

Cause

You receive this error message if the the Default User folder, in the Documents and Settings folder is missing.

Resolution

If the folder is missing, log on as the administrator and create a new folder in the Documents and Settings directory named "Default User" (the folder can remain empty).

This new Default Users folder inherits the default permissions from the Documents and Settings folder of the parent.

After you create the new folder, log off, and then attempt to log on again as the new domain user who was receiving the error message.

by graham.hilton920

I have found this too!!

Because of a problem with the Tapisrv.exe file, opening the Program Neighborhood client may prevent a roaming profile from being saved back to the server.

The problem with the Program Neighborhood client is similar to the problem described in the Microsoft TechNet Article Q241572 concerning the Internet Connection Wizard. When you launch pn.exe, it calls the Telephony service to get user information. The Telephony service opens a subkey of HKEY_CURRENT_USER by using the RegOpenKeyEx function and then closes the key when it is finished.

In this case, RegOpenKeyEx opens not only a subkey but a predefined root key, HKEY_CURRENT_USER. The problem is that when you log off, the HKEY_CURRENT_USER key is still open and Winlogon.exe cannot unload the registry. Therefore, your roaming profile is not saved to the server.

When using the Pass-through client feature, this issue becomes more obvious because many different users will run pn.exe on the machine where this file is published. In addition, the workaround described below will not apply because it is not possible to stop a service in a published application.

Resolution (from Q241572)

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

Workaround

To work around this behavior, st

by graham.hilton920

I have found this too!!

Because of a problem with the Tapisrv.exe file, opening the Program Neighborhood client may prevent a roaming profile from being saved back to the server.

The problem with the Program Neighborhood client is similar to the problem described in the Microsoft TechNet Article Q241572 concerning the Internet Connection Wizard. When you launch pn.exe, it calls the Telephony service to get user information. The Telephony service opens a subkey of HKEY_CURRENT_USER by using the RegOpenKeyEx function and then closes the key when it is finished.

In this case, RegOpenKeyEx opens not only a subkey but a predefined root key, HKEY_CURRENT_USER. The problem is that when you log off, the HKEY_CURRENT_USER key is still open and Winlogon.exe cannot unload the registry. Therefore, your roaming profile is not saved to the server.

When using the Pass-through client feature, this issue becomes more obvious because many different users will run pn.exe on the machine where this file is published. In addition, the workaround described below will not apply because it is not possible to stop a service in a published application.

Resolution (from Q241572)

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

Workaround

To work around this behavior, st

by graham.hilton920

I have found this too!!

Because of a problem with the Tapisrv.exe file, opening the Program Neighborhood client may prevent a roaming profile from being saved back to the server.

The problem with the Program Neighborhood client is similar to the problem described in the Microsoft TechNet Article Q241572 concerning the Internet Connection Wizard. When you launch pn.exe, it calls the Telephony service to get user information. The Telephony service opens a subkey of HKEY_CURRENT_USER by using the RegOpenKeyEx function and then closes the key when it is finished.

In this case, RegOpenKeyEx opens not only a subkey but a predefined root key, HKEY_CURRENT_USER. The problem is that when you log off, the HKEY_CURRENT_USER key is still open and Winlogon.exe cannot unload the registry. Therefore, your roaming profile is not saved to the server.

When using the Pass-through client feature, this issue becomes more obvious because many different users will run pn.exe on the machine where this file is published. In addition, the workaround described below will not apply because it is not possible to stop a service in a published application.

Resolution (from Q241572)

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

Workaround

To work around this behavior, st

by luv2bike2

The current server pack for metaframe is SP3 and for Terminal server it is 5A. I have been told that it has corrected some of the problem but the problem still exists. Any other solutions?
Thanks for your input!!!!
Robin

This discussion is closed to new replies.