locked
EMC 2010 Unavailable... RRS feed

  • Question

  • Hi Everybody, My name is Matt and I'm a 15 year veteran in IT. I have gone back to college for additional training and certification. Currently we are in our "CapStone" class, undergoing a large project which we have to define a solution. For our team solution we are using Windows Server 2008 R2 Enterprise x64, SQL Server 2008 R2, SharePoint Server 2010 Enterprise, and Exchange 2010. I've managed to get my core network up and running such as the ADDS, WSUS, WDS, etc... We are running with three servers (ADM, MAIL, SQL). ADM runs ADDS, DNS, DHCP, WSUS, WDS. MAIL runs Exchange and SharePoint, and SQL is well... SQL. I succesfully installed SQL, no complaints, and SharePoint. However after I installed SharePoint, I proceeded to install Exchange 2010, only to learn that the EMC wanted to connected to port 80. I look into this and found in IIS that I had a site "SharePoint - 80" with bindings to port 80. Went back into the SharePoint Admin Web App and removed "SharePoint -80" and recreated it as "SharePoint -8080". I now receive the follwing error from the EMC... INITIALIZATION FAILED The following error occured when searching for On-Premises Exchange server: [mail.capstone.edu] Connecting to remore server failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true'. I've gone around and around for the last two hours trying to read up on anything that would help, to no avail. Can anyone help me with this? If all else fails I could just re-image the server and install Exchange first then SharePoint, unless anyone know of any incompatibilities?
    Matthew
    Friday, April 22, 2011 10:15 PM

All replies

  • I am dizzy from reading your post.  Suffice it to say that if you've mucked with IIS, you very well could have screwed up WinRM (remote PowerShell, upon which the Exchange Management Console is based) since it is served up by IIS.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • Proposed as answer by Terence Yu Monday, April 25, 2011 3:30 AM
    • Unproposed as answer by Matthew Elliott Monday, May 2, 2011 8:30 PM
    Saturday, April 23, 2011 12:46 AM
  • Hi
       I find many interesting solution.
       1. Update 2010 to SP1 and turn off Antivirus software.
       2. In my case I had removed the http binding on port 80 from my default web site that Exchange is using for OWA etc.  I left if with just HTTPS bound.  I belive this is what caused the issue.  As soon as I added a http port 80 binding back to the default web site everything started working again.
       3. You can read this
    article.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, April 25, 2011 3:50 AM
  • Thanks for the input.  I discovered that WinRM wasn't installed before I installed Exchange, however installing is after-the-fact hasn't help either.

    I'm going to try and install Exhange SP1 and see if that resolves the issue now that SharePoint isn't consuming the TCP:80 port.

    Should this fail to resolve my issue, I going to install Hyper-V and install Windows Server 2008 R2 to the virtual machine and load exchange there.

    Should that approach fail then I'll just re-image the server all together, need to resolve this as easily as possible by tonight so my team can begin development.

    I really do appreciate the help.


    Matthew
    • Edited by Matthew Elliott Monday, April 25, 2011 4:24 PM Grammatical corrections
    Monday, April 25, 2011 4:23 PM
  • Hi
      Do you have anything to update your issue ?
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, April 29, 2011 3:19 AM
  • Update? Sure... LOL

    I re-imaged the server same night after reading from the posts here.  Imaged via WSUS and got the server back up in about a half hour. Went to re-install Exchange 2010, something about the Exchange installer found within Active Directory the previous, or from it's perspective, existing Exchange installation, though it notated that "the server is in a state of inconsistency". Which then forced me into using the setup.com /mode:RecoverServer disaster receovey installation, which was all done within the command prompt enviroment. Never-the-less it failed. And the SP1 setup.exe couldn't help either, it was literally check-mate. The installers detected the previous installation attempts and wouldn't let me continue. Left school @ 10pm that night defeated and angry, played some Conan on the PS3 and felt better.

    The following morning I re-imaged the Mail server again, went into ADDS and removed all the Microsoft Exchange OU CN's, etc... Hoping to clear out what ever the installer is finding in AD that is preventing a fresh install. Another FAIL, so last night I blew out and removed and reinstalled my ADDS on the ADM server.  I'm now in the process of re-joining the other computers and server to the domain, I'll recreate my users later after I can have a successful installation of Exchange 2010 SP1 and have MSC working properly.

    I'll keep you all posted as to the outcome. <crossing-fingers>


    Matthew
    Friday, April 29, 2011 6:25 PM
  • Matthew,

    Just a note that might be useful for your studies (and general Exchange knowledge).

    I was reading somewhere (Exchange 2010 Best Practices?) that the command -

    setup.com /mode:RecoverServer

    is NOT an option for recovering a failed Exchange installation.

    I did not know that and, in fact, was "exchanging" with someone else, in another forum, who was planning to (re)install Exchange after a failed install with that switch.

    If any of the MS people, or MVPs, or anyone else, knows what the "Best Practice" is for recovering from a messed up install, I'd like to know myself.

    It's a tricky situation once you get all that info in Active Directory.

    I suppose... you could isolate the schema master - and Exchange server - when doing setup /ps and setup /p (I'm using the shortcut commmands there) and if the install is an absolute disaster, with the schema extension, etc. already complete however, you could wipe the schema master DC and seize FSMO roles on a DC to which the changes would not have replicated. 

    Maybe, but that seems a bit complicated (???)

    Enough thinking out loud.


    Friday, April 29, 2011 6:43 PM
  • Pre-installation Update:

    I am on the verge of installing Microsoft Exchange 2010 SP1. ...again.  In order to try and save time and effort should installation go badly I am performing the following, Windows Server Backup -Full Backup once to a pre-install folder, Creating a system restore for the ADM server.  Hopefully with the backup and system restore available, should the install go badly I can revert my Active Directory information to a state before the install and avoid the hassle I suffered eariler this week.

    Still crossing those fingers...


    Matthew
    Friday, April 29, 2011 8:21 PM
  • Update: As of Friday evening, I have a successful install of Exchange 2010 SP1. The slight ugly of this? With the new ADDS I lost all users and computers, which was expected. Though short-sighted, I lost the ability to authenticate to the SQL Server 2008 R2 application and had to re-install SQL Server 2008 R2, as for SharePoint 2010 I had to remove the existing server farm and it will be recreated as well. But in comparison, the time it will take to redo all of this is utterly insignificant compared to the time I spent trying to get a working Exchange Server.

    Again, thank you all for your input, it was very much appreciated.


    Matthew
    Monday, May 2, 2011 8:27 PM