user account problem

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

I was wondering if anyone can help me with this error. I
have a W2K server environment with both W2k and NT4
clients.

I have one user who cannot access a shared program file on
the network from his new W2K machine. But he can access it
from his old NT4 machine. This is not an issue for any
other users who have been upraded from an NT4 machine to a
W2K machine. In the event viewer log on his W2K machine I
get this error, which I believe is associated with the
problem:

"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)). "

He does not have a roaming profile.

Can anyone help me?

Jeff
 
There is a hotfix available that address the error, 827825. There are a
number of software packages that can also cause the error, notably Norton
AV. Symantec has a patch if this is the case
--------------------
I was wondering if anyone can help me with this error. I
have a W2K server environment with both W2k and NT4
clients.

I have one user who cannot access a shared program file on
the network from his new W2K machine. But he can access it
from his old NT4 machine. This is not an issue for any
other users who have been upraded from an NT4 machine to a
W2K machine. In the event viewer log on his W2K machine I
get this error, which I believe is associated with the
problem:

"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)). "

He does not have a roaming profile.

Can anyone help me?

Jeff
Click to expand...

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
 
I applied service pack 4, and the event error went away,
which is good. But the user still cannot access the
shared program file. This is getting rather frustrating.

What else can I do?
 
Back
Top