Profiles Won't Load

  • Thread starter Thread starter Eric32
  • Start date Start date
E

Eric32

Guest
I know this issue has been around for a while but I can't find a solid
solution for it. We're running a Windows Server 2003 Terminal Server (no
roaming profiles). Every now and then we run into the problem where various
users cannot login -- they get an error that their profile cannot be loaded.
This particular server had this problem last year at one point and then was
fine for several months. Now this week it's happening again. One day it was
a few users, the next it was one or two users, and now today it's several.
The workaround we've done is to rename their profile and have them login
again (which creates a new profile). That's fine if it's one user but when
we have several it's a pain.

We've used the UPH Clean utility but that doesn't always appear to work.
Another thing is that this box is running Symantec AntiVirus which if I
remember correctly can cause problems. We have that set to exclude the Docs
and Settings folder where the profiles are stored. It also seems like UPH
Clean conflicts with Symantec AntiVirus.

Does anyone know of a good solution? Is it a Microsoft thing or could it be
a Symantec thing?
 
Re: Profiles Won't Load

As you wrote, there are a number of things that can cause this
problem. Check the EventLog on the server to see which of these
articles apply to your situation:

935649 - Error message when you try to log on to a Windows Server
2003-based terminal server: "Windows cannot load the user's profile
but has logged you on with the default profile for the system"
http://support.microsoft.com/?kbid=935649

944984 - The user profile may not be correctly unloaded when you
log off from a Windows Server 2003-based computer, and event 1517
is logged
http://support.microsoft.com/?kbid=944984

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?RXJpYzMy?= <Eric32@discussions.microsoft.com> wrote on
06 mar 2008 in microsoft.public.windows.terminal_services:

> I know this issue has been around for a while but I can't find a
> solid solution for it. We're running a Windows Server 2003
> Terminal Server (no roaming profiles). Every now and then we
> run into the problem where various users cannot login -- they
> get an error that their profile cannot be loaded. This
> particular server had this problem last year at one point and
> then was fine for several months. Now this week it's happening
> again. One day it was a few users, the next it was one or two
> users, and now today it's several. The workaround we've done is
> to rename their profile and have them login again (which creates
> a new profile). That's fine if it's one user but when we have
> several it's a pain.
>
> We've used the UPH Clean utility but that doesn't always appear
> to work. Another thing is that this box is running Symantec
> AntiVirus which if I remember correctly can cause problems. We
> have that set to exclude the Docs and Settings folder where the
> profiles are stored. It also seems like UPH Clean conflicts
> with Symantec AntiVirus.
>
> Does anyone know of a good solution? Is it a Microsoft thing or
> could it be a Symantec thing?
 
Back
Top