Link to home
Start Free TrialLog in
Avatar of Brendan M
Brendan MFlag for Australia

asked on

Unable to use EMS after Exchange 2013 CU1 Upgrade

Hi Everyone

After upgrading Exchange 2013 to CU1, I keep receiving the following error when trying to open the EMS.
VERBOSE: Connecting to EXCHANGE.<internaldomain>.
New-PSSession : [exchange.<internaldomain>] Connecting to remote server exchange.<internaldomain> failed with the
following error message : The WinRM client received an HTTP status code of 303 from the remote WS-Management service.
For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : -2144108273,PSSessionOpenFailed

Open in new window


I also get the following when trying to open the Toolbox
FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}
Type is not resolved for member 'Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataAdapterInvocationException,Microsoft.Exchange.Configuration.ObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
   at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Open in new window


Any help will be greatly appreciated.

Thank you
SOLUTION
Avatar of simpsonehh
simpsonehh

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Brendan M

ASKER

Hi,

I am unable to run Remove-PowershellVirtualDirectory, or I am unsure how to open powershell modules?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
hey clonyxlro, yeah I has to modify it to get it to work with 2013, but with no luck, thanks
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Found solution when researching the web again.

the Question on https://www.experts-exchange.com/questions/27204657/Exchange-2010-WinRM-Error.html hinted me the the cause of the issue, though the solution on that question also may not have resolved the issue