This article is a compilation of the various errors you may encounter when doing a migration with Groupwise as the Source endpoint.
Cannot Export a Groupwise Contact Form
Error Message
Cannot Export a Groupwise Contact Form
Explanation
In some cases, address book folders (including private or shared personal address books) may become corrupted or inaccessible. In those cases, MigrationWiz logs this error message to alert you of this condition and proceeds with the migration.
Resolution
Check to see if the user can access the contact folder using a web or rich client. If the contact folder is shared, review permissions. In some cases, folder content may be corrupted. If so, we recommend running consistency checks on the database/mailbox.
- Multi-user folders are not migrated, and are not supported for migration. These will need to be filtered out of the migration. For more information, see Folder Filtering & Mapping in MigrationWiz
- If the affected calendar is a multi-user calendar, see GroupWise cursor create failed. Error: Access denied Code 53540 below.
Cannot migrate email from GroupWise
Error message
Cannot migrate email from GroupWise
Explanation
GroupWise versions prior to 7.0.3 are unable to return MIME content for email messages using the SOAP endpoint. As a result, while appointment, contact and task items can be migrated, email cannot be migrated.
Resolution
There are multiple possible resolutions to this error message. The simplest would be to upgrade to GroupWise version 7.0.3 or later, in which case it will become possible to migrate email using the SOAP endpoint.
If an upgrade is not feasible, the following options can be used:
- Select the mailbox in the migration project and from the Start menu select Full Migration.
- In the Select what you want to migrate: section, un-check all the boxes except Contacts and Calendars.
- Click the Start Migration button.
To migrate email items
- Create a second mailbox migration project with IMAP as the source endpoint.
This will allow you to add your users and run the migration to migrate email items.
EXAMINE (820E)
Error message
EXAMINE (820E)
Explanation
GroupWise systems may return this error when under excessive load, due to database contention issues.
Resolution
Follow Novell's instructions regarding this error code.
Folder (Folder Name)'s parent hierarchy contains a loop
Error message
Folder (Folder Name)'s parent hierarchy contains a loop.
Explanation
This error can occur in GroupWise migrations when the specified Source folder is its own parent.
Resolution
To resolve the error, either delete the folder or fix the hierarchy.
GroupWise cursor create failed. Error: Access denied Code: 53540
Error message
GroupWise cursor create failed. Error: Access denied Code: 53540
Explanation
This error occurs when attempting to migrate a Multi-User Calendar view that is pointing back to the user currently being migrated.
Resolution
- Check the permissions on the task folder
OR
- Skip the migration of Tasks for that user.
GroupWise login failed. Error: User not on post office Code: 53505
Error message
GroupWise login failed. Error: User not on post office Code: 53505
Explanation
This error occurs when migrating from GroupWise using a trusted key, and MigrationWiz is unable to find the user in the Source environment. GroupWise uses an Email Address and a Login Name, but those two values are not always the same. Instead, the Login Name is often the name of the mailbox without the domain.
Resolution
Confirm that the Login Name provided to MigrationWiz is the correct one.
Redirect User to Different Post Office Error
Error message
Redirect user to a different post office
Explanation
This error indicates that the mailbox, as specified in MigrationWiz, is not located on the target GroupWise POA (Post Office Agent), and that we were informed of a redirect which we were unable to follow. For example, the POA may have redirected us to an IP or host name which is only accessible from the local Intranet.
Resolution
- Check that the specified user name is on the target POA.
- If the user is on a linked POA, make sure the link references a publicly-accessible name/IP.
- If necessary, update POA links to use publicly-accessible names/IPs.
User not on post office
Error message
User not on post office
Explanation
This error indicates that the mailbox, as specified in MigrationWiz, is not located on the target GroupWise POA (Post Office Agent).
Resolution
- Check that the specified user name is a true GroupWise user name.
- Typically this is not an email address (i.e., specify Joe, not Joe@company.com).
- Check that the specified user name is on the target POA.
- If the user is on a linked POA, make sure the link references a publicly accessible name/IP.
- Make sure you can log in using the specified GroupWise user name using GroupWise Web Access at the target POA.
- Check GroupWise settings for the specified user/email address.