Source: GroupWise engine; database interface.
Explanation: User not found.
Possible Cause: The GroupWise user ID is not found in the post office database during login.
Action: If using startup switches, check the /ph switch to make sure the path to the post office is correct.
Action: Start the GroupWise client using the /@u or /la startup option to specify the GroupWise user ID.
Possible Cause: The user is not yet set up as a GroupWise user.
Action: Set the user up as a GroupWise user. See "Creating GroupWise Accounts" in "Users" in the GroupWise 6.5 Administration Guide.
Possible Cause: The user ID provided when the user was set up as a GroupWise user is not correct.
Action: Check the GroupWise user information in ConsoleOne. Make sure the common name (CN) of the user is provided. No additional information is needed in the Network ID field.
Possible Cause: User information has not replicated from the domain to the post office the user is trying to access.
Action: Wait for replication to take place. Make sure the MTA is running. Check the current scan cycles of the MTA. See "Adjusting MTA Polling of Input Queues in the Domain and Post Offices" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.
Action: Synchronize the user manually. See "Synchronizing Individual Users or Resources" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: The user is logging into a specific machine, rather than into the tree, causing the network ID information not to match.
Action: Log in to the tree rather than to a specific machine.
Possible Cause: If this error occurs when a user sends a message to a group, the group might contain user IDs that have been deleted from the system.
Action: Recreate the group, selecting users from the Address Book to ensure they are valid GroupWise users.
Possible Cause: If this error occurs when the user tries to delete users from the Subscribe to Notify window, the users might no longer exist in the GroupWise system.
Action: Check the Address Book to see if the users are still valid. If they are not, repair the user database (userxxx.db). See "Maintaining User/Resource and Message Databases" in "Databases" in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck on the post office database (wphost.db). See "Standalone Database Maintenance Programs" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: The user was not found in the post office database (wphost.db) during the parsing of To: line or group.
Action: Find the user in the To: line or Group. Either delete the user, or find the correct user ID in the Address Book.
Possible Cause: If this error occurs for all users in a post office, the post office database might be damaged.
Action: Rebuild the post office database (wphost.db). See "Rebuilding Domain or Post Office Databases" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs in systems where new users are added from multiple administrator machines, preferences might be set differently on different administrator machines.
Action: On each machine where users are added in ConsoleOne, click Tools > GroupWise System Operations > System Preferences. Make sure that the When Creating or Modifying Objects, For Network ID Use setting is the same on all machines. If some machines are set to Full Distinguished Name and some are set to Common Name, users will be set up differently depending on which machine they were created from, causing problems when users access GroupWise.
Possible Cause: If this error occurs only when using GroupWise Remote, the user ID might be specified incorrectly under Remote Options.
Action: Check the user ID specified in the GroupWise client. Look up "Remote, specifying user and system information" in GroupWise client Help. Make sure the user ID specified is correct.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .