7.23 DB4x 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.

DB40 Cannot delete gateway used in link

Source: GroupWise engine; administration engine.
Explanation: Gateway links exist.
Possible Cause: The gateway you are attempting to delete is used in a gateway link.
Action: Reconfigure the links before deleting the gateway. See Editing a Domain Link in Domains in the GroupWise 2012 Administration Guide.

DB41 Database does not match domain or post office

Source: GroupWise engine; administration engine.
Explanation: Incorrect database path
Possible Cause: The database found at the specified path does not match the specified domain/post office name.
Action: Enter the correct path.

DB42 Information lost during recovery

Source: GroupWise engine; administration engine.
Explanation: Information lost.
Possible Cause: Some records were lost during the recover operation.
Action: You might want to rebuild the database at this time. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

DB43 Maximum number of open post offices reached

Source: GroupWise engine; administration engine.
Explanation: Maximum number of post offices are opened.
Possible Cause: You have tried to open too many post offices.
Action: Close one or more post offices. See Disabling a Post Office in Post Offices in the GroupWise 2012 Administration Guide.

DB45 GroupWise system not found

Source: GroupWise engine; administration engine.
Explanation: No system found.
Action: Verify the path to the domain database (wpdomain.db).
Action: Make sure you are logged in to the server where the GroupWise system resides.

DB46 Path too long

Source: GroupWise engine; administration engine.
Explanation: Path too long.
Action: You can map a drive to a lower level.

DB47 Invalid area

Source: GroupWise engine; administration engine.
Explanation: Invalid BLOB area specified.
Possible Cause: ConsoleOne is unable to copy the GroupWise client view files from the software distribution directory into the post office directory structure.
Action: Make sure the software distribution directory has been created in your GroupWise system. See Software Directory Management in System in the GroupWise 2012 Administration Guide and GroupWise Software Distribution Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.

DB48 Cannot delete domain that has links

Source: GroupWise engine; administration engine.
Explanation: System link exists.
Possible Cause: You are trying to delete a domain that is specified as the link domain for an external system.
Action: Remove the external system or specify a different external domain as the link for the system. See Using Direct Links in Connecting to Other GroupWise Systems in the GroupWise 2012 Multi-System Administration Guide.
Possible Cause: You are trying to delete a domain that is set up for external system synchronization.
Action: Remove the external system synchronization entry, then delete the domain. See Using Direct Links in Connecting to Other GroupWise Systems in the GroupWise 2012 Multi-System Administration Guide.

DB49 Cannot use limited visibility distribution list as administrator

Source: GroupWise engine; administration engine.
Explanation: The selected distribution list cannot be used for the administrator because it is not visible to all users in your GroupWise system.
Action: Create a new distribution list to use as the administrator that contains only users that can be visible throughout your GroupWise system. For information about changing distribution list properties, see Creating and Managing Distribution Lists in Distribution Lists, Groups, and Organizational Roles in the GroupWise 2012 Administration Guide.
Action: Change the visibility of the selected distribution list to system so that all users can see it.

DB4A Cannot delete Internet domain name that is still referenced

Source: GroupWise engine; administration engine.
Explanation: The specified Internet domain name is being referenced in a system, domain, post office, or user.
Possible Cause: You are trying to delete an Internet domain record that is still in use.
Action: Change or delete the Internet domain association. See Configuring Internet Addressing in System in the GroupWise 2012 Administration Guide.

DB4C Database recovery required to update database structure

Source: GroupWise engine; administration engine.
Explanation: The database needs to be recovered.
Possible Cause: The database dictionaries (*.dc files) are newer than the current database, so a recover is needed to update the database.
Action: The admin thread of the POA or MTA should take care of this recovery automatically. If not, perform the recovery manually. See Recovering Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

DB4D Cannot delete default gateway

Source: GroupWise engine; administration engine.
Explanation: The gateway is used in default routing.
Possible Cause: You are trying to delete a GWIA object that is used as the default gateway for routing Internet messages.
Action: Select a different GWIA as the default gateway for Internet messages. See Configuring Internet Addressing in System in the GroupWise 2012 Administration Guide.

DB4E Cannot delete POA that performs message transfer

Source: GroupWise engine; administration engine.
Explanation: The POA is used as the message transfer recipient for its post office.
Possible Cause: You are trying to delete a a POA that is part of the TCP/IP link between the post office and domain through which messages arrive in the post office.
Action: Set up a different POA to provide the link to the domain MTA. See Using Client/Server Access to the Post Office in Post Office Agent in the GroupWise 2012 Administration Guide. After another POA has been set up to provide the link with the MTA, the original POA can be deleted.

DB4F External sync message from unknown system

Source: GroupWise engine; administration engine.
Explanation: An external synchronization message was received from a system that the local GroupWise system cannot identify.
Possible Cause: The local GroupWise system is not set up to synchronize with the system that sent the synchronization message.
Action: Configure the local GroupWise system for external synchronization with that system. See Exchanging Information Between Systems in Connecting to Other GroupWise Systems in the GroupWise 2012 Multi-System Administration Guide.
Possible Cause: The external synchronization record in the domain database has been damaged.
Action: Delete the external synchronization record. In ConsoleOne, click Tools > GroupWise System Operations > External System Synchronization. Select an external system, then click Delete > Close. Exit and restart the MTA and POA. Re-create the external synchronization record. See Exchanging Information Between Systems in Connecting to Other GroupWise Systems in the GroupWise 2012 Multi-System Administration Guide.