Roaming Profile cannot be found with several errors in Userenv.log

[jmp242]

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
administrator.

DETAIL - %1

This is detailed here
http://www.microsoft.com/technet/su...odVer=5.2&EvtID=1506&EvtSrc=Userenv&LCID=1033

The problem is the event logs don't 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'm not sure what to make of this as the user does have permissions and is
the owner of the profile folder . . .

Any ideas?

 

[big anton]

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 4.2.40.10.

any solutions yet ?

regards, tony



jmp242 wrote:

Roaming Profile cannot be found with several errors in Userenv.log
15-Apr-10

We have a bunch of Windows XP SP3 workstations that are logging into
Windows NT4 domain and have roaming profiles stored on an NT4 fileserver. I
the past 2 days, several different users have started getting an error
Your roaming profile is not available. You are logged on with the locall
stored profile. Changes to the profile will not be copied to the server
Possible causes of this error include network problems or insufficien
security rights. If this problem persists, contact your networ
administrator

DETAIL - %

This is detailed here
http://www.microsoft.com/technet/su...rodVer=5.2&EvtID=1506&EvtSrc=Userenv&LCID=103

The problem is the event logs do not show anything but the 1506 EVID. Th
computer is on the network, and can browse and read the server copy of th
profile in Windows Explorer. The permissions are set with the user havin
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 : GetFileSecurit
failed with 5
USERENV(3d4.3d8) 10:07:14:750 IsCentralProfileReachable: Ownership chec
failed with 8007003
USERENV(3d4.3d8) 10:07:14:765 ReportError: Impersonating user
USERENV(3d4.3d8) 10:07:22:812 GetUserDNSDomainName: MyGetUserNameEx faile
for NameDnsDomain style name with 133

I am not sure what to make of this as the user does have permissions and i
the owner of the profile folder . .

Any ideas?

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
BizTalk: Writing and using a custom referenced functoid.
http://www.eggheadcafe.com/tutorial...08-71c2b1127e40/biztalk-writing-and-usin.aspx

 

[big anton]

the issue has most likely to do with a recent security patch by microsoft (KB980232, see: http://support.microsoft.com/kb/980232/en-us).

When i uninstalled it (i ignored the dependency warning for KB979309) everything went back to normal and the user profiles were again successfully written to and copied from the NT4 Server.
Someone should contact Microsoft and address this issue to them since the web page related to the security patch does not list any known problems. Microsoft rates the bugfix critical so automatic update will try to re-install it as long as you do not disable/hide the update via wsus or windowsupdate.



big anton wrote:

same here...
16-Apr-10

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 4.2.40.10.

any solutions yet ?

regards, tony

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Report Engine, Part 2
http://www.eggheadcafe.com/tutorial...c9-cf3a9ee210a7/wpf-report-engine-part-2.aspx

 

[dg]

Thanks. removing KB979309 worked for me. I appreciate you taking the time to
help!

 

[PA Bear [MS MVP]]

KB979309 is a Critical security update. If it's not installed, the computer
remains vulnerable to the exploits addressed by the update. Translationi:
You want it installed.

See the "How to obtain help" section of
http://support.microsoft.com/kb/979309

For home users, no-charge support is available by calling 1-866-PCSAFETY
(1-866-727-2338; and/or 1-866-234-6020 and/or 1-800-936-5700) in the United
States and in Canada or by contacting your local Microsoft subsidiary.
There is no-charge for support calls that are associated with security
updates. When you call, clearly state that your problem is related to a
Security Update and cite the update's KB number (e.g., KB979309).

Or you can...

Start a free Windows Update support incident email request:
https://support.microsoft.com/oas/default.aspx?gprid=6527

Customers who experience issues installing Microsoft security updates also
can visit the following page for assistance:
https://consumersecuritysupport.microsoft.com/

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.