A.1 Error Messages

Access to a recipient in the message has been denied while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The sender or the recipient has no access to the gateway.
Action: Verify that the sender or recipient has access to the gateway.

Configuration database not found

Source: GroupWise Exchange Gateway.
Explanation: The gateway home directory is not defined during the gateway startup.
Action: Run the gateway from the gateway home directory or specify the /home startup switch correctly in the gwexch.cfg file.

Conversion cleanup error while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to delete the message from the mts-out folder of the gateway mailbox after converting it to a GroupWise message.
Action: Verify that the Microsoft Exchange server is running.

Conversion error while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to spawn a thread to convert a message from Exchange to GroupWise format.
Possible Cause: Insufficient memory to perform the operation.
Possible Cause: The gateway server might have too many applications running.
Action: Stop some applications or move them to a different server.
Possible Cause: The gateway server might not meet the system memory requirements listed in Section 2.0, Exchange Gateway System Requirements.
Action: Install additional memory.

Conversion initialization error while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to find the configuration parameters for gwin.dll under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MAPI Conversions.
Action: Verify that this registry entry exists. If not, reinstall the gateway after uninstalling the previous instance of the gateway. See Section 7.4, Uninstalling the Exchange Gateway.

Conversion initialization error while processing outbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to find the configuration parameters for gwout.dll under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MAPI Conversions.
Action: Verify that this registry entry exists. If not, reinstall the gateway after uninstalling the previous instance of the gateway. See Section 7.4, Uninstalling the Exchange Gateway.

Could not connect to server share

Source: GroupWise Exchange Gateway.
Explanation: Permissions do not exist on the server for remote login during installation.
Action: Set appropriate permissions on the Windows server to enable remote login.
Explanation: Network problems are preventing access to the server share during installation.
Action: Check the network status.

Could not remove the file named gwproxydll.bak

Source: GroupWise Exchange Gateway.
Explanation: If you are installing a new version of the gateway while an older version of the gateway exists on the server, the Installation program tries to replace the gwproxy.dll, but the process cannot be completed because the existing version of gwproxy.dll is loaded into memory.
Action: Remove gwproxy.dll from memory. You can do this by stopping the System Attendant service and restarting it immediately. You can then click Retry. Do not click Retry before the services and their dependencies have started.

Error accessing Microsoft Exchange message property while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The message might be damaged.
Action: Send the message again.
Explanation: The Exchange server might not be running.
Action: Verify that the Microsoft Exchange server is running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

Error converting addresses between Microsoft Exchange and GroupWise formats while processing inbound or outbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to locate the Exchange address table to map addresses between Exchange and GroupWise formats.
Action: Verify that the GWISE address type is installed. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.
Action: Verify that the Exchange server is running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

Exchange server was down while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The Exchange server services are not running.
Action: Run the Exchange server services as described in Section 5.0, Configuring the Exchange Side of the Exchange Gateway, then restart the gateway. See Section 7.1, Starting the Exchange Gateway.

Export from Exchange reported problems while performing an inbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The export of user objects from Exchange has encountered a problem. The gateway is unable to obtain objects to exchange with the GroupWise system.
Action: Any corruption in the Exchange system needs to be identified and corrected.

Foreign domain information not available while performing an inbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The domain information is not available for the object being processed.
Possible Cause: The object does not have a GroupWise-type address or the address is invalid.
Action: Install the addressing components on the server. See Section 4.4, Installing the Exchange Gateway Addressing Components.

Foreign host information not available while performing an inbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The host information is not available for the object being processed.
Possible Cause: The object does not have a GroupWise-type address or the address is invalid.
Action: Install the addressing components on the server. See Section 4.4, Installing the Exchange Gateway Addressing Components.

Foreign user information not available while performing an inbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The user information is not available for the object being processed.
Possible Cause: The object does not have a GroupWise-type address or the address is invalid.
Action: Install the addressing components on the server. See Section 4.4, Installing the Exchange Gateway Addressing Components.
Action: Ensure that the address format for GWISE contains %m as a component. See Section 3.8, Selecting User Address Type and Format and Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

Gateway Object Identifier in the registry was invalid while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The Gateway Object Identifier in the registry no longer matches a gateway object in the Exchange Directory.
Action: Uninstall the old gateway and reinstall the gateway. See Section 7.4, Uninstalling the Exchange Gateway and Section 4.0, Installing the Exchange Gateway.

Ignoring recipient FirstName/LastName (Bad GroupWise proxy)

