7.10 D11x Errors

D110 Unexpected error

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

D113 Open database maximum exceeded

Source: GroupWise engine; database interface.
Explanation: The current operation has attempted to open more than the maximum number of databases allowed.
Possible Cause: You are proxied to too many users in direct mapped mode.
Action: Close some mailboxes that are currently proxied, then try the operation again. Look up “proxy, deleting users from Access List” in GroupWise client Help.

D114 Group not found

Source: GroupWise engine; database interface.
Explanation: Bad personal group or public distribution list.
Action: Check the spelling of the group name, or select the group in the Address Book.

D115 Database error

Source: GroupWise engine; database interface.
Explanation: Invalid database.
Possible Cause: Attempted to open an invalid database.
Action: Check and repair the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 7 Administration Guide .
Action: Run GWCheck. See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide .
Possible Cause: This could represent a security breach of unauthorized, foreign packets being introduced into your GroupWise system.
Action: Check your system security.

D116 File not database

Source: GroupWise engine; database interface.
Explanation: Attempt to open a DOS file as a GroupWise database.
Possible Cause: The database is damaged.
Action: Check and, if necessary, repair the user database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 7 Administration Guide .
Action: Run GWCheck. See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide.
Action: If a user database cannot be repaired, you can rename the existing user database, then recreate it. See Re-creating a User Database in Databases in the GroupWise 7 Administration Guide .
Action: If the database cannot be recreated, you must restore it from backup. See Restoring GroupWise Databases from Backup in Databases in the GroupWise 7 Administration Guide .

D117 GroupWise version too old

Source: GroupWise engine; database interface.
Explanation: Old program version.
Possible Cause: An attempt was made to open a database with an older version of GroupWise software. You are running an older version of the GroupWise client. Your post office has been updated to a newer version.
Action: Reinstall GroupWise with the version of the software that matches the database. See in Installing the GroupWise Windows and Cross-Platform Clients in the GroupWise 7 Installation Guide .

D118 Database error

Source: GroupWise engine; database interface.
Explanation: Field not found.
Possible Cause: Unable to find the field in the database.
Action: Check and repair the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 7 Administration Guide .
Action: Run GWCheck. See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide .

D119 Unexpected error

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

D11B Too many items in mailbox

Source: GroupWise engine; database interface.
Explanation: Too many records.
Possible Cause: There are more than 5,000 items in your mailbox. Only the first 5,000 items are displayed. When you delete messages, additional items are displayed.
Action: Have users clean out their mailboxes. You might want to run a statistics check on the mailboxes. Gathering Mailbox Statistics in Databases in the GroupWise 7 Administration Guide .
Action: Users could move items to different folders.
Action: Users could archive items. See “archive, items” in GroupWise client Help.

D11C Cannot use group name

Source: GroupWise engine; database interface.
Explanation: Groups cannot be listed as users here.
Possible Cause: A group name was used where a user name was expected. For example, the startup option /@u- group_name was used, or a group name was used in a domain where there is no entry in the Address Book for this group.
Action: Check your Address Book for correct addressing syntax. If the syntax is correct, you might want to add the group to the Address Book.
Possible Cause: The user has specified a distribution list in another post office that has visibility set to none.
Action: Change the visibility of the distribution list so that users in other post offices can use it. For information about visibility, see Creating and Managing Distribution Lists in Distribution Lists, Groups, and Organizational Roles in the GroupWise 7 Administration Guide .

D11D GroupWise version newer than database

Source: GroupWise engine; database interface.
Explanation: New program version.
Possible Cause: The GroupWise client has been installed on a workstation where the GroupWise demo that comes with the PerfectOffice Suite 3.0 had already been installed. The GroupWise demo creates a post office database ( wphost.db ) on the local workstation, which can interfere with the functioning of the full GroupWise client.
Action: Search the workstation for a local wphost.db file. If found, rename or delete it.
Possible Cause: The GroupWise client and agents were updated, but ConsoleOne was not. As a result, the database dictionary ( *.dc) files do not get updated.
Action: Copy the *.dc files from the domain and po subdirectories of the new distribution media to the domain and post office directories of your GroupWise system.
Possible Cause: The version of GroupWise you are running is newer than the database. The software cannot do an auto-upgrade on the older database.