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

Exchange 2010 installed partially, but won't open EMC or EMS

So I have just installed Exchange 2010 on a 2008R2 server. The install process completed 10 of the 12 tasks successfully, failed on the last 2, and after a restart Exchange services won't load automatically (but will load manually when I tell them to later), and EMC or EMS won't open and fail with the following errors:

EMC error:
Connecting to remote server failed with the following error message: The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL. For more information, see the about_Remote_Troubleshooting Help topic

EMS error:
 Connecting to remote server failed with the following error message : The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
    + FullyQualifiedErrorId : PSSessionOpenFailed

The install pre-req's were all completed, the server is fresh, and has only been used as a file server to date.

1 problem may be the domain topology that we are upgrading from:
Originally there was a single Windows 2000 server running Exchange ENTERPRISE 2000.
Then we moved the mailboxes to a Windows 2003 server, running Exchange 2003 STANDARD. This is still running generally O.K, but ultimately we will be moving everything Exchange to the 2008R2/EX2010 box. The 2000 Exchange was uninstalled after all mailboxes were removed, then we demoted the 2000 box to a member server. It is still there, but can be taken down if needed.

This is the point at which the Exchange 2010 install was done.

There is no A/V on the new server or during the failed install, Windows firewall is turned on. All pre-req's were met.

I have done much reading and seem to be heading towards a IIS issue, or permission issue preventing the system accessing something it needs. This is the article I am referring to, but as yet have been unwilling to try it. Thoughts?


  • 4
  • 4
1 Solution
1. Make sure the MSExchangePowerShellAppPool is running. If it is, try recycling the Application Pool and check for errors or warnings in the Event logs.

Also make sure SSL is disabled on the Powershell virtual directory and accept certificate is enabled on Powershell virtual directory.

2. Make sure that the user that is trying to connect is Remote PowerShell Enabled
If the user that is attempting to connect is not Remote PowerShell enabled. To check if a user is enabled for Remote PowerShell, you need to open the Exchange Management Shell with an account that has been enabled, and run the following query.

(Get-User <username>).RemotePowershellEnabled

This will return a True or False. If the output shows False, the user is not enabled for Remote PowerShell. To enable the user, run the following command.

Set-User <username> -RemotePowerShellEnabled $True

3. Make sure WinRM is properly configured on the server.

a. Run WinRM Quick Config on the server and ensure that both tests pass and no actions are required. If any actions are required, answer Yes to the prompt to allow the WinRM configuration changes to be made.

b. Run WinRM enumerate winrm/config/listener and ensure that a listener is present for the HTTP protocol on port 5985 listening on all addresses.

To prevent a guessing game. You need to review the setup log to establish what failed and why.

You can find the setup log at <system drive>\ExchangeSetupLogs\ExchangeSetup.log. The <system drive> variable represents the root directory of the drive where the operating system is installed.

The setup log file tracks the progress of every task that is performed during the Exchange 2010 installation and configuration. The file contains information about the status of the prerequisite and system readiness checks that are performed before installation starts, the application installation progress, and the configuration changes that are made to the system. Check this log file to verify that the server roles were installed as expected.

KillersmitsAuthor Commented:
Sumit - I recycled the App pool, yes it was running and no it didn't make any difference.

I can't use the Exchange system powershell it doesn't let me do anything as it can't connect to a local exchange server.

I haven't run the WM tests yet, will do today and let you know.

Radweld - Attached is the last part of the Exchange log, where things start to go wrong. Have a look and see if anything famililar jumps out at you. Exchange-erros-start-here.docx
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

For the error you are getting while installing sp1 please follow this article

KillersmitsAuthor Commented:
Sorry sumit, I don't follow, what SP1? I haven't tried to install any....for Exchange anyway..
Sorry, but it was for the error u are getting the in Exchange setup logs.
KillersmitsAuthor Commented:
Sumit - Sorry, The version of Excchange I was using was Exchange 2010 with SP1, but I didn't install SP1 after Exchange...

Anyway, I hadn't gotten anywhere with it in the last week. The main issue is that the server it was installed on is our main file server, so I can't restart it during the day, and I lie awake at night fearing I will break it by getting too heavy handed with various fixes suggested that I have been reading about. Anyway this afternoon, I uninstalled Exchange 2010. The uninstall went fairly smoothly once I figured out how to remove the Hub transport connectors to the 2003 box. Once I got that done the rest uninstalled clean. I restarted and tested mail flow from the 2003 box and all looks good.

I have now joined a fresh 2008R2 server to the domain which will have no roles other than those required for Exchange 2010, and will do an install tomorrow to see how it goes. This way I will be able to reboot it whenever I want, as it doesn't do anything else. However it will prove a few things to me once I get the install started, regardless of it being successful, or otherwise. Theis will help me rule out a few theories, and will at least give me a backup exchange server incase my primary (2003) starts giving me trouble, assuming the install works, and I can then pursue the failure of the other install in relative comfort on the original.

I still suspect permission errors to do with the article I posted in my first post. If anyone cares to read it, it matches our upgrade path and problems descibed almost identically, but im too scared to run the script for fear of breaking the AD. Anyone care to comment on this script, and the article/theory in general?

Thanks for your help. I won't close the question as it is still ongoing, and I will keep you up to date.

Any update on this
KillersmitsAuthor Commented:
Yes the Exchange install on the fresh box worked fine. It all installed as expected, and we are able to move mailboxes to it. We haven't however tried to reinstall Exchange on the server we originally had problems with.

I could try installing Exchange again on this server, but I am scared of breaking it, and I don't see any great advantage in havinjg Exchange on that particular box, other than having one less Server. Also this way I have all my roles more evenly spread so if 1 box goes down we don't lose the whole thing.

To be honest I can't see me going back anytime soon to solve this problem. So the points are yours Sumit arora. Thanks again for your help and interest.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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