A.1 Error Messages

Error accessing VIM link

Source: GroupWise Notes Gateway; directory exchange and synchronization.
Possible Cause: Invalid VIM configuration; the Notes Gateway cannot access the link to the Notes system.
Action: Make sure that the Notes client is installed on the Windows server running the gateway.
Action: Make sure that the Notes/Domino server is running.

Error creating Address Book 'WPNAMES.NSF'. You are not authorized to perform that operation

Source: GroupWise Notes Gateway; initial startup.
Possible Cause: The Notes Gateway user is not provided with access rights to create databases on the Notes/Domino server that the gateway communicates with. Therefore, the gateway cannot start and cannot create the Notes Address Book where GroupWise user information will be stored.
Action: The Notes Gateway user should be provided with access rights to create databases on the Notes/Domino server that the gateway communicates with. See Providing Access to Notes Databases.

After giving access rights, restart the Notes/Domino server before starting the gateway.

Error opening character set translation file

Source: GroupWise Notes Gateway; startup.
Possible Cause: The gateway is not able to find the path to the domino and domino\data directories where the character set translation file is located.
Action: Make sure that the notes and notes\data directories are included in the system path on the server running the Notes client for the gateway. See Section 4.1, Adding the Notes Software Directory to the Path Variable.

Error processing attachment: attachment_name. You are not authorized to perform that operation

Source: GroupWise Notes Gateway; outbound messaging.
Possible Cause: The gateway is not able to process the attachment in a message addressed to a Notes user from GroupWise.
Action: None. The Gateway drops an attachment if it cannot process it and continues with processing of remaining part of the message.

Error processing Notes Address Book information; You are not authorized to use the remote console on the server

Source: GroupWise Notes Gateway; directory exchange
Possible Cause: The Notes Gateway user is not provided with the required access rights.
Action: Make sure that the Notes Gateway user is listed as an Administrator on the Notes/Domino server that the gateway communicates with. See Providing Access to the Notes/Domino Server.

Error reading character set translation file

Source: GroupWise Notes Gateway; startup.
Possible Cause: The gateway is not able to find the path to the domino and domino\data directories.
Action: Make sure that the notes and notes\data directories are included in the system path on the server running the Notes client for the gateway. See Section 4.1, Adding the Notes Software Directory to the Path Variable.

Error synchronizing modified Notes user to GroupWise; Unsupported datatype in Name and Address Book document

Source: GroupWise Notes Gateway; directory exchange and synchronization.
Possible Cause: The Notes Gateway user is not provided with the required access rights.
Action: Give access rights as described in Section 4.5, Setting Up Server and Database Access for the Notes Gateway User.

File object is truncated; file may have been damaged

Source: GroupWise Notes Gateway; general processing.
Possible Cause: The wpnames.nsf file on Notes/Domino server connected to GroupWise is damaged and the gateway is not able to find the People view in the Notes version of the GroupWise Address Book (wpnames.nsf).
Action: Replace the damaged wpnames.nsf database on the Notes/Domino server with the backup copy that is populated with GroupWise addresses.
Action: If you don’t have a backup copy of wpnames.nsf, follow the steps:

  1. Delete the damaged wpnames.nsf database on the Notes/Domino server connected to the gateway.

    If your Notes system is configured to replicate the wpnames.nsf file to multiple servers, delete it from all the Notes/Domino servers.

  2. Delete the 000.prc directory from the gateway home directory, after making copies of the log files if necessary.

  3. From the gateway root directory, copy the wpnames.nsf database to the domino\data directory on the Notes/Domino server that the Notes Gateway communicates with.

  4. Do a fresh directory exchange.

    If the Notes Gateway is running as an application, use Actions > Synchronize Directories at the Notes Gateway server console.

    If the Notes Gateway is running as a service, the directory exchange will occur during the regular nightly exchange, as described in Section 7.1, Enabling Directory Synchronization and Exchange.

  5. If required by your Notes system configuration, replicate wpnames.nsf to other Notes/Domino servers.