Source: GroupWise Exchange Gateway.
Explanation: Every Exchange recipient object has a GroupWise-type address generated for it when the gateway starts for the first time. If for some reason, this address could not be created, the user cannot be exchanged/synchronized with GroupWise because vital information is missing.
Action: View the application event log (Start > Programs > Administrative Tools > Event Viewer) for reasons as to why  the address was not created. Reasons could include invalid characters, absence of vital components such as the mailbox name, and so forth.
Explanation: A GroupWise-type address for the recipient object exists but the address has a domain name that is the same as that of the GroupWise primary domain name.
Action: If this is a problem with most of the objects, then you might need to change the address format for GWISE. See Determining Connections between Systems, Section 3.8, Selecting User Address Type and Format, and Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

Ignoring recipient (No FirstName/LastName) (Bad GroupWise proxy)

Source: GroupWise Exchange Gateway.
Explanation: Every Exchange recipient object has a GroupWise-type address generated for it when the gateway starts for the first time. If for some reason, this address could not be created, the user cannot be exchanged or synchronized with GroupWise because vital information is missing.
Action: View the application event log (Start > Programs > Administrative Tools > Event Viewer) for reasons as to why the address was not created. Reasons could include invalid characters, absence of vital components such as the mailbox name, and so forth.
Explanation: A GroupWise-type address for the recipient object exists but the address has a domain name that is the same as that of the GroupWise primary domain name.
Action: If this is a problem with most of the objects, then you might need to change the address format for GWISE. See Determining Connections between Systems, Section 3.8, Selecting User Address Type and Format, and Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

MAPI initialization failed while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The MAPI subsystem does not exist or is corrupted.
Action: Reinstall the MAPI subsystem.

Memory allocation failed while performing an inbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: Insufficient memory to perform the current operation.
Possible Cause: The gateway server might have too many applications running.
Action: Stop some applications or move them to a different server.
Possible Cause: The gateway server might not meet the system memory requirements listed in Section 2.0, Exchange Gateway System Requirements.
Action: Install additional memory.

Memory allocation failed while performing an outbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: Insufficient memory to perform the current operation.
Possible Cause: The gateway server might have too many applications running.
Action: Stop some applications or move them to a different server.
Possible Cause: The gateway server might not meet the system memory requirements listed in Section 2.0, Exchange Gateway System Requirements.
Action: Install additional memory.

Message server directories do not exist

Source: GroupWise Exchange Gateway.
Explanation: The MTA is not running or the gateway has not been configured on the GroupWise system.
Action: Start the MTA for the domain that the gateway belongs to. See the appropriate section of the GroupWise 7 Installation Guide for the platform of your MTA:
Action: Check the GroupWise configuration in ConsoleOne to ensure that the gateway object exists and is correctly configured. See Section 6.2, Providing Gateway Information.

No active recipients while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway could not determine who to route the message to.
Possible Cause: The message might be damaged.
Action: Resend the message.
Possible Cause: The sender or recipient might not have access to the gateway.
Action: Verify that sender or recipient has access to the gateway. See Section 8.4, Controlling Gateway Access.

No active recipients while processing outbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway could not determine who to route the message to.
Possible Cause: The message might be damaged.
Action: Resend the message.
Possible Cause: The sender or recipient might not have access to the gateway.
Action: Verify that sender or recipient has access to the gateway. See Section 8.4, Controlling Gateway Access.

Unable to access the Microsoft Exchange gateway mailbox

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to access the mts-in or mts-out folder in the gateway’s Mailbox in the Exchange system during inbound or outbound message processing.
Action: Verify that all Exchange server services are running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.
Action: Verify that the user logged into Windows has enough rights to the Exchange system and the Mailbox store. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

Unable to add data to correlation record while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway cannot write to the correlation database (gwcorr.db).
Possible Cause: There might not be enough disk space to perform the operation.
Action: Verify that there is enough free disk space to update the correlation database with new records.
Action: Make sure that the gateway server meets the disk space requirements listed in Section 2.0, Exchange Gateway System Requirements.
Possible Cause: The correlation database might be damaged.
Action: Delete the corr.db file, then restart the gateway. This results in lost message status information but re-creates a valid correlation database. For more information, see Section 8.7, Enabling Message Status for Sent Items.

Unable to commit correlation record while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway cannot write to the correlation database (gwcorr.db).
Possible Cause: There might not be enough disk space to perform the operation.
Action: Verify that there is enough free disk space to update the correlation database.
Action: Make sure that the gateway server meets the disk space requirements listed in Section 2.0, Exchange Gateway System Requirements.
Possible Cause: The correlation database might be damaged.
Action: Delete the corr.db file, then restart the gateway. This results in lost message status information but re-creates a valid correlation database. For more information, see Section 8.7, Enabling Message Status for Sent Items.

Unable to construct message while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to add a GroupWise field to the message.
Possible Cause: Insufficient memory to perform the operation.
Possible Cause: The gateway server might have too many applications running.
Action: Stop some applications or move them to a different server.
Possible Cause: The gateway server might not meet the system memory requirements listed in Section 2.0, Exchange Gateway System Requirements.
Action: Install additional memory.

