You experience the following symptoms after you use the Import-Mailbox cmdlet to import data to a mailbox in Microsoft Exchange Server 2007 Service Pack 1.

Back to the top

Symptom 1

In Microsoft Outlook, users cannot see the free/busy information for the mailbox to which you imported data.

Back to the top

Symptom 2

In Outlook Web Access, you use the Address Book feature to find the user of the mailbox to which you imported data, and then you click that mailbox user. Then, you receive the following error message:Additionally, the MSExchangeOWAAppPool application pool crashes, and the following events are logged in the Application log.

Event ID 4999

Event Type: Error
Event Source: MSExchange Common
Event Category: General
Event ID: 4999
Description:
Watson report about to be sent to dw20.exe for process id: Process Id, with parameters: E12IIS, Processor.Version, OWA, M.E.D.Storage, M.E.D.S.Folder.InternalBind[T], System.ArgumentException, 6e81, 08.01.0240.005. ErrorReportingEnabled: False

Event ID 1011

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Description:
A process serving application pool 'MSExchangeOWAAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was 'Process Id'. The data field contains the error number.

Event ID 1002

Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Description:
Application pool 'MSExchangeOWAAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

Note These events are raised because Internet Information Service automatically starts a new instance of the W3wp.exe process to host the Exchange Server 2007 Outlook Web Access Web service.

Back to the top

This problem occurs because the PR_IPM* EntryID fields in the Inbox do not match the PR_ENTRYID EntryID fields of the folders that are associated with the items. The Import-Mailbox cmdlet copies the PR_IPM* EntryID fields from the .pst file. However, the PR_ENTRYID EntryID fields on the folders are not updated.

Back to the top

To resolve this problem, install Update Rollup 2 for Microsoft Exchange Server 2007 Service Pack 1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Workaround 1

Send a meeting request to every user to whose mailbox you imported data, and then ask them to accept it.

Back to the top

Workaround 2

Follow these steps to log on to each mailbox to which you imported data:

1.	Stop Microsoft Outlook.
2.	Open a command prompt, and then switch the working directory to the folder where the Outlook.exe file exists.
3.	Type the following command at the command prompt, and then press ENTER: Outlook.exe /CleanFreeBusy

Back to the top

Workaround 3

1.	Obtain Microsoft Exchange Server MAPI Editor (MfcMapi.exe) from the following Microsoft Download Center Web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=55fdffd7-1878-4637-9808-1e21abb3ae37 (http://www.microsoft.com/downloads/details.aspx?FamilyID=55fdffd7-1878-4637-9808-1e21abb3ae37)
2.	On a client computer that has a mailbox profile that is configured for Microsoft Outlook, start the MfcMapi.exe program.
3.	Click OK to dismiss the warning message.
4.	On the Session menu, click Logon and Display Store Table.
5.	In the Profile Name list, select the profile, and then click OK.
6.	The Mailbox - Username store and the Public Folders store are displayed. Double-click Mailbox - Username.
7.	In the Mailbox - Username window, expand Root - Mailbox in the console tree, expand IPM_SUBTREE, and then click Calendar.
8.	In the details pane, double-click PR_ENTRYID, PR_MEMBER_ENTRYID.
9.	Select and copy the value of the Bin text box, and then click Cancel.
10.	Under IPM_SUBTREE, click Inbox.
11.	In the details pane, double-click PR_IPM_APPOINTMENT_ENTRYID.
12.	Clear the value of the Bin text box, paste into it the text that you copied in step 9, and then click OK.
13.	Close Exchange Server MAPI Editor.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about the Import-Mailbox cmdlet, visit the following Microsoft TechNet Web site:For more information about how to convert identifiers, visit the following Microsoft Developer Network Web site:

Back to the top