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

Cannot get Exchange 2010 running in environement and cannot find a working solution

Alright, upgrading a network to 2008R2 and Exchange 2010 SP1.  I have run though all prereqs and the install and it continuously fails on the mailbox role.  

I have been trough every single roubleshooter I can find and still cannot get anywhere.

Right now I am trying to uninstall the Hub Transport Role and cannot remove a connector that was made because I cannot launch the Management Console or shell.

This is the error from them both.

[server.domain.local] 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) [], PSRemotingTransportException
    + FullyQualifiedErrorId : PSSessionOpenFailed

I am just at a complete loss right now.
0
eclricochet
Asked:
eclricochet
1 Solution
 
Schnell SolutionsSystems Infrastructure EngineerCommented:

Validate that the necessary server services are running. Specially "world wide web" and "internet information service". Check for Operating System errors in the system event viewer and try to get information about possible errors.

If it is a problem with the operating system you can reinstall it and reinstall exchange with the switch /m:recoverserver. It is considering that the O.S. error can not be detected easily and that you just have a new installation that doesn't contain relevant information

0
 
eclricochetAuthor Commented:
Yup, all running.

Went as far as managing to remove Exchange once before and completely blowing away the server and reinstalling.  Still came up with issues.

If I do reload the server can I remove the box from the domain prior so I can use the same hostname?  

MSExchange PowerShell AppPool keeps failing with this in the eventlog

A listener channel for protocol 'http' in worker process '3984' serving application pool 'MSExchangePowerShellAppPool' reported a listener channel failure.  The data field contains the error number.
0
 
Dustin99352Commented:
You can find the cause at http://msexchangeteam.com/archive/2010/02/04/453946.aspx 

That should help you fix it.

Thanks
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
eclricochetAuthor Commented:
Been though there and no such luck.  Like I said, I have been troubleshooting this pretty hard.
0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:

If you remove the box in the Domain you will remove the exchange computer object in the configuration partition and it will be more complex (it shall be just the last alternative)

0
 
eclricochetAuthor Commented:
Could we say that this could cause the issue to continue after a reinstall?

I should say that this is an ESXi VM so manipulating it is fairly easy.

So the consensus at this point would be to delete this VM, install a new R2 box and then start the install in recovery mode?
0
 
eclricochetAuthor Commented:
Screenshot 1
I have run the powershell commands to reload the default role assignments outlined here:

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/8f9a1881-d66d-4d8a-a6ff-06729a701999/

Step 5 genereated an error about the mailbox being version 6.5 and needing to v14.1

0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:

Yes, you can just reinstall the box and install it with the /m:recoverserver switch, like this:

setup /m:recoverserver

The procedure shall be like this:

1. If there are certificate servers, custom informations on server or databases, backthem up or copy them somewhere

2. Reinstall the computer

3. Reset the computer account in AD

4. Join the computer to the domain with the same name of the resetted account

5. Install all the Exchange prerequisites on the server

6. Install Exchange in Recover Server mode (setup /m:recoverserver)

7. Reapply any certificate, custom configuration or DB that was originally on it



0
 
eclricochetAuthor Commented:
So I ended up breaking down and calling M$ about this issue and after about three hours we identified inherited permissions issues through ADSI edit that were the cause.  All is well now and I can move forward with my migration.

Thanks all....
0
 
eclricochetAuthor Commented:
Best solution ever....
0
 
nemesis2860Commented:
Can you post what you had to change?  I am having the same issue and would like to see how you resolved it.
0
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

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

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