Foreign Domain missing or not configured in Name and Address Book

Source: GroupWise Notes Gateway; initialization.
Possible Cause: The gateway cannot find the foreign domain that represents the GroupWise system in the Notes system.
Action: Create a foreign domain for the GroupWise system on the Notes/Domino server. See Section 4.3, Defining the GroupWise System As a Notes Foreign Domain
Action: Make sure the Foreign ID field on the Identification page of the Notes Gateway object in ConsoleOne matches the Foreign Domain name for the GroupWise system in the Notes system. See Section 5.1, Providing Gateway Information and Section 4.3, Defining the GroupWise System As a Notes Foreign Domain.

Invalid name for foreign domain

Source: GroupWise Notes Gateway; directory exchange.
Possible Cause: Directory exchange has been enabled, but no foreign (non-GroupWise) domain has been specified in the Required Parameters page in ConsoleOne®.
Action: See Section 7.1, Enabling Directory Synchronization and Exchange

Invalid password

Source: GroupWise Notes Gateway; startup.
Possible Cause: The Notes ID password entered on the Required Parameters page of the Notes Gateway object in ConsoleOne is not correct.
Action: See Section 5.2, Setting Required Parameters.

Invalid password for Lotus Notes

Source: GroupWise Notes Gateway; initialization.
Possible Cause: The password specified on the Required Parameters page of the Notes Gateway object in ConsoleOne is not the same as the password for the Notes Gateway user.
Action: Make sure that the Notes ID Password field on the Required Parameters page of the Notes Gateway object in ConsoleOne is same as the Notes Gateway user password. See Section 5.2, Setting Required Parameters and Section 4.4, Registering the Notes Gateway As a Notes User.

Memory access error

Source: GroupWise Notes Gateway; general processing.
Possible Cause: The gateway requires more memory than is currently available.
Action: Free up memory on the Windows server.

Memory allocation error

Source: GroupWise Notes Gateway; general processing.
Possible Cause: The gateway requires more memory than is currently available.
Action: Free up memory on the Windows server.

No route to the gateway

Source: Notes client; sending a message to a GroupWise user through the Notes Gateway.
Explanation: When a Notes user tries to initiate a mail message to a GroupWise user, or if the Notes user replies to a GroupWise message, this message is displayed in the Notes client, and the message does not get delivered.
Possible Cause: The Notes/Domino Gateway Server Name field for the foreign domain document on the Notes/Domino server is not hierarchical.
Action: In the Foreign Domain Document in the Notes/Domino Administrator, edit the Gateway Server Name field so that it contains the full hierarchical name of the Notes/Domino server that routes the messages to the Notes Gateway. See Section 4.3, Defining the GroupWise System As a Notes Foreign Domain.

NOTES.INI file cannot be found on the search path pathname

Source: GroupWise Notes Gateway; initialization.
Possible Cause: The gateway cannot find the notes.ini file in the system path on the server running the gateway.
Action: Include the directory containing notes.ini in the system path. See Section 4.1, Adding the Notes Software Directory to the Path Variable.

No active recipients

Source: GroupWise Notes Gateway; outbound messaging.
Possible Cause: The message did not include the address of any active recipients.
Action: Select users from the GroupWise Address Book, rather than trying to type names in the To field.

Path not found error

Source: GroupWise Notes Gateway; startup.
Possible Cause: Invalid file path.
Action: Make sure the gateway has network access and rights to the GroupWise domain directory, Notes/Domino server, and any directories to which you have redirected files. See Section 3.2, Meeting Installation Prerequisites and Section 10.0, Using Notes Gateway Startup Switches.

Purging expired GroupWise directory information from Notes. Error purging GroupWise users from Notes. Entry not found in index

