Exchange 2016 ECP / Powershell Error

Question

Good Evening Everyone

I am having some issues in my Exchange 2016 CU23 instance that were discovered after users reported not being able to search on the server side. I am in the process of rebuilding the server side index but wanted to see if anyone saw any correlation between that and two other issues i noticed (Especially #2) today along with getting some guidance on the best way to address them.

1. Clicking View Details for a user in the ECP creates the error message: Could not load file or assembly 'Microsoft.Exchange.OfficeGraph.GrainTransactionStorage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Access is denied.
2. EMS is giving the following error when using the Get-MailboxDatabaseCopyStatus commandlet and also produces the same error when running it standalone without parameters:

[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus * | sort name | Select name,status,contentindexstate
WARNING: An unexpected error has occurred and a Watson dump is being generated: The type initializer for
'Microsoft.Exchange.Cluster.Shared.RegistryParameters' threw an exception.
The type initializer for 'Microsoft.Exchange.Cluster.Shared.RegistryParameters' threw an exception.
    + CategoryInfo          : NotSpecified: (:) [Get-MailboxDatabaseCopyStatus], TypeInitializationException
    + FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.Exchange.Management.SystemConfigurationTask
   s.GetMailboxDatabaseCopyStatus

Answer 1

Hi @steve w,

Glad to know the issue has been resolved, thanks for sharing the solution so others with the same issue can easily reference it ! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer : )

[Exchange 2016 ECP / Powershell Error]

Problem symptoms:

Clicking View Details for a user in the ECP creates the error message and EMS errors occur when using the Get-MailboxDatabaseCopyStatus commandlet with or without parameters.

Resolution:

“This turned out to be corruption related and fixing that resolved all my issues along with rebuilding the index to resolve the original issue.”

Answer 2

Check the Service Health Portal:

https://admin.microsoft.com/Adminportal/Home?source=applauncher#/servicehealth

Answer 3

This turned out to be corruption related and fixing that resolved all my issues along with rebuilding the index to resolve the original issue. It's always easy to overlook that and i wanted to share the solution incase it helps anyone else.