You receive an error message when you use the Exmerge tool to retrieve a list of mailboxes from a recovery storage group in Exchange Server 2003 (919088)
The information in this article applies to:
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
SUMMARYThis article describes an error message that you may receive when you run the Exmerge tool to retrieve a list of mailboxes in Microsoft Exchange Server 2003. This issue occurs if the original user account of a mailbox has been deleted. This article describes how to work around this issue by moving the affected mailbox into the original mailbox store. SYMPTOMSConsider the following scenario. In Microsoft Exchange Server 2003, you use the Exmerge tool to extract mail from the mailboxes that are located in a recovery storage group. Then, you try to retrieve the list of mailboxes that reside on a selected server. In this scenario, you receive the following error message: An error was encountered with one or more users when retrieving the list of
mailboxes homed in the selected databases on server 'Server_Name'. Please refer to
the log file, 'ExMerge.log', for more information. Additionally, when you run the Exmerge tool, you may not see all the mailboxes that are displayed when you view the recovery storage group in Exchange System Manager. If you view the ExMerge.log file, you will see the following error:
[17:37:20] Error! Cannot identify the user with the msExchMailboxGuid GUID. The
legacyExchangeDN is /O=ORG/OU=SITE/CN=RECIPIENTS/CN=USER. [17:37:20] Skipped 1 mailbox(es) homed on database 'STORAGE GROUP/MAILBOX STORE'
because of errors. [17:37:20] Skipped 1 mailbox(es) homed on the specified databases because of
errors. CAUSEThis issue occurs if the original user account for a mailbox has been deleted. When you run the Exmerge tool against the recovery storage group, the tool searches for the msExchMailboxGuid attribute of the user account that was originally connected to the mailbox. If the tool cannot find the attribute, it returns the error that is described in the "Symptoms "section. WORKAROUNDTo work around this issue, move the affected mailbox into the original mailbox store. To do this, follow these steps. Step 1: Dismount the recovery storage group mailbox store- Start Exchange System Manager.
- Expand Servers, and then expand the appropriate recovery storage group.
- Right-click the affected mailbox store, click Dismount Store, and then click Yes.
Wait for the process to be completed.
Step 2: Run the Eseutil tool against the recovery storage group database- Start a command prompt.
- Move to the Drive_letter:\Program Files\Exchsrvr\Bin folder.
- Type Eseutil /mh path of the recovery storage group database file, and then press ENTER. For example, type the following text, and then press ENTER:
type eseutil /mh c:\Program Files\Exchsrvr\RSG-1\Mailbox Store (Server_Name).edb - In the output, verify that "Clean Shutdown" appears in the State line.
Step 3: Create a new storage group- Start Exchange System Manager.
- Right-click Server_Name, point to New, and then click Storage Group.
- In the Name box, type an appropriate name, and then click OK.
For example, type Temp Storage Group, and then click OK.
Step 4: Create a new mailbox store under the new storage group- Right-click the new storage group that you created in step 3, point to New, and then click Mailbox Store.
- In the Name box, type the name of the original mailbox store, and then click OK.
- When you are prompted to mount the database, click No.
- Right-click the mailbox store object, and then click Properties.
- Click the Database tab.
In the Exchange database box, note the path of the database file. For example, this path will resemble the following path:
C:\Program Files\Exchsrvr\Storage_Group_Name\Mailbox_Store_Name (Server_Name).edb
Step 5: Copy the database from the Recovery Storage Group folder to the new mailbox store folder- Under the Recovery Storage Group container, right-click the mailbox store object, and then click Properties.
- Click the Database tab.
In the Exchange database box, note the path of the database file. For example, this path will resemble the following path:
C:\Program Files\Exchsrvr\Recovery_storage_group_name\Mailbox_Store_Name (Server_Name).edb - In Windows Explorer, open the folder of the database file that you noted in step 5b.
Then, copy the two files that have the .edb and .stm file name extensions to the folder of the new storage group. The folder that you noted in step 4d is the folder of the new storage group.
Step 6: Reconnect the affected mailbox to a new user account- Under the new storage group that you created, right-click the mailbox store, and then click Mount Store.
- Click OK.
-
Right-click the Mailboxes container, and then click Run Cleanup Agent.
- In the Mailboxes container, right-click the disconnected mailbox. Then, click Reconnect.
Note A red "X" will appear on the disconnected mailbox. - Click the appropriate user in the Select a new user for this mailbox dialog box.
Step 7: Move the affected mailbox back to its original mailbox store- In the right pane, right-click the affected mailbox, and then click Exchange tasks.
- In the Exchange Task Wizard that appears, click Next.
- On the Available Tasks page, click Move Mailbox under Select a task to perform. Then, click Next.
- On the Move Mailbox page, click the appropriate server in the Server list. Then click the original mailbox store in the Mailbox Store list.
- Click Next.
- Configure a method to use to handle any corrupted messages that are found during the move. Then, click Next two times.
- Exit Exchange System Manager.
MORE INFORMATIONIf you create a new user account that has the same name as the original account, the error that is described in the "Symptoms" section will still be returned. This behavior occurs because the msExchMailboxGuid attribute of the new user account will be different.REFERENCES
For more information about how to recover data by using the Exmerge tool, visit the following Microsoft Web site:
Modification Type: | Minor | Last Reviewed: | 8/29/2006 |
---|
Keywords: | kbtshoot kbprb KB919088 kbAudITPRO |
---|
|