7.9 D10x Errors

NOTE:This guide does not include a comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved.

D101 User not found

Source: GroupWise engine; database interface.
Explanation: User not found.
Possible Cause: The GroupWise user ID is not found in the post office database during login.
Action: If using switches, check the /ph switch to make sure the path to the post office is correct.
Action: Start the GroupWise client using the /@u or /la startup option to specify the GroupWise user ID.
Possible Cause: The user is not yet set up as a GroupWise user.
Action: Set the user up as a GroupWise user. See Creating GroupWise Accounts in Users in the GroupWise 2012 Administration Guide.
Possible Cause: The user ID provided when the user was set up as a GroupWise user is not correct.
Action: Check the GroupWise user information in ConsoleOne. Make sure the common name (CN) of the user is provided. No additional information is needed in the Network ID field.
Possible Cause: User information has not replicated from the domain to the post office the user is trying to access.
Action: Wait for replication to take place. Make sure the MTA is running. Check the current scan cycles of the MTA. See Adjusting MTA Polling of Input Queues in the Domain, Post Offices, and Gateways in Message Transfer Agent in the GroupWise 2012 Administration Guide.
Action: Synchronize the user manually. See Synchronizing Individual Users or Resources in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The user is logging into a specific server, rather than into the tree, causing the network ID information not to match.
Action: Log in to the tree rather than to a specific server.
Possible Cause: If this error occurs when a user sends a message to a group, the group might contain user IDs that have been deleted from the system.
Action: Recreate the group, selecting users from the Address Book to ensure they are valid GroupWise users.
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.
Action: Check the Address Book to see if the users are still valid. If they are not, repair the user database (userxxx.db). See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: Run GWCheck on the post office database (wphost.db). See Stand-Alone Database Maintenance Programs in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The user was not found in the post office database (wphost.db) during the parsing of To: line or group.
Action: Find the user in the To: line or Group. Either delete the user, or find the correct user ID in the Address Book.
Possible Cause: If this error occurs for all users in a post office, the post office database might be damaged.
Action: Rebuild the post office database (wphost.db). See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs in systems where new users are added from multiple administrator workstations, preferences might be set differently on different administrator workstations.
Action: On each workstation where users are added in ConsoleOne, click Tools > GroupWise System Operations > System Preferences. Make sure that the When Creating or Modifying Objects, For Network ID Use setting is the same on all workstations. If some workstations are set to Full Distinguished Name and some are set to Common Name, users will be set up differently depending on which workstation they were created from, causing problems when users access GroupWise.
Possible Cause: If this error occurs only when using the GroupWise client in Remote mode, the user ID might be specified incorrectly under Remote Options.
Action: Check the user ID specified in the GroupWise client. Look up “Remote, specifying user and system information” in GroupWise client Help. Make sure the user ID specified is correct.

D102 Ambiguous user ID

Source: GroupWise engine; database interface.
Explanation: The GroupWise user ID is ambiguous.
Possible Cause: There is more than one user with same user ID in the same post office.
Action: Select the correct user ID in the pop-up list or select the user in the Address Book.
Possible Cause: If this error occurs when a user starts the GroupWise client, the user’s information in the post office database might not be correct.
Action: Check the information provided for the GroupWise user in ConsoleOne. Correct the information as needed. See Creating GroupWise Accounts for eDirectory Users in Users in the GroupWise 2012 Administration Guide.
Action: Even if the information in the user record looks correct, make a change somewhere so the record is written out again.
Action: If the problem persists, rebuild the post office database (wphost.db). See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

D103 Post office not found during login

Source: GroupWise engine; database interface.
Explanation: Post office not found.
Action: If using switches, check the /ph switch to make sure the path to the post office is correct. If it is incorrect, enter the correct /ph switch.
Action: If the path is correct, the post office was not found during parse of the To: line buffer. In that case, find the post office in To: line. Delete the post office qualifier, or select the user from the Address Book.

D104 Ambiguous post office

Source: GroupWise engine; database interface.
Explanation: The post office is ambiguous.
Possible Cause: There are multiple post offices in the same domain.
Action: The GroupWise client pops up a list so the user can correct the ambiguity manually. Select the correct user in the pop-up list, or use the Address Book to find the user.

D105 Directory Services data missing

Source: GroupWise engine; database interface.
Explanation: Directory Services error.
Possible Cause: Domain or post office not found during user or post office lookup.
Action: Check the /ph switch when starting the GroupWise client to make sure it specifies the correct path to the user’s post office. Also check the /@u switch to make sure it specifies a valid user in the specified post office.

D106 Database error

Source: GroupWise engine; database interface.
Explanation: General database error.
Possible Cause: The index is not synchronized with the data.
Action: Check and repair the database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

D107 Record not found

Source: GroupWise engine; database interface.
Explanation: Record not found.
Possible Cause: Relational integrity problem.
Possible Cause: The user database (userxxx.db) and/or message database (msgnnn.db) is damaged.
Action: Check and, if necessary, repair the database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: Run GWCheck. See Stand-Alone Database Maintenance Programs in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: A user tried to read an attachment for which the corresponding file has already been deleted from the offiles directory in the post office.
Action: None, unless you want to restore the contents of the offiles directory from a backup.

D108 Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D109 Bad parameter

Source: GroupWise engine; database interface.
Explanation: A GroupWise program passed invalid information to another GroupWise program.
Possible Cause: The user’s mailbox contains a damaged message.
Action: Run a structural rebuild on the user database (userxxx.db) and message database (msgnnn.db). See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: A delay in Directory replication is preventing the user from logging in to the GroupWise client.
Action: Start the client using the /@u-? switch to bypass eDirectory authentication.
Action: Wait for eDirectory replication to complete.
Possible Cause: The user’s Client Options settings have been damaged.
Action: Reset the user’s Client Options setting back to the default. See Resetting Client Options to Default Settings in Client in the GroupWise 2012 Administration Guide.

D10A Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D10B Database needs to be repaired

Source: GroupWise engine; database interface.
Explanation: Database invalid or damaged.
Possible Cause: A record is no longer valid.
Action: Validate the database, then take the appropriate actions to either recover or rebuild the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: Run GWCheck. See Stand-Alone Database Maintenance Programs in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs when running the GroupWise client under Windows for Workgroups, the user login name might be incorrect.
Possible Cause: Check the user login name on the station where the error occurs. In Windows for Workgroups, click Main > Control Panel > Network > Login Name. The login name must match the user’s GroupWise ID.

D10C Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D10D Cannot open any more mailboxes

Source: GroupWise engine; database interface.
Explanation: Maximum databases open.
Possible Cause: The maximum number of databases that can be opened at one time has been exceeded. The maximum number is approximately 12.
Action: Shut down some databases by removing proxies. Look up “proxy, deleting users from Access List” in GroupWise client Help.