Remote Powershell XML Syntax Error

%3CLINGO-SUB%20id%3D%22lingo-sub-2201602%22%20slang%3D%22en-US%22%3ERemote%20Powershell%20XML%20Syntax%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2201602%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReally%20hope%20someone%20has%20seen%20this%20before%20and%20knows%20how%20to%20fix%20it%20as%20it%20is%20driving%20me%20insane!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBasically%20we%20have%20just%20rebuilt%20one%20of%20our%20on-prem%20Exchange%202016%20CU19%20servers%20using%20the%20%2Fm%3ARecoverServer%20switch%20(not%20added%20to%20DAG%20at%20this%20point)%20everything%20appears%20to%20be%20in%20order%20so%20far%20but%20I'm%20facing%20this%20error%20when%20opening%20the%20EMS%20on%20the%20new%20server%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVERBOSE%3A%20Connecting%20to%20server01.local.%3CBR%20%2F%3ENew-PSSession%20%3A%20%5Bserver01.local%5D%20Connecting%20to%20remote%20server%20server01.local%20failed%20with%20the%3CBR%20%2F%3Efollowing%20error%20message%20%3A%20%3CFONT%20color%3D%22%23FF0000%22%3EWinRM%20cannot%20process%20the%20request%20because%20the%20input%20XML%20contains%20a%20syntax%20error%3C%2FFONT%3E.%20For%20more%3CBR%20%2F%3Einformation%2C%20see%20the%20about_Remote_Troubleshooting%20Help%20topic.%3CBR%20%2F%3EAt%20line%3A1%20char%3A1%3CBR%20%2F%3E%2B%20New-PSSession%20-ConnectionURI%20%22%24connectionUri%22%20-ConfigurationName%20Microsoft.Excha%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20OpenError%3A%20(System.Manageme....RemoteRunspace%3ARemoteRunspace)%20%5BNew-PSSession%5D%2C%20PSRemotin%3CBR%20%2F%3EgTransportException%3CBR%20%2F%3E%2B%20%3CFONT%20color%3D%22%23FF0000%22%3EFullyQualifiedErrorId%20%3A%20-2144108477%3C%2FFONT%3E%2CPSSessionOpenFailed%3CBR%20%2F%3EVERBOSE%3A%20Connecting%20to%20server02.local.%3CBR%20%2F%3EVERBOSE%3A%20Connected%20to%20server02.local.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%202012R2%20VM%20and%20I've%20compared%20all%20the%20IIS%20settings%20and%20installed%20features%20across%20the%20other%20DAG%20members%20and%20everything%20matches%2C%20again%20it%20isn't%20actually%20added%20to%20the%20DAG%20at%20this%20point.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20you%20can%20see%20from%20the%20output%20above%2C%20it%20has%20no%20trouble%20connecting%20to%20other%20DAG%20members%20using%20remote%20powershell.%20The%20issue%20is%20specific%20to%20this%20server.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20quick%20google%20seems%20to%20suggest%20a%20time%20sync%20error%20with%20the%20host%2Fguest%20but%20the%20time%20is%20correct.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETIA!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2201602%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Senior Member

Hi all, 

 

Really hope someone has seen this before and knows how to fix it as it is driving me insane! 

 

Basically we have just rebuilt one of our on-prem Exchange 2016 CU19 servers using the /m:RecoverServer switch (not added to DAG at this point) everything appears to be in order so far but I'm facing this error when opening the EMS on the new server:

 

VERBOSE: Connecting to server01.local.
New-PSSession : [server01.local] Connecting to remote server server01.local failed with the
following error message : WinRM cannot process the request because the input XML contains a syntax error. 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], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
VERBOSE: Connecting to server02.local.
VERBOSE: Connected to server02.local.

 

This is a 2012R2 VM and I've compared all the IIS settings and installed features across the other DAG members and everything matches, again it isn't actually added to the DAG at this point. 

 

As you can see from the output above, it has no trouble connecting to other DAG members using remote powershell. The issue is specific to this server. 

 

A quick google seems to suggest a time sync error with the host/guest but the time is correct.

 

TIA! 

0 Replies