Mark Galvin
asked on
Unable to connect to Exchange Management Shell - Excahnge 2010 Hosted mode
My client has an Exchange 2010 server running in hosted mode and therefore aonly accessible via the Exchange Management Shell. All was working fine until about 2 weeks ago.
Now when the client runs up the Exchange Management Shell they get:
As text:
VERBOSE: Connecting to server.domain.forest.ads
[server.domain.forest.ads] Connecting to remote server failed with the following error message : The WinRM client cannot complete the operation with
in the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management serv
ice is enabled. For more information, see the about_Remote_Troubleshooti ng Help topic.
+ CategoryInfo : OpenError: (System.Manageme....Remote Runspace:R emoteRunsp ace) [], PSRemotingTransportExcepti on
+ FullyQualifiedErrorId : PSSessionOpenFailed
No change has been made on the server. No updates. Nothing.
We have tried restarting the Exchange services, rebooting the server.
Any ideas?
Thanks
Mark/
Now when the client runs up the Exchange Management Shell they get:
As text:
VERBOSE: Connecting to server.domain.forest.ads
[server.domain.forest.ads]
in the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management serv
ice is enabled. For more information, see the about_Remote_Troubleshooti
+ CategoryInfo : OpenError: (System.Manageme....Remote
+ FullyQualifiedErrorId : PSSessionOpenFailed
No change has been made on the server. No updates. Nothing.
We have tried restarting the Exchange services, rebooting the server.
Any ideas?
Thanks
Mark/
Is the WWW Publishing Service started on the server? Anything in Event Viewer?
ASKER
The last screenshot would be where I would start. If there is a problem with the Exchange PowerShell Virtual Directory in IIS, this is likely the root cause. Ran across this - http://kb.prismmicrosys.com/evtpass/evtpages/EventId_5139_Microsoft-Windows-WAS_64841.asp
Might be easier to just bounce the server. When was the last restart?
Might be easier to just bounce the server. When was the last restart?
ASKER
ASKER
Also, I have just followed the step by step in that article and get the same result in the EMS.
ASKER
Still working on this. We are upgrading the RAM in the server over the coming weeks from 6GB to 38GB. I'm hoping that this change and a full reboot will bring back the EMS to being able to connect to the server.
Thanks
Mark
Thanks
Mark
ASKER
Been doing some more trouble shooting today. Still not working.
I have downloaded the
And the results:
**********************
Windows PowerShell Transcript Start
Start time: 20150224144356
Username : DOMAIN\Administrator
Machine : SERVER (Microsoft Windows NT 6.1.7601 Service Pack 1)
**********************
VERBOSE: Connecting to SERVER.DOMAIN.FOREST.ads
[SERVER.DOMAIN.FOREST.ads] Connecting to remote server failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooti ng Help topic.
+ CategoryInfo : OpenError: (System.Manageme....Remote Runspace:R emoteRunsp ace) [], PSRemotingTransportExcepti on
+ FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:
SERVER.DOMAIN.FOREST.ads
**********************
Windows PowerShell Transcript End
End time: 20150224144701
**********************
Also, still getting the WAS error in the System log and the IIS error from the application server.
Nightmare.
I have downloaded the
And the results:
**********************
Windows PowerShell Transcript Start
Start time: 20150224144356
Username : DOMAIN\Administrator
Machine : SERVER (Microsoft Windows NT 6.1.7601 Service Pack 1)
**********************
VERBOSE: Connecting to SERVER.DOMAIN.FOREST.ads
[SERVER.DOMAIN.FOREST.ads]
+ CategoryInfo : OpenError: (System.Manageme....Remote
+ FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:
SERVER.DOMAIN.FOREST.ads
**********************
Windows PowerShell Transcript End
End time: 20150224144701
**********************
Also, still getting the WAS error in the System log and the IIS error from the application server.
Nightmare.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found after many hours of research.