object invoked disconnected from its clients

[mirojr]

Hi

 

I decided to take the plunge and update our server and take it up to SP1, mainly because of the pain in the backend that is IE11 on the clients and having no ability to configure it centrally from the server.

 

Anyway that aside, I updated it at weekend and it all seemed fine.

 

I could log in and it all seemed wonderful, and I breathed a sigh of relief. Yes.

 

Err NO...

 

Come in this morning and I cannot remotely log in.

 

I go locally to the machine and login but get this message "The object invoked has disconnected from its clients"

 

So basically I have to wait till later so I can reboot the damned thing.

 

I wondered if anyone has encountered this error and managed to fix it?

 

Thanks.

[Seanc]

Hi Duxbuz, did you ever get a solution to the object invoked etc problem at login. I have an SQL server that's functioning just fine but if i try to login with either local or domain acounts i get the error you described.

 

 

Many thanks

 

 

Sean

[mirojr]

I got it working again, and wish now I had posted a follow up because I am trying to remember what I did.

 

I know I went through some reboot process first.

 

Let me get back to you see if I can recall what went on

[mirojr]

I am guessing that a reboot remedied my issue. Its just I cannot remember any other solution that I pondered over but I do remember panicking like heck when I came across the issue. I think it would have stuck in my mind more if I found some detailed solution.

 

I have looked through the Event Viewer and it mentions several "The WinRM service is not listening for WS-Management requests. " Event ID 10149 around the time of the issue.

 

Although I do not always understand the behemoth that is windows server 2008 OS and its intricacies, so maybe take my ideas around the services with a pinch of salt.

 

It should be possible to manage the services remotely and see if that service is running.

 

I do think rebooting the server solved my problem.

[Seanc]

Thank you for the replies duxbuz. I was thinking that reboot was the next option but was hoping for inspiration.

Typically its reports season and its the one server everybody is hitting just now.

Many thanks

S

[mirojr]

Yes I had an excruciating wait to try out the solution myself

[dbavedb]

I had this happen to me today on a Windows 8.1 HP laptop today, and feelings of panic ensued. All I wanted to do was use a live boot CD to load Linux. To do so I thought I needed to disable UEFI in this case and change the boot order. As it turns out that is not necessary. In any regard Windows8.1 would boot alright but display this message at login.

 

To solve the issue I went back to BIOS and in a Boolean way attempted to reverse my changes one by one, and reboot/retest my changes. Reversing only the 'enable legacy support' BIOS option (ie. Non-UEFI support) was not the only change required. For some reason the Legacy boot order was also important to revert. Then with the proper legacy boot devices order, I left legacy support turned on, and the boot/login proceeded fine. On the last boot I reverted the legacy support option to disabled, returning the system to the default state, and all was well... I believe my heart may have also recovered as well.