Action: Wait for replication to take place. D10B Database needs to be repaired Source: GroupWise engine; database interface. Possible Cause: The user is not yet set up as a GroupWise user. D10D Cannot open any more mailboxes Source: GroupWise engine; database interface. Check This Out
Possible Cause: The user ID provided when the user was set up as a GroupWise user is not correct. Login as admin and click Reply on the mail with the Subject "Test using Telnet"4. Action: Log in to the tree rather than to a specific server. Possible Cause: Relational integrity problem.
The mails will then get rejected with the D023 error and the loop will be broken. Confirm that you wish the address to be deleted. See Creating GroupWise Accounts for eDirectory Users in Users in the GroupWise 8 Administration Guide. Action: Find the user in the To: line or Group.
Make sure Internet Addressing in enabled in GWIA2. The box will not appear again for that address. Action: Start the GroupWise client using the /@u or /la startup option to specify the GroupWise user ID. Action: Rebuild the post office database (wphost.db).
Correct the information as needed. Possible Cause: If this error occurs when the user tries to delete users from the Subscribe to Notify window, the users might no longer exist in the GroupWise system. It is recommended that expired users are removed from any distribution lists as they will still be sent emails as part of groups which will get rejected by the POA anyway. D102 Ambiguous user ID Source: GroupWise engine; database interface.
Bookmark Email Document Printer Friendly Favorite Rating: ERROR: "GroupWise Error [d101] User not found" when replying to external emailsThis document (7000455) is provided subject to the disclaimer at the end of Possible Cause: The user was not found in the post office database (wphost.db) during the parsing of To: line or group. Resolution This problem happened after an expired user was moved to a new post office. Explanation: Maximum databases open.