7.1 D00x Errors

D001 Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D002 Folder not empty

Source: GroupWise engine.
Explanation: Folder not empty.
Action: Delete all items in the folder before attempting to delete it.

D004 Database error

Source: GroupWise engine.
Explanation: Database error. Attempt to read or modify settings failed.
Possible Cause: The user database (userxxx.db) contains inconsistent information.
Action: Check and, if necessary, repair the user database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 8 Administration Guide.

D005 Settings field list is not valid

Source: GroupWise engine.
Possible Cause: The post office database (wphost.db) is damaged.
Action: Rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 8 Administration Guide.

D006 Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D009 Cannot use group name in distribution list

Source: GroupWise engine.
Explanation: A group has been included in a Workflow.
Possible Cause: A group name was entered in the distribution list for a routed item. Groups are not supported in a workflow step.
Action: Delete the group name, then provide the names of the individual users in the group.

D00A Syntax error in address

Source: GroupWise engine.
Explanation: Syntax error.
Possible Cause: A syntax error was detected in the distribution list. One of the following conditions exists:
  • There is a colon (:), at-sign (@), or a period (.) inside a parenthesized list.

  • There are parentheses with nothing between them () or an opening parenthesis followed by a comma (, in the distribution list. There must be a user ID between the parenthesis and the comma.

  • There is a comma followed by a closing parenthesis ,) in the distribution list. There must be a user ID between the comma and the parenthesis.

  • There is a colon (:) somewhere after a closing parenthesis.

Action: Locate the syntax error in the distribution list. A pointer indicates where the error is. Correct the syntax error, then retry the operation.

D00B Missing closing quotation mark (")

Source: GroupWise engine.
Explanation: No closing quotation mark.
Possible Cause: A closing quotation mark (”) is missing in a distribution list.
Action: Type the closing quotation mark, then retry the operation.

D00C Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D00D Cannot match parentheses

Source: GroupWise engine.
Explanation: Problem with parentheses.
Possible Cause: Cannot match the parentheses in the distribution list. While processing the To:, BC:, and CC: buffers of a send window, a problem was found matching up parentheses. See also D00A Syntax error in address.
Action: Check the distribution list for incorrect usage of parentheses and resend.

D00E Distribution list contains nested groups

Source: GroupWise engine.
Explanation: Groups are nested too deep.
Possible Cause: The distribution list contains groups that are nested more than five levels deep or it might contain a circular reference. For example, if a personal group contains a recipient with the same name as the personal group, a circular reference is created.
Action: Edit the groups to remove the circular reference, or include the contents of one of the subgroups in a higher level group to reduce the levels in the structure.

D00F Remote mail error

Source: GroupWise engine.
Explanation: Invalid remote mail request.
Possible Cause: Remote mail error. This error is displayed whenever a more specific error is not available. The most common cause is a request for items that have already been deleted.
Action: Check and repair the databases of the master mailbox. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 8 Administration Guide.
Action: In Remote mode, the GroupWise client should automatically repair any problems with the remote databases. If the client is unable to repair the problem, you can delete the rofdata directory on the remote computer, then request all information from the master mailbox again.