BlackBerry Connection > IT Edition > Admin Tips: Windows Server 2008 Changes in BlackBerry Environments

Admin Tips: Windows Server 2008 Changes in BlackBerry Environments

With Windows Server® 2008, you may have noticed some changes in the default behavior when it comes to Named Service Provider Interface (NSPI) connections in your BlackBerry® Enterprise Server.

Before Windows Server 2008, any individual Messaging Application Programming Interface (MAPI) client could make virtually unlimited NSPI connections to a Global Catalog without consequence. NSPI is the interface that allows MAPI to interact with the Global Catalog server to use the Microsoft® Exchange address book and to perform name resolution tasks requiring the information stored in the Global Catalog.

To better manage these connections from MAPI clients, Windows Server 2008 now sets a limit of 50 NSPI connections per user, and also changes the default behavior of the Domain Controller with regards to NSPI connections. According to Windows Support, the changes are to protect domain controllers against clients that open too many NSPI connections without then closing them. Too many such connections can cause resource depletion.

What administrators should watch for...

It all makes sense, but if you're experiencing odd behavior in your environment because of these changes, you might need to make some changes too. For example, are you seeing multiple log lines noting events such as the following?

	
	[40000] (12/22 08:58:11.719):{0x1A38} Setting PR_PROFILE_CONNECT_FLAGS
	CONNECT_IGNORE_NO_PF true
	[40206] (12/22 08:58:11.719):{0x1A38}
		

Or:

	
	CDOCalendar::Initialize - Code = 800406f9, WCode = 04f9, Code meaning =
	IDispatch error #1273,
	[30002] (12/22 09:44:49.764):{0x4EC} Server = mercmbx11, Mailbox = 
	<Mailbox Distingushed Name> Description = The information store 
	could not be opened. [MAPI 1.0 - [MAPI_E_LOGON_FAILED(80040111)]]
		

Note: For the full list of debug log items that may point to a problem connected to the change in Windows Server 2008, please review KB17325.

If you are seeing such messages, it’s worth taking a few preventive steps to mitigate any potential impact. For starters, multiple BlackBerry Enterprise Server instances in the environment can be run under different service accounts. You can also increase the limit on the number of NSPI connections per BlackBerry® smartphone user.

First, you need to find out if the NSPI connection limit is the issue. Start by turning on additional logging on the Global Catalog Server, and then follow these steps:

  1. On the domain controller that is targeted for the NspiBind connection, click Start, click Run, type regedit, and then click OK.
  2. Double-click the following registry entry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Diagnostics\4 MAPI Interface Events
  3. In the Value data box, type 5, and then click OK.

Now look in the Directory Services event log on the Global Catalog Server for the following event:

	Event ID: 2820
	NSPI max connection limit for the user has reached.

		

Now that you know connections have been limited, you can apply this easy workaround:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS
  3. On the Edit menu, point to New, and then click Key.
  4. Type Parameters, and then press ENTER.
  5. Click the Parameters key.
  6. On the Edit menu, point to New, and then click DWORD Value.
  7. Type NSPI max sessions per user, and then press ENTER.
  8. Double-click NSPI max sessions per user, type the maximum number of the NSPI connections that you want to have, and then click OK.
  9. Exit the Registry Editor.

You should complete this task on any Global Catalog Server that the BlackBerry Enterprise Server may be required to connect to (for example, all Global Catalog Servers in the same site as the service account mailbox). As long as the limit exceeds the number of required connections found above normal, functionality can be restored.

If you anticipate large-scale growth in the future for your BlackBerry smartphone deployment, it is recommended that you account for that BlackBerry smartphone user volume. If you want to emulate the behavior of Windows Server® 2003, set the value high enough that it is unlikely to ever be reached (for example: 1,000).

Where to get help

Start a discussion on the BlackBerry® Enterprise Solution topic in the BlackBerry® Support Community Forums.

KB 17325: BlackBerry Enterprise Server May Encounter issues in a Microsoft Windows Server 2008-based Microsoft Active Directory environment »

BlackBerry Enterprise Server Express

Support Forums

The BlackBerry® Support Community Forums are a great place for your BlackBerry device users to get help—and a place for you to connect with other IT administrators. Do you have questions about BlackBerry Enterprise Solutions? Are you looking for support on devices or accessories? Visit the BlackBerry Support Community Forums.