6.0 WebAccess Agent Problems

This section suggests ways to fix the following problems:

GroupWise WebAccess Login Screen Does Not Appear

Explanation: When a user clicks a language button on the initial GroupWise WebAccess screen, the login screen does not appear.
Action: Make sure the commgr.cfg file is in the cgi-bin\gw8 of the Web Server. See Configuring the WebAccess Agent and Configuring the WebAccess Application in WebAccess in the GroupWise 8 Administration Guide.

If you are running the GroupWise WebAccess CGI Extension on a Novell Web server, make sure the srm.cfg file (in the web\config directory, where web is the Web server’s root directory) includes the following line:

loadablemodule /cgi-bin/gw8/gwweb.exe 
sys:web/cgi-bin/gw8/gwweb.nlm

where web is the Web server’s root directory and us is the language code. You must have an entry for each language you have installed. See Specifying a WebAccess Agent in the WebAccess URL in WebAccess in the GroupWise 8 Administration Guide.

Initial GroupWise WebAccess Screen Does Not Appear

Explanation: When a user enters the IP address or host name of the Web server, the initial GroupWise WebAccess page does not appear.
Action: Make sure the user is typing the correct IP address or hostname.

User is Logged Out of GroupWise WebAccess

Explanation: A GroupWise WebAccess user is automatically logged out of GroupWise WebAccess after a period of time.
Action: Each user has a timeout period after which he or she is logged out if he or she has not used GroupWise WebAccess. By default, this timeout period is 20 minutes. If necessary, you can modify the timeout setting. See Controlling User Access to Mailboxes in WebAccess in the GroupWise 8 Administration Guide.

User Receives Invalid User ID or Password Error Message

Explanation: When logging in to GroupWise WebAccess, a user receives an invalid user ID or invalid password error.
Action: Make sure the user entered his or her GroupWise user ID or full name (as defined in eDirectory and the GroupWise Address Book). Make sure the user has a password on his or her mailbox and that the password was entered correctly. Passwords are case sensitive.
Action: Make sure the user has access to GroupWise WebAccess. See Controlling User Access to Mailboxes in WebAccess in the GroupWise 8 Administration Guide.
Action: Make sure the WebAccess Agent has access to the user’s post office. See Managing Access to Post Offices in WebAccess in the GroupWise 8 Administration Guide.

WebAccess Agent Cannot Access a Post Office

Explanation: When processing a request from a user, the WebAccess Agent could not access the user’s post office.
Action: Make sure the link information for the post office is defined in ConsoleOne. See Managing Access to Post Offices in WebAccess in the GroupWise 8 Administration Guide.
Action: If the WebAccess Agent is using direct access to the post office, make sure it has a user account that provides access to the post office server and appropriate rights to the post office directory structure. See Domain and Post Office Access in Installing GroupWise WebAccess in the GroupWise 8 Installation Guide.
Action: If the WebAccess Agent is using client/server access to the post office, make sure TCP/IP is set up on the servers running the WebAccess Agent and the Post Office Agent. See Configuring the WebAccess Agent in WebAccess and Configuring the POA in Post Office Agent in the GroupWise 8 Administration Guide.
Action: Make sure login to the post office is not disabled. See Disabling a Post Office in Post Offices in the GroupWise 8 Administration Guide.

WebAccess Agent Doesn’t Create Log Files

Explanation: Disk logging is turned off by default, so the WebAccess Agent doesn’t automatically create log files.
Action: To enable and configure disk logging, see Configuring the WebAccess Agent in WebAccess in the GroupWise 8 Administration Guide.

WebAccess Agent Shuts Down Unexpectedly

Explanation: The WebAccess Agent (gwinter) has been running smoothly, but stops unexpectedly.
Action: If the WebAccess Agent is connecting to the post office directly, its processing can be disrupted by damaged databases just like the POA. To protect the stability of the WebAccess Agent, you can configure it to communicate with the POA by way of TCP/IP in client/server mode only, thus disallowing direct database accesses. See Modifying Links to Post Offices in WebAccess in the GroupWise 8 Administration Guide.

WebAccess Agent Does Not Start

Explanation: The WebAccess Agent does not start.
Action: Edit the strtweb.ncf or strtweb.bat file. Make sure the /home startup switch includes the complete path to domain\wpgate\webacc, where domain is the path to the domain directory and webacc is the gateway home directory.
Action: For the NetWare WebAccess Agent, make sure the /user and /password startup switches include the user ID and password for an account that gives the WebAccess Agent access to the domain directory.
Action: For the WebAccess Agent, make sure the server is connected to the server where the domain directory resides.

WebAccess Client Doesn’t Print Messages

Explanation: When printing a message in the Java version of the WebAccess client, only the header gets printed.
Explanation: The Java version of the WebAccess client uses an applet to display messages. Not all browsers can print applets.
Action: Run the HTML version of the WebAccess client to print messages.

WebAccess Users Want to Skip the Language Selection Page

Explanation: By default, the WebAccess client starts on a page where you choose your display language. On a system where only one language is available, this is an unnecessary step.
Action: After selecting the language, users can create a bookmark to the main WebAccess login page, so they never need to select the language again.
Action: Create a link directly to the WebAccess login page from some other page convenient to users.

Messages Viewed through WebAccess Client Could Be Viewed through Browser’s Cache

Explanation: Some users might consider it a security breach that messages originally viewed through the WebAccess client could be viewed later through their browser’s cache.
Explanation: The configuration of the browser cache and history list is each user’s responsibility.
Action: To set cache options in Mozilla Firefox, click Tools > Options > Privacy, then configure history and cache settings as needed to meet your security concerns.
Action: To set cache options in Internet Explorer, click View > Internet Options > Temporary Internet Files > Settings. Configure caching as needed to meet your security concerns. To control the length of your history list, click View > Internet Options > History, then set Days to Keep Pages in History as needed.