DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2019948 - Last Review: May 5, 2014 - Revision: 3.0

Symptoms

Outlook Dialogue box pop- up stating “Trying to Connect to Microsoft Exchange Server.”  You may get a MAPI_E_LOGON_FAILED

Cause

Windows Server 2008 GC’s have a limitation of 50 concurrent NSPI connections per user. 
Applications such as Outlook 2007, Blackberry Enterprise Server, or any application that will create multiple NSPI connections to a DC/GC can experience these symptoms.

Resolution

  1. To Resolve this issue, modify the following registry entry. 
  2. Click Start, click Run, type regedit, and then click OK
  3. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS 
  4. On the Edit menu, point to New, and then click Key.
  5. Type Parameters, and then press ENTER. 
  6. Click the Parameters key. 
  7. On the Edit menu, point to New, and then click DWORD Value
  8. Type NSPI max sessions per user, and then press ENTER. 
  9. Double-click NSPI max sessions per user, type the number of the NSPI connections required, and then click OK.

Note: While the upper limit of this setting is 0xffffffff (or 4294967295), configuring the server with a value larger than the default will consume additional memory on the server – one new page per connection. If the value is set too high and too many connections are created for each user application instance, the server will run low on memory or become completely unresponsive. The lower default NSPI connection limit in Windows Server 2008 was based on customer experience, where previous operating systems would allow themselves to be overwhelmed by third party products in what amounts to a denial of service attack. Use a common sense approach to increasing beyond the default value; for example, start with decimal 250 (hex 0x000000FA), then test to see the memory overhead created and that the errors have ceased. Your long-term solution must be to contact the vendor of your NSPI product and ask them to change their behavior; the registry value is only as a workaround to provide error relief.

More Information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Applies to
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Windows Server 2008 Standard
  • Windows Server 2008 Enterprise
Keywords: 
KB2019948
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support