19.0 Remote Mode Windows Client Error Messages

A previous request to retrieve items has not been completed

Source: GroupWise Windows client; Remote mode.
Possible Cause: Because requests sent to the master GroupWise system are processed and then returned to your Remote mailbox, there are times when your Remote mailbox waits for responses from the master system. If this is the case, making a new request will duplicate the response that is returned from the previous request, resulting in wasted transmission time and, possibly, long-distance charges.
Action: If you need a new request because of differing date ranges or item filtering, click Yes to confirm that an additional request is required. Otherwise, click No so the outstanding request will be processed completely before another request is issued.

Cannot access your Master Mailbox

Source: GroupWise Windows client; Remote mode.
Possible Cause: For GroupWise to access your Master Mailbox remotely, GroupWise must give your Master Mailbox password to the master GroupWise system. Otherwise, access is denied without the appropriate password.
Action: Run GroupWise before leaving your office, then set a password on your Master Mailbox.
Action: If you are already away, have someone at your office set a password for you. Then, specify that password in Remote Options.
Action: The administrator can reset the password for a user in ConsoleOne. See Creating or Changing a Mailbox Password in Users in the GroupWise 8 Administration Guide. Notify the user of the new password.

Cannot find the post office

Source: GroupWise Windows client; Remote mode.
Possible Cause: The application is unable to use the provided network connection path. The path might be entered incorrectly or there might be network changes.
Action: Verify that the specified network connection path is valid and points to a GroupWise master system post office.
Action: Check the setting of the /ph startup switch used to start the GroupWise client.
Action: In ConsoleOne, right-click the Post Office object, then click Properties. Verify that the /ph switch setting matches the path specified on the post office Identification page. On the network, make sure the specified location still exists.

Cannot find the post office in the specified path

Source: GroupWise Windows client; Remote mode.
Possible Cause: The path to your post office, as specified in your network connection, doesn’t exist.
Action: If you know the path will be valid at a later time, or if you’re currently not logged on to your network, click No to accept the path. If you think the path is valid, click Yes to return to the Network Connection dialog box to edit or browse the path for accuracy. To check the path in ConsoleOne, right-click the Post Office, then click Properties. Verify the path specified on the post office Identification page. On the network, make sure the specified location still exists.

Cannot find your remote Mailbox folder

Source: GroupWise Windows client; Remote mode.
Possible Cause: The folder specified in Hit the Road or with the /ps startup switch on the command line doesn’t exist.
Action: Click Yes to let GroupWise create the folder for you, or click No, then modify the command line in Windows to include the existing directory.

Cannot log in to the gateway. Check the gateway login ID...

Source: GroupWise Windows client; Remote mode.
Possible Cause: The gateway login ID specified in the modem connection doesn’t match the login ID of the gateway the modem is dialing.
Action: Verify that the gateway login ID in the modem connection definition is correct. In ConsoleOne, double-click the Domain object where the gateway is located, then double-click the Gateway object. On the GroupWise client Profiles page, select the profile that is not working, then click Edit. Verify the login ID displayed in the Remote Profile dialog box. Correct it if necessary.

Cannot log in to the gateway. Check the gateway login password...

Source: GroupWise Windows client; Remote mode.
Possible Cause: The password to the gateway specified in the modem connection doesn’t match the gateway password the modem is dialing. The password might be entered incorrectly or there might be a password change.
Action: Verify that the gateway password in the modem connection definition is correct. In ConsoleOne, double-click the Domain object where the gateway is located, then double-click the Gateway object. On the GroupWise client Profiles page, select the profile that is not working, then click Edit. Verify the password displayed in the Remote Profile dialog box and correct it if necessary.

LDAP failure detected

Source: GroupWise Windows client; Remote mode.
Explanation: A GroupWise client user is using LDAP to authenticate to GroupWise but GroupWise is unable to authenticate.
Possible Cause: The LDAP server is down.
Action: Contact the administrator of the LDAP server. For more information about using LDAP for authentication, see Providing LDAP Authentication for GroupWise Users in Post Office Agent in the GroupWise 8 Administration Guide.

Required information is missing from the connection

Source: GroupWise Windows client; Remote mode.
Possible Cause: The connection definition is incomplete.
Action: Verify the required information:

Phone Number for Modem Connections: To check the phone number in ConsoleOne, double-click the Domain object where the gateway is located, then double-click the Gateway object. On the GroupWise client Profiles page, select the profile that is not working, then click Edit. Verify the phone number displayed in the Remote Profile dialog box.

