I have tried everything listed, but still am unable to open EMC or EMS for Exchange 2010. The error I continue to recieve for EMC is below: INITIALIZATION FAILED The following error occurred while searching for the on-premise Exchange server. Object reference not set to an instance of an object. It was running the command 'Discover-ExchangeServer -UserWIA $true -SuppressError $true -CurrentVersion 'Version 14.1 (Build 218.15)". On EMS I recieve: VERBOSE: Connecting to server.domain.local Object reference not set to an instance of an object. +CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:Remoterunspace) [], RemoteException +FullyQualifiedErrorId : PSSessionOpenFailed I have tried everything from every article I have found and nothing has helped. I have even reinstalled IIS and Exchange via the "setup /m:recoverserver". In addition, I am also able to access OWA with no issues. If anyone could shed some light, I would be very grateful. I really would not like to lose any data in Exchange and I would also not like to reinstall the OS. I've seen so many articles on this, I can't believe there is not a better solution for this. Thanks in advance.

Once after it EMC failed, have you tried to connect/add another exchange forest option and tried to connect any one of the exchange server you have? >>:::.... if you find it useful, mark this as answer ...:::<< Thanks & Regards, Sandheep [...:::""I can't do it" never yet accomplished anything; "I will try" has performed wonders ":::...]

Not an answer to your question, but are you able to load the Exchange PsSnapin in Windows Powershell? (just type: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 ) :MartinaPlease 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.

Yes, I've tried to add another exchange forest. Below is the error I receive when doing so. Object reference not set to an instance of an object. Additional Information: at System.Management.Automation.Runspaces.AsyncResult.EndInvoke() at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult) at System.Management.Automation.Runspaces.RunspacePool.Open() at System.Management.Automation.RemoteRunspace.Open() at Microsoft.Exchange.Configuration.MonadDataProvider.MonadRemoteRunspaceFactory.TestConnection(Uri uri, String shell, PSCredential credential, AuthenticationMechanism mechanism, Int32 maxRedirectionCount, Boolean skipCertificateCheck) at Microsoft.Exchange.Management.SnapIn.ConnectionRetryDiscoverer.TryAuthenticationMechanisms(PSCredential cred, AuthenticationMechanism[] authMechanisms) at Microsoft.Exchange.Management.SnapIn.ConnectionRetryDiscoverer.DiscoverConnectionInfoInternal() at Microsoft.Exchange.Management.SnapIn.ConnectionRetryDiscoverer.DiscoverConnectionInfo(Boolean& rememberCredentialChecked, SupportedVersionList& supportedVersionList, String slotVersion) at Microsoft.Exchange.Management.SnapIn.Esm.AddExchangeForestDataHandler.OnSaveData(CommandInteractionHandler interactionHandler) at Microsoft.Exchange.Management.SystemManager.WinForms.DataHandler.Save(CommandInteractionHandler interactionHandler) at Microsoft.Exchange.Management.SystemManager.WinForms.DataContext.SaveData(CommandInteractionHandler interactionHandler) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Yes, I am able to load the Exchange Pssnapin from windows powershell. I've also made sure to try some of the commands that are associated like making sure a user is added to the remoteuser group and other common solutions recommended.

Are you trying to do this from a workstation, or the server? And did you check to see if IPV6 is enabled? [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Doing everything from the Server itself. IPV6 is enabled.

By the error messages it looks to be a problem with the remoting bits. Have you verified the WSMAM/WinRM config?[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

I agree, just can't figure out how it broke or what will fix it. Winrm quickconfig shows that both receive requests and remote management are already configured. Anything else I should check?

Not that I know of off the top of my head, but I've never needed to diagnose that problem so I may not be much help. I take it you've been through this: http://technet.microsoft.com/en-us/library/dd351136.aspx?wa=wsignin1.0[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Yes, I have been through that document. Still getting the errors listed above.

Hi Phat78boy, Could you please install Exchange 2010 Management Tool on a client to test? Install the Exchange 2010 Management Tools http://technet.microsoft.com/en-us/library/bb232090.aspx Please also try to use another Organization Management admin to log on to Exchange server to open EMC. Frank Wang Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

I will try from another station tonight and reply with my findings. I have already tried another admin account, it gives the same error on whatever account I use.

I have tried to install the client on another machine and i receive the same error as listed in my first post. Anyone have any other thoughts?

Hi Phat78boy, Did you install all Exchange server roles on a single Windows OS? If you don't install latest Service Pack and Rollup, please install it now. Please run the Winrm qc and post the result here. Please check whether "WinRM IIS Extension" is installed or not. If not, please install it(Server Manager->Features->Add Features). Frank Wang Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Below is the results from winrm qc. C:\>winrm qc WinRM already is set up to receive requests on this machine. WinRM already is set up for remote management on this machine. WinRM IIS Extention is installed and I've also tried the remove and re-add it. I have the latest Service Packs and Rollups installed. During my reinstall of Exchange with the "/recoverserver" option, I also reapplied the Service Packs and Rollups.

Hello friend, Can you please tell me did you installed any other application on exchange server, I also faced one problem like this in my company my company Dynamics Team installed CRM application with the exchange server 2010 & they were not able to open the EMS, EMC & OWA was still working, I go in group policy & allow administartor to use Exchange management, I tried to restart the services & check IIS configuraion, in under the IIS configuration Exchange Admin was not add & they were using CRM Admin for access the EMS, EMC, I changed their Exchange Admin in the place of CRM\administrator & restart the Exchange service, IIS Services & also the WinRM service, after that i was able to access the EMC, EMS. please try to do this. If you find it helpfull, please mark it as a answer. Thanks Arun chaudhary MCP, MCTS, MCITPArun Chaudhary MCP, MCTS, MCITP Microsoft Exchange Corporate Trainer India