Forum Discussion
IvanSalvade
Jul 11, 2019Copper Contributor
Exchange Management Shell not opening in Exchange Server 2019 on Windows Server 2019
In a new installation of Exchange Server 2019 CU2 on Windows Server 2019 fully patched, with .NET Framework 4.7.2, the Exchange Management Shell is not connecting to Exchange with this error :
"New-PSSession : [server.domain.com] Processing data from remote server server.domain.com failed with the following error message: [ClientAccessServer=SERVER,BackEndServer=server.domain.com,RequestId=29e42dd0-3fd1-4787-
a68c-20a70846c584,TimeStamp=dd/mm/yyyy hh:mm:ss] [FailureCategory=WSMan-Others] Unable to load the assembly "Microsoft.Exchange.Configuration.ObjectModel.dll" specified in the "InitializationParameters" section. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
After this error, EMS is able to connect to an old Exchange 2013 server in coexistence in the same domain.
Someone else experienced the same problem? Could be a bug in Exchange 2019 CU2?
Thank you
- El_KhiyatiCopper ContributorI resolved the problem, changing the path exchange installation variable in setting windows
- Matt_B010Copper Contributor
I am experiencing the same problem with Exchange 2016 on Server 2016 on a child domain. My root domain is running Exchange 2016 and I had no issues when I migrated from 2010 to 2016. When I install a new Exchange 2016 (CU 13) server in the child domain I have run into this problem you are describing for 2019 editions respectively.
Did yo manage to find a solution/cause for your issue?
Hi Matt_B010,
Can you try to run "Set-ExecutionPolicy Unrestricted" in PowerShell in Run As Administrator and after run Exchange Powershell in Run Ad Administrator as well ?
- Matt_B010Copper ContributorTried that yesterday and it didn't work either.
- IvanSalvadeCopper Contributor
- KnautilusCopper ContributorI just want to add a "Me too" here. I had this error on a new Exchange 2019 server. 3 servers were deployed, but only 1 exhibited this error. Uninstall / reinstall of Exchange fixed the problem.