Fix: Groupwise user stuck as pending after moving to new post office


After moving a user in one domain to a post office in another domain, we could no longer access the account. We also saw the following symptoms:

Errors:
0xd70e Duplicate entry found in database<
0xdb0a – record not found

Observations:
1. User was appearing in both source and destination post office
2. Both Groupwise user objects were stuck with Pending Move and could not be edited or modified
3. Source post office showed userxxx.db file as 1,922 KB. Destination post office showed userxxx.db file as 112Kb in size.
4. Groupwise User Move Utilify would intermittently show the account. Other times the account did not appear.
5. Pending Operations were not shown for the Groupwise System
6. Destination POA event log repeatedly showed
ADM: Completed: Update object in post office – User GWDOM1.PO5.D105
7. Source POA event log repeatedly showed
ADM: Completed: Update object in post office – User GWDOM2.PO1.D105

Steps taken to resolve stuck user:

1. Connected to primary domain – validated domain database to rule out corruption
2. Connected to source domain – validated domain database, then post office database
3. Connected to target domain – validated domain database, then post office database
4. Connected to primary domain – synchronized primary domain with source domain
5. Connected to primary domain – synchronized primary domain with target domain
6. Disassociated the Groupwise account from the eDirectory account
7. Waited 15 minutes
8. Connected to primary domain – synchronized primary domain with source domain
9. Connected to primary domain – synchronized primary domain with target domain
10. Reassociated the Groupwise account in the source post office with the eDirectory account.
11. Connected to primary domain – synchronized primary domain with target domain
12. Connected to primary domain – synchronized primary domain with source domain

Was then able to access the user’s mailbox with all items intact. The user’s Groupwise account appeared back in the source domain, not the target domain. I ran a GWcheck on the affected user to verify structural intergrity of the user and message database. We will attempt to move the user again after the holiday.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: