Exchange Server minLength > maxLength
Hey,
I’ve recently encountered this strange error in Exchange Server with no online documentation of it except for my own post on spiceworks.
It doesn’t effect mail flow, however I can’t add or remove users, modify certain parts of the database, etc.
Whenever I run `Get-User` or access the mailboxes area of ECP, I get the following error:
[PS] C:Windowssystem32>Get-User
WARNING: An unexpected error has occurred and a Watson dump is being generated: minLength > maxLength
minLength > maxLength
+ CategoryInfo : NotSpecified: (:) [Get-User], ArgumentException
+ FullyQualifiedErrorId : System.ArgumentException,Microsoft.Exchange.Management.RecipientTasks.GetUser
+ PSComputerName : GLTX-EXCH-01.galactix.local
I have tried running a mailbox repair, but it comes back clean. I am utterly confused at why this might not be working.
Upon trying to deploy a secondary Exchange server on my network, I also found that fails too due to this bug.
The HealthCheck tool provided by MS doesn’t return anything out of the ordinary either, adding to my confusion.
Does anyone know how I might resolve this issue?
Hey,I’ve recently encountered this strange error in Exchange Server with no online documentation of it except for my own post on spiceworks.It doesn’t effect mail flow, however I can’t add or remove users, modify certain parts of the database, etc. Whenever I run `Get-User` or access the mailboxes area of ECP, I get the following error:[PS] C:Windowssystem32>Get-User
WARNING: An unexpected error has occurred and a Watson dump is being generated: minLength > maxLength
minLength > maxLength
+ CategoryInfo : NotSpecified: (:) [Get-User], ArgumentException
+ FullyQualifiedErrorId : System.ArgumentException,Microsoft.Exchange.Management.RecipientTasks.GetUser
+ PSComputerName : GLTX-EXCH-01.galactix.local I have tried running a mailbox repair, but it comes back clean. I am utterly confused at why this might not be working. Upon trying to deploy a secondary Exchange server on my network, I also found that fails too due to this bug. The HealthCheck tool provided by MS doesn’t return anything out of the ordinary either, adding to my confusion. Does anyone know how I might resolve this issue? Read More