C.1 Error Message List

Could not attach to eDirectory context

Source: GroupWise Migration Utility for Microsoft Exchange.
Explanation: The Migration Utility could not locate the eDirectory context where it has been instructed to create User objects for Exchange users.
Possible Cause: The context does not exist in eDirectory.
Action: Create the eDirectory context using ConsoleOne®.
Action: Specify an existing context in the Migration Utility.

Could not log onto Exchange server through MAPI

Source: GroupWise Migration Utility for Microsoft Exchange.
Explanation: The Migration Utility cannot access the Exchange server.
Possible Cause: The Exchange server is down.
Action: Make sure that the Exchange server is running.
Possible Cause: The workstation where you are running the Migration Utility has Outlook 2002 but no Service Packs have been applied to it.
Action: Apply Outlook 2002 Service Pack 1 or later.

Could not log onto mailbox

Source: GroupWise Migration Utility for Microsoft Exchange.
Explanation: The Migration Utility cannot access a mailbox that was selected for migration.
Possible Cause: The mailbox was deleted from the Exchange system between the time it was selected for migration and the time when the migration session was run.
Action: None. The mailbox is no longer available for migration.

Could not open Exchange mailbox table

Source: GroupWise Migration Utility for Microsoft Exchange.
Explanation: The Migration Utility could not read the list of mailboxes in your Exchange system.
Possible Cause: The user that is running the Migration Utility does not have administrator rights to the Exchange server or the Domain object in the Exchange system.
Action: Configure the user that runs the Migration Utility to have administrator rights, as described in Section 4.1.2, Designating a Service Account Administrator on Exchange 5.5 or Section 4.1.3, Ensuring Administrative Rights on Exchange 2000/2003, depending on your version of Exchange.
Possible Cause: The workstation where you are running the Migration Utility does not have a username and password that matches a username and password with administrator rights on the Exchange server.
Action: Set up a username and password on the workstation where you are running the Migration utility that matches a username and password on the Exchange server.

Could not open Exchange private store

Source: GroupWise Migration Utility for Microsoft Exchange
Explanation: The Migration Utility could not access the mailbox store on the Exchange server. This error might be accompanied by the additional error, “Properties for this information service must be defined prior to use.”
Possible Cause: The Windows desktop account being used by the user running the Migration Utility does not have Admin rights.
Action: Before running the Migration Utility, follow the instructions in Section 4.1.2, Designating a Service Account Administrator on Exchange 5.5 or Section 4.1.3, Ensuring Administrative Rights on Exchange 2000/2003, depending on your version of Exchange. When you log into the Windows desktop, make sure that you use the account you set up specifically for use with the Migration Utility.
Possible Cause: Outlook has been installed on the Windows machine where you want to run the Migration Utility but you have not yet run Outlook. Outlook must be run at least once in order for its MAPI providers to be available for use by the Migration Utility.
Action: Run Outlook before running the Migration Utility.

When starting, if Outlook prompts you to fix another application that is installed on the workstation, click Yes. If it does not prompt you, click Help > Detect and Repair, then click Start after Outlook is running.

Could not open GroupWise MAPI store provider for specified user

Source: GroupWise Migration Utility for Microsoft Exchange.
Explanation: The Migration Utility could not access the GroupWise mailbox that it previously created for the user.
Possible Cause: The Post Office Agent (POA) for the post office where the user is being migrated is not running.
Possible Cause: The mailbox was created during a previous migration session and has now been removed from the GroupWise system.
Action: Select the mailbox again in a subsequent migration session.
Possible Cause: The eDirectory object for the user exists but the GroupWise account could not be created.
Action: Select the mailbox again in a subsequent migration session.

Generated exception accessing Exchange mailbox store

Source: GroupWise Migration Utility for Microsoft Exchange.
Explanation: The Migration Utility cannot access the mailbox store on the Exchange server.
Possible Cause: The workstation where you are running the Migration Utility has Outlook 2002 but no Service Packs have been applied to it.
Action: Apply the latest Outlook 2002 Service Pack.

User not created

Source: GroupWise Migration Utility for Microsoft Exchange.
Explanation: The Migration Utility could not create a GroupWise account for the Exchange user.
Possible Cause: The username already exists in eDirectory™.
Action: Rename the Exchange mailbox so that the associated username is unique in eDirectory.
Action: Rename the existing GroupWise user so that the Exchange username is unique in eDirectory. See Renaming Users and Their GroupWise Accounts in Users in the GroupWise 7 Administration Guide.
Possible Cause: The eDirectory account file does not contain an eDirectory context for the username.
Action: Provide complete information in the eDirectory account file, as described in Section 3.1.4, Planning eDirectory Object Organization.
Possible Cause: The Post Office Agent (POA) for the post office where the user is being migrated is not running.