From: big on 16 Apr 2010 04:46
i can confirm the behaviour you mention as well as the day it first occurred (April 15th). Must either have something to do with the MS updates from the latest patch day or with us recently upgrading virus scanners from ESET NOD32 4.0.474 to 184.108.40.206.
any solutions yet ?
Roaming Profile cannot be found with several errors in Userenv.log
We have a bunch of Windows XP SP3 workstations that are logging into a
Windows NT4 domain and have roaming profiles stored on an NT4 fileserver. In
the past 2 days, several different users have started getting an error:
Your roaming profile is not available. You are logged on with the locally
stored profile. Changes to the profile will not be copied to the server.
Possible causes of this error include network problems or insufficient
security rights. If this problem persists, contact your network
DETAIL - %1
This is detailed here:
The problem is the event logs do not show anything but the 1506 EVID. The
computer is on the network, and can browse and read the server copy of the
profile in Windows Explorer. The permissions are set with the user having
Full Control of the remote profile folder and as owner with no change.
In userenv.log we see:
USERENV(3d4.3d8) 10:07:14:671 CheckRoamingShareOwnership : GetFileSecurity
failed with 58
USERENV(3d4.3d8) 10:07:14:750 IsCentralProfileReachable: Ownership check
failed with 8007003A
USERENV(3d4.3d8) 10:07:14:765 ReportError: Impersonating user.
USERENV(3d4.3d8) 10:07:22:812 GetUserDNSDomainName: MyGetUserNameEx failed
for NameDnsDomain style name with 1332
I am not sure what to make of this as the user does have permissions and is
the owner of the profile folder . . .
Previous Posts In This Thread:
Submitted via EggHeadCafe - Software Developer Portal of Choice
BizTalk: Writing and using a custom referenced functoid.