Submit a ticketCall us
Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > OWA Form Login component intermittently fails

OWA Form Login component intermittently fails

Table of contents
No headers

Issue: OWA Form Login component intermittently fails.

Cause (From Microsoft): "This issue occurs because the Exchange 2010 Store limits the number of non-MAPI sessions that other services generate, such as IMAP, POP, Outlook Web Access, Microsoft Exchange ActiveSync (EAS), or Exchange Web Services (EWS). By default, sessions per user are limited to 32, and service sessions per user are limited to 16."

Resolution (From Microsoft): Follow the steps outlined below:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows.

To resolve this issue, first determine whether this situation is caused by a different issue. If this is not the case, then increase the limit that your organization requires for non-MAPI sessions. To do this, follow these steps:

  1. On the server that is running the Exchange Server 2010 Mailbox role, click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type Maximum Allowed Service Sessions Per User, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Type the decimal value that specifies the number of sessions that you want to use, and then click OK.
  7. Exit Registry Editor.

Note The registry value Maximum Allowed Service Sessions Per User affects all Mailbox Databases on the server and is not applied on a per-user basis. If you increase this value, server performance may be adversely affected. For example, doubling the number of service sessions from 16 to 32 could slow server performance.

For more information, refer to the entire Microsoft article: 980049 (© 2016 Microsoft, available at, obtained on June 27, 2015.)


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

.OWA Form Login component intermittently fails



Last modified