Citrix Error: Your user profile was not loaded correctly

citrixwindows-server-2003

We get this error from out citrix server:

Your user profile was not loaded correctly!
You have been logged on with a temporary profile.
Changes you make to this profile will be lost when you log off.
Please see the event log for details or contact your administrator.

I am well aware there is a workaround by Citrix, that can be found here, but that doesn't permanently fix our issue. It seems to come back.

Any idea why that happens? Any suggestions on how to fix it?

Citrix version is 4.5 running on Windows 2003 x32

EDIT 14.IX.2012 @ 16.03 CT

I am sorry, let me clarify, it happens to some users, not all and not all the time.

Best Answer

I would advice you delete the user profile and then make a little adjustment to the profile username (Meaning do a rename of the username so it creates a fresh profile not minding the former username).

Regards

Related Solutions

Install Active Directory on Windows Server 2003 R2 SP2 without Event Log Errors

I've been installing Active Directory on W2K and W2K3 for years without any of the gyrations you're talking about.

Item 1 - That's an event ID 1005 from source DSrestor (per http://www.eventid.net/display.asp?eventid=1005&eventno=4658&source=dsrestor&phase=1). I've got a W2K3 R2 test box in my lab, installed from a slipstreamed W2K3 SP2 VL media and DCPROMO'd immediately after install. I have the full events log back to the OS load and this event isn't in any of them. I also checked out the archived event logs from the first W2K3 domain controller (installed with RTM W2K3 media in 2004) at a Customer site and I don't find this error anywhere. I don't know exactly what you're doing to make this error occur, but I've never seen it anywhere.

Item 2 - Microsoft has never fixed this. I tend to just ignore it. My various event log notification applications have been configured to ignore it, too. Yeah, you can resolve it if you want to. It doesn't bother me.

Item 3 - This isn't an error at all! This is telling you to do something. Configure a time source external to the domain. It's a one command-line procedure, if you don't mind using public NTP servers: "NET TIME /setsntp:pool.ntp.org" (specify any NTP server you want). I have no idea why the article you refer to makes such a big deal about it. You need an external-to-the-forest time source. (BTW: This only happens on the PDC emulator FSMO role-holder in the forest root domain. All subsequent DCPROMOs of all other DCs in the forest won't generate this message...)

You mention an "Item 4" that's a "DNS error", but you're really talking about event ID 1555, source "NTDS replication" I think. This isn't an error either. This article describes how the feature works and it's actually in the product for a utility purpose. If the initial synchronization isn't happening on your FSMO role-holder DC(s) you should really fix the replication problem instead of just squelching the error message. I can understand doing this in a test environment or in a DR dry-run, but in real life you should be fixing initial synchronization issues with your FSMO role-holders.

In summary: I don't know what you're doing to make item 1 happen. I can't tell you why Microsoft hasn't fixed item 2 but I don't care about it. Item 3 isn't an issue. Item 4 is an issue insofar as it's telling you that you need to fix broken initial synchronization.

How to fix a custom Event Viewer Log that merges automatically with the Application log

I haven't really tried to use custom event logs. But I have seen the problem you describe, with the same events appearing in more than 1 log. This can happen because event logs are memory mapped files, and if the total size of all event logs is greater than 300MB you will start to have issues.

See the 2nd or so page of this article:

http://technet.microsoft.com/en-us/library/cc722385%28WS.10%29.aspx

>On Windows XP-based computers, member servers, and stand-alone servers, the
>combined size of the Application, Security, and System logs should not exceed 300 MBs.

Best Answer

Related Solutions

Install Active Directory on Windows Server 2003 R2 SP2 without Event Log Errors

How to fix a custom Event Viewer Log that merges automatically with the Application log

Related Topic