Link to home
Create AccountLog in
Avatar of Jsmply
Jsmply

asked on

Win2k8 keeps hanging on "Please wait for the user profile service"

Hi Everyone,

Our server 2008 box keeps hanging on "Please wait for the user profile service" when logging on or off, even locally.  Occasionally while signing on and off via TS you get the message that the terminal server is busy processing another request as well.

Done some google searching, can't find anything out of the ordinary.  The user profile service issue can occur even when no one is logged in via TS so although they may have a common cause, they can orruc independent of one another.  

Nothing really changed on the box recently.  This did occur a long time ago and seemed to resolve itself, but now it's back and happening almost daily.   it's used very infrequently and is not a Domain Server, it's actually not even presently joined to a domain.  

There is only ONE nic on this server (I mention that because a lot of other google results yielded two nics and an improper binding order as a cause).

Any input would be appreciated.
ASKER CERTIFIED SOLUTION
Avatar of sAiyAnstAr
sAiyAnstAr
Flag of Australia image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of Jsmply
Jsmply

ASKER

Hi,

The event logs don't show anything of interest.  This server was never a doman member.  It just runs some databases, nothing unique.  That's why it's so puzzling.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Avatar of Jsmply

ASKER

Hi Everyone,

Yes it's a production machine, but we can reboot it when needed (and can do daily after hours if necessary for troubleshooting, etc).  So far we have determined that a reboot does indeed fix the problem in the sense that we can login again, but after the first login or two the problem returns and the box gets locked (no real rhyme or reason we have identified yet as to which login is the magical one that triggers it).

As for a process being stuck, it's possible (or even likely) but seems odd that nothing has really changed on the server and its been running the same setup for a few years now.

We will have to look into the chkdsk possibility on next reboot, probably over the weekend.  
I think this is a process locking the user profiles.
The CitrixTools XenApp session cleaner is a good alternative to UPHClean and runs on 2008 variants.

It is also free:

http://www.citrixtools.net/Default.aspx?id=6&tabid=63

Registration (free) required for download.
Avatar of Jsmply

ASKER

Tony: It happens on local logins also though, not just TS.  Anotherwords a fresh reboot of the box, no TS connections.  It can occur after a few terminal logins.  Is UPHClean related only to TS issues?
No, UPHClean is not just related to terminal server sessions.  I'm not familiar with the Citrix tool, though, and according to a previous post, UPHClean isn't compatible with Server 2008.
Avatar of Jsmply

ASKER

Thanks.  Any obvious things we can check to see if this is is needed?  I recall UPHClean helping with some issues of access denied messages in the event log, not seeing that though.
It was generally associated with situations where a user profile would get corrupted in some way during logoff.  This happens usually because of a process that is still running so that the user's registry hive can't be closed properly when they log off.  To be honest, I can't think of any useful way to try to troubleshoot the specific process if you're not actually getting an error message during logoff, or if there aren't any errors in the event logs. You could simply try installing UPHClean on the server if it will even install on Server 2008 and see if it seems to resolve the issue.
Sorry meant to add that the alternative tool I pointed to (used to) work with pure RDS - Citrix not being a pre-requisite.

However, they've updated it since so I have to caveat it.

It certainly won't hurt and the symptoms you describe align perfectly with it.
Avatar of Jsmply

ASKER

Very odd, it seems to be getting stuck in more and more situations.  Today for example, their are Windows Updates that need to be applied and machine needed to be restarted.  Went ahead and restarted and it's been stuck on installing update 7 for about 2 hours.  We will let it go though and see if it eventually restarts.

Avatar of Jsmply

ASKER

Okay found something in the registry.  Looked on via the console session while logging off an RDP session.  Found a message that a printer might be causing an issue?  Not sure what would be causing it though, no physical printers are connected, just the normal XPS writter and another image writter.  They have been installed for years.  

\REGISTRY\USER\S-1-5-21-xxxx-xxxx-xxxxx-xxxxx-xxxxxx\Printers\DevModePerUser

Substituted the x's only because didn't write that part down exactly before shutting down for the day.  Can grab it tomorrow if it actually mattered.  
Avatar of Jsmply

ASKER

Oh and looked in the registry under that area, the exact user doesn't exist, and all the similiar ones don't show anything out of the ordinary in the printers\devmodeperuser
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Avatar of Jsmply

ASKER

It seems like the issue was resolved by disabling the redirection of client printers in the RDP configuration.  Since doing that, no further hang ups have occurred.

Can anyone suggest a way to distribute the points fairly?
It was your idea to disable redirection... You give some points to people who helped with ideas, and grant most for your last comment.
Avatar of Jsmply

ASKER

It wouldn't let me award points to my comment, that's fine though.  I'd prefer to share them.  Thanks everyone for the input.  Seems every answer was right under certain circumstances.