7.13 D50x Errors

D506 Security violation

Source: GroupWise engine; administration services.
Explanation: No authentication.
Possible Cause: An administration command was received that did not contain the proper authentication. This command might have originated outside the system, or the administration database (wpdomain.db or wphost.db) at the destination domain/post office has been replaced with an invalid version.
Action: Monitor and log the source of the command. Rebuild the domain or post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 8 Administration Guide.
Possible Cause: If this error occurs after a configuration change (for example, after changing which domain is the primary domain of your GroupWise system), the configuration change might not have replicated throughout the system in time to support a following change (for example, adding a user).
Action: Wait for replication to complete, then synchronize the object that caused the error. See Synchronizing Database Information in Databases in the GroupWise 8 Administration Guide.
Action: If you do not want to wait for replication to complete, you can rebuild the secondary domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 8 Administration Guide.
Possible Cause: If this error occurs when synchronizing domains or post offices, the databases might be damaged.
Action: Rebuild the databases, then synchronize the databases.

D507 Administrator record not found in database

Source: GroupWise engine; administration services.
Explanation: No administrator record found in database.
Possible Cause: An agent has attempted to send a message to the defined administrator; however, no administrator record was found in the database.
Action: To receive these messages, define an administrator for the domain. See Notifying the Domain Administrator in Message Transfer Agent in the GroupWise 8 Administration Guide.

D508 Transaction failed

Source: GroupWise engine; administration services.
Explanation: The transaction failed.
Possible Cause: The database was locked by another process and could not be updated.
Action: None. The message will be retried automatically.
Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner.
Action: For the locations of GroupWise databases in domains and post offices, see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
Possible Cause: The database has been damaged.
Action: If the ownership on the problem database is correct or you are unable to reset it, repair the database. See Maintaining Domain and Post Office Databases and Maintaining User/Resource and Message Databases in Databases in the GroupWise 8 Administration Guide.
Action: Run GWCheck. See Standalone Database Maintenance Programs in Databases in the GroupWise 8 Administration Guide.