Hello support,
I receive following error when i try to open client mailboxes.
"System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'GET_MAILBOX_GENERAL' task on '' EXCHANGE ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Connecting to remote server hex01.qloudwise.com failed with the following error message : [ClientAccessServer=HEX01,BackEndServer=hex01.qloudwise.local,RequestId=81baf0ba-e0c5-4faa-a6f5-2df2c61814c9,TimeStamp=4/13/2017 11:58:24 AM] [FailureCategory=AuthZ-OverConnectionLimit] Fail to create a runspace because you have exceeded the maximum number of connections allowed : 18 for the policy party : MaxConcurrency. Please close existing runspace and try again. Policy: CN=psws,CN=Global Settings,CN=QW-HEX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=qloudwise,DC=local; Snapshot: Owner: Sid~QLOUDWISEWPServer"
Everything was working fine until this yesterday, nothing was changed.
Best regards,
Nikola
Hello,
The error is having max connections allowed:
Fail to create a runspace because you have exceeded the maximum number of connections allowed
If you do an iisreset on the server hex01.qloudwise.com it should be fine again.
Optionally you can increase your max connection policy (however normally by default not needed).
Regards,
Marco
Hi Marco,
I have tried iisreset and now i get :
"Error reading mailbox general settings. See audit log for more details.
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'GET_MAILBOX_GENERAL' task on '' EXCHANGE ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Specified method is not supported. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse"
Now when i tested on all clients i can see that around 10% work fine and others throw this error. I can create new organizations and mailboxes without any issue.
Nikola
I'm afraid i haven't really seen this type of error before in combination with a working create org and mailboxes.
I would say it seems to indicate a misconfiguration. but the error isn't detailed enough to know where to look without further event logs.
