![]() The OwaMaxConcurrency parameter has a valid range from 0 through unlimited. However, the existing connections remain valid. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. ![]() A connection is held from the moment a request is received until a response is sent in its entirety to the requester. The OwaMaxConcurrency is a parameter specifies how many concurrent connections an Outlook on the web user can have against an Exchange server at one time. ![]() However, the existing connections remain valid.Ī valid value is an integer from 0 to unlimited. These connections are considered when the server receives the request from the user until the connection is closed(Eg: The connection is considered as terminated only when the User closes the browser,goes offline,sign outs) The RcaMaxConcurrency is a parameter which controls how many Simultaneous parallel connections an RPC Client Access user can establish against an Exchange server at same time. See the values of RcaMaxConcurrency and OwaMaxConcurrency for Global Throttling Policy and the Default Throttling Policy The Default value can be seen by running the below command So looked into the default connection OWA limit of the mailbox to see default values IIS logs location can be found on below locationįurther looked into the Event Viewer and found the event id 9646 with the below message for source MSExchangeISĬlient Type OWA Exceeded the maximum objects of 16 per session Looked into the IIS logs for the affected mailbox and there were multiple connections coming from different sources. This issue happened for only one mailbox and it was fine for rest of the users. This was a shared mailbox accessed by multiple team members. Recently one of the shared mailbox which resides on Exchange 2016 while trying to access from web mail the users were getting the below error.
0 Comments
Leave a Reply. |