Source: GroupWise Notes Gateway; directory exchange.
Possible Cause: The Notes version of the GroupWise Address Book (wpnames.nsf) on the Notes/Domino server that the Notes Gateway communicates with is damaged and gateway is not able to find the People view in the wpnames.nsf file.
Action: Replace the damaged wpnames.nsf database on the Notes/Domino server with a backup copy of wpnames.nsf that is populated with GroupWise addresses.
Action: If you don’t have a backup copy of wpnames.nsf, follow the steps:

  1. Delete the damaged wpnames.nsf database on the Notes/Domino server connected to the gateway.

    If your Notes system is configured to replicate the wpnames.nsf file to multiple servers, delete it from all the Notes/Domino servers.

  2. Delete the 000.prc directory from the gateway home directory, after making copies of the log files if necessary.

  3. From the gateway root directory, copy the wpnames.nsf database to the domino\data directory on the Notes/Domino server that the Notes Gateway communicates with.

  4. Do a fresh directory exchange.

    If the Notes Gateway is running as an application, use Actions > Synchronize Directories at the Notes Gateway server console.

    If the Notes Gateway is running as a service, the directory exchange will occur during the regular nightly exchange, as described in Section 7.1, Enabling Directory Synchronization and Exchange.

  5. If required by your Notes system configuration, replicate wpnames.nsf to other Notes/Domino servers.

Retry count exceeded

Source: GroupWise Notes Gateway; server connection.
Possible Cause: The gateway’s attempt to reconnect to the GroupWise domain directory or Notes/Domino server has failed the number of times specified on the Optional Gateway Settings page in ConsoleOne.
Action: See Section 9.3, Automating Network Reattachment for more information about network reattachment.

Unable to locate GWWORK directory

Source: GroupWise Notes Gateway; general processing.
Possible Cause: The gateway cannot find the gwwork directory.
Action: Make sure that connections between the Notes Gateway, the GroupWise system, and the Notes system are up and functioning.
Action: Verify the path specified for the /work startup switch in the notes.cfg file.

Unable to replicate Lotus Notes Address Book information to GroupWise. Unsupported datatype in Name and Address Book document

Source: GroupWise Notes Gateway; directory exchange.
Possible Cause: The Notes Gateway user is not provided with the required access rights.
Action: Make sure that the Notes Gateway user has the required access rights. See Section 4.5, Setting Up Server and Database Access for the Notes Gateway User.

Undeliverable file moved to: path\filename

Source: GroupWise Notes Gateway; outbound messaging.
Possible Cause: The gateway repeatedly failed on an outbound message.
Action: The file was moved to the domain\wpgate\notes\gwprob directory. No action is required.

If you want to be notified when messages are moved to the gwprob directory, use the /badmsg startup switch and establish a postmaster, as described in Section 7.6, Establishing Gateway Administrators.

Unknown return value

Source: GroupWise Notes Gateway; general processing.
Possible Cause: An uncommon error occurred.
Action: Record the conditions under which you encountered the error. For the latest error message solutions, look up the error message in the Novell Support Knowledgebase.

VIM init error. Directory exchange and migrate utilities inactive

Source: GroupWise Notes Gateway; initialization.
Possible Cause: The gateway is running on the same server as the Notes/Domino server.
Action: For the gateway to perform directory synchronization and exchange with some versions of Notes, the gateway must run on a server other than the Notes/Domino server. See Section 2.0, Notes Gateway System Requirements.
Action: Make sure that the Notes ID Password field in ConsoleOne is same as the Notes Gateway user password. See Section 5.2, Setting Required Parameters and Section 4.4, Registering the Notes Gateway As a Notes User
Action: If the problem still persists, restart both the Notes/Domino server and the gateway.

You are not authorized to use the remote console on this server

Source: GroupWise Notes Gateway; initial startup.
Possible Cause: The Notes Gateway user is not listed as an administrator for the Notes/Domino server that the Notes Gateway communicates with
Action: Make the Notes Gateway user an administrator of the Notes/Domino server. See Providing Access to the Notes/Domino Server.