Unable to convert a directory field while performing an inbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The gateway encountered a damaged field during conversion.
Action: None. The field might not have been exchanged.

Unable to convert attachment while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway failed to convert an attachment.
Possible Cause: The attachment might be damaged.
Action: Resend the message and attachment.
Possible Cause: There might not be enough disk space to perform the operation.
Action: Verify that there is enough free disk space to convert the attachment.
Action: Make sure that the gateway server meets the disk space requirements listed in Section 2.0, Exchange Gateway System Requirements.

Unable to convert attachment while processing outbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway failed to convert an attachment.
Possible Cause: The attachment might be damaged.
Action: Resend the message and attachment.
Possible Cause: There might not be enough disk space to perform the operation.
Action: Verify that there is enough free disk space to convert the attachment.
Action: Make sure that the gateway server meets the disk space requirements listed in Section 2.0, Exchange Gateway System Requirements.

Unable to convert message body while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway failed to convert an attachment.
Possible Cause: The attachment might be damaged.
Action: Resend the message and attachment.
Possible Cause: There might not be enough disk space to perform the operation.
Action: Verify that there is enough free disk space to convert the attachment.
Action: Make sure that the gateway server meets the disk space requirements listed in Section 2.0, Exchange Gateway System Requirements.

Unable to create directory

Source: GroupWise Exchange Gateway.
Explanation: The directory could not be created during the installation because of transient network problems.
Action: Click Retry in the pop-up.
Action: If the problem persists, manually reconnect to the server and try installing again.

Unable to create correlation record while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway cannot write to the correlation database (gwcorr.db).
Possible Cause: There might not be enough disk space to perform the operation.
Action: Verify that there is enough free disk space to update the correlation database.
Action: Make sure that the gateway server meets the disk space requirements listed in Section 2.0, Exchange Gateway System Requirements.
Possible Cause: The correlation database might be damaged.
Action: Delete the corr.db file, then restart the gateway. This results in lost message status information but re-creates a valid correlation database. For more information, see Section 8.7, Enabling Message Status for Sent Items.

Unable to create gateway profile while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: A profile with the same name might already exist.
Action: Restart the gateway so that a profile is created with a different name.

Unable to create message while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway cannot create a message file in its output queue.
Possible Cause: There might not be enough disk space to perform the operation.
Action: Verify that there is enough free disk space for the gateway to process message files in its queues (wpcsin and wpcsout).
Action: Make sure that the gateway server meets the disk space requirements listed in Section 2.0, Exchange Gateway System Requirements.
Possible Cause: The gateway might not have sufficient access rights to the gateway’s wpcsin directory.
Action: Verify that the gateway has sufficient access rights to the MTA input queue in the domain.

Unable to find gateway root directory while performing an outbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The gateway root directory (domain\wpgate\exchange) could not be found.
Action: Use the /home startup switch to specify the gateway root directory correctly in the gwexch.cfg file, then start the gateway. See Section 7.1, Starting the Exchange Gateway.

Unable to find inbound DLL while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The gateway requires gwin.dll but is unable to find it.
Action: Add the domain\wpgate\exchange directory to the path variable on the server where the Gateway runs.

At the gateway server:

  1. Right-click My Computer, then click Properties.

  2. Click Environment.

  3. In the User Variables for Administrator list, add the domain\wpgate\exchange directory to the end of the path variable value.

  4. Click Set, then click OK.

Unable to find outbound DLL while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The gateway requires gwout.dll but is unable to find it.
Action: Add the domain\wpgate\exchange directory to the path variable on the server where the Gateway runs.

At the gateway server:

  1. Right-click My Computer, then click Properties.

  2. Click Environment.

  3. In the User Variables for Administrator list, add the domain\wpgate\exchange to the end of the path variable value.

  4. Click Set, then click OK.

Unable to find primary domain name while performing an inbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The gateway was unable to find primary domain information while trying to add or detect the foreign domain.
Possible Cause: The situation is rare and the problem might be due to internal database damage.
Action: None.

Unable to generate accounting record while processing outbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway could not update the acct file.
Possible Cause: Insufficient memory to perform the operation.
Possible Cause: The gateway server might have too many applications running.
Action: Stop some applications or move them to a different server.
Possible Cause: The gateway server might not meet the system memory requirements listed in Section 2.0, Exchange Gateway System Requirements.
Action: Install additional memory.

Unable to generate status message while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to access the mts-in folder of the gateway mailbox in Microsoft Exchange.
Action: Verify that the Exchange server services are running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

Unable to get configuration information from registry while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to find the gateway’s Message Store in Exchange 5.5/2000/2003.
Possible Cause: The Exchange server services might not be running.
Action: Verify that all Exchange server services are running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.
Possible Cause: The user logged into Windows with insufficient rights to the Exchange system and the Mailbox store.
Action: Verify that the user logged into Windows has enough rights to the Exchange system and the Mailbox store. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

