• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 67
  • Last Modified:

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:
RMClient Error
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_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
    + 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/
0
Mark Galvin
Asked:
Mark Galvin
  • 7
  • 2
1 Solution
 
Gareth GudgerCommented:
Is the WWW Publishing Service started on the server? Anything in Event Viewer?
0
 
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Hi

WWW PS is running:
 WWWPSService
Seeing lots of these in the Application Log:
AppLogError
And these two in the System Log:
SysLogError1AND
SysLogError2
0
 
Gareth GudgerCommented:
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?
0
What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

 
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Server was last rebooted in the on the 4th Feb:
net statistics server
I can try again tonight but have a feeling it wont help.
0
 
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Also, I have just followed the step by step in that article and get the same result in the EMS.
0
 
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
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
0
 
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
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_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
    + 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.
0
 
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Finally!!!

Following the advice here https://social.technet.microsoft.com/Forums/en-US/641e0691-8f27-4f5a-a895-07b8e97d7e6d/lync-2010-application-pools-wont-start?forum=ocsplanningdeployment I managed to remove the errors from the event log that I had mentioned above and now the EMS is connecting fine.

Thanks
Mark
0
 
Mark GalvinManaging Director / Principal ConsultantAuthor Commented:
Found after many hours of research.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 7
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now