Novell GroupWise.

www.novell.com

6.5 TROUBLESHOOTING 1:

September 19, 2005 ERROR MESSAGES

Novell.

Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 1993-2005 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and in other countries.

Novell, Inc.

404 Wyman Street, Suite 500 Waltham, MA 02451

U.S.A.

www.novell.com

GroupWise 6.5 Troubleshooting 1: Error Messages September 19, 2005

Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see www.novell.com/documentation.

Novell Trademarks

ConsoleOne is a registered trademark of Novell, Inc in the United States and other countries. GroupWise is a registered trademark of Novell, Inc. in the United States and other countries. IPX is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc. in the United States and other countries. NDS is a registered trademark of Novell, Inc. in the United States and other countries.

NLM is a trademark of Novell, Inc.

Novell is a registered trademark of Novell, Inc. in the United States and other countries. OuickFinder is a trademark of Novell, Inc.

Third-Party Materials

All third-party trademarks are the property of their respective owners.

Contents

About This Guide

Part I GroupWise Engine Error Codes Oxxx Engine Error Codes 8xxx Engine Error Codes 9xxx Engine Error Codes Axxx Engine Error Codes Bxxx Engine Error Codes Cxxx Engine Error Codes Dxxx Engine Error Codes Exxx Engine Error Codes

Fxxx Engine Error Codes

Part II Agent Error Messages Post Office Agent Error Messages Message Transfer Agent Error Messages Internet Agent Error Messages WebAccess Agent Error Messages

Monitor Agent and Application Error Messages

Part Ill Administration Error Messages GroupWise Administrator Snap-In to ConsoleOne Error Messages GroupWise Check Error Codes GroupWise Time Stamp Utility Error Messages Part IV Client Error Messages Windows Client Error Messages Remote Windows Client Error Messages

Cross-Platform Client Error Messages

Part V Documentation Updates

September 19, 2005 (GroupWise 6.5 SP5). . : 2222 2m mn nn nn February 28, 2005 (GroupWise 6.5 SP4). . 2.2. .C nun nn nn August 23, 2004 (GroupWise 6.5 for Linux) . 2:22 2 22H nn nn nn

Contents

5

Oetober31,:2003% 214, Ar Mast ee ha al Ol Beer, Sach et ren Bede eye Ga oe Se als Sah ee July 1::2003:( SPA) 22 ek BPs hae Brake EA A Al kh Ak ee Rk M ja Se ek Soe AUR aes GroupWise Engine Error Codes... 2: 2 2 a

GroupWise 6.5 Troubleshooting 1: Error Messages

About This Guide

This Novell? Group Wise? 6.5 Troubleshooting 1 Guide guide covers error messages that appear in ConsoleOne*, Group Wise agents, and GroupWise clients, along with possible causes and suggested actions to resolve the problem. The guide is divided into the following sections:

+ “GroupWise Engine Error Codes” on page 9 + “Agent Error Messages” on page 155 + “Administration Error Messages” on page 209 + “Client Error Messages” on page 237 Other sources of troubleshooting assistance include: + Novell Support (http://support.novell.com) + Novell Support Knowledgebase (http://support.novell.com/search/kb_index.jsp) + GroupWise 6.x Support Forums (http://support.novell.com/forums/2gw.html)

+ GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)

Additional Documentation

