Hi Kael Yao,
MTA21 is now again in dual stack. Error when connecting Exchange Management Shell to SNMTA21:
VERBOSE: Connecting to SNMTA21.xxxx.
New-PSSession : [snmta21.xxxx] Connecting to remote server snmta21.xxxx failed with the following error
message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from
the destination computer. The content type is absent or invalid. 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], PSRemotin
- FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
And when trying to open EMC these errors occur:
Server Error in '/owa' Application.
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=126.96.36.199, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Line 67: the compiler. All assemblies in the GAC and owa\bin are referenced automatically.
Line 68: -->
Line 69: <add assembly="Microsoft.Exchange.Clients.Strings, Version=188.8.131.52, Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Line 70: <add assembly="Microsoft.Exchange.Data.Directory, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
Line 71: <add assembly="Microsoft.Exchange.Clients.Common, Version=220.127.116.11,Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Source File: C:\Exchange2019\V15\FrontEnd\HttpProxy\owa\web.config Line: 69
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Clients.Strings, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
My apologies for the late reply.
From your information, it seems that SNMTA21 may get corrupted.
I totally understand your frustration.
However, since troubleshooting all these issues may also take a lot of effort, I suppose that restoring the server would be the best solution in this case.
Did you successfully remove DAG?
If DAG has been removed, please first try uninstalling Exchange from SNMTA21.
If Exchange can be uninstalled successfully, please reinstall the operating system and install CU10 directly.