Discussion Locked

Event ID 1000 Can't Update Roaming Profiles

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

I and several of my clients are having a similar problem: When we log off and log back on our Windows 2000 computers (on a Windows 2000 domain) changes to our profiles are not saved. We receive Event ID 1000 in the Application event log (Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated.)

I have seen mention that this is related to hotfix 329170 and that the solution is to uninstall it. Unfortunately, we have SP4 installed and this hotfix can not be uninstalled, nor can it be installed over SP4 and then uninstalled. Does anyone have any other suggestions.

13 replies

by cluberti

Do you have the IPSEC Policy Agent running on the affected PC's? If not, enable the IPSEC Policy Agent in the services applet. Microsoft lists this as a workaround in Q319909.

The root of this problem is that the Activeds.dll file creates COM instances during initialization, which causes a handle to HKCU\Software\Classes to be cached. If activeds.dll is initialized by a service process (as it is when someone with roaming profiles logs on), the handle persists even after the user logs of (and thusly the profile isn't saved after log off).

According to Microsoft, the only workaround (if the service pack doesn't fix the problem) is to enable the IPSEC Policy Agent. If you want to read the details as to why this is happening, refer to Microsoft KB article Q319909.

by rgrisi

Found on Technet:

Check for a registry leak on the user's computer. You can find this by looking at Event Viewer:

Event ID: 1000

Category: None

Source: userenv

Text: Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.

To see if a disk quota has been exceeded

Make note of the size of the roaming user profile.
Check to see if there is a disk quota on the server that stores the roaming user profile.
Check to see if you have applied a Group Policy setting to limit roaming user profile size. The Group Policy setting that can limit the roaming user profile size is AdministrativeTemplates\UserSettings\System\LogonLogoff\Limit Profile Size.
To see if this Group Policy setting has been applied

Run Gpresult.exe in verbose mode.
Check the output to see if either of these registry keys exists:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DiskQuota\Limit

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DiskQuota\Threshold

If a disk quota is exceeded, as shown earlier, the following event is generated in the event log:

Event ID: 1000

Category: None

Source: userenv

Text: Windows cannot update your roaming profile. Contact your network administrator

by evilpeppard

Now, I have for sure found a solution to the roaming profile and 60 second logoff time problem. I have to thank members at www.asitis.org for helping find this solution (http://www.asitis.org/archives/000134.html).
I am running both SP3 and SP4 Windows 2000 servers in my Citrix Farm.

The problem lies with VNC Server. I am running the infamous Microsoft HotFix Q329170 on the SP3 servers. I found, on both the SP3 servers with the HotFix and the SP4 servers, if I removed VNC Server my roaming profiles started working again, the Userenv error disappeared and my logoff time dropped substantially.

Now, there were a few hoops I had to jump through to get VNC to uninstall properly before the roaming profiles started working. Please read this whole post before starting.

When I did a regular uninstall, I would get a message stating some components of VNC Server could not be removed and I needed to remove them manually. I also noticed the VNC Server Service was still registered and listed in the services. So this is what I did:
Go to the RealVNC or VNC program group depending on your version) and run the "unregister the VNC server service". Open Control Panel and uninstall VNC. (May get message stating some items could not be removed, remove them manually).Reboot server.Once the server came back up, if you are running Citrix or Terminal Server, immediately disallow remote logins.
Change user mode of the server to "install mode" by opening a command prompt and typing "change user/install". (TS and Citrix only).Run a fresh install of VNC and make sure you set the VNC Server service to re-register. You may get prompted about the directory and such already existing...overwrite everything and finish the install. Once the install is complete, you may be asked to reboot. Reboot server, disallow logins, change to "install mode" again and immediately go to the Control Panel and uninstall VNC. This time it will successfully unregister the VNC Server Service itself an

by Former member

A simlpe solution might be the effective security on the server profiles. I inadvertantly took ownership of all my server profiles, and locked out the indicuals, which effectively stopped them updating there own profiles...

This discussion is closed to new replies.