We help IT Professionals succeed at work.

Roming Profile Problems 2003 Server & Windows XP Pro

1,127 Views
Last Modified: 2010-06-25
I am a Linux admin, so my windows knowledge is lacking.  We have Server 2003 SP2 and our roaming profiles seem to work inconsistently.  For instance I have one user that can log into two machines fine and his profile follows him.  On another two machines he is unable to get his profile.  Other users can log into all machines fine.  It also seems that for whatever reason one particular machine is more susceptible to this issue at times.  I didn't set any of this up, so I'm at a loss on how to fix this.  For the user above, here are the three event log entries associated with his failed roaming profile.

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1509
Date:            7/10/2008
Time:            9:28:56 AM
User:            MYDOMAIN\John.Doe
Computer:      CUBE-1
Description:
Windows cannot copy file \\server\users$\jdoe\UserData\8V65EDO1\KN14HDCAQ56GT7CAL836G3CAGFC0S0CAFBY9FSCA5BFT1KCAS2CP10CAR2L7UCCA2CE88NCAJVHFS6CARUQ32WCALV3QN7CA7ENQF3CAF0DGAYCAY9L837CAG7U0INCAZHQ3VXCA9G6R3BCAOQX3K5CARVIINPCADN4OMRCAQPMXQRCAUUTRCGCAYYW9Z1CAIN13AC.xml to location C:\Documents and Settings\john.doe\UserData\8V65EDO1\KN14HDCAQ56GT7CAL836G3CAGFC0S0CAFBY9FSCA5BFT1KCAS2CP10CAR2L7UCCA2CE88NCAJVHFS6CARUQ32WCALV3QN7CA7ENQF3CAF0DGAYCAY9L837CAG7U0INCAZHQ3VXCA9G6R3BCAOQX3K5CARVIINPCADN4OMRCAQPMXQRCAUUTRCGCAYYW9Z1CAIN13AC.xml.

Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.

 DETAIL - The filename or extension is too long.


Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1515
Date:            7/10/2008
Time:            9:28:56 AM
User:            MYDOMAIN\John.Doe
Computer:      CUBE-1
Description:
Windows has backed up this user's profile. Windows will automatically try to use the backed up profile the next time this user logs on.

Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1511
Date:            7/10/2008
Time:            9:28:57 AM
User:            MYDOMAIN\John.Doe
Computer:      CUBE-1
Description:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

Also, I seem to get this in all machine event logs, maybe this is causing the inconsistent roaming profiles?


Event Type:      Warning
Event Source:      Userenv
Event Category:      None
Event ID:      1525
Date:            7/10/2008
Time:            9:28:05 AM
User:            MYDOMAIN\John.Doe
Computer:      CUBE-1
Description:
Windows has detected that Offline Caching is enabled on the Roaming Profile share - to avoid potential profile corruption, Offline Caching must be disabled on shares where roaming user profiles are stored.

Please let me know if any other information would help in resolving this.
Comment
Watch Question

Commented:
The length of the file names is an issue but the quickest way to fix this is to delete the local cached copies of the profiles on the problem machines from c:\documents and settings and then create new profiles for the affected users at the 2003 server via the ADUC. Copy the necessary documents from the old profiles first i.e favourites, documents etc.

Author

Commented:
I guess I'm confused with the long file name issue.   It does not seem to be an issue when the user logs into other boxes, only two of the boxes do I see this error.  

Also, as a linux admin, could you break down your instructions a little more?  I don't want to mess up his profile on the server so he is unable to get roaming profiles to work on any machine.

Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Commented:
did anyone ever come up with an answer for thsi one? we just started getting the same issue here and there with the long xml filename!?

Commented:
Seeing the long .xml file names here too.  I have always addressed this by deleting the long-named xml files.  I would like to know where the heck they are coming from though.  I don't like the solution myself, but I can't imagine that this will ever rise to the level of importance for MS to fix or otherwise work around it.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.