Forum Discussion
Problem with EMS console, Exchange Toolbox console and permission to serialize tokens
Hi,
we setup fresh Windows Server 2025 and install Exchange 2019 with all updates for Server and Exchange. Then we made Upgrade In-Place to Exchange Subscription Edition but problems remained.
After installation:
- Cannot launch "Exchange Toolbox console". Expand console in progress and crash. Error:
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'.
Exeption type: System.Runtime.Serialization.SerializationException
Exception stack trace:
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)
- EMS console. When it runs...
VERBOSE: Connecting to ex01.domain.com.
New-PSSession : [ex01.domain.com] Connecting to remote server ex01.domain.com 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], PSRemotingTransportException
+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
But If i run this command on localy on server
New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://ex01.domain.com/PowerShell/ -Authentication Kerberos
everything is ok.
Snapin: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn - works.
3. Search mailbox
When I run: Get-MailboxSearch I get error: Get-MailboxSearch : The requesting account does not have permission to serialize tokens.
AD Exchange server computer account is member of:
- Domain Computers
- Exchange Install Domain Servers
- Exchange Servers
- Exchange Trusted subsystem
- Managed Availability Servers
So exchange computer account doesn't belong to:
- Domain Admins
- Schema Admins
- Enterprise Admins
- Organization Management
I created a new user account: Admin123 and added it to
- local server Administrators group
- Discovery Management group
- Domain Users
- Server Management
but Get-MailboxSerach give the same error.
Could somebody help to solve these problems?
Tanks in advance
Tom
3 Replies
Problems appeared when installing Ex2019 on WS 2025, although according to the documentation Ex2019 should work on WS 2025. We hoped that the update from Ex2019 to ExSE would fix the existing problems.
Hi,thank you ror your relpy.
- Why?
We use Ex2016 on WS22016. We setup WS2025 with EX2019 as temporary Exchange server to upgrade it to Ex SE (as suggested in the article below). Everything should be simple, because Ex SE is an unusual CU for Exchange 2019 (as described in this article): Why “in-place upgrade” from Exchange 2019 to Exchange SE is low risk | Microsoft Community Hub
- Disabling antivirus software doesn't change anything. Of course, all exceptions have been added to the antivirus software (we use the built-in Defender and Palo Alto Cortex).
- I used Healtchecker of course. No errors.
- Why?
My first question is why did you go this route? It should not have resulted in your situation, but I'm still curious why you didn't just do a fresh install of Exchange Server SE on Windows Server 2025 and skip Exchange Server 2019 completely. Since you went this route, what build of Exchange Server 2019 did you start with?
Second, are you running antivirus software on this server and, if so, have you added the appropriate exclusions?
Finally, see if you can get Health Checker to run on your system to look for configuration issues, especially those related to virtual directories. See https://aka.ms/HealthChecker to download the tool.