Gateway Login ID for Modem Connections: To check the gateway login ID in ConsoleOne, double-click the Domain object where the gateway is located, then double-click the Gateway object. On the GroupWise client Profiles page, select the profile that is not working, then click Edit. Verify the login ID displayed in the Remote Profile dialog box.

Gateway Password for Modem Connections: To check the gateway password in ConsoleOne, double-click the Domain object where the gateway is located, then double-click the Gateway object. On the GroupWise client Profiles page, select the profile that is not working, then click Edit. Verify the password displayed in the Remote Profile dialog box.

Path to Post Office for Network Connections: To check the path to the post office in ConsoleOne, right-click the Post Office object, then click Properties. Verify the path displayed in the post office Identification page.

IP Address and Port for TCP/IP Connections: To check the IP address and port in ConsoleOne, double-click the Post Office object to connect to, right-click the POA object, then click Properties. In the Network Address box, click Edit. Verify the IP address and TCP port displayed in the Edit Network Address dialog box.

Some setup files are missing

Source: GroupWise Windows client; Remote mode.
Possible Cause: Some of the files needed to run the GroupWise client against your Remote mailbox are missing. These files might have been deleted inadvertently.
Action: Reinstall GroupWise on your computer. See Installing the GroupWise Clients in the GroupWise 8 Installation Guide.

The following information necessary to run GroupWise against...

Action: GroupWise Windows client; Remote mode.
Possible Cause: Hit the Road sets up your Remote mailbox with all the needed setup information. If you didn’t use Hit the Road, this message appears the first time you run the GroupWise client against your Remote mailbox after a new installation.
Action: Verify the necessary information:

  • Full Name

  • User ID

  • Master Mailbox Password

  • Domain

  • Post Office

  • Connection Definition

To check the first five items for a user in ConsoleOne, double-click the User object, then click GroupWise Account. The user’s full name, user ID, domain, and post office are displayed. The user’s GroupWise password can be reset if it has been forgotten.

To check the connection definition in ConsoleOne, double-click the Domain object where the gateway is located, then double-click the Gateway object. Verify the information displayed on the GroupWise client Profiles page.

The master GroupWise system is unable to process a request...

Source: GroupWise Windows client; Remote mode.
Possible Cause: Transmission errors damaged a response file from the master GroupWise system.
Action: Send another request to the master GroupWise system to receive a new response file.

The master GroupWise system is unable to process your current...

Source: GroupWise Windows client; Remote mode.
Possible Cause: Your master GroupWise system encountered an error while processing your requests. Your master system might have a problem.
Action: Send another request to the master GroupWise system.
Action: Record the conditions under which you encountered the error. For technical services, see Novell Support .

This item uses a custom view that was not retrieved...

Source: GroupWise Windows client; Remote mode.
Possible Cause: The view file of an item you want to read is too large to download as specified in the Retrieve Options dialog box.
Action: In your Remote mailbox, right-click the item, then click Retrieve Selected Items. Or, click Remote > Send/Retrieve > Advanced, then click Size Limits to increase the maximum size for attachments.

This transmission cannot be completed due to network problems

Source: GroupWise Windows client; Remote mode.
Possible Cause: This is caused by general failures in the network connection.
Action: Make sure your network software is operating correctly. You might also need to exit and restart Windows.
Action: Record the conditions under which you encountered the error. For technical services, see Novell Support .

Unable to create folder

Source: GroupWise Windows client; Remote mode.
Possible Cause: The folder specified in the Hit the Road Wizard or with the /ps startup switch cannot be created. Either you don’t have rights to the specified folder or the path includes more than one folder that does not exist.
Action: Modify the command line in Windows and include a valid path and folder in Hit the Road or with the /ps startup switch.

{filename.ext} could not be opened as a modem script file

Source: GroupWise Windows client; Remote mode.
Possible Cause: The file you specified to open is not in a script file format.
Action: If you want your script file to have the specified filename and overwrite the existing file, open the Modem Connection dialog box, then click Edit Script. Specify the script information, then click Save. Otherwise, select a different script filename

{filename.ext} failed to open

Source: GroupWise Windows client; Remote mode.
Possible Cause: This usually occurs because the script file is in use by another application or access to the file is restricted.
Action: Select a different filename, or open the Modem Connection dialog box. Click Edit Script, enter the script information, then click Save As.