This issue may go out by itself. But if the user is still experiencing the issue, try to close the IP connections, and investigate what on his desktop (or on other desktops if he has multiple opened connections) can generate too much MAPI connections.

Usually, it can be caused by VPN connections closing and users re-opening them. When a VPN connection closes, the MAPI session to an Exchange Server is not released. Then re-establighing the VPN then the MAPI connection just add more MAPI connections

It can also be caused by an external MAPI based device such as Blackberry or application such as scripts or third-party mail applications.

1- First, checkout the IP address of UserAlias listed in the Distinguished Name of the event :

Get-LogonStatistics UserAlias | ft Name,ClientIPAddress

Note: if the client is not more connected to the Exchange server or the MAPI sessions finally closed by themselves, the ClientIPAddress property will be blank

2- Using a tool like TCPView (http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx), close the connections from your Exchange server that refer to the ClientIPAddress you just get with the PowerShell command in Step-1

Again, forcing TCP connections without knowing the cause of what caused them is not very clever. The MAPI connections exhaustion may come back.

Check with the user’s devices and applications he is using to connect to the Exchange server as you may be able to solution the issue for a broader number of users.

Mike Pfeiffer wrote  a good and concise article that shows step by step how to install the ADGWS on your AD servers, AND how to install the Active Directory Module on the Windows workstations (that need RSAT tools – Remote Server Administration Tools) :

http://www.mikepfeiffer.net/2010/01/how-to-install-the-active-directory-module-for-windows-powershell/

Bonjour,

Avec mes excuses pour le lien erroné dans le cours PowerShell, voici le lien vers le poster original de référence rapide des CmdLets Active Directory (pour rappel, pour pouvoir administrer des serveurs avec les outils PowerShell, ADMGS ou Active Directory Management Gateway Service est nécessaire sur les serveurs Windows 2003 SP2, Windows 2003 R2 SP2, Windows 2008 et Windows 2008 SP2 – ADMGS est installé par défaut sur Windows 2008 R2)

(http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/CommunityServer-Components-PostAttachments/00-09-45-35-90/ADPS_5F00_Overview.png)

Windows PowerShell Quick Reference

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=df8ed469-9007-401c-85e7-46649a32d0e0

Windows Management Instrumentation Tutorial

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=720F0CAE-64A7-457F-BB95-E4F33E0CBC55&displaylang=en

De : http://en.wikipedia.org/wiki/WS-Management

Web Services-Management (WS-Management) is a DMTF open standard defining a SOAP-based protocol for the management of servers, devices, applications and various Web services. The DMTF has published the standards document DSP0226 with version v1.1.0 of 2010-03-03 ….

De : http://en.wikipedia.org/wiki/SOAP_(protocol)

SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) for its message format, and usually relies on other Application Layer protocols, most notably Remote Procedure Call (RPC) and Hypertext Transfer Protocol (HTTP), for message negotiation and transmission. SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built……..more on http://en.wikipedia.org/wiki/SOAP_(protocol)

De : http://visualbasic.about.com/od/usingvbnet/l/blglossa.htm

Web Services
Software that runs over a network and provides information services based on XML standards that are accessed through a URI (Universal Resource Identifier) address and an XML defined information interface. The standard XML technologies normally used in web services include SOAP, WSDL, UDDI and XSD. See Quo Vadis, Web Services

For some particular issues, if you don’t have the means to create a new System Attendant Mailbox (that is by moving all users mailboxes from the store where the SA Mailbox resides)

We need the following tool: http://mfcmapi.codeplex.com/

1.) Create an Outlook Profile, in Online Mode.

2.) Launch MfcMapi.exe, select Session -> Logon Only ( Does Not display stores ), choose the profile created under the previous step, select MDB – get Mailbox Table.

3.) Enter the name of the server that owns the store/mailbox you wish to view.

4.) Double click the SystemMailbox.

To reset the FreeBusy messages if FreeBusy information are missing when some users are booking meetings, search for the system messages for Free/Busy informations :

5.) Under SpecialPrivateFolderFreeBusyStorage , you will see the Free Busy Messages, select them, right click them and do a hard delete and you're done.

From: Patrick from his blog - http://blogs.technet.com/b/ehlro/archive/2010/11/01/using-mfcmapi-to-connect-to-the-exchange-system-attendant-mailbox.aspx

Cached Mode Clients

- Uncheck Download Shared Folders or Download Public Folder favorites

- Ensure that Client’s desktop search is only indexing offline files, not online services/mailbox

- Confirm that clients are using 1 copy of the OAB (not multiple) and/or are directly accessing the online GAL to a “closest” GC

Online Clients

- Do not allow desktop search to index the online mailbox

- Do not allow File-level antivirus to scan the mailbox

- Do not integrate desktop applications with the mailbox (ex: BES, Adobe, etc)

All Outlook Clients

- Be sure that clients are running tested and approved versions of Outlook.  Try to keep them current

- Disable unused Outlook add-ins

- Do not use the To-Do bar

- Disable Planner Options (for most resources)

- Do not store OST/PST files on a network share

- Use TCPView to randomly check that clients are connecting to the correct servers using the expected protocols (TCP vs HTTP)

- Request users to close other user’s folder connections when they are no longer needed.  Many people will share a folder/calendar and never release it from their client

- Turn off/disable unused or unpopular features (ex: journaling, RSS feeds, Sharepoint integration, Internet calendars, etc)

Lorsque des clients Outlook 2007 utilisent la fonction de calendriers partagés, ils ouvrent implicitement des connections clientes de type “Exchange Administrator”.

D’après les premiers éléments recueillis, il s’agit d’un “flag” MAPI que le client Outlook positionne pour certaines connexions, dont ces connexions d’un utilisateur à un ou des calendriers partagés.

Voici l’article détaillant les opérations à réaliser si vos utilisateurs rencontrent des difficultés de connexion à des calendriers ou autres répertoires partagés à cause de la limite des 10 000 connections atteintes pour les instances “Exchange Administrator” :

Exchange Store Limits: Exchange 2010 Sp1 Help

http://technet.microsoft.com/en-us/library/ff477612.aspx

1. Start Registry Editor (regedit).

2. Navigate to the following registry subkey:
\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem.

3. Right-click ParametersSystem, point to New, and then click DWORD (32-bit) Value.

4. Enter the following for the Value Name
Value Name: Maximum Allowed Exchange Sessions Per Service
Value Data: 25,000 or whatever limit you want (Default when value is not present is 10,000). Maximum value is 65536
Note: The value data should be entered in Decimal.