For additional GroupWise documentation, see the following guides at the Novell GroupWise 6.5 documentation Web site (http://www.novell.com/documentation/lg/gw65):

* Installation Guide

+ Administration Guide

+ Multi-System Administration Guide * Interoperability Guide

+ GroupWise Client User Guides

Documentation Updates

For the most recent version ofthe GroupWise 6.5 Troubleshooting 1 Guide, visit the Novell GroupWise 6.5 documentation Web site (http://www.novell.com/documentation/lg/gw65).

Documentation Conventions

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (™, e etc.) denotes a Novell trademark. An asterisk denotes a third-party trademark.

About This Guide 7

User Comments

We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comment feature at the bottom of each page ofthe online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.

GroupWise 6.5 Troubleshooting 1: Error Messages

GroupWise Engine Error Codes

Group Wise engine code underlies all aspects of Group Wise*, including the Group Wise client, the agents, and the GroupWise snap-ins to ConsoleOne*. An engine error code can be displayed from any Group Wise component.

This part of Troubleshooting 1: Error Messages helps you resolve engine error codes in any Group Wise component.

+ “Oxxx Engine Error Codes” on page 11 + “8xxx Engine Error Codes” on page 13 + “Oxxx Engine Error Codes” on page 35 + “Axxx Engine Error Codes” on page 37 + “Bxxx Engine Error Codes” on page 45 + “Cxxx Engine Error Codes” on page 47 + “Dxxx Engine Error Codes” on page 69 + “Exxx Engine Error Codes” on page 123 + “Fxxx Engine Error Codes” on page 135 Other sources of assistance include: + Novell Support (http://support.novell.com) + Novell Support Knowledgebase (http://support.novell.com/search/kb index jsp) * GroupWise 6.x Support Forums (http://support.novell.com/forums/2gw.html)

+ GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)

GroupWise Engine Error Codes 9

10 GroupWise 6.5 Troubleshooting 1: Error Messages

0xxx Engine Error Codes

Range: 000x

“0002 Unexpected error” on page 11

“0003 Encryption password failed verification process” on page 11 “0004 Encryption password too long” on page 11

“0005 Unexpected error” on page 11

“0006 Unexpected error” on page 11

“0007 Unexpected error” on page 12

“0008 Unexpected error” on page 12

0002 Unexpected error Source: GroupWise engine; encryption.

Action: See “000x Unexpected error” on page 12.

0003 Encryption password failed verification process Source: GroupWise engine; encryption. Explanation: | Wrong encryption password.

Action: Enter the correct password.

0004 Encryption password too long Source: GroupWise engine; encryption. Explanation: Password too long.

Action: Reduce the password length.

0005 Unexpected error Source: GroupWise engine; encryption.

Action: See “000x Unexpected error” on page 12

0006 Unexpected error Source: GroupWise engine; encryption.

Action: See “000x Unexpected error” on page 12

Oxxx Engine Error Codes

11

0007 Unexpected error Source: GroupWise engine; encryption.

Action: See “000x Unexpected error” on page 12

0008 Unexpected error Source: GroupWise engine; encryption.

Action: See “000x Unexpected error” on page 12

000x Unexpected error Source: GroupWise engine; encryption. Explanation: An engine error has occurred for which GroupWise does not have a specific error message.

Action: Exit and then restart the GroupWise client.

12 GroupWise 6.5 Troubleshooting 1: Error Messages

8xxx Engine Error Codes

Range: + Blxx + 82xx + 85xx + 88xx + 89xx + 8Bxx + 8Cxx

+ 8Fxx

Range: 81xx

“8101 Memory error” on page 15

Range: 82xx

“8200 File I/O error” on page 16

“8201 Access to file denied” on page 16

“8202 Cannot access required file” on page 18 “8203 Cannot copy file or directory” on page 18 “8204 Disk full” on page 18

“8205 End of file” on page 19

“8206 Cannot open file” on page 19

“8207 Cannot locate file” on page 20

“8208 Cannot modify file” on page 20

“8209 Path not found” on page 20

“820B Path too long” on page 22

“820E Cannot lock file” on page 22

“8210 Cannot create path” on page 23

“8211 Cannot rename file” on page 24

“8212 Password incorrect” on page 24

“8214 Unsupported encryption level” on page 24 “8215 Path root error” on page 24

““8219 Cannot connect to remote network resource” on page 24

8xxx Engine Error Codes

13

Range: 85xx

“8502 Cannot initialize protocol” on page 25

“8503 Cannot connect to specified IP address” on page 25

“8509 Cannot access TCP/IP services” on page 25

“850F Connection no longer valid” on page 25

“8555 Port in use” on page 25

“8562 Client/server request packet contained invalid identifier” on page 26 “8563 Client/server request packet contained invalid identifier” on page 26 “8567 Data not in BCEF format” on page 26

“8568 HTTP port already in use” on page 27

“8569 SSL login required for this post office” on page 27

“8570 IMAP port already in use” on page 27

“8572 CAP port already in use” on page 27

“8573 LDAP port already in use” on page 27

Range: 88xx

“8809 Unexpected error” on page 28 “880B Unexpected error” on page 28 “880C Unexpected error” on page 28

Range: 89xx

“8901 Cannot use TCP/IP services” on page 28

“8902 Cannot load TCP/IP services” on page 28

“8903 Cannot use TCP/IP services” on page 28

“8906 Cannot use TCP/IP services” on page 28

“8907 Cannot use TCP/IP services” on page 29

“8908 Cannot connect to specified address” on page 29 “8909 Cannot use TCP/IP services” on page 29

“890A Cannot listen on specified port” on page 29 “890B Cannot accept incoming connection” on page 30 “890F Connection no longer valid” on page 30

“8910 Cannot read on connection” on page 30

“8911 Cannot write on connection” on page 30

“8912 Cannot read on connection; timed out” on page 31 “8913 Cannot write on connection; timed out” on page 31 “8916 Cannot use TCP/IP services” on page 31

“891A TCP/IP data is not ready for reading” on page 31 “891B No SSL certificate supplied” on page 31

“891C Bad SSL certificate” on page 32

“891D Bad SSL private key or password” on page 32

Range: 8Bxx

14 GroupWise 6.5 Troubleshooting 1: Error Messages

“8B02 Unexpected error” on page 32

Range: 8Cxx

“8C04 Unexpected error” on page 32 “8C09 Unexpected error” on page 33 “8COA Unexpected error” on page 33 “8C88 Unexpected error” on page 33

Range: 8Fxx

““8F03 Invalid configuration option” on page 33

8101 Memory error

Source: Explanation:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

GroupWise® engine; memory management. Memory function failure. Invalid memory handle.

If this error occurs in the NetWare® POA, there might be insufficient memory on the server for the POA to run. On the server where the POA runs, cache buffers should be around 60%. If cache buffers drop below 30%, there is not enough memory available.

Unload some other NLM programs or add memory to the server. In some cases, the insufficient memory condition is temporary. Group Wise automatically resends unsuccessful messages, so no action might be reguired.

If this error occurs in the NetWare POA, some current server parameters might be set too low. Increase the settings for the following NetWare® server parameters:

+ Minimum Packet Receive Buffers

+ Maximum Directory Cache Buffers

* Maximum Services Processes

Many factors influence what the proper settings should be for a particular server. Make sure each parameter is set to at least 1000 and increase settings from there as needed. For more information, see “Fine-Tuning Your NetWare POA Installation” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.

If this error occurs in the NetWare agents after updating your Group Wise system, you might not have updated the agents properly.

After exiting all the agents, unload the agent engine (gwenn4.nlm), then perform the update. See “Updating Your GroupWise 6.x System to Version 6.5” in “Update” in the GroupWise 6.5 Installation Guide.

If this error occurs when starting the GroupWise client, the user might have exceeded the limit of viewable 65,000 items per folder. Remember that Trash is considered a folder.

Delete items or move them to a different folder. Empty the Trash.

If this error occurs when manually addressing a message to multiple external recipients, the user might have typed one or more addresses incorrectly in such a way that the client exceeded available memory trying to resolve the erroneous external addresses. For example, leaving out at (@) signs can cause this problem.

8xxx Engine Error Codes 15

Action:

Possible Cause:

Action:

Possible Cause:

Action:

8200 File I/O error Source:

Explanation:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Users should select recipients from the Address Book whenever possible. Ifusers must type external addresses, care should be used to type the addresses correctly, especially in cases where the number of recipients is large.

If this error occurs in Group Wise Remote, Group Wise might not be installed correctly on the remote computer.

Reinstall Group Wise on the remote computer. See the platform-specific setup instructions for Group Wise Remote in “Group Wise Modes” in “Client” in the Group Wise 6.5 Administration Guide.

This error can occasionally be caused by damaged databases.

Check, and, if necessary, repair databases accessed by the user who is receiving the error. See “Maintaining User/Resource and Message Databases” in “Databases” in the Group Wise 6.5 Administration Guide.

Group Wise engine; file input/output.

Generic file I/O error. Any file I/O error that cannot be mapped to a more specific file I/O error message.

A GroupWise database has been damaged so as to be unrecognizable as a Group Wise database, for example, having a size of 0 KB or 2 GB.

For the locations of Group Wise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Restore the damaged database(s) from backup.

One or more of the GroupWise databases might have an invalid owner or no owner.

Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.

If this error occurs when users are trying to log in to GroupWise through the Group Wise Internet Agent from a POP3 mail client, the post office link information needed by the Group Wise Internet Agent might be incorrect.

Check the post office link set up for the GroupWise Internet Agent. In ConsoleOne, browse to and select the Domain object where the Internet Agent is installed. Right-click the GWIA object, then click Properties. Click Post Office Links, select the post office, then click Edit Link. Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server Access box. See “Internet Agent” in the GroupWise 6.5 Administration Guide.

8201 Access to file denied

Source:

Explanation:

Possible Cause:

Action:

Group Wise engine; file input/output.

Access denied. The program tried to access or open a file that did not have or allow sharing. The program might also have tried to create a file that already exists.

If this error occurs from the POA, the POA might not have access to a required file.

Start the POA including the /rights switch to determine the specific problem the POA is encountering. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.

16 GroupWise 6.5 Troubleshooting 1: Error Messages

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Action:

Possible Cause:

Ifthis error occurs when creating a post office, you might not be connected to the domain in which you are trying to create the post office.

Connect to the domain where you want the post office located. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.

If this error occurs when trying to access the account of a new user, some required files might be missing from the post office directory.

See “Post Office Directory” in “Directory Structure Diagrams” in Group Wise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Make sure all required files are present in the post office directory, especially the *.dc files, which are required for creating new user and message databases. If *.dc files are missing, copy them from another post office or from the po subdirectory ofthe software distribution directory.

Ifthis error occurs for a user who has previously been able to access GroupWise successfully, the user's Novell® eDirectory™ object might have become damaged.

Delete the user object from eDirectory, then recreate it. Do not delete the user's GroupWise account, because this would delete the user's mailbox as well.

If this error occurs when users exit the GroupWise client, the users might have their archive directory set to a location where they do not have sufficient rights.

In the GroupWise client, check the users’ path to the archive directory. Look up “archive, directory” in GroupWise client Help. Make sure users have sufficient rights to create and modify files there. Or have users change their archive directory to a location where they already have sufficient rights.

If this error occurs when users exit the GroupWise client, the user database (userxxx.db) might be damaged.

Check and, if necessary, repair the user database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.

Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.

If this error occurs when a user is running in Caching mode or Remote mode, the user’s local databases might be damaged.

Repair the user’s Caching or Remote mailbox. See “Tools for Analyzing and Correcting GroupWise Client Problems” in “Client” in the GroupWise 6.5 Administration Guide.

The GroupWise databases might be owned by an invalid user.

For the locations of GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.

Another program might already have the required file open with exclusive access.

Check the open/lock activity on GroupWise databases and other files. You might find that a backup program or virus scanner is holding the file open.

Use backup software that interacts properly with GroupWise file locking, as described in “Target Service Agents” in “Databases” in the GroupWise 6.5 Administration Guide.

The Group Wise client has been installed on the local drive, so the program can still run, but the network connection to the post office has been lost.

8xxx Engine Error Codes 17

Action:

When the network connection to the post office is reestablished the Group Wise client will function normally again. Rebootthe server. Ifthe post office still cannot be accessed, resolve those network problems.

8202 Cannot access reguired file

Source: Explanation: Possible Cause: Action: Possible Cause:

Action:

Group Wise engine; file input/output.

Bad file handle.

GroupWise is no longer able to access a reguired file.

Exit and then restart the Group Wise program that displayed the error. An invalid or old (closed) file handle was passed to a file I/O function.

Perform the action again. If the same error occurs, exit and then restart the Group Wise program that displayed the error.

8203 Cannot copy file or directory

Source: Explanation:

Possible Cause:

Action:

Possible Cause:

Action:

Action:

8204 Disk full Source: Explanation: Possible Cause: Action: Possible Cause:

Action:

Group Wise engine; file input/output. Copy error.

If this error occurs when trying to rebuild a post office database, the domain or the post office might not contain the correct files.

For the required contents of domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Make sure the post office you are trying to rebuild and the domain it belongs to contain the correct files (especially *.dc files).

If this error occurs in GroupWise Remote, there might be a problem with the structure or content of the Remote mailbox. For example, copying a GroupWise Remote installation from one laptop to another might introduce this problem.

Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.

Reinstall Group Wise Remote on the remote computer. See the platform-specific setup instructions for GroupWise Remote in “GroupWise Modes” in “Client” in the GroupWise 6.5 Administration Guide.

GroupWise engine; file input/output.

Disk full.

There is no space left on a disk when writing and/or creating a file.

Create space on disk by deleting unwanted or unnecessary files.

One or more of the GroupWise databases might have an invalid owner or no owner.

For the locations of GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in Group Wise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.

18 GroupWise 6.5 Troubleshooting 1: Error Messages

Possible Cause:

Action:

Action: Possible Cause:

Action:

Possible Cause:

Action:

8205 End of file

Source: Explanation: Possible Cause:

Action:

Possible Cause:

Action:

The owner of a GroupWise database has a space restriction on the volume where the database resides and that limit has been reached, so that the database cannot grow any larger.

Check the ownership ofthese databases and make sure that owner does not have disk space restrictions.

If disk space is available and database ownership is correct, the disk itself might need repair. If this error occurs from the POA, there might be a problem with its input queue.

Stop the POA. Rename the wpcsout directory in the post office. Restart the POA. This recreates the wpcsout directory structure for the post office. Ifthe POA now runs without the error, copy message files from the subdirectories of the original wpcsout structure into the corresponding subdirectories of the newly created wpcsout directory so the POA can process them.

If this error occurs on a server where the NetWare POA performs a substantial amount of indexing, temporary files that are created and deleted, but not purged, can build up on the server. Most of these temporary files are created and deleted in the index subdirectories of libraries and users' mailboxes, but some are placed at the root of the sys: volume on NetWare servers.

Purge deleted files from index subdirectories and the root of the sys: volume on the server where the problem is occurring.

GroupWise engine; file input/output. End of file was reached unexpectedly. The ngwguard.db file has been damaged.

Check the size of the ngwguard.rfl file (roll forward log). If it is less than 24 KB, it is considered empty. Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files. Delete the ngwguard.db file, then copy ngwguard.fbk to ngwguard.db. Be sure to copy it; do not rename it. See also “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.

One or more of the GroupWise databases might have an invalid owner or no owner. For the locations of critical GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.

Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.

8206 Cannot open file

Source: Explanation:

Possible Cause:

Action:

Possible Cause:

Action:

Group Wise engine; file input/output. File open error.

GroupWise cannot copy the specified file. During an explicit file copy function, failure to create the destination file will generate this error. If the destination file exists and is read only, this error might occur.

Check destination filename specified and ensure it is unique.

If this error occurs the first time a user tries to archive messages, the user might not have sufficient rights to the archive location.

Check the user's rights to the archive location. Grant the user the rights necessary to create the archive, or suggest a location where the user already has sufficient rights to create the archive.

8xxx Engine Error Codes 19

Possible Cause:

Action:

Possible Cause:

Action:

If this error occurs when updating the Group Wise client software, users might be running the client software.

Perform the update when no one is using the Group Wise client, or send a broadcast message asking all users to exit so you can update the software. Check the open/lock activity on the Group Wise program files.

If this error occurs from the POA, the POA might not have access to a required file.

Start the POA including the /rights switch to determine the specific problem the POA is encountering. See “Using POA Startup Switches” in “Post Office Agent” in the Group Wise 6.5 Administration Guide.

8207 Cannot locate file

Source: Explanation:

Possible Cause:

Possible Cause:

Action:

Action:

Group Wise engine; file input/output. File seek error.

A failure occurred when positioning file pointers during an explicit file copy function. Cannot open the specified file or directory.

If this error occurs when a specific user starts the Group Wise client, that user database (userxxx.db) might be damaged.

Check and, if necessary, repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.

Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.

8208 Cannot modify file

Source: Explanation:

Possible Cause:

Action:

Group Wise engine; file input/output. File modify error.

Cannot move or rename the file. An error occurred when renaming or moving a file to another location.

Check to see if another file with the same name exists (the filename must be unique). If so, rename that file, or move/rename the current file.

8209 Path not found

Source: Explanation: Possible Cause: Action: Possible Cause: Action:

Possible Cause:

Action:

Group Wise engine; file input/output.

Drive or path not found.

GroupWise cannot find the specified drive or path.

Use Browse to find the correct path.

The file you are trying to perform an action on does not exist. Enter a valid filename.

If this error occurs shortly after starting the Group Wise client, the path to the archive directory might not be correct.

In the GroupWise client, verify the path to the archive directory exists and that you have sufficient rights to create and modify files. Look up “archive, directory” in GroupWise client Help.

20 GroupWise 6.5 Troubleshooting 1: Error Messages

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Action:

Action:

Possible Cause:

Action:

Action:

Possible Cause:

Ifthe path to the archive directory is valid and this is the first time the user has tried to archive items, make sure the ngwguard.dc file exists in the post office. If it is missing, the databases required for archiving cannot be created. To restore the ngwguard.dc file if it is missing, copy it from the po directory in the software distribution directory to the post office directory. For the locations of these files, see “Post Office Directory” and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.

If this error occurs from the POA, the POA might not have access to a required file.

Start the POA including the /rights switch to determine the specific problem the POA is encountering. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.

If this error occurs from the MTA, the MTA might not have access to one or more of the post offices in the domain.

Verify the list of post offices belonging to the domain is correct. To view the list in ConsoleOne, browse to and right-click the Domain object, then click Properties. Click Group Wise > Post Offices. Check the properties of each Post office object to make sure that the post office directory for each post office exists. Make sure the post office path is correctly defined in the Post Office object. In ConsoleOne, right-click the Post Office object to display the post office Identification page. Also make sure the MTA has access to the post office.

If this error occurs when importing a document into GroupWise, there might be a problem with the library.

Check and, if necessary, fix the library. See “Maintaining Library Databases and Documents” in “Databases” in the GroupWise 6.5 Administration Guide. Then synchronize the library. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide.

If documents are being stored at the post office, make sure the docs subdirectory exists for the library.

If documents are being stored in a remote document storage area, make sure that the POA can access the location of the document storage area. In ConsoleOne, browse to and right-click the Library object, then click Properties. Click Group Wise > Storage Areas. Select a storage area, then click Edit. Check the location to make sure the required library directory structure exists. The structure of a remote document storage area is the same as the gwdms directory in the post office.

If this error occurs when trying to access a document in a library, the BLOB file containing the document might no longer exist.

You can determine what BLOB file the document was in from the GroupWise client. Right-click the document reference, then click Properties > Activity Log. If filenames are not currently displayed, right-click the menu bar, then click Filename to display the filename in the activity log. If the document is needed, you can restore the BLOB file from backup. See “Restoring Archived Documents” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.

If the document is not needed, you can delete it from the library to eliminate the error. Have the original sender of the message resend the attachment.

Some applications, such as Corel WordPerfect* 7, MS Word 95, and Excel 95, need a blank file stored in the c:/windows/shellnew directory. For example, Corel WordPerfect 7 needs a file named wordpfct.wpd to exist in the shellnew directory in order to create a new file when called from GroupWise. If this error occurs when creating a new document in the GroupWise client, the blank template file for the application might be missing.

8xxx Engine Error Codes 21

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

Check the shellnew directory for the existence of'a blank file for the application in use from GroupWise. Ifthe blank file is missing, start the application independently, then save an empty file under the reguired name in the shellnew directory. You should then be able to create new documents using that application from Group Wise.

A directory required for the normal flow of Group Wise messages could be missing.

See “Message Transfer/Storage Directories” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Verify the existence, ownership, and rights ofthe directories involved with message flow (domain, post office, and MTA local directory).

A required file or subdirectory could be missing from the directory structure of the user's post office.

See “Post Office Directory” in “Directory Structure Diagrams” in Group Wise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Verify the existence, ownership, and rights of the files and subdirectories in the user's post office. See “Group Wise User Rights” in “Security” in the GroupWise 6.5 Administration Guide.

If this error occurs when trying to add users to a post office or when trying to rebuild a user database, a reguired file might be missing from the post office directory.

Make sure the ngwguard.dc file exists in the post office directory. Ifit does not, copy it from the po subdirectory of your software distribution directory. For the specific location of this file, see “Post Office Directory” and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. New user databases (userxxx.db files) and message databases (msgnn.db files) cannot be created for new users if this file is missing.

820B Path too long

Source: Explanation:

Possible Cause:

Action:

Possible Cause:

Action:

GroupWise engine; file input/output. Path too long.

The file system cannot build or modify a path because the specified path contains too many characters.

Shorten the path name to a length that is valid for the operating system. If a filename will be appended to the path name, include the filename in the total length.

If this error occurs when you are trying to create anew GroupWise system, you might have mapped the drive where you are creating the Group Wise system to an object in the eDirectory tree, instead of to the correct volume on the server. For example, if you used Windows* Explorer or Network Neighborhood to map the drive, you might have browsed under the tree icon, rather than under the server icon.

Make sure you have mapped the drive where you are creating the GroupWise system to the correct volume on the server, not to an object in the eDirectory tree.

820E Cannot lock file

Source: Explanation: Possible Cause:

Action:

GroupWise engine; file input/output. File lock error. An attempt to lock a file failed.

Check to verify the file is not currently locked by another process that has terminated.

22 GroupWise 6.5 Troubleshooting 1: Error Messages

Possible Cause: Action: Action: Action: Possible Cause: Action:

Possible Cause:

Action:

Action:

You cannot open the specified file because another user might have the file open. Ask the other user to close the file.

Retry the action later.

If no valid user or process has the file open, delete the connection to unlock the file. You cannot open the specified file because you might not have rights to open the file. Obtain rights to the file.

Ifthis error occurs from the POA when rebuilding a database, a user might still have the database open. The POA reguires exclusive access to databases when rebuilding them.

Make sure no users associated with the database to be rebuilt are currently running the Group Wise client. If none are and the database is still locked, break the connection to unlock the file.

Exit, then restart the POA.

8210 Cannot create path

Source: Explanation:

Possible Cause:

Action:

Action:

Action:

Action:

Possible Cause:

Action:

Possible Cause:

Action:

GroupWise engine; file input/output. Path create failed. An attempt by the file system to create a unique file failed.

Ifthe error occurs as the user is exiting the GroupWise client, the client might be encountering a problem archiving messages. GroupWise might not be able to archive messages if the original sender's message database is damaged.

Manually archive any items that are old enough to be archived. You can use a filter to display only items that are older than a specified number of days. Look up “archive, item” and “filters, creating” in GroupWise client Help.

Iferrors occur during manual archiving, determine the user who sent the problem items. Ifthat user is not experiencing any problems with GroupWise, you can delete the problem items. Ifthe sending user is also having problems, check and, if necessary, repair the message database (msgnn.db) ofthe user who sent the problem items. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.

In the GroupWise client, open the archive, then use the Repair Mailbox feature to repair the archive. See “Enabling GroupWise Check in the Windows Client” in “Client” in the GroupWise 6.5 Administration Guide.

Run GWCheck on the archive. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. GWCheck provides additional repair options compared to the Repair Mailbox feature in the GroupWise client.

If this error occurs from the POA, the POA might not have access to a required location.

Start the POA including the /rights switch to determine the specific problem the POA is encountering. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.

On a NetWare server, deleted files must be purged to free up the disk space they occupy. Ifthe purge is not done, the deleted file space is not reused, causing insufficient disk space to create the path.

Purge deleted files to reclaim the disk space. Add more disk space to the volume. See “Managing Database Disk Space” in “Databases” in the GroupWise 6.5 Administration Guide.

8xxx Engine Error Codes 23

8211 Cannot rename file

Source: Explanation: Possible Cause: Action: Possible Cause:

Action:

GroupWise engine; file input/output.

File rename failed.

Attempt by the file system to rename a file failed.

Make sure the specified filename is unigue.

A directory required for the normal flow of Group Wise messages might be missing.

See “Message Transfer/Storage Directories” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Verify the existence, ownership, and rights ofthe directories involved with message flow (domain, post office, and MTA local directory).

8212 Password incorrect

Source: Explanation: Possible Cause:

Action:

GroupWise engine; file input/output. Invalid file password. The password entered by the user does not match the one stored in the encrypted file.

Reenter the password.

8214 Unsupported encryption level