12.0 GroupWise Administrator Snap-In to ConsoleOne Problems

Suggested solutions are provided for the following problems:

See also Administration Error Messages in GroupWise 2012 Troubleshooting 1: Error Messages.

ConsoleOne Can’t Access the Domain Database

Problem: You run ConsoleOne but cannot access the domain where you need to make changes.
Possible Cause: You have not yet authenticated to an eDirectory tree. On Linux, ConsoleOne does not automatically connect to the same domain database you were connected to during the previous ConsoleOne session.
Action: Manually connect. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide.
Possible Cause: You are not connected to the correct domain.
Action: Make sure you are connected to the correct domain. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide.
Possible Cause: You don’t have sufficient rights.
Action: Make sure you started ConsoleOne with sufficient rights to modify the Domain object.
Possible Cause: The domain database (wpdomain.db) is damaged.
Action: Rebuild the domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The domain database (wpdomain.db) is locked. Because ConsoleOne is designed to allow multiple administrators to access databases simultaneously, this theoretically should not happen, but occasionally it does.
Action: Exit ConsoleOne and restart.
Possible Cause: In a cross-platform environment where you are using Windows ConsoleOne to access a domain on Linux or Linux ConsoleOne to access a domain on Windows, the cross-platform connection is not set up correctly.
Action: Follow the applicable instructions in ConsoleOne in a Multiple-Platform Environment in System in the GroupWise 2012 Administration Guide.

You Aren’t Connected to the Right GroupWise Domain

Problem: You are attempting to modify a GroupWise object in ConsoleOne. A message informs you that you cannot perform the action because you are not connected to the correct GroupWise domain.
Action: Connect to the correct GroupWise domain. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide.

You Can’t Create or Delete GroupWise Objects

Problem: You are running ConsoleOne to create or delete a GroupWise object. However, you are unable to perform the action.
Possible Cause: You are not connected to the correct domain.
Action: Make sure you are connected to the correct domain. See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide.
Possible Cause: You do not have sufficient eDirectory rights.
Action: Make sure you started ConsoleOne with sufficient rights to the GroupWise object.
Possible Cause: You do not have sufficient file system rights.
Action: Make sure you have sufficient rights to the directory structure associated with the GroupWise domain or post office. See GroupWise Administrator Rights in Security Administration in the GroupWise 2012 Administration Guide.

Pending Operations Aren’t Completed

Problem: You have performed some actions on GroupWise objects in ConsoleOne. You see them listed in the Pending Operations dialog box, but they are not completed.
Action: Use the Retry option or the Undo option in the Pending Operations dialog box. See Pending Operations in System in the GroupWise 2012 Administration Guide.
Action: Check the MTA log files to see if the administrative message has been delivered. See Using MTA Log Files in Message Transfer Agent in the GroupWise 2012 Administration Guide.
Possible Cause: The MTA is not running.
Action: Make sure that the MTA is running and that no post offices or domains are closed. See Monitoring the MTA in Message Transfer Agent in the GroupWise 2012 Administration Guide.

Creation of a Secondary Domain Isn’t Completed

Problem: You are creating a secondary domain, but the process is interrupted before completion. For example, you click Cancel, or a power failure or hardware failure occurs. The result is that the new secondary domain appears in the GroupWise View but does not appear in the eDirectory tree.
Action: First, graft the new secondary domain into the eDirectory tree. See GW / eDirectory Association in System in the GroupWise 2012 Administration Guide. Next, select the secondary domain in the eDirectory tree, then rebuild it. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

Synchronization Isn’t Working

Problem: The MTA automatically synchronizes information throughout your GroupWise system. However, you notice that some GroupWise information is not being synchronized.
Action: Manually synchronize the information in ConsoleOne. See Synchronizing Database Information in Databases in the GroupWise 2012 Administration Guide.

You Can’t Move a User

Problem: You attempt to move a user from one post office to another, but the user does not appear in the destination post office.
Possible Cause: The agents aren’t functioning properly.
Action: Make sure the MTA and POA are configured correctly and are running. See Message Transfer Agent and Post Office Agent in the GroupWise 2012 Administration Guide.
Possible Cause: The move hasn’t been completed yet.
Action: If you are moving a user from one domain to another, view the pending operations to see if the operation is complete. See Pending Operations in System in the GroupWise 2012 Administration Guide. You can also use the Move User Status utility to watch the progress of user moves. See Monitoring User Move Status in Users in the GroupWise 2012 Administration Guide.
Possible Cause: The move failed.
Action: Check the MTA and POA log files to see if the process failed. If so, repeat the move.
Possible Cause: There is insufficient disk space in the destination post office.
Action: Verify that the post office to which you are moving the user has sufficient free disk space.

eDirectory Objects Aren’t Linking to GroupWise Objects

Problem: In ConsoleOne, eDirectory objects are not linking successfully to GroupWise objects.
Action: Record the conditions under which you encountered the problem. Seek assistance from Novell Support.