HyperV Server no longer accessible in HyperV Manager.

[DJ-1701]

Has anyone come across this message? HyperV has been working fine for a year, but now is refusing connection. Can't find anything helpful online, and the Hyper-V Virtual Machine Management service is running.

 

An error occurred while attempting to connect to server "HyperVServerHere". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.

 

The operation on computer 'HyperVServerHere' failed: The WS-Management service does not support that SOAP version specified in the request.

[Oaktech]

When was the last time it was restarted for updates? I wonder if you've got a CREDSSP error?

[DJ-1701]

Strangely 2 weeks ago, both clients and servers have the patch installed so I could remote desktop to it.

[Oaktech]

Strangely 2 weeks ago, both clients and servers have the patch installed so I could remote desktop to it.

 

Is it half term for you next week?

 

[DJ-1701]

First point of call. I did, but no dice. It appears to be effecting both the HyperVs here as well.

[Oaktech]

I'll keep googling with you!

[Oaktech]

The closest I can find seems to be something about a version issue between the RSAT tools on the workstation and the Win RM on the server. Maybe try a reinstall of the latest greatest RSAT tools?

[DJ-1701]

Certainly worth a shot. Cheers.

[DJ-1701]

Certainly worth a shot. Cheers.

 

Bah, no luck, same error.

[Oaktech]

Any useful information in here? https://msdn.microsoft.com/en-us/library/aa384372(v=vs.85).aspx

[DJ-1701]

Any useful information in here? https://msdn.microsoft.com/en-us/library/aa384372(v=vs.85).aspx

 

Doesn't appear to be. All been set previously of course, and re-ran the commands when I found that too. Just said it was already setup.

[DJ-1701]

As I am running Hyper-V Server 2012 V2, I'm going to try and see if an upgrade on the non-critical one to Hyper-V Server 2016 makes and difference as I am running out of ideas.

[HPlum78]

Have you tried to restart the Windows Remote Management service? one other thought not that its the message I would expect you have not set a GPO up that has disabled the Allow Remote Shell Access by any chance? (Computer Configuration > Administrative Templates > Windows Components > Windows Remote Shell > Allow Remote Shell Access) Edited May 25, 2018 by HPlum78

[DJ-1701]

Have you tried to restart the Windows Remote Management service?

 

I tried restarting the whole server.

[HPlum78]

Ah well that will cover the service right there then! :-P

[thebatman]

This may help to get you up an running, but is not a fix.

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters\

Type: REG_DWORD

Name: AllowEncryptionOracle

Value: 2 (Decimal)

I came across this error when the PC and Server didn't have the same KB (Cant think what one it was)

 

This is at client side.

Edited May 25, 2018 by thebatman

[DJ-1701]

This may help to get you up an running, but is not a fix.

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters\

Type: REG_DWORD

Name: AllowEncryptionOracle

Value: 2 (Decimal)

I came across this error when the PC and Server didn't have the same KB (Cant think what one it was)

 

This is at client side.

 

Both the Server and the Machine are updated with the correct KB though... I tried it anyway and unfortunately it didn't work.

 

Also apparently I can't upgrade to HyperV Server 2016 as I don't have SLAT on the processor, so that stops my 2016 testing.

[HPlum78]

Anything in the logs here C:\Windows\System32\LogFiles\HTTPERR\

?

[DJ-1701]

Anything in the logs here C:\Windows\System32\LogFiles\HTTPERR\

?

 

Only a file back from 2016.

[HPlum78]

Test-WSMAN -computername

 

I am just thinking out loud now.....

[HPlum78]

So you have two hyper-V server (win srv 2012 R2) and are connecting to these remotely from a server/ client? if so what's the OS?

[DJ-1701]

Test-WSMAN -computername

 

I am just thinking out loud now.....

 

Both server and client report fine.

 

So you have two hyper-V server (win srv 2012 R2) and are connecting to these remotely from a server/ client? if so what's the OS?

 

HyperVs are both HyperV Server 2012 R2 with latest updates, client is Windows 10 Education 1803 with latest updates.

[HPlum78]

I started thinking around the stack version between the servers and the client you are connecting from..... but based on that info I am thinking that they are/ should be the same. Edited May 25, 2018 by HPlum78

[Oaktech]

HyperVs are both HyperV Server 2012 R2 with latest updates, client is Windows 10 Education 1803 with latest updates.

 

Have you tried from a 1703/1709 machine with RSAT?

[DJ-1701]

Have you tried from a 1703/1709 machine with RSAT?

 

I haven't... as I already deployed 1803 out to all those machines, as ironically my one was working fine (including with HyperV) for several weeks. I'll give that a go, cheers.