Running Presentation server 4.0 and all of a suddent, users cannot connect to roaming profiles. Our roaming profiles are hosted on a Netapp CIFS share and has worked flawlessly since being moved there. Citrix servers are showing Event ID 1511 & 1521. When we attempt to browse the the profiles we can get there by netbios name, fqdn, and IP so connectivity dosn't seem to be an issue. The perms seem appropriate as well. We also tried the following KB as another forum recommended this (
http://support.microsoft.com/kb/935649 ) without success. I tried deleting my roaming profile as this has resolved manny issues for us in the past however now it won't write a new profile for me. Any ideas would really help. We are running W2k3 sp 1 in a 7 server farm.
Hi, was the share moved by someone? I would start by checking the permissions on the TSProfile share to make sure everyone can write.
All the perms are appropriate. I even tried tweeking my AD account to point to a different share on a windows box and I still have the same problem. On the new share I gave my account full share perms and full ntfs perms. I did the same on the old share to and nothing is working. I'm really at a loss on this one.
Is the Policy Set Path for TS Roaming Profiles still enabled in AD?
I apologize for my ignorance, but where would I check that?
At the OU where your Citrix Servers most likely are.
Computer ConfigurationAdministrative TemplatesWindows ComponetsTerminal ServicesSet Path for TS Roaming Profiles - open it and make sure it is enabled with the correct \\servername\sharename for your profiles
OK, thanks. That policy is not configured. We do all of that through ADUC
And just to clarify... you've checked both the SHARE permissions AND the FILE permissions on the share?
Why is it called "Common Sense"? It doesn't seem all that common!
Good point.....
ran the userenv.log and it shows the following:
USERENV(3d0.3968) 14:34:20:766 GetOldSidString: Failed to open profile profile guid key with error 2USERENV(3d0.3968) 14:34:20:766 GetProfileSid: No Guid -> Sid Mapping availableUSERENV(3d0.3968) 14:34:20:766 TestIfUserProfileLoaded: return with error 2.USERENV(3d0.3968) 14:34:20:766 GetOldSidString: Failed to open profile profile guid key with error 2USERENV(3d0.3968) 14:34:20:766 GetProfileSid: No Guid -> Sid Mapping availableUSERENV(3d0.3968) 14:34:20:766 LoadUserProfile: Expanded profile path is \\osifiler1\profiles$\Profiles\ndoumerc\ndoumerc.NAUSERENV(3d0.3968) 14:34:20:766 ParseProfilePath: Entering, lpProfilePath = <\\osifiler1\profiles$\Profiles\ndoumerc\ndoumerc.NA>USERENV(3d0.3968) 14:34:20:766 CheckXForestLogon: checking x-forest logon, user handle = 2652USERENV(3d0.3968) 14:34:20:766 CheckXForestLogon: policy set to disable XForest checkUSERENV(3d0.3968) 14:34:20:766 AbleToBypassCSC: Try to bypass CSCUSERENV(3d0.3968) 14:34:20:766 AbleToBypassCSC: tried NPAddConnection3ForCSCAgent. Error 53USERENV(3d0.3968) 14:34:20:782 ParseProfilePath: CSC bypassed failed. Ignoring Roaming profile pathUSERENV(3d0.3968) 14:34:20:782 ReportError: Impersonating user.USERENV(3d0.3968) 14:34:20:782 ReportError: Logging Error <Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator.
the profile path that it lists is wrong. Where would I adjust this? in ADUC it shows the correct unc path.
Are you sure there are no Group Policies assigning this? GPO will always override ADUC.
We searched the registry and found a ton of entries with the legacy path to our Roaming Profiles. We corrected these entries and viola, it worked like a champ. What a pain in the a$$. No idea why it did this. Looking forward to upgrading to a new farm.
While the upgrade will no doubt bring some improvements and a fresh start, it may be worth the time to figure out what caused the problem. I'd hate to go through the effort of building a new farm only to have a similar problem crop up again.