Brendan M
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.
I also get the following when trying to open the Toolbox
Any help will be greatly appreciated.
Thank you
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
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)
Any help will be greatly appreciated.
Thank you
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hey clonyxlro, yeah I has to modify it to get it to work with 2013, but with no luck, thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
ASKER
I am unable to run Remove-PowershellVirtualDi