Exchange 2007: Mapi session exceeded the maximum of 32 objects of type “session”

Error Message: “Mapi session “/o=Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=JohnSmith” exceeded the maximum of 32 objects of type “session”".
Source: MSExchangeIS
Event ID: 9646

On the client side, the user is unable to connect to Microsoft Exchange or getting this error:

Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server is down for maintenance.

This usually happens when the user loses network connectivity while Outlook is still open. The Exchange server wasn’t able to close the sessions properly so they just stayed there even when they are not in use.

By default, Exchange only allows up to 32 MAPI (Outlook) sessions per user. To fix this problem, you must close some of the sessions.

What to do:

1. Download and extract Sysinternals’ TCPView (free) on the Exchange server
2. Open the Exchange Management Shell and type in the following command to get a list of all the opened sessions. Make a note of the IP Addresses:
   Get-LogonStatistics jsmith | Sort-Object clientipaddress | Format-Table username,clientipaddress,logontime
3. Open Tcpview.exe on the server. Sort it by Remote Address, then sort it by Process.
4. Look for the IP Addresses from Step 2 in the Remote Address column (if you only see hostnames, go to Options -> uncheck Resolve Addresses) and close their connections for the store.exe process (right-click and choose Close Connection, you can select multiple connections by holding the Shift or Ctrl key)
5. Run the command from Step 2 again and you will see that the sessions disappeared. The user should now be able to connect to the Exchange server again.

NBX Call Reports: Problem retrieving records from the NBX

Error message: “An error occurred while retrieving information from the NCP. There may be a problem with your network connection. Error info: [12002 - Communications error: The request has timed out.]”

I got this error message earlier while trying to download call records from the NBX. The problem turned out to be Internet Explorer 7. After uninstalling IE7 and restarting my computer, it worked! The funny thing is it worked before even when I had IE7 installed. So I reinstalled IE7 back just to make sure it’s really IE7 causing this problem and sure enough the problem came back.

This problem is actually listed in the 3Com NBX R6.0.35 Release Notes:

NBX Call Report can have problems retrieving records when it is running on a computer that has Internet Explorer 7 installed. If you experience this problem, you can uninstall IE 7 or run NBX Call Reports from a different computer where IE 7 is not installed. Note: NBX R6.0 and the optional applications have not yet been tested with IE 7. (ID 46308)

You can download the entire release notes from here: 3Com NBX R6.0.35 Release Notes

Outlook 2003: The operation failed due to an installation problem

Error Message: “The operation failed due to an installation problem. Restart Outlook and try again.”

I received this error message this morning when I opened Outlook 2003 with a new user profile. It opened fine with the local Administrator account.

I checked the Windows Event Viewer and there’s a “Warning” entry there for MsiInstaller (Event ID 1004) with a description of “Detection of product… The resource ‘HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\UserData’ does not exist.”

Doing the following fixed the problem for me:

1. Start -> Run -> type in regedit.
2. Go to HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common (or HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook as others have pointed out, please check your event logs to see which one you need to select (thanks to Supercow for noticing this)).
3. (I recommend that you back up your registry first before making any changes) Right-click on Common -> New -> DWORD Value. Name it UserData.
4. Double click on the DWORD value that you just created (i.e. UserData) and set Value data: to 1.
5. Close the Registry Editor and open Outlook again.

BDD 2007: Can’t connect to the deployment share

Error message: “A connection to the deployment share (\\server\deployment_share) could not be made. The deployment will not proceed.”

I ran into this problem this morning when trying to load Windows XP on a new computer using Business Desktop Deployment and Windows Deployment Services. It turned out that the reason for this is because my WinPE boot image didn’t have the network drivers for the new computer (when you type in ipconfig /all in the command prompt in WinPE, you’ll notice that there’s no IP assigned).

I fixed this problem by doing the following:

1. Download the network drivers for the computer having this issue.
2. Open the Deployment Workbench.
3. Add the network drivers to Distribution Share->Out-of-Box Drivers.
4. Go to Deploy->Deployment Points, select your deployment point and click Update. This will update your WinPE boot image (LiteTouchPE_x86.wim) to include the new drivers.
5. Open Windows Deployment Services and replace your boot image.
6. Reboot the client machine and boot in WinPE again, it should now be able to connect to the deployment share.