Please wait for the User Profile Service...

[talksr]

Hi there,

I am not too sure what to do here, we bounced our 2008 R2 server last Thursday and since then, we have been unable to initiate an RDC connection with it. We are able to access all of the network shares, and staff and pupils are able to use the network as usual, but we are completely unable to login to the server either via RDC or physically when in front of it.

 

I have tried to log in locally, but the server is just showing the following which has been on the screen for hours:

 

Please wait for the User Profile Service...

 

I have been unable to bounce it again yet as it has been in constant use by staff. When I get the opportunity, it will be the first thing I do.

Can anyone suggest what the problem could be?

Despite this problem, I am able to remotely connect to its event viewer and have seen the following errors:

 

The winlogon notification subscriber is taking long time to handle the notification event (Logon).

Edited January 23, 2014 by talksr

[featured_spectre]

is the IP address the same? If you do an NSlookup, does it show that server? Should it show that server?

[talksr]

is the IP address the same? If you do an NSlookup, does it show that server? Should it show that server?

 

Thanks for your post, IP for server is statically assigned as: 10.75.44.250.

Nslookup for server hostname returns:

 

Server: UnKnown

Address: 10.75.44.250

So looks fine to me. Never had IP problems before. This seems more likely something wrong with software as I am unable to log into the server locally. I have attempted to and it is just showing the following on screen:

Please wait for the User Profile Service...

 

Has been showing it for hours.

[featured_spectre]

The server is coming back as UnKnown? is that how it is set?!

[Tys]

Server: UnKnown

Address: 10.75.44.250

So looks fine to me.

The fact that the server is showing up as UnKnown flags warnings signs up to me - DNS issues.

 

How is your DNS set up?

[SHimmer45]

if your forward Zone is working properly it should return the server:"your_servername" if you just type nslookup at a command prompt.

can you connect "directly" via IP using RDC?

[talksr]

It has been over a week and the server is still showing Please Wait for the User Profile Service on the login screen.

I have just pulled the plug and attempted to logon using safe mode but it said my password was wrong even through it ws not.

 

I then booted to Safe Mode with networking, logged in and I am getting the same Please Wait for the User Profile Service message. The server seems impossible to log in to.

Any suggestions?

[win]

I had the exact same problem with my SQL server running windows 2008r2. The way i solved it was too log into the physical machine and do a force shutdown on the hyper-v server. Right click on the problem server and click 'turn-off' rather than 'shutdown'. This is like holding down the power button. After that i managed to log in fine.

 

If the problem is with a physical server then you can try holding down the power button for a forced shutdown. I assume you have a backup just in case?

Edited January 30, 2014 by win

[win]

Sorry, just saw your recent post - we must have been typing at the same time!

[talksr]

Don't worry

Not sure what happened but pulled plug a few times and it now logs on first time, no problems or delays. Have bounced around 5/6 times and problem is not reoccurring. I did absolutely nothing to remedy this as I couldn't actually get onto the thing. No wonder some people have the perception that if they kick a computer it can fix the problem!

[win]

That's right, if a reboot doesn't work - a forced shutdown will Edited January 30, 2014 by win

[talksr]

That's right, if a reboot doesn't work - a forced shutdown will

 

 

Thanks for your helpful posts. A confusing issue, but I am just glad it has gone. Let's hope it does not come back!

[J_Worth]

I thought you needed to have a Reverse Lookup Zone so that server:"SERVER_NAME" would appear rather than "UnKnown" as when you do nslookup it looks up the hostname associated with the IP address of your DNS server.