For Exchange 5.5, the user logged into Windows should be a member of the Administrators, Domain Admins, and Domain Users groups and should have administrator permissions to the Exchange Organization, Site, and Configuration container property pages of the Exchange Server.

For Exchange 2000/2003, the user logged into Windows should be member of the Administrators, Domain Admins, and Enterprise Admins group and should have enough rights to the Exchange system. See Section 5.2, Configuring Exchange 2000/2003.

Unable to get configuration information from Site Addressing object while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The Microsoft Exchange server services might not be running.
Action: Run the Microsoft Exchange server services as described in Section 5.0, Configuring the Exchange Side of the Exchange Gateway, then restart the gateway.

Unable to get configuration information from the MAPI Session while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to find the gateway’s Message Store in Microsoft Exchange during initialization.
Possible Cause: The Exchange server services might not be running.
Action: Verify that all Exchange server services are running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.
Possible Cause: The user logged into Windows with insufficient rights to the Exchange system and the Mailbox store.
Action: Verify that the user logged into Windows has enough rights to the Exchange system and the Mailbox store. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

For Exchange 5.5, the user logged into Windows should be a member of the Administrators, Domain Admins, and Domain Users groups and should have administrator permissions to the Exchange Organization, Site, and Configuration container property pages of the Exchange Server.

For Exchange 2000/2003, the user logged into Windows should be member of the Administrators, Domain Admins, and Enterprise Admins group and should have enough rights to the Exchange system. See Section 5.2, Configuring Exchange 2000/2003.

Unable to get MAPI Session while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: Too many sessions have been opened simultaneously.
Action: Close unused sessions and restart the gateway.

Unable to locate gateway home directory

Source: GroupWise Exchange Gateway.
Explanation: The gateway home directory not defined.
Action: Run the gateway from the gateway home directory or specify the /home startup switch correctly in the gwexch.cfg file.

Unable to map recipients while processing outbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway cannot identify the Exchange recipients the message is being sent to.
Possible Cause: Insufficient memory to perform the operation.
Possible Cause: The gateway server might have too many applications running.
Action: Stop some applications or move them to a different server.
Possible Cause: The gateway server might not meet the system memory requirements listed in Section 2.0, Exchange Gateway System Requirements.
Action: Install additional memory.

Unable to obtain directory handle while initializing directory operations

Source: GroupWise Exchange Gateway.
Explanation: The gateway was unable to obtain a DAPI session.
Action: Check the application event log (Start > Programs > Administrative Tools > Event Viewer) for details of the problem.

Unable to obtain directory handle while performing an outbound directory operation

Source: GroupWise Exchange Gateway.
Explanation: The gateway was unable to obtain a DAPI session
Action: Check the application event log (Start > Programs > Administrative Tools > Event Viewer) for details.

Unable to open the configuration file from the MAPI session

Source: GroupWise Exchange Gateway.
Explanation: The Exchange Gateway does not have sufficient rights to access the configuration file.
Action: Make sure that the Send As/Receive As rights on the Exchange message store are properly set, as described in Section 5.2, Configuring Exchange 2000/2003.

Unable to open the event log while initializing the gateway

Source: GroupWise Exchange Gateway.
Explanation: The EventLog service might not be running.
Action: Run the EventLog service and restart the gateway.

Unable to send Non-Delivery Report while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to access the mts-in folder in the gateway mailbox.
Action: Verify that the Microsoft Exchange server is running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.

Unable to set Microsoft Exchange message property while processing outbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway is unable to access the mts-in folder of the gateway mailbox in Microsoft Exchange.
Possible Cause: The Exchange server services might not be running.
Action: Verify that the Exchange server services are running. See Section 5.0, Configuring the Exchange Side of the Exchange Gateway.
Possible Cause: Insufficient memory to perform the operation.
Possible Cause: The gateway server might have too many applications running.
Action: Stop some applications or move them to a different server.
Possible Cause: The gateway server might not meet the system memory requirements listed in Section 2.0, Exchange Gateway System Requirements.
Action: Install additional memory.

Undeliverable message while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The GroupWise recipient address is invalid.
Action: Verify that the recipient exists in the GroupWise domain by looking up the user in the GroupWise Address Book.

Unknown message type while processing inbound message

Source: GroupWise Exchange Gateway.
Explanation: The gateway does not recognize the type of message file it has received from the Exchange system.
Possible Cause: The message file is damaged.
Action: Resend the message.
Possible Cause: The gateway is working with a Microsoft Exchange system version with which it is not compatible.
Action: See Section 2.0, Exchange Gateway System Requirements for a list of supported Exchange versions.