[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Unable to connect to Exchange Management Shell - Excahnge 2010 Hosted mode

Posted on 2015-02-12
9
Medium Priority
?
65 Views
Last Modified: 2015-03-29
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
Comment
Question by:Mark Galvin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 2
9 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40605790
Is the WWW Publishing Service started on the server? Anything in Event Viewer?
0
 
LVL 13

Author Comment

by:Mark Galvin
ID: 40605810
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
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40605824
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
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 13

Author Comment

by:Mark Galvin
ID: 40605893
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
 
LVL 13

Author Comment

by:Mark Galvin
ID: 40605916
Also, I have just followed the step by step in that article and get the same result in the EMS.
0
 
LVL 13

Author Comment

by:Mark Galvin
ID: 40628012
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
 
LVL 13

Author Comment

by:Mark Galvin
ID: 40628247
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
 
LVL 13

Accepted Solution

by:
Mark Galvin earned 0 total points
ID: 40684384
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
 
LVL 13

Author Closing Comment

by:Mark Galvin
ID: 40694337
Found after many hours of research.
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question