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 Source: Explanation: Possible Cause: Action: Action: Group Wise engine; file input/output. Unsupported encryption level in file. Attempted to decrypt a file using an encryption level that is no longer supported. The file you are trying to open was created in a newer version of GroupWise and cannot be opened in an older version. Update to the latest version of GroupWise. To check the date of the Group Wise client you are using, click Help > About GroupWise. For technical services and file updates, see Novell Support (http://support.novell.com). Make sure the archive directory is not locked to an unusable location. In ConsoleOne, browse to and select the post office the user belongs to, then click Tools > GroupWise Utilities > Client Options > Environment > File Location. Check the setting in the Archive Directory field and whether or not it is locked. 8215 Path root error Source: Explanation: Possible Cause: Action: GroupWise engine; file input/output. At path root. If this error occurs as the GroupWise client starts, the user might have specified an archive path that does not exist. In the Group Wise client, verify the path to the archive directory exists and the user has sufficient rights to create and modify files there. Look up “archive, directory” in GroupWise client Help. 8219 Cannot connect to remote network resource Source: Explanation: Group Wise engine; file input/output. The POA cannot access a document storage area located on a remote server. 24 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Action: Action: Ifthis error occurs when running the Windows NT*/2000 agents, the user's user name and password on the server where the POA is running is different from their user name and password on the server where the document storage area is located. Use the same user name and password on the server where the POA is running and the server where the document storage area is located. Use the /user and /password switches to provide the login information for the server where the document storage area is located. See “Using POA Startup Switches” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object. 8502 Cannot initialize protocol Source: Explanation: Action: GroupWise engine; general communication. Cannot open protocol. See “8901 Cannot use TCP/IP services” on page 28. 8503 Cannot connect to specified IP address Source: Explanation: Action: GroupWise engine; general communication. Cannot open connection to specified address. See “8908 Cannot connect to specified address” on page 29. 8509 Cannot access TCP/IP services Source: Explanation: Possible Cause: Action: Action: GroupWise engine; general communication. TCP/IP bind failed. TCP/IP is not loaded on the server or is not loaded correctly. The TCP port is already in use by another process. Configure TCP/IP on the server correctly. If this error occurs on a NetWare server, make sure you have the latest version ofthe TCPIP NLM. For technical services and file updates, see Novell Support (http://support.novell.com). Reboot the server. 850F Connection no longer valid Source: Explanation: Possible Cause: Action: 8555 Port in use Source: Explanation: GroupWise engine; general communication. Connection was broken while in use. A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active. Exit and restart Group Wise when the machine is back up. GroupWise engine; general communication. Port inuse. 8xxx Engine Error Codes 25 Possible Cause: Action: Action: Possible Cause: Action: Possible Cause: Action: The POA defaults to TCP/IP communication, but the necessary TCP/IP information is not configured in ConsoleOne. The default TCP port used by the POA (1667) is in use by another program. To enable TCP/IP communication, configure the POA for ConsoleOne. See “Using Client/Server Access to the Post Office” in “Configuring the POA” in the GroupWise 6.5 Administration Guide. To disable TCP/IP communication, use the /notcpip switch when starting the POA. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. You are trying to run two POAs on the same server in client/server mode and you have not given them unique TCP port numbers. Check the TCP port for each POA object. See “Using Client/Server Access to the Post Office” in “Configuring the POA” in the GroupWise 6.5 Administration Guide. Change the TCP port for one ofthe POAS. You are trying to run two POAs on the same server in client/server mode and you haven't created a second POA object in ConsoleOne. In ConsoleOne, create a second POA object in the post office. Make sure you give it a unique TCP port number, different from what the first POA is using. Use the /name switch when starting each POA. You might want to create a separate startup file for each POA. See “Creating a POA Object in eDirectory” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. 8562 Client/server request packet contained invalid identifier Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: GroupWise engine; general communication. Client/server request packet contained an invalid identifier. Someone is trying to forge packets to break into the system. Check your system security. The server was shut down and brought back up while GroupWise clients were attached. Exit and restart the GroupWise clients. A TCP/IP packet was damaged in transit. None. 8563 Client/server request packet contained invalid identifier Source: Action: GroupWise engine; general communication. See “8562 Client/server request packet contained invalid identifier” on page 26 8567 Data not in BCEF format Source: Explanation: Possible Cause: Action: GroupWise engine; general communication. A packet of information received by an agent was not in the expected format. The packet was damaged somewhere between the source and the destination of the data. Use packet trace software to identify the source of the problem. It could be something like a bad network card or a problem with dial-up software. 26 GroupWise 6.5 Troubleshooting 1: Error Messages 8568 HTTP port already in use Source: Explanation: Possible Cause: Action: GroupWise engine; general communication. The HTTP port used by the POA for its Web console is already in use by another program on the server. You are trying to run two POAs on the same server and you have not given them unique HTTP port numbers. Check the HTTP port for each POA object. See “Setting Up the POA Web Console” in “Monitoring the POA” in the Group Wise 6.5 Administration Guide. Change the HTTP port for one ofthe POAS. 8569 SSL login required for this post office Source: Explanation: Possible Cause: Action: Action: GroupWise engine; general communication. Starting with GroupWise 6.5, the POA can be configured to require SSL connections with clients. Users of clients earlier than GroupWise 6.5 are trying to log in to the post office. Have users update their Group Wise client software. See “Updating Users’ Group Wise Clients” in “Update” in the GroupWise 6.5 Installation Guide. Configure the POA so that SSL is enabled rather than required, so that the older GroupWise clients can connect to the post office. See “Enhancing Post Office Security with SSL Connections to the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. 8570 IMAP port already in use Source: Explanation: Possible Cause: Action: GroupWise engine; general communication. The IMAP port used by the POA to communicate with IMAP e-mail clients is already in use by another program on the server. You are trying to run two POAs on the same server and you have not given them unique IMAP port numbers. Check the IMAP port for each POA object. See “Supporting IMAP Clients” in “Configuring the POA” in the GroupWise 6.5 Administration Guide. Change the IMAP port for one of the POAs. 8572 CAP port already in use Source: Explanation: Possible Cause: Action: GroupWise engine; general communication. The CAP port used by the POA to communicate with CAP clients is already in use by another program on the server. You are trying to run two POAs on the same server and you have not given them unique CAP port numbers. Check the CAP port for each POA object. See “Supporting CAP Clients” in “Configuring the POA” in the GroupWise 6.5 Administration Guide. Change the CAP port for one of the POAs. 8573 LDAP port already in use Source: Explanation: GroupWise engine; general communication. The LDAP port used by the POA is already in use by another program on the server. 8xxx Engine Error Codes 27 Possible Cause: You are trying to run two POAs on the same server and you have not given them unique LDAP port numbers. Action: Check the LDAP port for each POA object. See “Providing LDAP Authentication for Group Wise Users” in “Configuring the POA” in the Group Wise 6.5 Administration Guide. Change the LDAP port for one of the POAs. 8809 Unexpected error Source: GroupWise engine; inter- or intra-process communication Action: See “8xxx Unexpected error” on page 33. 880B Unexpected error Source: GroupWise engine; inter- or intra-process communication Action: See “8xxx Unexpected error” on page 33. 880C Unexpected error Source: GroupWise engine; inter- or intra-process communication Action: See “8xxx Unexpected error” on page 33. 8901 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Explanation: A fundamental TCP/IP call failed. Possible Cause: TCP/IP services couldn't be used. It is possible that TCP/IP is loaded incorrectly on this server. Possible Cause: Cannot load WINSOCK (Windows only), or the WINSOCK that did load is not supported. DNS is not loaded and you are trying to resolve DNS names. Action: Correctly configure TCP/IP on the server. 8902 Cannot load TCP/IP services Source: GroupWise engine; TCP/IP communication. Explanation: TCP/IP load failed because a required file was missing. Possible Cause: Unable to load TCP/IP services because one or more of the required files is missing: winsock.dll, wsoc32.dll, or tepip.nim. Action: Make sure that you have the required files, and that they are in the search path. Action: Correctly configure TCP/IP on the server. 8903 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Action: See “8901 Cannot use TCP/IP services” on page 28. 8906 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Action: See “8901 Cannot use TCP/IP services” on page 28. 28 GroupWise 6.5 Troubleshooting 1: Error Messages 8907 Cannot use TCP/IP services Source: Action: GroupWise engine; TCP/IP communication. See “8901 Cannot use TCP/IP services” on page 28. 8908 Cannot connect to specified address Source: Explanation: Possible Cause: Action: Action: Action: Possible Cause: Action: Action: Possible Cause: Action: Possible Cause: Action: Action: GroupWise engine; TCP/IP communication. Connection to the specified address failed. Unable to load TCP/IP services because one or more of the required files is missing: winsock.dll, wsoc32.dll, or tepip.nim. Make sure that you have the required files, and that they are in the search path. Correctly configure TCP/IP on the server. Make sure you are using a current IP stack. If you must use an older IP stack, try specifying the IP address in dotted numeric format (172.16.5.18), rather than as a host name that requires resolution, when setting the /ipa switch. When using direct mode rather than client/server, the GroupWise client still requires a valid winsock.dll to be available on the search path. Make sure a current, valid winsock.dll file is available on the workstation where the problem is occurring. The GroupWise client cannot establish a TCP/IP connection with the POA. Check the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Check the status ofthe POA server and the load on the network. If this error appears in the Message Transfer Status box ofthe POA, the MTA to which it is transferring messages is not running. Check the status ofthe MTA for the domain. Restart the MTA if necessary. If this error occurs from the GroupWise Internet Agent, the Internet Agent might not be able to establish a TCP/IP connection to the POA. Check the post office link set up for the Internet Agent. In ConsoleOne, click the domain where the Internet Agent is installed. Right-click the Internet Agent 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 box. Use a UNC or mapped link between the Internet Agent and the POA, rather than a TCP/IP link. 8909 Cannot use TCP/IP services Source: Action: GroupWise engine; TCP/IP communication. See “8901 Cannot use TCP/IP services” on page 28. 890A Cannot listen on specified port Source: Explanation: Possible Cause: GroupWise engine; TCP/IP communication. Listen failed. Unable to listen on the specified port. It is possible the specified port is in use by another process. For example, two GroupWise agents might be running on the same server where both were configured for the same port. 8xxx Engine Error Codes 29 Action: Verify the IP address and port provided in ConsoleOne are correct. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. 890B Cannot accept incoming connection Source: Explanation: Possible Cause: Action: GroupWise engine; TCP/IP communication. Acceptance failed. Hardware is overloaded. Upgrade the hardware. 890F Connection no longer valid Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: GroupWise engine; TCP/IP communication. Connection was broken while in use. A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active. Make sure the POA is running. Check the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. The GroupWise client is trying to use client/server mode to connect with the POA, but the POA is not set up for client/server processing. Configure the POA for client/server processing to match the needs ofthe client. See “Using Client/ Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages is not running. Check the status of the MTA for the domain. Restart the MTA if necessary. 8910 Cannot read on connection Source: Explanation: Action: Group Wise engine; TCP/IP communication. Read failed. Retry the operation. 8911 Cannot write on connection Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; TCP/IP communication. Cannot write on connection; the receiver isn't responding. A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active. Restart the Group Wise client. If this error occurs from the POA, the server where the POA runs might not have the most current version of TCP/IP. Install the latest TCP/IP. For technical services and file updates, see Novell Support (http:// support.novell.com). 30 GroupWise 6.5 Troubleshooting 1: Error Messages 8912 Cannot read on connection; timed out Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; TCP/IP communication. Cannot read on connection. The sender isn't writing the required information to Group Wise. A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active. Restart the Group Wise client when the machine is back up. If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages might be restarting. Check the status of the MTA for the domain. If the MTA is restarting, the message transfer status should change to Open after the restart is completed. 8913 Cannot write on connection; timed out Source: Explanation: Possible Cause: Action: GroupWise engine; TCP/IP communication. Cannot write on connection because it is no longer available. A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active. Restart the Group Wise client to reestablish the connection. 8916 Cannot use TCP/IP services Source: Explanation: Possible Cause: Possible Cause: Action: GroupWise engine; TCP/IP communication. No network error. TCP/IP services couldn't be used. It is possible that TCP/IP isn't loaded correctly on the server. Group Wise has encountered unusually long timeouts while trying to retrieve names from DNS. This probably occurred in Windows where the workstation is not connected to the network. Check the network connections for the workstation. 891A TCP/IP data is not ready for reading Source: Explanation: Possible Cause: Action: Action: GroupWise engine; TCP/IP communication. The TCP/IP connection is blocked. The data has been delayed by SSL encryption. None. TCP/IP services will continue to try to read the data. If the problem persists, check the line connection and the NIC card on the server. 891B No SSL certificate supplied Source: Explanation: Possible Cause: Action: GroupWise engine; TCP/IP communication. You have configured an agent for SSL, but the agent cannot locate the SSL certificate. In ConsoleOne, you enabled SSL on the Agent object Network Address page but did not provide the certificate information on the SSL Settings page. Finish configuring the agent for SSL. See the following sections of the GroupWise 6.5 Administration Guide, depending on which agent is encountering the problem: 8xxx Engine Error Codes 31 + “Enhancing Post Office Security with SSL Connections to the POA” in “Post Office Agent” + “Enhancing Domain Security with SSL Connections to the MTA” in “Message Transfer Agent” ¢ “Securing Internet Agent Connections Via SSL” in “Internet Agent” + “Securing WebAccess Agent Connections Via SSL” in “WebAccess” 891C Bad SSL certificate Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; TCP/IP communication. You have configured an agent for SSL, but the agent cannot read the SSL certificate. The SSL certificate is not in the reguired format. Obtain an SSL certificate in the proper format. See “Encryption and Certificates” in “Security” in the GroupWise 6.5 Administration Guide. The SSL certificate has been damaged. Replace the bad SSL certificate with a valid SSL certificate. 891D Bad SSL private key or password Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; TCP/IP communication. You have configured an agent for SSL, but the agent cannot read the private key file or the password. The SSL certificate that accompanies the private key file is not in the reguired format. Obtain an SSL certificate in the proper format. See “Encryption and Certificates” in “Security” in the Group Wise 6.5 Administration Guide. The password you provided on the agent object SSL Settings page in ConsoleOne does not match the password in the private key file. Correct the password information in ConsoleOne. See the following sections of the Group Wise 6.5 Administration Guide, depending on which agent is encountering the problem: + “Enhancing Post Office Security with SSL Connections to the POA” in “Post Office Agent” + “Enhancing Domain Security with SSL Connections to the MTA” in “Message Transfer Agent” ¢ “Securing Internet Agent Connections Via SSL” in “Internet Agent” + “Securing WebAccess Agent Connections Via SSL” in “WebAccess” 8B02 Unexpected error Source: Action: GroupWise engine; named memory. See “8xxx Unexpected error” on page 33. 8C04 Unexpected error Source: Action: Group Wise engine; process control. See “8xxx Unexpected error” on page 33. 32 GroupWise 6.5 Troubleshooting 1: Error Messages 8C09 Unexpected error Source: GroupWise engine; process control. Action: See “8xxx Unexpected error” on page 33. 8C0A Unexpected error Source: GroupWise engine; process control. Action: See “8xxx Unexpected error” on page 33. 8C88 Unexpected error Source: GroupWise engine; process control. Action: See “8xxx Unexpected error” on page 33. 8F03 Invalid configuration option Source: GroupWise engine; server toolkit. Explanation: Invalid startup switch specified when starting one of the agents. Action: Check the startup switches in use for the agent reporting the error. For lists of startup switches, see “Using POA Startup Switches” in “Post Office Agent” and “Using MTA Startup Switches” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. 8xxx Unexpected error Source: GroupWise engine. Explanation: An engine error has occurred for which Group Wise does not have a specific error message. Action: Exit and then restart the GroupWise client. 8xxx Engine Error Codes 33 34 GroupWise 6.5 Troubleshooting 1: Error Messages 9xxx Engine Error Codes Range: 90xx “9007 Client not set up for SSL” on page 35 “9008 Server does not support SSL” on page 35 Range: 92xx “920C Unexpected error” on page 36 Range: 93xx “9302 Unexpected error” on page 36 “9304 Unexpected error” on page 36 “9305 Unexpected error” on page 36 “9307 Unexpected error” on page 36 “9308 Unexpected error” on page 36 “9309 Unexpected error” on page 36 9007 Client not set up for SSL Source: Explanation: Possible Cause: Action: Action: Group Wise” engine; client/server. The POA is configured to require SSL communicate with the GroupWise client, but the client is not capable of SSL communication. SSL communication was introduced for the Group Wise client in GroupWise 6.5. You are running an older Group Wise client against a post office that has been updated to Group Wise 6.5 or higher. Update the client to GroupWise 6.5 or higher. Reconfigure the POA so that SSL is enabled rather than reguired. See “Enhancing Post Office Security with SSL Connections to the POA” in “Configuring the POA” in the Group Wise 6.5 Administration Guide. 9008 Server does not support SSL Source: Explanation: Possible Cause: Action: GroupWise engine; client/server. The Group Wise client is trying to use an SSL connection to the POA but the POA is not configured for SSL. The POA has been reconfigured without SSL since the client logged in. Restart the Group Wise client. It will not try to use SSL when it detects that the POA is not configured for SSL. 9xxx Engine Error Codes 35 920C Unexpected error Source: GroupWise engine; stream operations. Explanation: The GroupWise client cannot handle zero-byte file attachments. Possible Cause: The user tried to open a file attachment that was zero bytes in size. Action: Ignore the error. You do not need to restart the GroupWise client as the error message indicates. Action: Install Support Pack 5 or later to eliminate the error. 9302 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 36. 9304 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 36. 9305 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 36. 9307 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 36. 9308 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 36. 9309 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 36. 9xxx Unexpected error Source: GroupWise engine; loadable language resource. Explanation: An engine error has occurred for which GroupWise does not have a specific error message. Action: Exit and then restart the GroupWise client. 36 GroupWise 6.5 Troubleshooting 1: Error Messages Axxx Engine Error Codes Range: AOxx “A001 Unexpected error” on page 38 Range: A5xx “A501 Unexpected error” on page 38 “A502 Unexpected error” on page 38 “A504 Unexpected error” on page 38 Range: A6xx “A602 Unexpected error” on page 38 Range: A8xx “A801 Auto-Date formula too long” on page 38 “A802 Auto-Date formula has incorrect syntax” on page 39 “A803 Auto-Date formula not specified” on page 39 “A804 Auto-Date formula generates too many occurrences” on page 39 Range: AAxx “AAOI Unexpected error” on page 39 “AA02 Unexpected error” on page 39 “AA04 Unexpected error” on page 39 Range: ACxx “AC01 Zipped file has unsupported version number” on page 39 “AC02 Zipped file has incorrect format” on page 40 “AC03 Zipped file damaged” on page 40 Range: ADxx “AD01 No LDAP Support” on page 40 “AD06 The LDAP server information passed in is not valid” on page 40 “AD08 No username or password specified for logging into the LDAP server” on page 40 “AD09 The password for the LDAP user has expired” on page 40 Axxx Engine Error Codes 37 “ADOC No connection could be made to the LDAP server” on page 41 “AD10 SSL certificate was not found” on page 41 “AD11 SSL could not be initialized” on page 41 “AD20 The attribute specified in the reguest does not exist in the entry” on page 41 “AD21 The attribute specified in the request does not exist in the LDAP server’s schema” on page 42 “AD25 The object DN passed in is invalid because the target object cannot be found” on page 42 “AD29 The security (TLS versus plain) surrounding this reguest is not valid for the reguest” on page 42 “AD2E A dynamic memory allocation function failed when calling an LDAP function” on page 43 “AD2F The LDAP server cannot process the reguest because of server-defined restrictions” on page 43 A001 Unexpected error Source: Action: GroupWise® engine; sized string manipulation. See “Axxx Unexpected error” on page 43. A501 Unexpected error Source: Action: GroupWise engine; data array management. See “Axxx Unexpected error” on page 43. A502 Unexpected error Source: Action: Group Wise engine; data array management. See “Axxx Unexpected error” on page 43. A504 Unexpected error Source: Action: GroupWise engine; data array management. See “Axxx Unexpected error” on page 43. A602 Unexpected error Source: Action: GroupWise engine; data list management. See “Axxx Unexpected error” on page 43. A801 Auto-Date formula too long Source: Explanation: Possible Cause: Action: GroupWise engine; Auto-Date. Formula is too long. The user either entered formula text which was too large (4 KB is maximum), or the user selected from the graphical Auto-Date window and the generated formula was too large. Enter a shorter formula or reduce the number of days selected in the Auto-Date window. Look up “auto-dates” in GroupWise client Help. 38 GroupWise 6.5 Troubleshooting 1: Error Messages A802 Auto-Date formula has incorrect syntax Source: Explanation: Possible Cause: Action: GroupWise engine; Auto-Date. Formula is invalid. The user entered a formula which did not follow the correct syntax for Auto-Dates. Enter the correct formula by checking the syntax in your Auto-Date formula, or using the Dates tab to specify the dates you want to include. Look up “auto-dates” in Group Wise client Help. A803 Auto-Date formula not specified Source: Explanation: Possible Cause: Action: GroupWise engine; Auto-Date. Formula is empty. An attempt might have been made to switch from the Auto-Date formula mode to graphical mode; however, no formula was entered. Enter a formula in the formula window, or exit out and reenter the send window. This will generate a default formula, which will not give the above error. Look up “auto-dates” in Group Wise client Help. A804 Auto-Date formula generates too many occurrences Source: Explanation: Possible Cause: Action: GroupWise engine; Auto-Date. Auto-Date occurrences truncated. This error occurs when a user specifies a range for an Auto-Date that generates more than 365 occurrences. The first 365 instances will be generated. Ifthe user does not want to see the warning, the range over which the given Auto-Date spans needs to be shortened. The user can then regenerate additional occurrences for the same Auto-Date for another subrange of his or her original range. Look up “auto-dates” in Group Wise client Help. AA01 Unexpected error Source: Action: Group Wise engine; ASCII strings. See “Axxx Unexpected error” on page 43. AA02 Unexpected error Source: Action: Group Wise engine; ASCII strings. See “Axxx Unexpected error” on page 43. AA04 Unexpected error Source: Action: Group Wise engine; ASCII strings. See “Axxx Unexpected error” on page 43. AC01 Zipped file has unsupported version number Source: Explanation: Action: Group Wise engine; zip/compression. The zipped file has an unsupported version number. None. GroupWise cannot unzip the file. Axxx Engine Error Codes 39 AC02 Zipped file has incorrect format Source: Explanation: Action: Group Wise engine; zip/compression. The zipped file is not formatted correctly. None. GroupWise cannot unzip the file. AC03 Zipped file damaged Source: Explanation: Action: Group Wise engine; zip/compression. The zipped file failed a checksum test. None. GroupWise cannot unzip the file. AD01 No LDAP Support Source: Explanation: Possible Cause: Action: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Linux Group Wise Installation program requires that LDAP be running the on server during installation. This requirement is not being met. LDAP is not available on the Linux server where you are trying to install the Internet Agent or WebAccess Agent. Set up LDAP on the Linux server. Install the Internet Agent or WebAccess Agent on a Linux server where LDAP is already set up. AD06 The LDAP server information passed in is not valid Source: Explanation: Possible Cause: Action: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot communicate with the LDAP server because it is using incorrect information. Required LDAP information includes an IP address for the LDAP server, a port number, a username (in LDAP format) and a password. You have provided incorrect information. Review “Gathering LDAP Information (Linux Only)” in “Installing the GroupWise Internet Agent” or “LDAP Information (Linux Only)” in “Installing GroupWise WebAccess” in the GroupWise 6.5 Installation Guide for details about the information that the Installation program requires, then provide the correct information. Make sure that the LDAP Server object is correctly configured in ConsoleOne. AD08 No username or password specified for logging into the LDAP server Source: Explanation: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot log in to the LDAP server. You have not supplied a username or password. Supply the required information. AD09 The password for the LDAP user has expired Source: Explanation: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot log in to the LDAP server. 40 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Action: The password you supplied is no longer valid. Update the password information for the user on the LDAP Server object. Specify a user whose password has not expired. ADOC No connection could be made to the LDAP server Source: Explanation: Possible Cause: Action: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot communicate at all with the LDAP server you specified. The LDAP server is down. Check the status of the LDAP server and bring it up if necessary. Network problems are preventing communication between the Installation program and the LDAP server. Use the ping command to attempt to contact the LDAP server. If there is no response, resolve the network problem. AD10 SSL certificate was not found Source: Explanation: Possible Cause: Action: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux You selected to use an SSL connection with the LDAP server, but the Installation program cannot establish an SSL connection. You did not provide the correct SSL certificate file information to the Installation program. Review “Gathering LDAP Information (Linux Only)” in “Installing the Group Wise Internet Agent” or “LDAP Information (Linux Only)” in “Installing GroupWise WebAccess” in the GroupWise 6.5 Installation Guide for details about the SSL certificate file, then provide the correct information. The LDAP Server object in ConsoleOne is not properly configured for SSL. Make sure that the LDAP Server object is configured with the correct SSL certificate information in ConsoleOne. AD11 SSL could not be initialized Source: Explanation: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux You selected to use an SSL connection with the LDAP server, but the Installation program cannot establish an SSL connection. The LDAP Server object in ConsoleOne is not properly configured for SSL. Make sure that the LDAP Server object is configured with the correct SSL certificate information in ConsoleOne. AD20 The attribute specified in the request does not exist in the entry Source: Explanation: Possible Cause: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object but eDirectory is not providing the necessary attribute. The eDirectory schema has not yet been extended to accommodate GroupWise objects. Axxx Engine Error Codes 41 Action: Action: Extend the schema, as described in “Check eDirectory Schema (Linux Only)” in “System” in the Group Wise 6.5 Administration Guide. Run the Installation program again, as described in “Setting Up a Basic Group Wise System” in the Group Wise 6.5 Installation Guide AD21 The attribute specified in the reguest does not exist in the LDAP server's schema Source: Explanation: Possible Cause: Action: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object, but the LDAP server is not configured for the necessary attribute. The eDirectory schema has not yet been extended to accommodate GroupWise objects. Extend the schema, as described in “Check eDirectory Schema (Linux Only)” in “System” in the GroupWise 6.5 Administration Guide. Run the Installation program again, as described in “Setting Up a Basic GroupWise System” in the GroupWise 6.5 Installation Guide AD25 The object DN passed in is invalid because the target object cannot be found Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object, but the context you specified does not exist. You typed the context incorrectly. Browse to and select the context. You typed the context correctly, but the context does not exist. In ConsoleOne, create the container object you want to use, then browse to and select it in the Installation program. You typed an alias rather than a valid distinguished name. Check for the correct distinguished name in ConsoleOne. AD29 The security (TLS versus plain) surrounding this request is not valid for the request Source: Explanation: Possible Cause: Action: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object, but it does not have the necessary rights in eDirectory. The LDAP server is not configured to accept clear text passwords. In ConsoleOne, configure the LDAP Server object to accept clear text passwords. The LDAP server is not properly configured for SSL. Configure the LDAP server for SSL and make sure that the correct root certificate is used. AD2D The LDAP server is busy, unavailable, has timed out, or is down Source: Explanation: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program made initial contact with the LDAP server, but the LDAP server is no longer responding. Therefore, the Installation program cannot create an Agent object. 42 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Action: Resolve the problem with the LDAP server. Restart the LDAP server. AD2E A dynamic memory allocation function failed when calling an LDAP function Source: Explanation: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot function in the current environment. Insufficient memory. Stop some programs that are running on the server in order to free up some memory. AD2F The LDAP server cannot process the reguest because of server-defined restrictions Source: Explanation: Possible Cause: Possible Cause: Possible Cause: Possible Cause: Action: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot function in the current environment. The add entry request violates the server’s structure rules. The modify attribute request specifies attributes that users cannot modify. Password restrictions prevent the action. Connection restrictions prevent the action. Make sure that the user who is running the installation has sufficient rights to modify objects. Make sure that the user who is running the installation does not have any login restrictions. Axxx Unexpected error Source: Explanation: Action: GroupWise engine. An engine error has occurred for which GroupWise does not have a specific error message. Exit and then restart the GroupWise client. Axxx Engine Error Codes 43 44 GroupWise 6.5 Troubleshooting 1: Error Messages Bxxx Engine Error Codes Range: B3xx “B300 File transmission failed” on page 45 “B309 Port already in use” on page 45 “B30A No peer listening for connection” on page 45 B300 File transmission failed Source: Explanation: Possible Cause: Possible Cause: Action: GroupWise® engine; Message Transfer Protocol. The POA was not able to transfer a message file to the MTA. The MTA restarted during transmission of the file. The network experienced a slow-down, causing the MTA to time out while waiting for the rest of the file. None. The POA will automatically resend the message until the message is sent successfully. B309 Port already in use Source: Explanation: Possible Cause: Action: GroupWise engine; Message Transfer Protocol. The specified port is already in use. You have set up the POA to communicate with the MTA by way of TCP/IP but the TCP port you have chosen for the Message Transfer Protocol (MTP) link between them is already in use by another program. The message transfer port configured for the POA should be the same port number as the MTA is using to listen on. Make sure the MTA is set up correctly for TCP/IP links. Make sure the POA is configured with the message transfer port number matching the port number of the MTA. See “Changing the Link Protocol between the Post Office and the Domain” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. B30A No peer listening for connection Source: Explanation: Possible Cause: Action: Possible Cause: GroupWise engine; Message Transfer Protocol. The POA is attempting to communicate with the MTA by way of TCP/IP but the MTA is not responding. The MTA is not running. Start the MTA. The server where the MTA is running is overloaded so the MTA cannot respond to the POA in a timely manner. Bxxx Engine Error Codes 45 Action: Check the load on the server where the MTA is running. If necessary, stop some other programs or upgrade the server so adequate resources are available for the MTA to function properly. Possible Cause: The MTA is not configured for TCP/IP links. Action: Reconfigure the MTA for TCP/IP links. See “Changing the Link Protocol between Domains” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. 46 GroupWise 6.5 Troubleshooting 1: Error Messages Cxxx Engine Error Codes Range: + C00x + COlx + C02x + C03x + C04x + C05x + C06x + C07x + C08x Range: C00x “C003 Invalid object name has been passed in” on page 50 “C005 Invalid container has been selected for the GW objects” on page 50 “C006 Record, key, or key reference not found” on page 50 “C007 Database error” on page 51 “C008 Database error” on page 51 “C009 Database error” on page 51 “COOA Database error” on page 51 “C00B Database error” on page 51 “COOC Field type mismatch” on page 51 “C00D Database error” on page 51 “COOE Invalid index number” on page 51 “COOF Invalid password” on page 52 Range: C01x “C010 Database error” on page 52 “C011 Database being modified” on page 52 “C012 Database error” on page 53 “C013 Index full” on page 53 “C014 Database error” on page 53 “C015 Database error” on page 53 “C016 Database error” on page 53 Cxxx Engine Error Codes 47 “C017 Database error” on page 53 “C018 Database error” on page 53 “C019 Database error” on page 53 “COILA Database error” on page 53 “CO1B Database error” on page 54 “CO1C Database error” on page 54 “C01D Database error” on page 54 “COIE Database error” on page 54 “C01F Database error” on page 54 Range: C02x “C020 Database error” on page 54 “C021 Database error” on page 54 “C022 Database damaged” on page 54 “C023 Database error” on page 55 “C024 Database dictionary damaged” on page 55 “C026 Database error” on page 56 “C027 Database error” on page 56 “C028 Database error” on page 56 “C029 Database version unsupported” on page 56 “C02A Cannot access database dictionary file” on page 56 “C02B Database error” on page 56 “C02C Database error” on page 57 “C02D Database error” on page 57 “C02E Database error” on page 57 “C02F Database error” on page 57 Range: C03x “C032 Database error” on page 57 “C033 Database error” on page 57 “C034 Database error” on page 57 “C035 Database error” on page 57 “C037 Memory error” on page 57 “C038 Memory error” on page 57 “C03A Database requires newer version” on page 58 “C03B Database error” on page 58 “C03C Database error” on page 58 “C03D Unexpected error” on page 58 “C03F Database error” on page 58 Range: C04x “C040 Database error” on page 59 “C042 Database being modified” on page 59 “C043 Database error” on page 59 48 GroupWise 6.5 Troubleshooting 1: Error Messages “C044 Database error” on page 59 “C045 Unexpected error” on page 59 “C046 Database error” on page 59 “C047 Database error” on page 59 “C048 Unexpected error” on page 59 “C04A Unexpected error” on page 60 “C04B Database error” on page 60 “C04C Database error” on page 60 “C04D Memory error” on page 60 “C04E Database error” on page 60 “C04F Database checksum error” on page 60 Range: C05x “C050 Transaction aborted” on page 61 “C055 Unexpected error” on page 61 “C057 Database maintenance in progress; please exit” on page 61 “C059 Database file already exists” on page 62 “C05D Cannot open database file” on page 62 “COSE Unexpected error” on page 63 Range: C06x “C060 Unexpected error” on page 63 “C061 Unexpected error” on page 63 “C062 Unexpected error” on page 63 “C063 Database error” on page 63 “C066 Unexpected error” on page 63 “C067 Database error” on page 63 “C068 Database error” on page 64 “C069 Database error” on page 64 “C06A Database error” on page 64 “C06B Database error” on page 64 “C06C Database error” on page 64 “C06D Database error” on page 64 “C06E Unexpected error” on page 65 “C06F Store number mismatch” on page 65 Range: C07x “C071 Unexpected error” on page 65 “C072 Database error” on page 65 “C073 Unexpected error” on page 65 “C076 Unexpected error” on page 65 “C077 Unexpected error” on page 66 “C078 Unexpected error” on page 66 “C079 Unexpected error” on page 66 “C07A Unexpected error” on page 66 Cxxx Engine Error Codes 49 “C07B Database error” on page 66 “C07C Unexpected error” on page 66 “C07D Unexpected error” on page 66 “C07E Unexpected error” on page 66 “C07F Unexpected error” on page 66 Range: C08x “C080 Index not found” on page 66 “C081 Attachment missing” on page 67 C003 Invalid object name has been passed in Source: Explanation: Possible Cause: Action: Possible Cause: Action: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot create an Agent object with the name you specified. You did not specify the object name in the correct format. Use the following format: cn=username,ou=organizational_unit,o=organization An object by the name you specified already exists. Specify a different object name. C005 Invalid container has been selected for the GW objects Source: Explanation: Possible Cause: Action: C006 Record, key, Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot create an Agent object in the context you specified. The container object you specified was not a GroupWise Domain object, an Organizational Unit object, or an Organization object. Specify an appropriate container for the Agent object. or key reference not found Group Wise? engine; database services. A record or key was not found. In the Group Wise client, the user dragged away all the column headings. Restore the column headings. Right-click the bar where the column headings belong select some column headings such as From, Subject, Date, etc., from the drop-down list. If this error occurs when creating a post office, you might not be connected to the correct domain. If you try to create a post office in a secondary domain while connected to a different domain, you might not have sufficient rights to create the post office correctly. It might show up in the Group Wise View but not have an Novell® eDirectory™ object created for it. Connect to the secondary domain. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then graft the post office into the correct domain. See “GW / eDirectory Association” in “System” in the Group Wise 6.5 Administration Guide. If this error occurs when deleting a Library object representing a remote document storage area, the remote document storage area and its directory might have already been deleted. 50 GroupWise 6.5 Troubleshooting 1: Error Messages Action: In ConsoleOne®, display the GroupWise View. Right-click the Library object, then click Properties. Remove the path to the document storage area that no longer exists. Select Store Documents in Post Office, then click OK. Then delete the library object from the GroupWise View. C007 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page 67. C008 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67. C009 Database error Source: GroupWise engine; database services. Action: “C0xx Database error (Support assistance recommended)” on page 67. COOA Database error Source: GroupWise engine; database services. Action: “C0xx Database error (Support assistance recommended)” on page 67. C00B Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67. COOC Field type mismatch Source: GroupWise engine; database services. Explanation: Invalid field type in record being added. Possible Cause: If this error occurs when rebuilding a database, you might not be connected to the correct Group Wise system. Action: | Connect to the GroupWise system where the database is located. See “Select Domain” in “System” in the GroupWise 6.5 Administration Guide. Then perform the rebuild again. COOD Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. COOE Invalid index number Source: GroupWise engine; database services. Explanation: Invalid index number. Cxxx Engine Error Codes Possible Cause: Action: When converting a post office from 5.x to 6.x, the post office database (wphost.db) was missing in the post office. Restore the wphost.db file to the post office. Although the conversion does not actually use the old wphost.db file, it does attempt to access a file by that name in order to rename it. COOF Invalid password Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: Possible Cause: Action: Action: Group Wise engine; database services. Invalid password specified on database open. If this error occurs when a user has been moved to a different post office, the update to the post office database might not have completed. Move the user back to the original post office. Verify the user's password. Make sure the agents are running. Repeat the move user procedure. See “Moving GroupWise Accounts” in “Users” in the GroupWise 6.5 Administration Guide. If this error occurs when rebuilding a database, you might not be connected to the correct Group Wise system. Connect to the GroupWise system where the database is located. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then perform the rebuild again. The password information in the user database (userxxx.db) has been 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. If this error occurs in the Group Wise client when accessing archived messages, the archive might be damaged. 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 Group Wise 6.5 Administration Guide. Run GWCheck on the user's archive. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. C010 Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C011 Database being modified Source: Explanation: Possible Cause: Action: Group Wise engine; database services. Read encountered a modified block. A read operation encountered a block in the database that was being modified by another user. The read is unable to continue because transaction logging has been disabled for the database. Perform the operation again. This is a temporary condition and will generally correct itself. As a general rule, transaction logging should never be disabled on GroupWise databases. 52 GroupWise 6.5 Troubleshooting 1: Error Messages Action: If transaction logging has been disabled on the database, the only way to re-enable it is to rebuild the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/ Resource and Message Databases” in “Databases” in the Group Wise 6.5 Administration Guide. C012 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (general database repair strategies)” on page 67. C013 Index full Source: GroupWise engine; database services. Explanation: B-tree is full. Possible Cause: One of the B-trees in the database is full, which means either an index area or a record area in the database is full. Action: Delete some items from the mailbox (messages, trash, and so on) to free up space in the database. C014 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page 67. C015 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page 67. C016 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page 67. C017 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. C018 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. C019 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page 67. C01A Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. Cxxx Engine Error Codes 53 C01B Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (general database repair strategies)” on page 67. C01C Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C01D Database error Source: Action: Group Wise engine; database services. See “COxx Database error (Support assistance recommended)” on page 67. CO1E Database error Source: Action: GroupWise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C01F Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C020 Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C021 Database error Source: Action: Group Wise engine; database services. See “COxx Database error (Support assistance recommended)” on page 67. C022 Database damaged Source: Explanation: Action: Action: Possible Cause: Action: GroupWise engine; database services. The integrity of an item or structure in the database has been compromised. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. 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. 54 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Action: Possible Cause: Action: Action: Possible Cause: Action: Action: Action: Action: Possible Cause: Action: Action: See “Information Stored in the Post Office” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. If this error occurs when administering Group Wise, a domain database (wpdomain.db) or post office database (wphost.db) might be damaged. Validate and rebuild the domain or post office database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs from the POA after you have already rebuilt databases, restart the POA. 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“Setting Up GroupWise Modes and Accounts” in “Client” in the GroupWise 6.5 Administration Guide. The hard disk where the GroupWise databases are stored is damaged. Scan the hard disk for damage. Correct any problems with the hard disk. Repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If the database cannot be repaired, you must restore it from backup. See “Restoring GroupWise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide. In ConsoleOne®, you can set the proper user rights for all users in a post office or for an individual user. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide. If users are accessing a post office on a NetWare server through a Windows workstation using the Microsoft Gateway for NetWare, the gateway might not be providing adequate support for the number of users trying to access the post office. The Gateway Service for NetWare is not intended as a full service router for NetWare services. Use a more robust connection to the post office. Make sure you have all the latest NetWare patches installed. If using the Novell IPX™/IP gateway, make sure you have the latest version. C023 Database error Source: Action: Group Wise engine; database services. See “COxx Database error (Support assistance recommended)” on page 67. C024 Database dictionary damaged Source: Explanation: Possible Cause: Action: Group Wise engine; database services. Database dictionary compromised. The database dictionary (*.dc file) has been damaged. Make sure the ngwguard.dc file exists in the post office directory. If it does not, copy it from the po subdirectory of your software distribution directory. For the specific locations of this file, see Cxxx Engine Error Codes 55 “Post Office Directory” and “Software Distribution Directory” in “Directory Structure Diagrams” in Group Wise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Action: If this does not solve the problem, check and repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. C026 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. C027 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. C028 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. C029 Database version unsupported Source: GroupWise engine; database services. Explanation: | Unsupported version of database. Possible Cause: The database was created with an older version of GroupWise and cannot be opened by the current version. C02A Cannot access database dictionary file Source: GroupWise engine; database services. Explanation: Dictionary file access error. Possible Cause: In the GroupWise client, this error usually indicates there was a file I/O error accessing one of the database dictionary (*.dc) files which are used to create databases. Action: Check for any problems accessing the disk where the dictionary files reside. To determine the standard locations for the various database dictionary files, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Action: Make sure the ngwguard.dc file exists in the post office directory. If it does not, copy it from the po subdirectory of your software distribution directory. For the specific locations 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. Action: |The network might have gone down, or there might be some other transitory problem with the disk. The problem might go away simply by retrying. C02B Database error Source: GroupWise engine; database services. Action: See “COxx Database error (database dictionary file)” on page 68. 56 GroupWise 6.5 Troubleshooting 1: Error Messages C02C C02D C02E C02F C032 C033 C034 C035 C037 C038 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (database dictionary file)” on page 68. Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (database dictionary file)” on page 68. Database error Source: GroupWise engine; database services. Action: See “COxx Database error (database dictionary file)” on page 68. Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (database dictionary file)” on page 68. Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67. Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (general database repair strategies)” on page 67. Database error Source: GroupWise engine; database services. Action: See “COxx Database error (database dictionary file)” on page 68. Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67. Memory error Source: GroupWise engine; database services. Action: See “C0xx Memory error” on page 68. Memory error Source: GroupWise engine; database services. Action: See “COxx Memory error” on page 68. Cxxx Engine Error Codes 57 CO3A Database reguires newer version Source: Explanation: Possible Cause: Action: Group Wise engine; database services. Newer database error. GroupWise cannot access the database because it was created using a newer version of GroupWise. Make sure you are running a current version of the GroupWise software. For technical services and file updates, see Novell Support (http://support.novell.com). C03B Database error Source: Action: GroupWise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C03C Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (general database repair strategies)” on page 67. C03D Unexpected error Source: Action: Group Wise engine; database services. See “COxx Unexpected error” on page 68. C03F Database error Source: Explanation: Action: Action: Action: Action: Possible Cause: Action: Action: Group Wise engine; database services. GroupWise tried to open a file that could not be recognized as a valid GroupWise database. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. It can sometimes be helpful to run GWCheck multiple times, because as some errors are fixed, others are uncovered. If the damaged database cannot be repaired successfully, restore it from backup. If a damaged user database cannot be repaired or restored, it can be rebuilt. First, archive all personal appointments, tasks, and notes. Make a backup copy of the user database. Then, re-create the user database. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs each time the user exits the GroupWise client, the archive database might be damaged. 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 Group Wise 6.5 Administration Guide. Run GWCheck on the archive. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. 58 GroupWise 6.5 Troubleshooting 1: Error Messages C040 Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C042 Database being modified Source: Explanation: Possible Cause: Action: Action: GroupWise engine; database services. Read consistent view of record not available. A read operation encountered data that was being modified by another concurrent program. The read operation needs to see a prior version of the data; however, no prior version is available. This error should be handled by the GroupWise engine in most cases. If it finally does come through to the end user, it might indicate there is a problem with the database. However, it might also indicate the update activity on the database is currently very high. Generally, the error is transitory and will go away when the operation is retried. Make sure that others are not doing updates to the database, and retry the action. If the problem persists, validate and rebuild the database as necessary. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs on a message or user database, run GWCheck. See “Standalone Database Maintenance Programs” in the GroupWise 6.5 Administration Guide. C043 Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (general database repair strategies)” on page 67. C044 Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C045 Unexpected error Source: Action: Group Wise engine; database services. See “COxx Unexpected error” on page 68. C046 Database error Source: Action: GroupWise engine; database services. See “COxx Database error (general database repair strategies)” on page 67. C047 Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C048 Unexpected error Source: Action: Group Wise engine; database services. See “COxx Unexpected error” on page 68. Cxxx Engine Error Codes 59 CO4A Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C04B Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page 67. C04C Database error Source: GroupWise engine; database services. Action: See “COxx Database error (Support assistance recommended)” on page 67. C04D Memory error Source: GroupWise engine; database services. Action: See “C0xx Memory error” on page 68. C04E Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67. C04F Database checksum error Source: GroupWise engine; database services. Explanation: | Checksum error reading database. Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If the error returns, check for bad network cards on workstations from which the GroupWise client updates the databases. Action: If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. Possible Cause: The guardian database (ngwguard.db) is damaged. Action: Stop the POA. Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files. Delete the ngwguard.db file, then create a new, empty file named ngwguard.db. Start the POA. The POA will recognize the invalid ngwguard.db file and rebuild it from the ngwguard.fbk file, merging in transactions from the ngwguard.rfl file. See also “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Possible Cause: If this error occurs in GroupWise Remote, there might be a problem with the structure or content of the GroupWise Remote mailbox. 60 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Action: Possible Cause: Action: Delete the rofdata directory on the remote computer, then reguest all information from the master mailbox again. Reinstall Group Wise on the remote computer. See the platform-specific setup instructions for Group Wise Remote in “Setting Up GroupWise Modes and Accounts” in “Client” in the Group Wise 6.5 Administration Guide. If this error occurs in the Group Wise client next to the library name in the Find Results dialog box, the POA has not indexed the documents yet and might not be running. Start the POA. Check its indexing cycle. See “Regulating Indexing” in “Optimizing the POA” in the Group Wise 6.5 Administration Guide. After the documents have been indexed, the user will be able to use the Find feature in the GroupWise client to access them. C050 Transaction aborted Source: Explanation: Possible Cause: Action: GroupWise engine; database services. Attempted operation after critical error; transaction aborted. If this error occurs during domain-related activities, such as adding users or synchronizing domains, the domain database has been damaged. Check and, if necessary, repair the domain database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. C055 Unexpected error Source: Action: GroupWise engine; database services. See “COxx Unexpected error” on page 68. C057 Database maintenance in progress; please exit Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: GroupWise engine; database services. Maintenance in progress error. Database maintenance in progress (one of the databases is being recovered or rebuilt). Exit GroupWise and try again later. Depending on the size of the database, the maintenance could take from a few seconds to several minutes. Ifthe condition continues for an extended period and no GroupWise maintenance is being performed, 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 is holding the file open. If this error occurs constantly from the POA, a damaged message file might be blocking its processing. Check the priority subdirectories of the \wpcsout\ofs directory. See “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Move message files out to a temporary location until the damaged message file is eliminated. Undamaged message files can then be returned to their original subdirectories for processing. Cxxx Engine Error Codes 61 C059 Database file already exists Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise engine; database services. GroupWise attempted to create a user file, message file, or library file, but it could not because the file already existed. The ngwguard.db file has been renamed or deleted. When the POA detects the guardian database is missing, it creates a new one. The original guardian database contained a catalog of dependent databases (user, messages, library, and so on). The new guardian database lacks this catalog, so the POA attempts to create the needed dependent databases, but it cannot because they already exist. The POA does not overwrite existing files. See also “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Restore the original ngwguard.db file from backup. Ifthe original guardian database is not available, seek assistance. For technical services, see Novell Support (http://support.novell.com). A user was moved to a different post office and then moved back to the original post office. When the user is moved back to the original post office, the POA attempts to create the user database. If the user database was not deleted when the user was moved out, the POA cannot create the new user database. Delete the residual user database, then move the user back into the post office. See “Moving GroupWise Accounts” in “Users” in the GroupWise 6.5 Administration Guide. CO5D Cannot open database file 62 Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: GroupWise engine; database services. Store file not found. Cannot open a file associated with a multi-file database. For example, one of the dependent databases listed in ngwguard.db has been deleted. Restore the missing database from backup. If this error occurs when users send mail, the message database (msgnn.db) to which the users belong might be missing. If the message database cannot be restored from backup, perform a structural rebuild on the user(s) experiencing the problem. See “Performing a Structural Rebuild of a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. This will create a new, empty message database. Old messages will no longer be available to the affected users. If the message occurs for only a single user, that user's user database (userxxx.db) might be missing. If the user database cannot be restored from backup, re-create the user database. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. A library database is missing. Library databases must be restored from backup. They cannot be re-created. If this message occurs from the POA when starting its indexing cycle, a library directory structure might have been deleted without deleting the library object. Run GWCheck to perform a structural rebuild on the dmsh.db file in the post office, then verify the library. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. Then delete the library. See “Deleting a Library” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: If this message occurs from Group Wise Remote, a database might be missing from the Remote mailbox. Delete the rofdata directory on the remote computer, then reguest all information from the master mailbox again. CO5E Unexpected error Source: Action: Group Wise engine; database services. See “COxx Unexpected error” on page 68. C060 Unexpected error Source: Action: GroupWise engine; database services. See “COxx Unexpected error” on page 68. C061 Unexpected error Source: Action: GroupWise engine; database services. See “COxx Unexpected error” on page 68. C062 Unexpected error Source: Action: GroupWise engine; database services. See “C0xx Unexpected error” on page 68. C063 Database error Source: Action: Group Wise engine; database services. See “C0xx Database error (Support assistance recommended)” on page 67. C066 Unexpected error Source: Action: GroupWise engine; database services. See “C0xx Unexpected error” on page 68. C067 Database error Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Group Wise engine; database services. Invalid store number. The post office database (wphost.db) has been damaged. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs when a new user starts the GroupWise client, there might be a problem with the user database (userxxx.db). Perform a structural rebuild on the user. See “Performing a Structural Rebuild of a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. Reset the client options for that user. See “Resetting Client Options to Default Settings” in “Users” in the GroupWise 6.5 Administration Guide. Cxxx Engine Error Codes 63 Possible Cause: If this error occurs when new users exit Group Wise or try to archive items, the archive might be damaged. Action: Copy a new ngwguard.dc file from the po subdirectory of the software distribution directory into the post office directory. Delete new users’ archive directories, because they haven't been able to archive anything yet anyway. C068 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67 C069 Database error Source: GroupWise engine; database services. Action: See “COxx Database error (database dictionary file)” on page 68. COGA Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67. C06B Database error Source: GroupWise engine; database services. Explanation: Server not defined. Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid. Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. C06C Database error Source: GroupWise engine; database services. Explanation: Driver not found. Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid. Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. C06D Database error Source: GroupWise engine; database services. Explanation: Bad driver path. Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid. 64 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. CO6E Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. CO6F Store number mismatch Source: GroupWise engine; database services. Explanation: The store number in a database does not match the store number recorded in the store catalog. Possible Cause: The database is damaged. Action: Check and, if necessary, repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. Possible Cause: The database has been renamed to another valid database name (for example, renaming msg7.db to msg8.db). This circumstance could indicate tampering by a user attempting to access another user's messages. Action: Restore the original database. See “Restoring Group Wise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide. For information about databases in the post office, see “Post Office Directory” in “Directory Structure Diagrams” in Group Wise 6.5 Troubleshooting 3: Message Flow and Directory Structure. C071 Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C072 Database error Source: GroupWise engine; database services. Explanation: Guardian transaction active. Possible Cause: | Attempted to synchronize a dependent database dictionary file. However, the parent database dictionary file, which contains the definitions, was locked by another process. See “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Action: Retry the operation. C073 Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C076 Unexpected error Source: GroupWise engine; database services. Action: See “COxx Unexpected error” on page 68. Cxxx Engine Error Codes 65 C077 Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C078 Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C079 Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C07A Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C07B Database error Source: GroupWise engine; database services. Action: See “COxx Database error (general database repair strategies)” on page 67. C07C Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C07D Unexpected error Source: GroupWise engine; database services. Action: See “COxx Unexpected error” on page 68. C07E Unexpected error Source: GroupWise engine; database services. Action: See “C0Oxx Unexpected error” on page 68. C07F Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page 68. C080 Index not found Source: GroupWise engine; database services. Explanation: A QuickFinder™ index is missing. 66 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Action: Repair the indexes in the post office database (wphost.db). See “Rebuilding Database Indexes” in “Databases” in the Group Wise 6.5 Administration Guide. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. C081 Attachment missing Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: GroupWise engine; database services. An attachment file that should be available under offiles in the post office directory is missing. Files have been inadvertently removed from the offiles directory. Restore the files from backup. The post office has been copied to a new location and not all files in the offiles directory were copied successfully. Make sure that all files from the offiles directory are available in the new location. The user has archived the message with the attachment and the archive directory is not currently available. Check the current archive location. In the Group Wise client, click Tools > Options > Environment > File Location. A document in a GroupWise library is not accessible. Repair the library. See “Maintaining Library Databases and Documents” in “Databases” in the Group Wise 6.5 Administration Guide. Under the Analyze/Fix action, select the following: + Verify Library + Fix Document/Version/Element ¢ Verify Document Files + Validate All Document Security COxx Database error (Support assistance recommended) Source: Explanation: Action: GroupWise engine; database services. Generic database error. Typically, database errors in this group require assistance from Support. However, you might want to try to repair the database yourself before contacting Support. See “COxx Database error (general database repair strategies)” on page 67. COxx Database error (general database repair strategies) Source: Explanation: Action: Action: GroupWise engine; database services. Generic database error. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. Cxxx Engine Error Codes 67 Action: Ifthe damaged database cannot be repaired successfully, restore it from backup. Action: Ifa damaged user database cannot be repaired or restored, it can be rebuilt. First, archive all personal appointments, tasks, and notes. Make a backup copy of the user database. Then, re-create the user database. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. COxx Database error (database dictionary file) Source: GroupWise engine; database services. Explanation: Problem with a database dictionary (*.dc) file. Action: Copy the ngwguard.dc file from the po subdirectory of the software distribution directory to the post office directory. For the specific locations of the file, see “Software Distribution Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. COxx Memory error Source: GroupWise engine; database services. Explanation: | Generic memory error. Action: Retry the operation that caused the error. If it occurs again, restart GroupWise. If it occurs again, it might be necessary to run GroupWise in an environment with more available memory. COxx Unexpected error Source: GroupWise engine; database services. Explanation: An engine error has occurred for which GroupWise does not have a specific error message. Action: Exit and then restart the GroupWise client. 68 GroupWise 6.5 Troubleshooting 1: Error Messages Dxxx Engine Error Codes Dxxx Engine Error Codes 69 Range: D00x “D001 Unexpected error” on page 76 “D002 Folder not empty” on page 76 “D004 Database error” on page 76 “D005 Settings field list is not valid” on page 76 “D006 Unexpected error” on page 76 “D009 Cannot use group name in distribution list” on page 76 “DOOA Syntax error in address” on page 77 “DOOB Missing closing quotation mark (")” on page 77 “DOOC Unexpected error” on page 77 “DOOD Cannot match parentheses” on page 77 “DOOE Distribution list contains nested groups” on page 77 “DOOF Remote mail error” on page 78 Range: D01x “D017 Too many users in address” on page 78 “D018 Unexpected error” on page 78 “D019 Password incorrect” on page 78 “DOIA Password too long” on page 78 “DOIB Access to GroupWise denied” on page 79 “D01C Remote mail error” on page 79 “DO1E Cannot execute rule” on page 79 “DOIF Archive path not specified” on page 79 Range: D02x “D020 Rule caused infinite loop” on page 79 “D021 Cannot deliver message” on page 80 “D023 User ID expired” on page 80 “D024 Rule cannot forward, reply, accept, or delegate personal item” on page 80 “D025 Users not specified” on page 80 “D026 Missing opening brace in distribution list” on page 80 “D027 Missing closing brace in distribution list” on page 81 “D028 Lost attachment” on page 81 “D029 Recipient not specified” on page 81 “D02A Name for group not specified” on page 81 “D02F Database error” on page 81 Range: D03x “D030 Missing post office number for status” on page 82 “D039 Missing attachment” on page 82 “D03F Database error” on page 82 70 GroupWise 6.5 Troubleshooting 1: Error Messages Range: D04x “D040 Cannot delete folder used in rule” on page 82 “D041 No recipients in post office” on page 82 “D043 Inconsistent distribution list” on page 83 “D044 Auto-rebuild disabled” on page 83 “D049 Error reported from Novell NDS” on page 83 “DO4A Unexpected error” on page 83 “D04B Unexpected error” on page 84 “DO4F Unexpected error” on page 84 Range: D05x “D050 Cannot connect to specified post office” on page 84 “D051 Cannot connect to specified post office” on page 84 “D054 Cannot connect to specified post office” on page 84 “D055 Cannot connect to specified post office” on page 85 “D057 Cannot connect to any post office” on page 85 “D058 Version mismatch on Group Wise client/POA/post office” on page 85 “D059 Recursion limit exceeded during delivery” on page 85 “DOSA User database access denied” on page 86 “DOSD Post office intruder lockout is enforced” on page 86 “DOSE Message size exceeds limit” on page 87 “DOSF Box size limit exceeded” on page 87 Range: D06x “D060 Message size exceeds threshold limit” on page 87 “D061 Status denied to external Internet user” on page 87 “D062 Busy Search denied for external Internet user” on page 88 “D065 Attempt to purge item that has not been backed up” on page 88 “D066 Attempt to purge an item from a user that has not been backed up” on page 88 “D069 Attempt to open invalid backup location” on page 88 “D06B LDAP failure detected” on page 89 “DO6E Lockout of older GroupWise clients being enforced” on page 89 “D06F This GroupWise client doesn't match the user's license” on page 89 Range: D07x “D071 LDAP authentication failed because the password has expired” on page 89 “D072 Changing the LDAP password has been disabled” on page 89 “D073 Attempting to log in trusted without SSL” on page 89 “D074 Invalid key for trusted application” on page 90 “D075 Invalid IP address for trusted application” on page 90 “D076 Missing trusted application name” on page 90 “D077 The problem file is being rebuilt” on page 90 Dxxx Engine Error Codes 71 “D078 LDAP SSL key file not found” on page 91 “D07F Unexpected error” on page 91 Range: D10x “D101 User not found” on page 91 “D102 Ambiguous user ID” on page 92 “D103 Post office not found during login” on page 92 “D104 Ambiguous post office” on page 93 “D105 Directory Services data missing” on page 93 “D106 Database error” on page 93 “D107 Record not found” on page 93 “D108 Unexpected error” on page 94 “D109 Bad parameter” on page 94 “D10A Unexpected error” on page 94 “D10B Database needs to be repaired” on page 94 “D10C Unexpected error” on page 94 “D10D Cannot open any more mailboxes” on page 95 Range: D11x “D110 Unexpected error” on page 95 “D113 Open database maximum exceeded” on page 95 “D114 Group not found” on page 95 “D115 Database error” on page 95 “D116 File not database” on page 95 “D117 Group Wise version too old” on page 96 “D118 Database error” on page 96 “D119 Unexpected error” on page 96 “D11B Too many items in mailbox” on page 96 “D11C Cannot use group name” on page 97 “D11D GroupWise version newer than database” on page 97 Range: D12x “D124 Access to user denied” on page 97 Range: D20x “D201 Unexpected error” on page 97 “D202 General printing error” on page 98 Range: D50x “D506 Security violation” on page 98 “D507 Administrator record not found in database” on page 98 “D508 Transaction failed” on page 99 72 GroupWise 6.5 Troubleshooting 1: Error Messages Range: D70x “D701 Unexpected error” on page 99 “D704 Unexpected error” on page 99 “D705 Unexpected error” on page 99 “D706 Unexpected error” on page 99 “D707 Unexpected error” on page 99 “D708 Directory entry record not found” on page 99 “D709 Unexpected error” on page 100 “D70A Memory error” on page 100 “D70B Database inconsistency detected” on page 100 “D70D Unexpected error” on page 100 “D70E Duplicate entry in database” on page 100 “D70F Unexpected error” on page 101 Range: D71x “D710 Incompatible platform” on page 101 “D712 Post office currently disabled” on page 101 “D713 Database dictionary not found” on page 101 “D714 User database temporarily disabled” on page 102 Range: D90x “D901 Unexpected error” on page 102 “D902 Unexpected error” on page 102 “D904 Unexpected error” on page 102 “D90A Unexpected error” on page 102 “D90B Unexpected error” on page 102 “D912 Cannot process message file” on page 102 Range: DAOx “DAOC Incorrect DLL version” on page 103 “DAOD Cannot create directory in post office” on page 103 “DAOE Path to post office database not specified” on page 103 Range: DA1x “DA10 Cannot read post office configuration information” on page 103 “DA12 Invalid application configuration name” on page 104 “DA13 /name switch required” on page 104 “DA17 /user and /password switches required for this configuration” on page 104 Range: DBOx “DBO1 Operation cancelled” on page 104 Dxxx Engine Error Codes 73 “DB02 Database access error” on page 105 “DB03 Operation pending; cannot modify” on page 105 “DB04 Owner not valid user” on page 105 “DB05 Invalid path” on page 105 “DB08 Non-unigue name” on page 105 “DB09 User owns resource” on page 106 “DBOA Record not found” on page 106 “DBOB Reguired field empty” on page 106 “DBOC Cannot close database” on page 106 “DBOE Insufficient memory to initialize database” on page 106 “DBOF Domain not found” on page 107 Range: DB1x “DB10 Post office not found” on page 107 “DB11 Unexpected error” on page 107 “DB12 Maximum number of objects per post office reached” on page 107 “DB16 WP Office 3.1 host already exists in specified directory” on page 107 “DB17 Domain already exists in specified directory” on page 108 “DB19 Local post office not found” on page 108 “DBIA Insufficient administrative rights to perform operation” on page 108 “DBIB Message Transfer Agent not installed” on page 108 “DBIC Invalid object name” on page 108 “DBID Cannot delete post office” on page 109 “DBIF Cannot delete current domain” on page 109 Range: DB2x “DB20 Unexpected error” on page 109 “DB21 Database inconsistency detected” on page 109 “DB23 Password incorrect” on page 109 “DB24 Invalid link” on page 110 “DB25 Duplicate domain name” on page 110 “DB26 Secondary domains exist” on page 110 “DB29 Invalid character” on page 110 “DB2A Invalid name” on page 111 “DB2B Non-unique entry” on page 111 “DB2C Invalid post office database” on page 111 “DB2D Platform error” on page 111 “DB2E Link record not found” on page 111 “DB2F Correct database type not found” on page 111 Range: DB3x “DB30 Gateway directory not found” on page 112 “DB31 Required field missing or empty” on page 112 “DB32 Required field missing” on page 112 74 GroupWise 6.5 Troubleshooting 1: Error Messages “DB33 Cannot open all post offices” on page 112 “DB34 Time zone definition not found” on page 112 “DB35 No pending operation for record” on page 112 “DB37 Cannot delete current domain” on page 113 “DB38 Cannot delete domain that has post offices” on page 113 “DB39 Domain database not found” on page 113 “DB3A Cannot delete domain that has links” on page 113 “DB3B Remote management message sent” on page 113 “DB3C Domain database in use” on page 114 “DB3D Database sorting language changed” on page 114 “DB3F Cannot delete reguired field” on page 114 Range: DB4x “DB40 Cannot delete gateway used in link” on page 114 “DB41 Database does not match domain or post office” on page 114 “DB42 Information lost during recovery” on page 114 “DB43 Maximum number of open post offices reached” on page 115 “DB45 Group Wise system not found” on page 115 “DB46 Path too long” on page 115 “DB47 Invalid area” on page 115 “DB48 Cannot delete domain that has links” on page 115 “DB49 Cannot use limited visibility distribution list as administrator” on page 116 “DBAA External sync message from unknown system” on page 116 “DB4B Cannot delete Internet domain name that is still referenced” on page 116 “DBAD Database recovery reguired to update database structure” on page 116 “DB4E Cannot delete default gateway” on page 117 “DBAF Cannot delete POA that performs message transfer” on page 117 Range: DB5x “DB50 Access to this library has been enabled by WebPublisher” on page 117 “DB51 Required network address information is missing” on page 117 “DB52 Required path information is missing” on page 118 “DB53 No message transfer POA has been selected” on page 118 “DB55 No POA is available for client/server” on page 118 “DB56 Specified e-mail address conflicts with the address of an existing gateway alias” on page 118 “DB57 Specified e-mail address conflicts with the address of an existing user” on page 118 “DB58 Specified e-mail address conflicts with an address from a post office alias record” on page 118 “DB59 This GroupWise administration version is older than the minimum allowed by the system administrator” on page 119 Range: DB6x “DB60 The LDAP server is being used for eDirectory synchronization” on page 119 Range: DExx Dxxx Engine Error Codes 75 “DE02 Cannot perform delayed action reguest” on page 119 “DE05 Unexpected error” on page 119 Range: DFxx “DF10 Required file or directory missing” on page 119 “DF15 Records lost during rebuild” on page 120 “DF17 Cannot create reguired directory” on page 120 “DF1C Document storage area definitions are not identical” on page 120 “DF27 Invalid NGWCHECK.DB database migration level” on page 121 “DF28 Failure using the NGWCHECK.DB database” on page 121 D001 Unexpected error Source: Action: GroupWise® engine. See “Dxxx Unexpected error” on page 121. D002 Folder not empty Source: Explanation: Action: Group Wise engine. Folder not empty. Delete all items in the folder before attempting to delete it. D004 Database error Source: Explanation: Possible Cause: Action: GroupWise engine. Database error. Attempt to read or modify settings failed. The user database (userxxx.db) contains inconsistent information. Check and, if necessary, repair the user database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. D005 Settings field list is not valid Source: Possible Cause: Action: GroupWise engine. The post office database (wphost.db) is damaged. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. D006 Unexpected error Source: Action: Group Wise engine. See “Dxxx Unexpected error” on page 121. D009 Cannot use group name in distribution list Source: Explanation: Possible Cause: Action: Group Wise engine. Group in Workflow. A group name was entered in the distribution list for a routed item. Groups are not supported in a workflow step. Delete the group name, then provide the names of the users in the group. 76 GroupWise 6.5 Troubleshooting 1: Error Messages DOOA Syntax error in address Source: GroupWise engine. Explanation: Syntax error. Possible Cause: A syntax error was detected in the distribution list. One of the following conditions exists: ¢ There is a colon (:), at-sign (@), or a period (.) inside a parenthesized list. ¢ There are parentheses with nothing between them () or an opening parenthesis followed by a comma (, in the distribution list. There must be a user ID between the parenthesis and the comma. + There is a comma followed by a closed parenthesis ,) in the distribution list. There must be a user ID between the comma and the parenthesis. ¢ There is a colon (:) somewhere after a closed parenthesis. Action: Locate the syntax error in the distribution list. A pointer to the location of the syntax error points out where the error is. Correct the syntax error, then retry the operation. DOOB Missing closing quotation mark (") Source: GroupWise engine. Explanation: No closing quotation mark. Possible Cause: A closing quotation mark (") is missing in a distribution list. Action: Type the closing quotation mark, then retry the operation. DOOC Unexpected error Source: GroupWise engine. Action: See “Dxxx Unexpected error” on page 121. DOOD Cannot match parentheses Source: GroupWise engine. Explanation: Problem with parentheses. Possible Cause: | Cannot match the parentheses in the distribution list. While processing the To:, BC:, and CC: buffers of a send window, a problem was found matching up parentheses. See also “DOOA Syntax error in address” on page 77. Action: Check the distribution list for incorrect usage of parentheses and resend. DOOE Distribution list contains nested groups Source: GroupWise engine. Explanation: Groups are nested too deep. Possible Cause: The distribution list contains groups that are nested more than five levels deep or it might contain a circular reference. For example, if a personal group contains a recipient with the same name as the personal group, a circular reference is created. Action: Edit the groups to remove the circular reference, or include the contents of one of the sub-groups in a higher level group to reduce the levels in the structure. Dxxx Engine Error Codes 77 DOOF Remote mail error Source: Explanation: Possible Cause: Action: Action: Action: GroupWise engine. Invalid remote mail request. Remote mail error. This error is displayed whenever a more specific error is not available. The most common cause is a request for items that have already been deleted. Check and repair the databases ofthe master mailbox. 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. GroupWise Remote should automatically repair any problems with the remote databases. Ifthe client is unable to repair the problem, you can delete the rofdata directory on the remote computer, then request all information from the master mailbox again. D017 Too many users in address Source: Explanation: Possible Cause: Action: GroupWise engine. Reply buffer full. When Reply to All is selected, personal groups and public distribution lists are expanded into a complete list of users. Ifthe expanded list exceeds 6 KB, this error occurs. Ifthe reply is sent, some ofthe users included in the original groups might not receive the reply. To reply to all the users, create a personal group that contains the users and send the reply to that group. If replying to these groups is common, the personal groups could be made into public distribution lists and selected manually when replying to all users. D018 Unexpected error Source: Action: GroupWise engine. See “Dxxx Unexpected error” on page 121 D019 Password incorrect Source: Explanation: Action: Possible Cause: Action: Action: GroupWise engine. Invalid password. Type the correct password. Note that passwords are case sensitive. The password information in the post office database (wphost.db) has been damaged. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Ifrebuilding the post office database does not resolve the problem, rebuild the domain database (wpdomain.db). DO1A Password too long Source: Explanation: Action: GroupWise engine. Password too long. Passwords can contain a maximum of 64 characters. Type a password with fewer than 64 characters. 78 GroupWise 6.5 Troubleshooting 1: Error Messages DO1B Access to GroupWise denied Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine. Access to the user database reguired for this operation has not been granted. You are trying to proxy to a user's mailbox, or perform an action as a proxy on another user's mailbox, but the mailbox owner has not granted you sufficient rights. Ask the owner to grant you the necessary rights. The user should add your user ID to his or her access list to grant proxy access. Look up “proxy, rights” and “access” in Group Wise client Help. You are trying to perform an action in a shared folder, but you do not have rights to perform the reguested operation. Ask the owner of the shared folder to grant you the necessary rights. Look up “shared folders” in GroupWise client Help. D01C Remote mail error Source: Explanation: Possible Cause: Action: Action: Action: GroupWise engine. Invalid remote mail reguest. Remote mail error. This error is displayed whenever a more specific error is not available. The most common cause is a request for items that have already been deleted. Check and repair the databases ofthe master mailbox. 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. GroupWise Remote should automatically repair any problems with the remote databases. If the client is unable to repair the problem, you can delete the rofdata directory on the remote computer, then request all information from the master mailbox again. DO1E Cannot execute rule Source: Explanation: Possible Cause: Action: GroupWise engine. Invalid rule action. An archive rule was given an invalid execution type. GroupWise does not allow you to create a rule that automatically archives messages when they are received. Edit the rule and select a valid execution type. Look up “rules” in GroupWise client Help. DO1F Archive path not specified Source: Explanation: Possible Cause: Action: GroupWise engine. No archive path. No archive path specified in the GroupWise client. Specify the archive path before attempting to archive items. Look up “archive, directory, setting up” in GroupWise client Help. D020 Rule caused infinite loop Source: GroupWise engine. Dxxx Engine Error Codes 79 Explanation: Possible Cause: Action: Rule hop count exceeded. The execution ofa rule has caused a message to be sent, which caused the execution ofa rule, and so on. To prevent the possibility of infinite looping, the rule execution has been terminated. Edit the rule to correct the looping condition. Look up “rules” in GroupWise client Help. D021 Cannot deliver message Source: Explanation: Possible Cause: Action: Action: Group Wise engine. Remote send reguested with no agents present. Message cannot be delivered to a user in a different post office because the POA and MTA are not available. Set up the POA for the post office. See “Installing and Starting the POA” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. Set up the MTA for the domain. See “Installing and Starting the MTA” in “Message Transfer Agent” inthe GroupWise 6.5 Administration Guide. D023 User ID expired Source: Explanation: Action: Group Wise engine. User account is expired. You can extend or remove the user's expiration date. See “Expiring a GroupWise Account” in “Users” in the GroupWise 6.5 Administration Guide. D024 Rule cannot forward, reply, accept, or delegate personal item Source: Explanation: Action: GroupWise engine. Action not valid for personal item. Edit the conditions of the rule so that personal items are not included. Look up “rules” in Group Wise client Help. D025 Users not specified Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise engine. No users specified. No users have been specified in the distribution list. Type the names of users, or select users from the Address Book to include in the distribution list. If this message occurs from the POA, it might be attempting to process a damaged message file. Check the priority subdirectories of the \wpcsout\ofs directory in the post office. Check the POA log to determine the offending message file. Delete the offending message file so that subsequent messages can be processed. D026 Missing opening brace in distribution list Source: Explanation: Group Wise engine. No opening brace. 80 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Mismatched braces in distribution list. While processing the To:, CC:, and BC: addresses in a message, the end ofthe input buffer was reached before finding the closing brace. Check the address for incorrect use of braces, then resend the message. D027 Missing closing brace in distribution list Source: Explanation: Possible Cause: Action: GroupWise engine. No closing brace. Mismatched braces in distribution list. While processing the To:, CC:, and BC: addresses in a message, the end ofthe input buffer was reached before finding the closing brace. Check the address for incorrect use of braces, then resend the message. D028 Lost attachment Source: Explanation: Possible Cause: Action: GroupWise engine. Attachment could not be associated with a message. The attachment pointer was damaged. Resend the message. D029 Recipient not specified Source: Explanation: Possible Cause: Action: GroupWise engine. No distribution list for delegate rule. No recipient has been specified in a delegate rule. The delegate rule must contain a valid user ID to which to delegate the item. This error might indicate the user who sees the message, or some other user, has an incorrect delegate rule. Make sure the delegate rule contains a valid distribution list. Look up “rules” in Group Wise client Help. DO2A Name for group not specified Source: Explanation: Possible Cause: Action: GroupWise engine. No group name. No name has been specified for the distribution list. Enter a unigue group name. DO2F Database error Source: Explanation: Possible Cause: Action: Action: Group Wise engine. No document record number (DRN) for status. The domain database (wpdomain.db) or post office database (wphost.db) might be damaged. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. If rebuilding the post office database does not resolve the problem, rebuild the domain database. Dxxx Engine Error Codes 81 D030 Missing post office number for status Source: Explanation: Possible Cause: Action: Action: GroupWise engine. Necessary information cannot be accessed. Inconsistent database information. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the Group Wise 6.5 Administration Guide. Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. D039 Missing attachment Source: Explanation: Possible Cause: Action: GroupWise engine. An attachment for a message can no longer be found. If this error occurs in Group Wise Remote, there might be a problem with the structure or content ofthe Remote mailbox. Delete the rofdata directory on the remote computer, then request all information from the master mailbox again. DO3F Database error Source: Explanation: Possible Cause: Action: Action: GroupWise engine. No item type. The user database (userxxx.db) and/or message database (msgnn.db) for the user have been damaged. Check and, if necessary, repair the user and/or message databases. 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. D040 Cannot delete folder used in rule Source: Explanation: Possible Cause: Action: GroupWise engine. Folder being used in a rule. User cannot delete the folder because it is referenced in a rule. Change or delete the rule, then delete the folder. Look up “rules” in GroupWise client Help. D041 No recipients in post office Source: Explanation: Possible Cause: Action: GroupWise engine. Insufficient recipient information. A Remote user sent a message using a personal group that exists in the user's master mailbox but has not been downloaded to Remote. Download the personal group. 82 GroupWise 6.5 Troubleshooting 1: Error Messages D043 Inconsistent distribution list Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: Action: Group Wise engine. Information in the distribution list does not match information elsewhere in the system. Outdated information in a distribution list, a damaged distribution list, or a damaged message file could cause this error from the POA. Check the priority subdirectories of the \wpcsout\ofs directory in the post office. Check the POA log file to determine the offending message file. See “Using POA Log Files” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Determine the originator of the offending message. Check and, if necessary, repair the user database (userxxx.db) for that user. 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. The POA has been started with the /norecover startup switch and damage to a user or message database has been detected. Repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Start the POA without the /norecover startup switch so that the POA can automatically recover any databases where damage is detected. D044 Auto-rebuild disabled Source: Explanation: Possible Cause: Action: Action: Group Wise engine. Automatic recovery of damaged databases by the POA has been turned off. The POA has been started with the /norecover startup switch and damage has been detected in a database. Repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Start the POA without the /norecover startup switch so that the POA can automatically recover any databases where damage is detected. D049 Error reported from Novell NDS Source: Explanation: Possible Cause: Action: Group Wise engine. The GroupWise Administrator snap-in to ConsoleOne was unable to retrieve information from Novell® eDirectory™. You might be running ConsoleOne with insufficient Browse, Read, or Compare rights to the required eDirectory object. Check the rights to the Group Wise user, post office, and agent objects in eDirectory. DO4A Unexpected error Source: Action: Group Wise engine. See “Dxxx Unexpected error” on page 121. Dxxx Engine Error Codes 83 D04B Unexpected error Source: Action: GroupWise engine. See “Dxxx Unexpected error” on page 121. D04F Unexpected error Source: Action: GroupWise engine. See “Dxxx Unexpected error” on page 121. D050 Cannot connect to specified post office Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Action: GroupWise engine. No TCP/IP services. The GroupWise client cannot connect to the specified post office in client/server mode because an IP address has not been provided. The POA in a remote post office is required for cross-post office proxy and library access. Set up the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. The GroupWise client cannot connect to the specified post office in client/server mode because the POA in that post office is not running. The POA in a remote post office is required for cross- post office proxy and library access. Make sure the POA is running in the remote post office. See “Monitoring the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Make sure the POA in the remote post office is configured with the correct IP address and TCP port. Make sure the POA in the remote post office is configured to allow TCP/IP connections. Make sure it has not been started with the /notcpip switch. D051 Cannot connect to specified post office Source: Explanation: Possible Cause: Action: Group Wise engine. TCP/IP not allowed. An attempt to connect to a post office by way of a direct or mapped mode was rejected. No IP address information is available to attempt a client/server connection. The administrator hasn't set up the client/server addressing. Set up the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. D054 Cannot connect to specified post office Source: Explanation: Possible Cause: Action: GroupWise engine. Missing path for direct mode connection. The post office rejected the client/server mode connection but is allowing direct mode. The path might be set up, but not for this platform. Set up the path for the specified post office in the post office Identification page in ConsoleOne. 84 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Action: To start the Group Wise client in direct mode, use the /ph switch to provide the path to the post office. If you want to use client/server mode, you can setup an additional POA to handle client/server communication. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. D055 Cannot connect to specified post office Source: Explanation: Possible Cause: Action: GroupWise engine. Cannot use direct (mapped) connection. The post office rejected the direct mode connection but is allowing client/server mode. Make sure the IP address for the POA is setup correctly. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. D057 Cannot connect to any post office Source: Explanation: Possible Cause: Possible Cause: Action: Possible Cause: Action: GroupWise engine. TCP/IP default address failed. An attempt to connect to a post office using the GroupWise IP address defaults (NGWNAMESERVER and NGWNAMESERVER2) was unsuccessful. No client/server or direct information was specified or available. Make sure the GroupWise name server is properly set up and running. See “Simplifying Client/ Server Access with a GroupWise Name Server” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. The GroupWise name server cannot locate any post offices. Make sure the network connections to the servers where post offices reside are functioning properly. D058 Version mismatch on GroupWise client/POA/post office Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise engine. The post office directory, with its associated user databases (userxxx.db) and message databases (msgnn.db) was created by a version of Group Wise that is older than the version of the Group Wise client that is accessing the post office. A user is running the latest version of the Group Wise client, but the post office has not yet been updated. Update the post office. See “Update” in the GroupWise 6.5 Installation Guide. The post office has been updated, but the latest version of the POA has not yet been installed and started. Update the POA. See “Updating Post Offices” in “Update” in the GroupWise 6.5 Installation Guide. D059 Recursion limit exceeded during delivery Source: Group Wise engine. Dxxx Engine Error Codes 85 Explanation: Possible Cause: Action: Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: Possible Cause: Action: Action: Possible Cause: Action: Action: Source: Explanation: Action: The POA received a message that contained more than 36 levels of encapsulation. The POA could not deliver the message. This can be caused by rule forwarding loops that include one hop to an external user, or by some Internet 'chain letters." Check the rule configuration of the Group Wise recipient. Disable any rules that forward mail to an external user who might be forwarding the mail back into Group Wise. Look up “rules” in GroupWise client Help. DO5A User database access denied GroupWise engine. The GroupWise client cannot start because it cannot access the user's user database (userxxx.db). The user tried to access a mailbox that does not have a password using the wrong NetWare user ID, in a post office with security set to high. Set apassword on the user's mailbox. See “Creating or Changing a Mailbox Password” in “Users” in the GroupWise 6.5 Administration Guide. The user's current login ID, either from NetWare, eDirectory, or Windows, does not match the network login ID stored in the GroupWise user database. Make sure the user is using the correct login ID. Password information in the user database might be damaged. Check and, ifnecessary, repair the database, including resetting user options to reset the password. 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. The post office database (wphost.db) might be damaged. Rebuild the index ofthe post office database. See “Rebuilding Database Indexes” in “Databases” in the Group Wise 6.5 Administration Guide. If rebuilding the index is not sufficient to resolve the problem, validate the database, then take the appropriate actions to either recover or rebuild the database. See “Maintaining Domain and Post Office Databases” in “Databases” inthe GroupWise 6.5 Administration Guide. The IP address of the POA has changed, but GroupWise client users are still trying to start the client using old /ipa and /ipp client startup switch settings. Update the information in users' /ipa and /ipp switch settings with the current IP address information. Remove the /ipa and /ipp switches and let the client and/or the POA resolve the address. See “Simplifying Client/Server Access with a GroupWise Name Server” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. DO5D Post office intruder lockout is enforced Group Wise engine. The POA has detected a possible intruder. The user has been locked out. You have several options for handling the situation. See “Enabling Intruder Detection” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. GroupWise 6.5 Troubleshooting 1: Error Messages DOSE Message size exceeds limit Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine. A user tried to send a message that exceeded that user's message size limit as set by the administrator. The user is not aware that there is a message size limit on his or her mailbox. Notify the user of the message size limit so that the user can send messages of appropriate size. The administrator has set a message size limit that is too restrictive. Increase the message size limit. Increase the maximum message size for the user. See “Send Options: Disk Space Management” in “Users” in the Group Wise 6.5 Administration Guide. D05F Box size limit exceeded Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine. A user’s Group Wise mailbox exceeds the size limit set by the administrator The user is not aware that there is a size limit on his or her mailbox. Notify the user of the mailbox size limit so that the user can delete unneeded messages from the mailbox. The administrator has set a mailbox size limit that is too restrictive. Increase the message size limit. Increase the maximum mailbox size for the user. See “Send Options: Disk Space Management” in “Users” in the GroupWise 6.5 Administration Guide. D060 Message size exceeds threshold limit Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine. A user's GroupWise mailbox is close to exceeding the size limit set by the administrator The user is not aware that there is a size limit on his or her mailbox. Notify the user of the mailbox size limit so that the user can delete unneeded messages from the mailbox. The administrator has set a mailbox size limit that is too restrictive. Increase the message size limit. Increase the maximum mailbox size for the user. See “Send Options: Disk Space Management” in “Users” in the GroupWise 6.5 Administration Guide. D061 Status denied to external Internet user Source: Explanation: Action: GroupWise engine. The local Group Wise system is configured so that users outside the local Group Wise system cannot receive status information about messages. To permit access to status information by external users, enable Allow External Status Tracking. See “System Preferences” in “System” in the GroupWise 6.5 Administration Guide. Dxxx Engine Error Codes 87 D062 Busy Search denied for external Internet user Source: Explanation: Action: Group Wise engine. The local GroupWise system is configured so that users outside the local GroupWise system cannot perform Busy Searches on local users. To permit Busy Search access by external users, enable Allow External Busy Search. See “System Preferences” in “System” in the GroupWise 6.5 Administration Guide. D065 Attempt to purge item that has not been backed up Source: Explanation: Action: Group Wise engine. Client Cleanup options are set so that items cannot be purged from users’ mailboxes until they have been backed up. A user has tried to purge an item that has not yet been backed up. You can allow users to purge items that have not yet been backed up. See “Environment Options: Cleanup” in “Users” in the GroupWise 6.5 Administration Guide. See also “GroupWise Time Stamp Utility” in “Databases” in the GroupWise 6.5 Administration Guide. D066 Attempt to purge an item from a user that has not been backed up Source: Explanation: Action: Group Wise engine. Client Cleanup options are set so that items cannot be purged from users’ mailboxes until they have been backed up. A process has tried to purge an item that has not yet been backed up. You can allow purging of items that have not yet been backed up. See “Environment Options: Cleanup” in “Users” in the GroupWise 6.5 Administration Guide. See also “GroupWise Time Stamp Utility” in “Databases” in the GroupWise 6.5 Administration Guide. D069 Attempt to open invalid backup location Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: Group Wise engine. The user attempted to open a backup location that did not contain a valid backup of a Group Wise post office or mailbox. The user is unsure of the backup location. Make sure users know where their backed-up messages have been restored. See “Restoring Deleted Mailbox Items” in “Databases” in the GroupWise 6.5 Administration Guide. The backup location path includes a directory name that has more than eight characters. Rename any long directory names to eight characters maximum, then make matching changes to the restore area information in ConsoleOne. See “Setting Up a Restore Area” in “Databases” in the GroupWise 6.5 Administration Guide. The restore area is in a location where the POA does not have the necessary rights to access it. If the restore area is on a different server from where the POA is running, provide a username and password for the POA to use to access the remote location. You can provide this information in ConsoleOne in the Remote File Server Settings box on the Post Office Settings page of the Post office object or in the POA startup file using the /user and /password switches. If the restore area is on the same server, add a trustee assignment to the restore area directory that provides the POA with object file system rights to the directory. 88 GroupWise 6.5 Troubleshooting 1: Error Messages D06B LDAP failure detected Source: Explanation: Action: GroupWise engine. Group Wise was unable to authenticate using LDAP. Make sure your LDAP server is functioning correctly. DO6E Lockout of older GroupWise clients being enforced Source: Explanation: Possible Cause: Action: Group Wise engine. The POA is not allowing GroupWise client users with older versions of the client software to access the post office. The administrator does not want older versions of the GroupWise client to access the post office. The client version can be controlled as described in “Checking What GroupWise Clients Are in Use” in “Post Office Agent” in the GroupWise 6.5 Administration Guide Group Wise client users must update their client software before they can access the post office. See “Updating Users' GroupWise Clients” in “Updating Your GroupWise 6.x System to Version 6.5” in the GroupWise 6.5 Installation Guide. DO6F This GroupWise client doesn't match the user's license Source: Explanation: Action: Action: Group Wise engine. The Group Wise administrator has restricted client users to the WebAccess client and a user is attempting to access his or her mailbox using the Windows client. Explain to the user that he or she must use the WebAccess client. Allow the user to use the Windows client. See “Setting Client Options” in “Users” in the Group Wise 6.5 Administration Guide. D071 LDAP authentication failed because the password has expired Source: Explanation: Action: Group Wise engine. The Group Wise client was attempting to authenticate using LDAP, but the user's LDAP password has expired. The user needs to contact the administrator of the LDAP server and get the password reset. D072 Changing the LDAP password has been disabled Source: Explanation: Action: Action: Group Wise engine. A user tried to change his or her LDAP password from the GroupWise client but the administrator has disabled that capability for the user’s post office. Enable LDAP password changes in ConsoleOne. See “Providing LDAP Authentication for GroupWise Users” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Show the user what application he or she needs to use to change the LDAP password. D073 Attempting to log in trusted without SSL Source: Explanation: Possible Cause: Group Wise engine. A trusted application to log in to the POA and was not successful because an SSL connection could not be established. The POA is not configured to support SSL connections. Dxxx Engine Error Codes 89 Action: Enable SSL for the POA that the trusted application needs to log in to. See “Enhancing Post Office Security with SSL Connections to the POA” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. D074 Invalid key for trusted application Source: Explanation: Possible Cause: Action: Group Wise engine. A trusted application tried to login to the POA and was not successful because the key was invalid. The private key offered by the application did the match the private key the POA was configured to accept. Verify the private key that the POA is configured to accept. See “Enhancing Post Office Security with SSL Connections to the POA” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. D075 Invalid IP address for trusted application Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise engine. A trusted application tried to log in to the POA and was not successful because the POA was configured for a specific IP address and the trusted application was not running there. The trusted application is running on a different server from where it was designed to run. Run the trusted application on the server with the IP address that the POA is expecting. The POA is configured with an incorrect IP address for the trusted application. In eDirectory, change the expected IP address to the IP address of the server where the trusted application is running. See “Trusted Applications” in “System” in the Group Wise 6.5 Administration Guide. D076 Missing trusted application name Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise engine. A trusted application tried to log in to the POA and was not successful because no application name was provided. The trusted application is not providing an application name. Add an application name to the trusted application. The POA is configured with an incorrect application name for the trusted application. In eDirectory, change the expected application name to the application name that the trusted application is providing. See “Trusted Applications” in “System” in the GroupWise 6.5 Administration Guide. D077 The problem file is being rebuilt Source: Explanation: Possible Cause: Action: GroupWise engine. The database you want to repair cannot be accessed. You are trying to perform database maintenance on a database that is currently being repaired. None. Your database maintenance request will be deferred until the build in completed. 90 GroupWise 6.5 Troubleshooting 1: Error Messages Source: Explanation: Possible Cause: Action: Source: Action: Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: D078 LDAP SSL key file not found GroupWise engine. The POA is configured to use SSL on its LDAP connection, but it cannot locate the SSL key file. The SSL key file has not been specified or has been specified incorrectly. Provide the full path to a valid SSL key file. See “Providing LDAP Authentication for Group Wise Users” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. See also “Server Certificates and SSL Encryption” in “Security” in the Group Wise 6.5 Administration Guide. D07F Unexpected error GroupWise engine. See “Dxxx Unexpected error” on page 121. D101 User not found GroupWise engine; database interface. User not found. The Group Wise user ID is not found in the post office database during login. Ifusing startup switches, check the /ph switch to make sure the path to the post office is correct. Start the Group Wise client using the /@u or /la startup option to specify the Group Wise user ID. The user is not yet set up as a Group Wise user. Set the user up as a Group Wise user. See “Creating Group Wise Accounts” in “Users” in the GroupWise 6.5 Administration Guide. The user ID provided when the user was set up as a Group Wise user is not correct. Check the Group Wise user information in ConsoleOne. Make sure the common name (CN) ofthe user is provided. No additional information is needed in the Network ID field. User information has not replicated from the domain to the post office the user is trying to access. Wait for replication to take place. Make sure the MTA is running. Check the current scan cycles ofthe MTA. See “Adjusting MTA Polling of Input Oueues in the Domain and Post Offices” in “Message Transfer Agent” in the Group Wise 6.5 Administration Guide. Synchronize the user manually. See “Synchronizing Individual Users or Resources” in “Databases” in the Group Wise 6.5 Administration Guide. The user is logging into a specific server, rather than into the tree, causing the network ID information not to match. Log in to the tree rather than to a specific server. If this error occurs when a user sends a message to a group, the group might contain user IDs that have been deleted from the system. Recreate the group, selecting users from the Address Book to ensure they are valid GroupWise users. If this error occurs when the user tries to delete users from the Subscribe to Notify window, the users might no longer exist in the GroupWise system. Dxxx Engine Error Codes 91 Action: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Check the Address Book to see if the users are still valid. If they are not, repair the user database (userxxx.db). See “Maintaining User/Resource and Message Databases” in “Databases” in the Group Wise 6.5 Administration Guide. Run GWCheck on the post office database (wphost.db). See “Standalone Database Maintenance Programs” in “Databases” in the Group Wise 6.5 Administration Guide. The user was not found in the post office database (wphost.db) during the parsing of To: line or group. Find the user in the To: line or Group. Either delete the user, or find the correct user ID in the Address Book. If this error occurs for all users in a post office, the post office database might be damaged. Rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs in systems where new users are added from multiple administrator workstations, preferences might be set differently on different administrator workstations. On each workstation where users are added in ConsoleOne, click Tools > GroupWise System Operations > System Preferences. Make sure that the When Creating or Modifying Objects, For Network ID Use setting is the same on all workstations. If some workstations are set to Full Distinguished Name and some are setto Common Name, users will be set up differently depending on which workstation they were created from, causing problems when users access GroupWise. Ifthis error occurs only when using GroupWise Remote, the user ID might be specified incorrectly under Remote Options. Check the user ID specified in the GroupWise client. Look up “Remote, specifying user and system information” in GroupWise client Help. Make sure the user ID specified is correct. D102 Ambiguous user ID Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Action: GroupWise engine; database interface. User ambiguous. There is more than one user with same user ID on the same post office. Select the correct user ID in the pop-up list or select the user in the Address Book. Ifthis error occurs when a user starts the GroupWise client, the user's information in the post office database might not be correct. Check the information provided for the GroupWise user in ConsoleOne. Correct the information as needed. See “Creating GroupWise Accounts for eDirectory Users” in “Users” inthe GroupWise 6.5 Administration Guide. Even if the information in the user record looks correct, make a change somewhere so the record is written out again. If the problem persists, rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. D103 Post office not found during login Source: Explanation: GroupWise engine; database interface. Post office not found. 92 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Action: Ifusing startup switches, check the /ph switch to make sure the path to the post office is correct. Ifit is incorrect, enter the correct /ph switch. Ifthe path is correct, the post office was not found during parse of'the To: line buffer. In that case, find the post office in To: line. Delete the post office gualifier, or select the user from the Address Book. D104 Ambiguous post office Source: Explanation: Possible Cause: Action: GroupWise engine; database interface. Post office ambiguous. There are multiple post offices in the same domain. The Group Wise client pops up a list so the user can correct the ambiguity manually. Select the correct user in the pop-up list, or use the Address Book to find the user. D105 Directory Services data missing Source: Explanation: Possible Cause: Action: GroupWise engine; database interface. Directory Services error. Domain or post office not found during user or post office lookup. Check the /ph switch when starting the Group Wise client to make sure it specifies the correct path to the user's post office. Also check the /@u switch to make sure it specifies a valid user in the specified post office. See “Startup Switches for the Group Wise Client” in “Client” in the GroupWise 6.5 Administration Guide. D106 Database error Source: Explanation: Possible Cause: Action: GroupWise engine; database interface. General database error. The index is not synchronized with the data. Check and repair the database. See “Maintaining Domain and Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. D107 Record not found Source: Explanation: Possible Cause: Possible Cause: Action: Action: Possible Cause: Action: GroupWise engine; database interface. Record not found. Relational integrity problem. The user database (userxxx.db) and/or message database (msgnn.db) is 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. A user tried to read an attachment for which the corresponding file has already been deleted from the offiles directory in the post office. None, unless you want to restore the contents ofthe offiles directory from a backup. Dxxx Engine Error Codes 93 D108 Unexpected error Source: Action: Group Wise engine; database interface. See “Dxxx Unexpected error” on page 121. D109 Bad parameter Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Possible Cause: Action: Group Wise engine; database interface. A GroupWise program passed invalid information to another GroupWise program. The user’s mailbox contains a damaged message. Run a structural rebuild on the user database (userxxx.db) and message database (msgnn.db). See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. A delay in Directory replication is preventing the user from logging in to the GroupWise client. Start the client using the /@u-? switch to bypass eDirectory authentication. Wait for eDirectory replication to complete. The user’s Client Options settings have been damaged. Reset the user’s Client Options setting back to the default. See “Resetting Client Options to Default Settings” in “Client” in the GroupWise 6.5 Administration Guide. D10A Unexpected error Source: Action: GroupWise engine; database interface. See “Dxxx Unexpected error” on page 121. D10B Database needs to be repaired Source: Explanation: Possible Cause: Action: Action: Possible Cause: Possible Cause: GroupWise engine; database interface. Database invalid or damaged. A record is no longer valid. Validate the database, then take the appropriate actions to either recover or rebuild the database. See “Maintaining Domain and Post Office Databases” and “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 running the GroupWise client under Windows for Workgroups, the user login name might be incorrect. Check the user login name on the station where the error occurs. In Windows for Workgroups, click Main > Control Panel > Network > Login Name. The login name must match the user's Group Wise ID. D10C Unexpected error Source: Action: GroupWise engine; database interface. See “Dxxx Unexpected error” on page 121. 94 GroupWise 6.5 Troubleshooting 1: Error Messages D10D Cannot open any more mailboxes Source: GroupWise engine; database interface. Explanation: Maximum databases open. Possible Cause: The maximum number of databases that can be opened at one time has been exceeded. The maximum number is approximately 12. Action: Shutdown some databases by removing proxies. Look up “proxy, deleting users from Access List” in Group Wise client Help. D110 Unexpected error Source: GroupWise engine; database interface. Action: See “Dxxx Unexpected error” on page 121. D113 Open database maximum exceeded Source: GroupWise engine; database interface. Explanation: The current operation has attempted to open more than the maximum number of databases allowed. Possible Cause: You are proxied to too many users in direct mapped mode. Action: Close some mailboxes that are currently proxied, then try the operation again. Look up “proxy, deleting users from Access List” in GroupWise client Help. D114 Group not found Source: GroupWise engine; database interface. Explanation: Bad personal group or public distribution list. Action: Check the spelling of the group name, or select the group in the Address Book. D115 Database error Source: GroupWise engine; database interface. Explanation: Invalid database. Possible Cause: | Attempted to open an invalid database. Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the Group Wise 6.5 Administration Guide. Possible Cause: This could represent a security breach of unauthorized, foreign packets being introduced into your Group Wise system. Action: | Check your system security. D116 File not database Source: GroupWise engine; database interface. Explanation: Attempt to open a DOS file as a GroupWise database. Dxxx Engine Error Codes 95 Possible Cause: Action: Action: Action: Action: The database is damaged. Check and, if necessary, repair the user database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the Group Wise 6.5 Administration Guide. Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. If a user database cannot be repaired, you can rename the existing user database, then recreate it. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. Ifthe database cannot be recreated, you must restore it from backup. See “Restoring GroupWise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide. D117 GroupWise version too old Source: Explanation: Possible Cause: Action: GroupWise engine; database interface. Old program version. An attempt was made to open a database with an older version of GroupWise software. You are running an older version of the GroupWise client. Your post office has been updated to a newer version. Reinstall GroupWise with the version ofthe software that matches the database. See in “Installing the GroupWise Windows and Cross-Platform Clients” in the GroupWise 6.5 Installation Guide. D118 Database error Source: Explanation: Possible Cause: Action: Action: GroupWise engine; database interface. Field not found. Unable to find the field in the database. Check and repair the database. See “Maintaining Domain and Post Office Databases” and “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. D119 Unexpected error Source: Action: GroupWise engine; database interface. See “Dxxx Unexpected error” on page 121. D11B Too many items in mailbox Source: Explanation: Possible Cause: Action: Action: Action: GroupWise engine; database interface. Too many records. There are more than 5,000 items in your mailbox. Only the first 5,000 items will be displayed. When you delete messages, additional objects will be displayed. Have users clean out their mailboxes. You might want to run a statistics check on the mailboxes. “Gathering Mailbox Statistics” in “Databases” in the GroupWise 6.5 Administration Guide. Users could move items to different folders. Users could archive items. See “archive, items” in GroupWise client Help. 96 GroupWise 6.5 Troubleshooting 1: Error Messages D11C Cannot use group name Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; database interface. Groups cannot be listed as users here. A group name was used where a user name was expected. For example, the startup option /@u- group name was used, or a group name was used in a domain where there is no entry in the Address Book for this group. Check your Address Book for correct addressing syntax. Ifthe syntax is correct, you might want to add the group to the Address Book. The user has specified a distribution list in another post office that has visibility set to none. Change the visibility of the distribution list so that users in other post offices can use it. For information about visibility, see “Creating and Managing Distribution Lists” in “Distribution Lists, Groups, and Organizational Roles” in the GroupWise 6.5 Administration Guide. D11D GroupWise version newer than database Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: GroupWise engine; database interface. New program version. The GroupWise client has been installed on a workstation where the Group Wise demo that comes with the PerfectOffice Suite 3.0 had already been installed. The GroupWise demo creates a post office database (wphost.db) on the local workstation, which can interfere with the functioning of the full GroupWise client. Search the workstation for a local wphost.db file. If found, rename or delete it. The GroupWise client and agents were updated, but ConsoleOne was not. As aresult, the database dictionary (*.dc) files do not get updated. Copy the *.DC files from the domain and po subdirectories of the new distribution media to the domain and post office directories of your GroupWise system. The version of GroupWise you are running is newer than the database. The software cannot do an auto-upgrade on the older database. D124 Access to user denied Source: Explanation: Possible Cause: Action: GroupWise engine; database interface. Access rights failure. A required field was not found. Moving a resource causes the resource owner to lose access to the resource. In ConsoleOne, browse to and select the Resource object, then click Tools > GroupWise Utilities > Mailbox/Library Maintenance. Select Reset Client Options in the Action drop-down list. D201 Unexpected error Source: Action: GroupWise engine; mail/calendar import and print services. See “Dxxx Unexpected error” on page 121. Dxxx Engine Error Codes 97 D202 General printing error Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: Group Wise engine; mail/calendar import and print services. You have attempted to print an item that is missing information. The user workstation is missing its temporary directory, or there is insufficient disk space available to create the temporary files needed to print the item. Check for the existence of the temporary directory on the user workstation. Check for available disk space. The link to the item to print has been damaged. Check and, if necessary, repair the message database (msgnn.db). See “Maintaining User/ Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. D506 Security violation Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Possible Cause: Action: GroupWise engine; administration services. No authentication. An administration command was received that did not contain the proper authentication. This command might have originated outside the system, or the administration database (wpdomain.db or wphost.db) at the destination domain/post office has been replaced with an invalid version. Monitor and log the source ofthe command. Rebuild the domain or post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Ifthis error occurs after a configuration change (for example, after changing which domain is the primary domain of your GroupWise system), the configuration change might not have replicated throughout the system in time to support a following change (for example, adding a user). Wait for replication to complete, then synchronize the object that caused the error. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide. If you do not want to wait for replication to complete, you can rebuild the secondary domain database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs when synchronizing domains or post offices, the databases might be damaged. Rebuild the databases, then synchronize the databases. D507 Administrator record not found in database Source: Explanation: Possible Cause: Action: Group Wise engine; administration services. No administrator record found in database. An agent has attempted to send a message to the defined administrator; however, no administrator record was found in the database. To receive these messages, define an administrator for the domain. See “Notifying the Domain Administrator” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. 98 GroupWise 6.5 Troubleshooting 1: Error Messages D508 Transaction failed Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: Group Wise engine; administration services. The transaction failed. The database was locked by another process and could not be updated. None. The message will be retried automatically. 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. The database has been damaged. If the ownership on the problem database is correct or you are unable to reset it, repair the database. See “Maintaining Domain and Post Office Databases” and “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. D701 Unexpected error Source: Action: Group Wise engine; directory services access. See “Dxxx Unexpected error” on page 121. D704 Unexpected error Source: Action: Group Wise engine; directory services access. See “Dxxx Unexpected error” on page 121. D705 Unexpected error Source: Action: GroupWise engine; directory services access. See “Dxxx Unexpected error” on page 121. D706 Unexpected error Source: Action: Group Wise engine; directory services access. See “Dxxx Unexpected error” on page 121. D707 Unexpected error Source: Action: Group Wise engine; directory services access. See “Dxxx Unexpected error” on page 121. D708 Directory entry record not found Source: Explanation: GroupWise engine; directory services access. Requested record not found. Dxxx Engine Error Codes 99 Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: The directory entry record was not found. This can occur if multiple processes are updating the database at the same time. Cancel the current operation, refresh the listing, then select again from the available items. The database is damaged. Rebuild the problem database. See “Maintaining Domain and Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. The path to the software distribution directory might be incorrect. Make sure the post office where the problem is occurring has a software distribution directory assigned. See “Editing Post Office Properties” in “Post Offices” in the GroupWise 6.5 Administration Guide. Check the current path to the software distribution directory. See “Software Directory Management” in “System” in the Group Wise 6.5 Administration Guide. Correct the path as needed. Make sure the specified software distribution directory actually exists. D709 Unexpected error Source: Action: Group Wise engine; directory services access. See “Dxxx Unexpected error” on page 121. D70A Memory error Source: Explanation: Possible Cause: Action: D70B Database Source: Explanation: Possible Cause: Action: Group Wise engine; directory services access. Memory error. Unable to lock or allocate memory. The Group Wise client user should exit and restart GroupWise. inconsistency detected Group Wise engine; directory services access. Database invalid or damaged. The directory services database (wpdomain.db or wphost.db) is inconsistent. The identifier used to identify which domain or post office owns this database has been lost. Ifthe database is a primary domain, restore it from backup; otherwise, rebuild the database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. D70D Unexpected error Source: Action: GroupWise engine; directory services access. See “Dxxx Unexpected error” on page 121. D70E Duplicate entry in database Source: Explanation: Possible Cause: GroupWise engine; directory services access. Duplicate entry found in database. You provided a non-unique entry in a field that requires a unique entry. 100 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Possible Cause: Action: Provide a new, unigue value in the field. The database is damaged. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. D70F Unexpected error Source: Action: Group Wise engine; directory services access. See “Dxxx Unexpected error” on page 121. D710 Incompatible platform Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; directory services access. Reguested platform path not found. In a multiple-platform environment, a path was reguested for a given platform but none was found. This is not an error. It is a notification by the program of the return value. If this error occurs when the POA is trying to start, a path to a document storage area might be incorrect. Check the location and existence of any document storage areas for libraries associated with the post office. To list the available libraries, see “Editing Post Office Properties” in “Post Offices” in the GroupWise 6.5 Administration Guide. To check the path to a document storage area, see “Managing Document Storage Areas” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. Correct any incorrect path, then try to start the POA. D712 Post office currently disabled Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: GroupWise engine; directory services access. Post office is disabled. The system administrator has disabled the post office. This is not an error. It is a notification by the program ofthe return value. To enable the post office, deselect Disable Logins in the post office Identification page in ConsoleOne. See “Disabling a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. Ifthis error occurs when the Disable Logins option is not selected, the flag might be set improperly on the post office database. After making sure the Disable Logins option is not selected, stop and restart the POA. See “Starting the POA” in “Post Office Agent” inthe GroupWise 6.5 Administration Guide. Rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. D713 Database dictionary not found Source: Explanation: Possible Cause: GroupWise engine; directory services access. Dictionary not found. A database create request was made and the corresponding database dictionary file was not found. Dxxx Engine Error Codes 101 Action: 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 locations 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. D714 User database temporarily disabled Source: Explanation: Possible Cause: Action: Action: Group Wise engine; directory services access. The administrator has temporarily disabled Group Wise login for a specific user. The user is being moved from GroupWise 5.x to 6.x. Wait for the move to be completed. If the problem persists, rebuild the user database (userxxx.db). See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. D901 Unexpected error Source: Action: Group Wise engine; messaging services. See “Dxxx Unexpected error” on page 121. D902 Unexpected error Source: Action: Group Wise engine; messaging services. See “Dxxx Unexpected error” on page 121. D904 Unexpected error Source: Action: Group Wise engine; messaging services. See “Dxxx Unexpected error” on page 121. D90A Unexpected error Source: Action: Group Wise engine; messaging services. See “Dxxx Unexpected error” on page 121. D90B Unexpected error Source: Action: Group Wise engine; messaging services. See “Dxxx Unexpected error” on page 121. D912 Cannot process message file Source: Explanation: Possible Cause: Action: Group Wise engine; messaging services. The message file has been opened too many times. It has been moved to the problem directory. The POA might be attempting to process a damaged message file and is unable to move it to the problem directory. Check the priority subdirectories of the \wpcsout\ofs directory. Check the POA log file to determine the offending message file. See “Using POA Log Files” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Delete the offending message file so that subsequent messages can be processed. 102 GroupWise 6.5 Troubleshooting 1: Error Messages DAOC Incorrect DLL version Source: Explanation: Possible Cause: Action: GroupWise engine; Post Office Agent. Wrong DLL. The DLL being used with the POA executable is either an older or a newer version. The DLL cannot be used with the executable. Make sure the POA executable is the same version as the POA DLL. For a list of agent files, see “Windows Installation Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. DAOD Cannot create directory in post office Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: GroupWise engine; Post Office Agent. Post office directory structure problem. A required post office directory could not be created or one or more database dictionary files is missing. Make sure all of the database dictionary files are present. For file locations, see “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Make sure the POA process has the required network rights. See “Creating a NetWare Account for Agent Access (Optional)” in “Installing GroupWise Agents” in the GroupWise 6.5 Installation Guide. The post office has been created in the root directory of a NetWare volume. Move all post office directories and files into a subdirectory off the root. See “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Adjust the path to the post office in the post office Identification page in ConsoleOne. DAOE Path to post office database not specified Source: Explanation: Possible Cause: Action: Group Wise engine; Post Office Agent. No post office path. The path to the post office database (wphost.db) was not specified. Use the /home startup switch to specify the location of the post office database. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. DA10 Cannot read post office configuration information Source: Explanation: Possible Cause: Action: GroupWise engine; Post Office Agent. Error reading post office configuration information. An error was detected while reading POA configuration information from the post office database (wphost.db). The post office database might be in an inconsistent state. Start the POA with /noconfig, and validate the post office database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Dxxx Engine Error Codes 103 DA12 Invalid application configuration name Source: Explanation: Possible Cause: Action: GroupWise engine; Post Office Agent. Invalid application name. The eDirectory distinguished name (DN) specified on the command line when starting the POA was invalid. The DN might be misspelled. Specify a valid DN. A list of valid DNs for a given post office can be obtained by failing to specify one on the POA command line (with the /name switch) when the system is configured such that one is reguired. You can then choose one from the list. A DN must be specified in a system that has been configured to run more than one POA process for a single post office. In that case, the DN is used by the POA to find configuration information for a specific POA process (such as TCP/ IP address, port, and other configuration information). DA13 /name switch reguired Source: Explanation: Possible Cause: Possible Cause: Action: GroupWise engine; Post Office Agent. Ambiguous application name. An eDirectory distinguished name (DN) was not specified where one is required. Your system is configured in a way that reguires the /name switch to be specified when starting the POA. This post office has been configured to run more than one POA process for it. The DN is used by the POA to identify the configuration information and options that it should use when running. The /name switch should be used in conjunction with one ofthe DNs specified in the error message. DA17 /user and /password switches required for this configuration Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: GroupWise engine; Post Office Agent. The /user and /password switches are required when the POA must log into a remote server. The POA needs to log in to a remote server where a document storage area is located, but it does not have the necessary user and password information to log in with. See “Using POA Startup Switches” and “Installing and Starting the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object. You have renamed the server where a document storage area is located. The POA can no longer access the original document storage area location, so the POA cannot start. First, provide the new location ofthe document storage area. See “Moving a Document Storage Area” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. Next, start the POA using the /noconfig, /user, and /password switches so the POA can start and process the administrative message containing the new storage location without having to access the old storage location. Finally, exit, then restart the POA with its typical configuration. DB01 Operation cancelled Source: Explanation: GroupWise engine; administration engine. Operation cancelled. 104 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Operation cancelled by user. None. DB02 Database access error Source: Explanation: Possible Cause: Action: Action: Group Wise engine; administration engine. Database access error. Cannot complete the requested operation because the database is being updated. Retry the operation later. If you still cannot access the database, check file activity using your network administration utilities. Rebuild the database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DB03 Operation pending; cannot modify Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. Unsafe record modification. This record has a pending operation and cannot be modified. A remote operation has been requested for this record. Wait for the MTA or POA to complete the pending operation, or undo the operation. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide. DB04 Owner not valid user Source: Explanation: Possible Cause: Action: Action: DB05 Invalid path Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. Invalid owner. The owner you specified is not a valid user in the same post office as the resource. Select an owner for the resource from among the users in the same post office as the resource. See “Changing a Resource's Owner” in “Resources” in the GroupWise 6.5 Administration Guide. Create a new user in the post office to function as the owner of the resource. See “Creating GroupWise Accounts” in “Users” in the GroupWise 6.5 Administration Guide. Group Wise engine; administration engine. Invalid path specified. The specified path exists; however, it is not a directory. Enter a new path, or remove the invalid path. DB08 Non-unigue name Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Non-unique name. The specified name (object.po.domain) conflicts with an existing user, resource, group, or nickname. Specify a new, unique name. Dxxx Engine Error Codes 105 DB09 User owns resource Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: Action: Group Wise engine; administration engine. User owns a resource. The specified user cannot be deleted or moved because he or she owns a resource. Remove the resource. See “Deleting a Resource” in “Resources” in the GroupWise 6.5 Administration Guide. Reassign the resource to another owner. See “Changing a Resource's Owner” in “Resources” in the GroupWise 6.5 Administration Guide. Ifthis error occurs after removing resources from a user to be deleted or moved, the change might not yet have replicated through the system. Wait for replication to occur or manually synchronize the resource(s) and user. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide. Rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DBOA Record not found Source: Explanation: Possible Cause: Action: Action: Action: Group Wise engine; administration engine. Record not found. Cannot find a record that was previously in the database. The record might have been deleted. Check Pending Operations to see if the command is still awaiting execution. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide. Retry the command. Make sure the record was replicated throughout the system. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide. DBOB Required field empty Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Required field empty. A required field has no value. Supply a value for all required fields. DBOC Cannot close database Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. Error closing database. An error was encountered while attempting to close the database. Check the network connection to the database location. DBOE Insufficient memory to initialize database Source: Group Wise engine; administration engine. 106 GroupWise 6.5 Troubleshooting 1: Error Messages Explanation: Possible Cause: Action: Database initialization failure. The database failed to initialize due to insufficient memory. ConsoleOne reguires at least 500 KB of available RAM. Check the amount of available memory and reconfigure your system if necessary. DBOF Domain not found Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; administration engine. Domain not found. Cannot find the specified domain. Make sure that the domain exists and that the domain name is correct. In ConsoleOne, browse to and right-click the Domain object, then click Properties. If this error occurs from the POA, the post office database (wphost.db) might be damaged so that valid domain information is not available. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DB10 Post office not found Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Post office not found. Cannot find the specified post office. Make sure that the post office exists and that the post office name is correct. In ConsoleOne, browse to and right-click the Post Office object, then click Properties. DB11 Unexpected error Source: Action: GroupWise engine; administration engine. See “Dxxx Unexpected error” on page 121. DB12 Maximum number of objects per post office reached Source: Explanation: Possible Cause: Action: Action: Action: GroupWise engine; administration engine. No more file ID combinations exist for the post office. The maximum user limit has been reached for this post office. The maximum number of FID combinations is approximately 46,000 per post office. Delete obsolete users. See “Removing GroupWise Accounts” in “Users” in the Group Wise 6.5 Administration Guide. Remove unneeded resources. See “Deleting a Resource” in “Resources” in the GroupWise 6.5 Administration Guide. Create additional post offices. See “Creating a New Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. DB16 WP Office 3.1 host already exists in specified directory Source: GroupWise engine; administration engine. Dxxx Engine Error Codes 107 Explanation: WordPerfect* Office 3.1 host exists. Possible Cause: WordPerfect Office 3.1 host already exists in the specified directory. Action: Select a new directory or remove the WordPerfect Office 3.1 host. Group Wise 6.x is not compatible with WordPerfect Office 3.1. DB17 Domain already exists in specified directory Source: GroupWise engine; administration engine. Explanation: Directory exists. Possible Cause: A domain already exists in the specified directory. Action: Specify a new domain directory or remove the existing domain. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. DB19 Local post office not found Source: GroupWise engine; administration engine. Explanation: No local post office record found. Possible Cause: GroupWise was unable to find a local post office. The post office database (wphost.db) might have been damaged. Action: Validate the post office database and rebuild if necessary. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DB1A Insufficient administrative rights to perform operation Source: GroupWise engine; administration engine. Explanation: No administrative rights to perform action. Possible Cause: The current domain has no administrative rights to perform the specified action for the selected record. Action: Connect to the GroupWise system that owns this record. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. DB1B Message Transfer Agent not installed Source: GroupWise engine; administration engine. Explanation: The MTA is not installed. Possible Cause: The MTA is not installed, or the MTA record is missing from the database. Action: Set up the MTA. See “Installing GroupWise Agents” in the GroupWise 6.5 Installation Guide. DB1C Invalid object name Source: GroupWise engine; administration engine. Explanation: Invalid object. Possible Cause: An invalid object name was specified for an administrator, group name, or other object. Action: Make sure the specified object ID is correct. 108 GroupWise 6.5 Troubleshooting 1: Error Messages DB1D Cannot delete post office Source: GroupWise engine; administration engine. Explanation: Error deleting post office. Possible Cause: You do not have sufficient rights to perform the operation. Action: Make sure you have rights to delete files and directories by checking rights for file and directory removal. Possible Cause: The post office directory or files in that directory are in use by another user. Action: Check the open/lock activity on files. DB1F Cannot delete current domain Source: GroupWise engine; administration engine. Explanation: Error deleting current domain. Possible Cause: The attempt to delete the current domain failed. Action: Connect to the primary domain. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then delete the secondary domain from the primary domain. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Action: Ifthe current domain is the primary domain, you cannot delete it unless you delete all secondary domains first (meaning that you want to delete your entire Group Wise system) or you designate a different domain as the primary domain. See “Converting a Secondary Domain to a Primary Domain” in “Domains” in the Group Wise 6.5 Administration Guide. DB20 Unexpected error Source: GroupWise engine; administration engine. Action: See “Dxxx Unexpected error” on page 121. DB21 Database inconsistency detected Source: GroupWise engine; administration engine. Explanation: Database invalid or damaged. Possible Cause: The database is invalid. Action: Rebuild the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DB23 Password incorrect Source: GroupWise engine; administration engine. Explanation: Invalid password. Action: Enter the correct password. Dxxx Engine Error Codes 109 DB24 Invalid link Source: Explanation: Action: Group Wise engine; administration engine. A link between domains is invalid. Select a valid link type and link protocol for the domain link. See “Editing a Domain Link” in “Domains” in the GroupWise 6.5 Administration Guide. DB25 Duplicate domain name Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Duplicate domain name. The name of the external domain being merged conflicts with the name of an existing local domain. The names of all primary and secondary domains must be unique in both systems when merging systems. Remove one of the duplicate domains. See “Deleting a Domain” in “Domains” in the Group Wise 6.5 Administration Guide. DB26 Secondary domains exist Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Secondary domains exist. Multiple local domains were found in an external domain being merged. Release all secondary domains from the domain to be merged, or release the domain to be merged from its owning primary domain. See “Merging with GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide. DB29 Invalid character Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; administration engine. Invalid character. Invalid character in a domain, post office, or object name. Check the contents ofthe name strings for invalid characters. Do not use any ofthe following characters in GroupWise object names: Space Period . At-sign @ Asterisk (*) Comma , Colon : Double guote Parentheses ( ) Braces { } ASCII characters 0-13 If this error occurs when trying to synchronize users through the GroupWise Gateway to Lotus Notes*, users might be defined under the gateway, rather than in a foreign domain. Define Lotus Notes users in a foreign domain. See “Connecting to Non-GroupWise Messaging Systems” in the GroupWise 6.5 Multi-System Administration Guide. 110 GroupWise 6.5 Troubleshooting 1: Error Messages DB2A Invalid name Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. Invalid name. An invalid or restricted name has been specified. Enter a valid name. DB2B Non-unique entry Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Non-unique entry. A new entry conflicts with an existing entry in an index that must be unique. This can occur with a user's network ID. Check the network ID for uniqueness on the post office where the user will reside. DB2C Invalid post office database Source: Explanation: Action: GroupWise engine; administration engine. Invalid post office database (wphost.db). Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. DB2D Platform error Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Wrong platform. No valid path could be found for the current platform type. Enter a path for the current platform. DB2E Link record not found Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. No link record exists. No link record has been defined between an external domain to be merged and any local domain. Define a link record between an external domain to be merged and any local domain. See “Merging with GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide. DB2F Correct database type not found Source: Explanation: Possible Cause: Action: Action: GroupWise engine; administration engine. No database exists. Specified database type does not exist in the specified directory. Check the domain path. In ConsoleOne, browse to and right-click the Domain object, then click Properties. Check the setting of the /home switch in the MTA startup file. See “Using MTA Startup Switches” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. Dxxx Engine Error Codes 111 DB30 Gateway directory not found Source: Explanation: Action: Group Wise engine; administration engine. Gateway directory does not exist. Check the specified gateway directory path and make sure the requested gateway is installed. For a list of gateways, see GroupWise 6.x Gateways (http://www.novell.com/documentation/ gw6xgate/index.html). GroupWise 5.5 gateways can be used with GroupWise 6.x. DB31 Required field missing or empty Source: Explanation: Action: GroupWise engine; administration engine. A required field is missing or empty. Provide a value for the required field(s). DB32 Required field missing Source: Explanation: Action: Group Wise engine; administration engine. A required field is missing. Check the record for a missing required field. DB33 Cannot open all post offices Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise engine; administration engine. Unable to open all post offices. There are more post offices defined than the operating system file handles allow. All directory synchronized commands will be performed through the MTA for the closed post offices. The link to the post office has been lost. Reestablish the link to the post office. See “Strategies for Message Delivery Problems” in GroupWise 6.5 Troubleshooting 2: Solutions to Common Problems. DB34 Time zone definition not found Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. No time zone defined. Unable to find a time zone definition for the current domain or post office. Select a time zone in the Identification page for the current domain or post office in ConsoleOne. See “Time Zones” in “System” in the GroupWise 6.5 Administration Guide DB35 No pending operation for record Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. No pending operation for record. The pending operation has been completed. Refresh the list of pending operations. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide. 112 GroupWise 6.5 Troubleshooting 1: Error Messages DB37 Cannot delete current domain Source: Explanation: Action: Action: GroupWise engine; administration engine. Cannot delete the current domain. Connect to the primary domain. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then delete the secondary domain from the primary domain. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Ifthe current domain is the primary domain, you cannot delete it unless you delete all secondary domains first (meaning that you want to delete your entire GroupWise system) or you designate a different domain as the primary domain. See “Converting a Secondary Domain to a Primary Domain” in “Domains” in the GroupWise 6.5 Administration Guide. DB38 Cannot delete domain that has post offices Source: Explanation: Possible Cause: Action: Action: GroupWise engine; administration engine. Post offices exist for this domain. An attempt was made to delete a domain that has post offices assigned to it. Move the post offices to another domain. See “Moving a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. Then delete the domain after it is empty. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Delete the post offices. See “Deleting a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. Then delete the domain after it is empty. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. DB39 Domain database not found Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; administration engine. Database is not available. No domain database (wpdomain.db) was found; however, arecover.ddb file was found. The database is currently being rebuilt. Allow the rebuild operation to finish. A database rebuild failed. Rename recover.ddb to wpdomain.db in the domain directory, then rerun the rebuild. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DB3A Cannot delete domain that has links Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Domain has indirect links. Cannot delete the domain because it is used in indirect routing. Reconfigure domain links before deletingthe domain. See “Editing a Domain Link” in “Domains” in the GroupWise 6.5 Administration Guide. DB3B Remote management message sent Source: GroupWise engine; administration engine. Dxxx Engine Error Codes 113 Explanation: Action: Remote management message sent. None. This is not an error. It is a notification by the program that the operation to be performed has been sent to the parent domain. DB3C Domain database in use Source: Explanation: Possible Cause: Action: Action: Group Wise engine; administration engine. Exclusive open error. An exclusive open for a domain to be merged or released failed because the domain is already in use. Have all administrators exit the domain database (wpdomain.db) before running the merge or release. Stop the MTA in the domain to be merged or released. DB3D Database sorting language changed Source: Explanation: Action: Group Wise engine; administration engine. Database language has changed. Rebuild the database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DB3F Cannot delete required field Source: Explanation: Action: GroupWise engine; administration engine. Cannot remove a required field. You must supply valid data for all required fields. DB40 Cannot delete gateway used in link Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Gateway links exist. The gateway you are attempting to delete is used in a gateway link. Reconfigure the links before deleting the gateway. See “Editing a Domain Link” in “Domains” in the GroupWise 6.5 Administration Guide. DB41 Database does not match domain or post office Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Incorrect database path The database found at the specified path does not match the specified domain/post office name. Enter the correct path. DB42 Information lost during recovery Source: Explanation: Group Wise engine; administration engine. Information lost. 114 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Some records were lost during the recover operation. You might want to rebuild the database at this time. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DB43 Maximum number of open post offices reached Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. Maximum number of post offices are opened. You have tried to open too many post offices. Close one or more post offices. See “Disabling a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. DB45 GroupWise system not found Source: Explanation: Action: Action: GroupWise engine; administration engine. No system found. Verify the path to the domain database (wpdomain.db). Make sure you are logged in to the server where the GroupWise system resides. DB46 Path too long Source: Explanation: Action: DB47 Invalid area Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. Path too long. You can map a drive to a lower level. Group Wise engine; administration engine. Invalid BLOB area specified. ConsoleOne is unable to copy the GroupWise client view files from the software distribution directory into the post office directory structure. Make sure the software distribution directory has been created in your GroupWise system. See “Software Directory Management” in “System” in the GroupWise 6.5 Administration Guide and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. DB48 Cannot delete domain that has links Source: Explanation: Possible Cause: Action: Possible Cause: Group Wise engine; administration engine. System link exists. You are trying to delete a domain that is specified as the link domain for an external system. Remove the external system or specify a different external domain as the link for the system. See “Using Direct Links” in “Connecting to GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide. You are trying to delete a domain that is set up for external system synchronization. Dxxx Engine Error Codes 115 Action: Remove the external system synchronization entry, then delete the domain. See “Using Direct Links” in “Connecting to GroupWise 5.x and 6.x Systems” in the Group Wise 6.5 Multi-System Administration Guide. DB49 Cannotuse limited visibility distribution list as administrator Source: Explanation: Action: Action: Group Wise engine; administration engine. The selected distribution list cannot be used for the administrator because it is not visible to all users in your Group Wise system. Create a new distribution list to use as the administrator that contains only users that can be visible throughout your GroupWise system. For information about changing distribution list properties, see “Creating and Managing Distribution Lists” in “Distribution Lists, Groups, and Organizational Roles” in the GroupWise 6.5 Administration Guide. Change the visibility of the selected distribution list to system so that all users can see it. DB4A External sync message from unknown system Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; administration engine. An external synchronization message was received from a system that the local GroupWise system cannot identify. The local GroupWise system is not set up to synchronize with the system that sent the synchronization message. Configure the local GroupWise system for external synchronization with that system. See “Exchanging Information Between Systems” in “Connecting to GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide. The external synchronization record in the domain database has been damaged. Delete the external synchronization record. In ConsoleOne, click Tools > GroupWise System Operations > External System Synchronization. Select an external system, then click Delete > Close. Exit and restart the MTA and POA. Re-create the external synchronization record. See “Exchanging Information Between Systems” in “Connecting to GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide. DB4B Cannot delete Internet domain name that is still referenced Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. The specified Internet domain name is being referenced in a system, domain, post office, or user. You are trying to delete an Internet domain record that is still in use. Change or delete the Internet domain association. See “Internet-Style Addressing” in “System” in the GroupWise 6.5 Administration Guide. DB4D Database recovery required to update database structure Source: Explanation: Possible Cause: Group Wise engine; administration engine. The database needs to be recovered. The database dictionaries (*.dc files) are newer than the current database, so a recover is needed to update the database. 116 GroupWise 6.5 Troubleshooting 1: Error Messages Action: The admin thread of the POA or MTA should take care of this recovery automatically. If not, perform the recovery manually. See “Recovering Domain or Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. DB4E Cannot delete default gateway Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. The gateway is used in default routing. You are trying to delete a Group Wise Internet Agent object that is used as the default gateway for routing Internet messages. Select a different Internet Agent as the default gateway for Internet messages. See “Internet-Style Addressing” in “System” in the GroupWise 6.5 Administration Guide. DB4F Cannot delete POA that performs message transfer Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. The POA is used as the message transfer recipient for its post office. You are trying to delete a a POA thatis part ofthe TCP/IP link between the post office and domain through which messages arrive in the post office. Set up a different POA to provide the link to the domain MTA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. After another POA has been set up to provide the link with the MTA, the original POA can be deleted. DB50 Access to this library has been enabled by WebPublisher Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. An action cannot be completed because of how the library is configured. A library cannot be deleted because it is configured for access by WebPublisher. Remove the WebPublisher access to the library. See “Modifying WebPublisher Settings” in “WebAccess” in the GroupWise 6.5 Administration Guide. Then delete the library. DB51 Required network address information is missing Source: Explanation: Possible Cause: Action: Action: Action: Action: GroupWise engine; administration engine. An action cannot be completed because of insufficient configuration information. An agent has not been properly configured with an IP address or TCP port. The POA is not properly configured. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. The MTA is not properly configured. See “Changing the Link Protocol between Domains” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. The Internet Agent is not properly configured. In ConsoleOne, browse to and right-click the GWIA object, then click Properties. Click Post Office Links, then correct the link information as needed. See “Internet Agent” in the GroupWise 6.5 Administration Guide. The WebAccess Agent is not properly configured. See “Managing Access to Post Offices” in “WebAccess” in the GroupWise 6.5 Administration Guide. Dxxx Engine Error Codes 117 DB52 Required path information is missing Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. An action cannot be completed because of insufficient configuration information. A domain or post office has not been properly configured with the path to the directory where the domain or post office is located. Check the UNC path information provided for the domain or post offices. See “Editing Domain Properties” in “Domains” or “Editing Post Office Properties” in “Post Offices” in the GroupWise 6.5 Administration Guide. DB53 No message transfer POA has been selected Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. An action cannot be completed because of insufficient configuration information. A post office has been configured with a TCP/IP link to its domain, but no POA has been selected to provide the link to the MTA. Configure the link between the POA and the MTA. See “Editing a Post Office Link” in “Domains” in the GroupWise 6.5 Administration Guide. DB55 No POA is available for client/server Source: Explanation: Possible Cause: Action: GroupWise engine; administration engine. An action cannot be completed because of incorrect configuration. A post office has been configured for client/server access mode, but no POA has been configured for client/server processing. Configure a POA for client/server mode. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. DB56 Specified e-mail address conflicts with the address of an existing gateway alias Source: Possible Cause: Action: GroupWise engine; administration engine. You are creating or modifying a gateway alias in such a way that its new name conflicts with an existing gateway alias. Choose a different name for the new gateway alias. Check for existing names first. See “Email Address Lookup” in “System” in the GroupWise 6.5 Administration Guide. DB57 Specified e-mail address conflicts with the address of an existing user Source: Possible Cause: Action: Group Wise engine; administration engine. You are creating, modifying, or moving a user in such a way that its new name conflicts with an existing user name. Choose a different name for the new user. Check for existing names first. See “Email Address Lookup” in “System” in the Group Wise 6.5 Administration Guide. DB58 Specified e-mail address conflicts with an address from a post office alias record Source: Group Wise engine; administration engine. 118 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: You are creating or modifying a post office alias in such a way that its new name conflicts with an existing post office alias. Choose a different name for the new post office alias. Check for existing names first. See “Email Address Lookup” in “System” in the GroupWise 6.5 Administration Guide. DB59 This GroupWise administration version is older than the minimum allowed by the system administrator Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. Although you can start ConsoleOne, the GroupWise snap-ins are out of date. In ConsoleOne, the Lock Out Older GroupWise Administration Snapins option has been selected under Tools > GroupWise System Operations > System Preferences > Admin Lockout Settings and you are trying to run ConsoleOne with a version of the snap-ins that is too old. Update the GroupWise snap-ins. See “ConsoleOne” in “Installing a Basic GroupWise System” in the GroupWise 6.5 Installation Guide. DB60 The LDAP server is being used for eDirectory synchronization Source: Explanation: Possible Cause: Action: Group Wise engine; administration engine. An MTA that performs eDirectory user synchronization obtains its eDirectory information from a server that is also being used in your GroupWise system as an LDAP server. You are trying to delete an LDAP server that is being used for eDirectory user synchronization as well as for LDAP. Reconfigure eDirectory synchronization. See “Using eDirectory User Synchronization” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. Then delete the LDAP server. DEO2 Cannot perform delayed action request Source: Explanation: Possible Cause: Action: Group Wise engine; data store and deferment. Error in defer routine. Unable to perform delayed action request. Insufficient memory. Wait and retry the operation later. DE05 Unexpected error Source: Action: GroupWise engine; data store and deferment. See “Dxxx Unexpected error” on page 121. DF10 Required file or directory missing Source: Explanation: Possible Cause: Action: Group Wise engine; mailbox/library maintenance. Path error. If this error occurs from the POA, the path specified by the /home switch might be incorrect. Check the /home setting in the POA startup file. Make sure the specified path exists. Make sure the path is provided in the format required for the platform on which the POA is running. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Dxxx Engine Error Codes 119 Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: NetWare Note: On a NetWare server, make sure the grpwise.ncf file contains the correct information. The ngwguard.dc file is missing from the post office directory. Copy the ngwguard.dc file from another post office or from the po subdirectory of the software distribution directory. Mailbox/Library Maintenance or GWCheck has been run more that 26 times in less than 2 weeks, so all possible temporary file names are already used and a new backup file cannot be created. Check for backup user databases (userxxx.db) files with extensions *.dba through *.dbz. If found, move these backup databases to another directory, then try Mailbox/Library Maintenance or GWCheck again. If no userxxx.db file exists (that is, only backup files exist), rename the most recent backup (for example, userxxx.dbz) to userxxx.db. The post office has been created in the root directory of a NetWare volume. Move all post office directories and files into a subdirectory off the root. See “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Adjust the path to the post office in the post office Identification page in ConsoleOne. DF15 Records lost during rebuild Source: Explanation: Possible Cause: Action: GroupWise engine; mailbox/library maintenance. The POA has been unable to rebuild a database. An administrative message requesting a rebuild in the POA input queue is damaged. Rename POA input queue (wpcsout). Start the POA. This recreates the input queue. Repair the database again. See “Maintaining Domain and Post Office Databases” and “Maintaining User/ Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. DF17 Cannot create required directory Source: Explanation: Possible Cause: Action: Action: GroupWise engine; mailbox/library maintenance. The POA cannot create one or more directories required for processing messages. The POA has insufficient rights to create the directory. Make sure the POA has the necessary network rights to access the directories in the post office. See “Creating a NetWare Account for Agent Access (Optional)” in “Installing GroupWise Agents” in the GroupWise 6.5 Installation Guide. 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” the GroupWise 6.5 Administration Guide. DF1C Document storage area definitions are not identical Source: Explanation: GroupWise engine; mailbox/library maintenance. The location of the document storage area, as stored in the post office database (wphost.db), does not match the guardian database (ngwguard.db). The error message includes the conflicting locations. 120 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Modify the UNC path to the document storage area as needed so that the post office database and the guardian database are both updated with the same current information. Ifthe information looks correct as is, simply delete and retype one character so that the correct information is written out to all affected databases. See “Managing Document Storage Areas” in “Libraries and Documents” in the Group Wise 6.5 Administration Guide. DF27 Invalid NSWCHECK.DB database migration level Source: GroupWise engine; mailbox/library maintenance. Explanation: The GWCheck database (ngwcheck.db) contains invalid information. Action: Delete the GWCheck database, then rerun GWCheck or Mailbox/Library Maintenance. DF28 Failure using the NGWCHECK.DB database Source: GroupWise engine; mailbox/library maintenance. Explanation: The GWCheck database (ngwcheck.db) cannot be accessed by GWCheck. Action: Delete the GWCheck database, then rerun GWCheck or Mailbox/Library Maintenance. Dxxx Unexpected error Source: GroupWise engine. Explanation: An engine error has occurred for which Group Wise does not have a specific error message. Action: Exit and then restart the Group Wise client Dxxx Engine Error Codes 121 122 GroupWise 6.5 Troubleshooting 1: Error Messages Exxx Engine Error Codes Range: + E50x + ESlx + E52x + E5xx + E80x + E8lx + E82x + E584x Range: E50x “E501 Document version not available” on page 125 “E503 Unexpected error” on page 125 “E507 Unexpected error” on page 125 “E508 Unexpected error” on page 125 “ES0A Unexpected error” on page 125 “E50B Unexpected error” on page 126 “E50C Unexpected error” on page 126 “ESOD Maximum number of libraries per post office reached” on page 126 “E50E Unexpected error” on page 126 Range: E51x “E511 Document version available” on page 126 “E512 Invalid user ID” on page 126 “E513 Unexpected error” on page 127 “E514 Document version must be checked out and in by same user” on page 127 “E515 Cannot delete last version of document” on page 127 “E516 Unexpected error” on page 127 “E517 Unexpected error” on page 127 “E51B Access to feature denied” on page 127 “E51C Disk space limit exceeded” on page 127 Range: E52x Exxx Engine Error Codes 123 “E520 Unexpected error” on page 128 “E522 Library not empty” on page 128 “E523 Document not modified” on page 128 “E524 Document not available for synchronization to server” on page 128 “E525 Cannot delete lookup table; it is not empty” on page 128 “E526 Cannot delete lookup table; it is in use” on page 128 “E527 Cannot create library; record already exists” on page 129 “E528 Cannot transfer data to server” on page 129 “E529 All document blob areas full” on page 129 “E52A Document not available” on page 129 Range: E5xx “E700 Invalid Address Book record” on page 129 “E716 Personal Address Book memory error” on page 130 Range: E80x “E801 Unexpected error” on page 130 “E803 Unexpected error” on page 130 “E804 Unexpected error” on page 130 “E805 Unexpected error” on page 130 “E806 Unexpected error” on page 130 “E807 Unexpected error” on page 130 “E808 Unexpected error” on page 130 “E809 Unexpected error” on page 131 “E80C Unexpected error” on page 131 “E80D Unexpected error” on page 131 “E80F Unexpected error” on page 131 Range: E81x “E810 Unexpected error” on page 131 “E811 Unexpected error” on page 131 “E812 Unexpected error” on page 131 “E813 Unexpected error” on page 131 “E814 Unexpected error” on page 131 “E815 Unexpected error” on page 131 “E816 Insufficient rights to perform operation” on page 132 “E818 Unexpected error” on page 132 Range: E82x “E820 Invalid attribute value” on page 132 “E821 Unexpected error” on page 132 “E823 Unexpected error” on page 132 “E824 Unexpected error” on page 132 124 GroupWise 6.5 Troubleshooting 1: Error Messages “E82B Unexpected error” on page 132 “E82C Unexpected error” on page 132 “E82E Unexpected error” on page 133 “E82F Unexpected error” on page 133 Range: E84x “E848 Unexpected error” on page 133 E501 Document version not available Source: GroupWise® engine; document management. Explanation: Document version not available. Possible Cause: The document is currently in use. Action: Have the user who retrieved the document version close it. Possible Cause: The document is currently checked out. Action: Have the user who checked it out check it back in. Look up “documents, checking in” in Group Wise client Help. Possible Cause: The document is neither in use nor checked out, but is erroneously marked as such. This situation can arise because: + A user opened the document with a non-integrated application. A non-integrated application cannot check the document back into the GroupWise library when the user closes the document. * A user's workstation went down while the document was open. Action: Manually reset the document status. Look up “document, status” in GroupWise client Help. E503 Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 133. E507 Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 133. E508 Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 133. E50A Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 133. Exxx Engine Error Codes 125 E50B Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 133. E50C Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 133. E50D Maximum number of libraries per post office reached Source: GroupWise engine; document management. Explanation: Maximum libraries reached. Possible Cause: The maximum number of libraries allowed per post office has been reached. Each post office can have as many as 256 libraries. A user attempted to create the 257th library. Action: Delete any unnecessary libraries on the post office. Then create the new library. See “Creating and Managing Libraries” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. Action: Create the new library on another post office. E50E Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 133. E511 Document version available Source: GroupWise engine; document management. Explanation: Version is available. Possible Cause: The user is attempting to check in a document version that is not checked out, or to end access to a version that is not in use. Action: Do not attempt to check in or end access to a version that is already available. E512 Invalid user ID Source: GroupWise engine; document management. Explanation: The user ID on a document is not valid. Possible Cause: User information on the document has been damaged. Action: Repair the document information in the library. See “Maintaining Library Databases and Documents” in “Databases” in the GroupWise 6.5 Administration Guide. Action: Run GWCheck on the library. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. Possible Cause: A user tried to start the GroupWise client as a resource, that is, using the /@u-userID startup switch and specifying a resource rather than a user. Action: None. You cannot start the GroupWise client as a resource. You must use a valid user ID. 126 GroupWise 6.5 Troubleshooting 1: Error Messages E513 Unexpected error Source: Action: GroupWise engine; document management. See “Exxx Unexpected error” on page 133. E514 Document version must be checked out and in by same user Source: Explanation: Possible Cause: Action: GroupWise engine; document management. User IDs do not match. The user is attempting to check in or close a document version using a different user ID than the one used to check it out. A document version must be checked in or closed by same user who checked it out or opened it. Log in to Group Wise as the user who checked out or opened the document version, then check in or close the document. Look up “documents, checking in” in Group Wise client Help. You can find out who originally checked out or opened the document by checking its activity log. Look up “activity logs” in Group Wise client Help. E515 Cannot delete last version of document Source: Explanation: Action: GroupWise engine; document management. Cannot delete last version. Delete the entire document, not just the version. Look up “documents, deleting” in Group Wise client Help. E516 Unexpected error Source: Action: GroupWise engine; document management. See “Exxx Unexpected error” on page 133. E517 Unexpected error Source: Action: GroupWise engine; document management. See “Exxx Unexpected error” on page 133. E51B Access to feature denied Source: Explanation: Possible Cause: Action: GroupWise engine; document management. Access to requested feature denied. The user is attempting to use a document management feature that is not available to this user on this library. Ifthe user should be allowed to use this feature, grant the appropriate library membership rights. See “Managing Library Access” in “Libraries and Documents” in the Group Wise 6.5 Administration Guide. E51C Disk space limit exceeded Source: Explanation: GroupWise engine; document management. The user has exceeded his or her limit of disk space in the library. Exxx Engine Error Codes 127 Possible Cause: Action: The user is trying to add or modify a document and has run out of space in the library. The user must delete some documents or versions in order to free up disk space. E520 Unexpected error Source: Action: GroupWise engine; document management. See “Exxx Unexpected error” on page 133. E522 Library not empty Source: Explanation: Possible Cause: Action: GroupWise engine; document management. Library not empty. Group Wise cannot perform the requested operation until the library is empty. Delete all documents from the library. Look up “documents, deleting” in Group Wise client Help. E523 Document not modified Source: Explanation: Possible Cause: Action: GroupWise engine; document management. Document not modified. The document has not been modified and does not need to be sent to the server. Make changes to the document, then save the document. E524 Document not available for synchronization to server Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise engine; document management. Document not available for synchronization. The document is currently in use. Close the document. The document is archived. Restore the document. See “Restoring Archived Documents” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. E525 Cannot delete lookup table; it is not empty Source: Explanation: Possible Cause: Action: GroupWise engine; document management. Lookup table not empty. Cannot delete the lookup table because it is not empty. Delete all entries from the lookup table, then retry the operation. See “Customizing Document Properties” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide for information about lookup tables. E526 Cannot delete lookup table; it is in use Source: Explanation: GroupWise engine; document management. Lookup table in use by a library. 128 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: The lookup table cannot be deleted because it is being used by a library. Remove all library references to the lookup table, then retry the operation. See “Customizing Document Properties” in “Libraries and Documents” in the Group Wise 6.5 Administration Guide for information about lookup tables. E527 Cannot create library; record already exists Source: Explanation: Action: GroupWise engine; document management. Library already exists. Use a unigue library name to create the library. See “Creating and Managing Libraries” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. E528 Cannot transfer data to server Source: Explanation: Possible Cause: Action: GroupWise engine; document management. Transport to a server failed. The system was unable to contact a needed server. Make sure the needed server is up, and that all transport hardware is functioning correctly. E529 All document blob areas full Source: Explanation: Possible Cause: Action: GroupWise engine; document management. All BLOB areas are full. All of the areas that hold binary large objects (BLOBs) are full, so the system was unable to create anew BLOB. Create a new library. See “Creating and Managing Libraries” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. E52A Document not available Source: Explanation: Possible Cause: Action: GroupWise engine; document management. The document cannot be restored because it is no longer available on disk. The document has been moved from the library archive to a backup medium. Move the document back into the library so it is available to users. See “Restoring Archived Documents” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. To see where the document belongs, right-click the document reference in the GroupWise client, then click Properties. Click Version, then check the current location and current filename information. E700 Invalid Address Book record Source: Explanation: Possible Cause: GroupWise engine; Personal Address Book. The POA could not access a user's Personal Address Book. The POA is attempting to perform nightly user upkeep for a new user that has not yet used the Group Wise client, which means that the Personal Address Book does not yet exist. Exxx Engine ErrorCodes 129 Action: None. After the user starts the Group Wise client and sends or receives a message, the Personal Address Book will be created and the POA will no longer encounter the problem. Action: Ifthe error persists when the Personal Address Book already exists, see “8101 Memory error” on page 15. E716 Personal Address Book memory error Source: GroupWise engine; Personal Address Book. Explanation: An action involving the Personal Address Book could not be performed due to insufficient memory. Action: Exit some programs so that more memory is available. Action: Restart the workstation where the error is occurring. E801 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E803 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E804 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E805 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E806 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E807 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E808 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. 130 GroupWise 6.5 Troubleshooting 1: Error Messages E809 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E80C Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E80D Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E80F Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E810 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E811 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E812 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E813 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E814 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E815 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. Exxx Engine Error Codes 131 E816 Insufficient rights to perform operation Source: Explanation: Possible Cause: Action: Group Wise engine; object framework. Security access denied. User does not have rights to perform this operation on this object. Have the document owner grant you rights. Look up “documents, permission to access” in Group Wise client Help. Also see “Managing Library Access” in “Libraries and Documents” in the Group Wise 6.5 Administration Guide. E818 Unexpected error Source: Action: Group Wise engine; object framework. See “Exxx Unexpected error” on page 133. E820 Invalid attribute value Source: Explanation: Possible Cause: Action: Group Wise engine; object framework. Validation error when creating or updating a document. The user supplied a value for a document property that does not match the valid values specified by the corresponding lookup table. For example, the value was too large or too small. Retry the operation with valid values for document properties. E821 Unexpected error Source: Action: Group Wise engine; object framework. See “Exxx Unexpected error” on page 133. E823 Unexpected error Source: Action: Group Wise engine; object framework. See “Exxx Unexpected error” on page 133. E824 Unexpected error Source: Action: Group Wise engine; object framework. See “Exxx Unexpected error” on page 133. E82B Unexpected error Source: Action: GroupWise engine; object framework. See “Exxx Unexpected error” on page 133. E82C Unexpected error Source: Action: Group Wise engine; object framework. See “Exxx Unexpected error” on page 133. 132 GroupWise 6.5 Troubleshooting 1: Error Messages E82E Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E82F Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. E848 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 133. Exxx Unexpected error Source: GroupWise engine. Explanation: An engine error has occurred for which GroupWise does not have a specific error message. Action: Exit and then restart the GroupWise client. Exxx Engine Error Codes 133 134 GroupWise 6.5 Troubleshooting 1: Error Messages Fxxx Engine Error Codes Range: + FOOx + FOlx + F02x + F03x + F04x + FO5x + F06x + F07x + F08x + FO9x * FOAx + FOBx + FOCx + Flxx Range: F00x “F000 Memory error” on page 139 “F007 End of command reached unexpectedly” on page 139 “F008 Missing parenthesis in search command” on page 139 “F009 Missing operator in search command” on page 139 “FOOA Switch at end of search command ignored” on page 139 “FOOB Unknown switch in search command” on page 139 “F00C Ambiguous switch; supply more characters” on page 139 Range: FO1x “F010 Search cancelled” on page 139 “F012 File I/O error” on page 140 “F013 Database error” on page 140 “F014 Database error” on page 140 “F016 Database error” on page 140 “F018 Number contains non-numeric characters” on page 140 Fxxx Engine Error Codes 135 “F019 Search switch requires *=n*” on page 140 “FOLA Document summary field name or number required” on page 140 “FO1B Unknown field in search command” on page 141 “FOIC Ambiguous field; supply more characters” on page 141 “FO1D Empty quotation marks not allowed” on page 141 “FOIE /nowildcard and /prefix cannot be used together” on page 141 “FO1F Invalid syntax in search query” on page 141 Range: F02x “F020 Date expected” on page 141 “F021 Dates of range in wrong order” on page 141 “F022 Missing switch after ’/’” on page 141 “F023 Word missing between operators” on page 141 “F026 Database error” on page 141 “FO2A Search query must specify words to search for” on page 142 “FO2D Missing word after operator” on page 142 “FO2E Invalid date” on page 142 “FO2F Word too long for search” on page 142 Range: F03x “F030 Empty parentheses not allowed” on page 142 “F037 Memory error” on page 142 “FO3E Memory error” on page 142 Range: F04x “F045 Unexpected error” on page 142 “F046 File I/O error” on page 142 “F047 File I/O error” on page 142 “F048 File I/O error” on page 143 “F049 File I/O error” on page 143 “FO4A File I/O error” on page 143 “FO4C File I/O error” on page 143 “FOAD File I/O error” on page 143 “FO4E File not found during QuickFinder indexing” on page 143 “FO4F File I/O error” on page 143 Range: F05x “F050 Database error” on page 143 “F051 Database error” on page 143 “F052 Database error” on page 143 “F056 Database error” on page 144 Range: F06x 136 GroupWise 6.5 Troubleshooting 1: Error Messages “F060 Database error” on page 144 “F061 Database error” on page 144 “F062 Database error” on page 144 “F063 Database error” on page 144 “F064 Database error” on page 144 “F065 Database error” on page 144 “F066 Database error” on page 144 “F067 Database error” on page 144 “F068 Database error” on page 144 “F069 Database error” on page 145 “FO6A Database error” on page 145 “FO6B Database error” on page 145 “F06C Database error” on page 145 “FO6D Database error” on page 145 “FO6E Database error” on page 145 “FO6F Database error” on page 145 Range: F07x “F070 Database error” on page 145 “F071 Database error” on page 145 “F072 Database error” on page 145 “F073 Database error” on page 146 “F074 Database error” on page 146 “F075 Database error” on page 146 “F076 Database error” on page 146 “F077 Database error” on page 146 “F078 Database error” on page 146 “F079 Database error” on page 146 “F07A Database error” on page 146 “F07B Database error” on page 146 “F07C Database error” on page 146 “F07D Database error” on page 147 “FOTE Database error” on page 147 “F07F Database error” on page 147 Range: F08x “F080 Database error” on page 147 “F082 Database error” on page 147 “F083 Database error” on page 147 “F084 Database error” on page 147 “F085 Database error” on page 147 “F086 Database error” on page 147 “F087 Database error” on page 147 “F088 Database error” on page 148 “F089 Database error” on page 148 Fxxx Engine Error Codes 137 “FO8A Database error” on page 148 “FO8SB Database error” on page 148 “F08D Database error” on page 148 “FOSE Database error” on page 148 “FO8F Database error” on page 148 Range: F09x “F090 Database error” on page 148 “F091 Database error” on page 148 “F092 Database error” on page 148 “F093 Database error” on page 149 “F094 Database error” on page 149 “F095 Database error” on page 149 “F096 Database error” on page 149 “F097 Database error” on page 149 “F098 Database error” on page 149 “F099 Database error” on page 149 “FO9A Database error” on page 149 “FO9B Memory error” on page 149 Range: FOAx “FOA1 Memory error” on page 149 Range: FOBx “FOB2 Memory error” on page 150 “FOB5 File I/O error” on page 150 “FOB9 Unexpected error” on page 150 “FOBA Database error” on page 150 “FOBB Database error” on page 150 “FOBC Database error” on page 150 “FOBD Database error” on page 150 “FOBE Database error” on page 150 “FOBF Database error” on page 150 Range: FOCx “FOCO Database error” on page 150 “F0C2 Database error” on page 151 “F0C4 Database error” on page 151 Range: F1xx “F101 Cannot connect to remote server” on page 151 “F102 Cannot connect to remote server” on page 151 “F103 Cannot connect to remote server” on page 151 138 GroupWise 6.5 Troubleshooting 1: Error Messages “F104 Cannot connect to remote server” on page 151 “F105 Cannot connect to remote server” on page 151 “F106 Cannot connect to remote server” on page 151 “F107 Cannot connect to remote server” on page 151 “F108 Cannot connect to remote server” on page 151 F000 Memory error Source: Group Wise? engine; QuickFinder™. Action: See “F0xx Memory error” on page 152. F007 End of command reached unexpectedly Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. F008 Missing parenthesis in search command Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. F009 Missing operator in search command Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. FOOA Switch at end of search command ignored Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. FOOB Unknown switch in search command Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. FOOC Ambiguous switch; supply more characters Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. F010 Search cancelled Source: GroupWise engine; QuickFinder. Explanation: Search cancelled. Action: Search was cancelled at user's request. Fxxx Engine Error Codes 139 F012 File I/O error Source: GroupWise engine; QuickFinder. Explanation: The QuickFinder process used by the Find feature cannot access a required file. Possible Cause: The QuickFinder index is damaged. Action: Rebuild the index of the database where the error occurred. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide. Possible Cause: The disk is full where the QuickFinder index is located, so the QuickFinder process cannot write more information to disk. Action: Free up disk space. See “Managing Database Disk Space” in “Databases” in the GroupWise 6.5 Administration Guide. Possible Cause: You do not have rights to the location where the QuickFinder index is located. Action: Check your access rights. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide. Action: In ConsoleOne®, you can set the proper user rights for all users in a post office or for an individual user. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide. F013 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error” on page 152. F014 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error” on page 152. F016 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F018 Number contains non-numeric characters Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. F019 Search switch requires ’=n’ Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. FO1A Document summary field name or number required Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. 140 GroupWise 6.5 Troubleshooting 1: Error Messages FO1B F01C FO1D FO1E FOAF F020 F021 F022 F023 F026 Unknown field in search command Source: GroupWise engine; OuickFinder. Action: See “FOxx Query syntax error” on page 152. Ambiguous field; supply more characters Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Empty quotation marks not allowed Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Inowildcard and /prefix cannot be used together Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Invalid syntax in search query Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Date expected Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Dates of range in wrong order Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Missing switch after ’/’ Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Word missing between operators Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Fxxx Engine Error Codes 141 FO2A FO2D FO2E FO2F F030 F037 FO3E F045 F046 F047 142 Search query must specify words to search for Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Missing word after operator Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Invalid date Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Word too long for search Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Empty parentheses not allowed Source: GroupWise engine; QuickFinder. Action: See “FOxx Query syntax error” on page 152. Memory error Source: GroupWise engine; QuickFinder. Action: See “FOxx Memory error” on page 152. Memory error Source: GroupWise engine; QuickFinder. Action: See “FOxx Memory error” on page 152. Unexpected error Source: GroupWise engine; QuickFinder. Action: See “FOxx Unexpected error” on page 153. File I/O error Source: GroupWise engine; QuickFinder. Action: See “FOxx File I/O error” on page 152. File I/O error Source: GroupWise engine; QuickFinder. Action: See “FOxx File I/O error” on page 152. GroupWise 6.5 Troubleshooting 1: Error Messages F048 File I/O error Source: GroupWise engine; OuickFinder. Action: See “FOxx File I/O error” on page 152. F049 File I/O error Source: GroupWise engine; QuickFinder. Action: See “FOxx File I/O error” on page 152. FO4A File I/O error Source: GroupWise engine; QuickFinder. Action: See “FOxx File I/O error” on page 152. FO4C File I/O error Source: GroupWise engine; QuickFinder. Action: See “FOxx File I/O error” on page 152. FO4D File I/O error Source: GroupWise engine; OuickFinder. Action: See “FOxx File I/O error” on page 152. FO4E File not found during QuickFinder indexing Source: GroupWise engine; QuickFinder. Action: See “FOxx File I/O error” on page 152. F04F File I/O error Source: GroupWise engine; OuickFinder. Action: See “FOxx File I/O error” on page 152. F050 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F051 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F052 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Fxxx Engine ErrorCodes 143 F056 F060 F061 F062 F063 F064 F065 F066 F067 F068 144 Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Memory error” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. GroupWise 6.5 Troubleshooting 1: Error Messages F069 Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. FO6A Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. FO6B Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. FO6C Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. FO6D Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. FO6E Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. FO6F Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F070 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F071 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F072 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Fxxx Engine Error Codes 145 F073 F074 F075 F076 F077 F078 F079 FO7A F07B F07C 146 Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. GroupWise 6.5 Troubleshooting 1: Error Messages F07D F07E FO7F F080 F082 F083 F084 F085 F086 F087 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Fxxx Engine Error Codes 147 F088 Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. F089 Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. FOBA Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F08B Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. F08D Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. FO8E Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. FO8F Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F090 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F091 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. F092 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. 148 GroupWise 6.5 Troubleshooting 1: Error Messages F093 F094 F095 F096 F097 F098 F099 FO9A FO9B FOA1 Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Database error Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Memory error Source: GroupWise engine; QuickFinder. Action: See “FOxx Memory error” on page 152. Memory error Source: GroupWise engine; QuickFinder. Action: See “FOxx Memory error” on page 152. Fxxx Engine Error Codes 149 FOB2 Memory error Source: Action: FOB5 File I/O error Source: Action: GroupWise engine; OuickFinder. See “F0xx Memory error” on page 152. GroupWise engine; QuickFinder. See “FOxx File I/O error” on page 152. F0B9 Unexpected error Source: Action: Group Wise engine; QuickFinder. See “FOxx Unexpected error” on page 153. FOBA Database error Source: Action: Group Wise engine; QuickFinder. See “FOxx Database error (index)” on page 152. FOBB Database error Source: Action: Group Wise engine; QuickFinder. See “FOxx Database error (index)” on page 152. FOBC Database error Source: Action: GroupWise engine; OuickFinder. See “FOxx Database error (index)” on page 152. FOBD Database error Source: Action: GroupWise engine; QuickFinder. See “FOxx Database error (index)” on page 152. FOBE Database error Source: Action: GroupWise engine; QuickFinder. See “FOxx Database error (index)” on page 152. FOBF Database error Source: Action: GroupWise engine; QuickFinder. See “FOxx Database error (index)” on page 152. FOCO Database error Source: Action: Group Wise engine; QuickFinder. See “FOxx Database error (index)” on page 152. 150 GroupWise 6.5 Troubleshooting 1: Error Messages FOC2 Database error Source: GroupWise engine; OuickFinder. Action: See “FOxx Database error (index)” on page 152. FOC4 Database error F101 F102 F103 F104 F105 F106 F107 F108 Source: GroupWise engine; QuickFinder. Action: See “FOxx Database error (index)” on page 152. Cannot connect to remote server Source: GroupWise engine; NetWare” remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 153. Fxxx Engine Error Codes 151 FOxx Query syntax error Source: Explanation: Action: FOxx File I/O error Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: Group Wise engine; QuickFinder. While using the Find feature in the Group Wise client, you received a message indicating a problem with the syntax of your search query. Correct the query syntax, then retry the operation. Look up “find, using operators and conditions” in GroupWise client Help. Group Wise engine; QuickFinder. The QuickFinder process used by the Find feature cannot access a required file. The QuickFinder index is damaged. Rebuild the index of the database where the error occurs. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide. The disk is full where the QuickFinder index is located, so the QuickFinder process cannot write more information to disk. Free up disk space. You do not have rights to the location where the QuickFinder index is located. Check your access rights. In ConsoleOne®, you can set the proper user rights for all users in a post office or for an individual user. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide. FOxx Database error Source: Explanation: Action: Action: Group Wise engine; QuickFinder. Generic database error. Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. FOxx Database error (index) Source: Explanation: Action: Group Wise engine; QuickFinder. Generic database error. Rebuild the index of the database where the error occurs. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide. FOxx Memory error Source: Explanation: Action: Action: Group Wise engine; QuickFinder. Generic QuickFinder memory error. Exit and restart the GroupWise client. Free up more memory before running the Group Wise client. 152 GroupWise 6.5 Troubleshooting 1: Error Messages FOxx Unexpected error Source: GroupWise engine; QuickFinder. Explanation: An engine error has occurred for which GroupWise does not have a specific error message. Action: Exit and then restart the GroupWise client. F1xx Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Explanation: GroupWise cannot connect to a remote server where needed information is located. Possible Cause: The POA can no longer access the remote server where a document storage area is located. Action: Make sure the remote server is running. Action: Make sure the POA startup file contains the /user and /password or /dn startup switches so the POA can log in to the remote server. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Action: In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object. Action: Make sure the user the POA is logging in as has sufficient rights to access the needed location on the remote server. See “Creating a NetWare Account for Agent Access (Optional)” in “Installing GroupWise Agents” in the GroupWise 6.5 Installation Guide. Fxxx Engine ErrorCodes 153 154 GroupWise 6.5 Troubleshooting 1: Error Messages Agent Error Messages The GroupWise® agents are responsible for message transfer and delivery throughout your GroupWise system. This part of Troubleshooting 1: Error Messages helps you resolve agent error messages that appear in agent log files and other places where agent status information is displayed. + “Post Office Agent Error Messages” on page 157 + “Message Transfer Agent Error Messages” on page 169 + “Internet Agent Error Messages” on page 189 + “WebAccess Agent Error Messages” on page 195 + “Monitor Agent and Application Error Messages” on page 205 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) Agent Error Messages 155 156 GroupWise 6.5 Troubleshooting 1: Error Messages Post Office Agent Error Messages “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: Admin database for post office could not be recovered” on page 158 Administrator record not found in database” on page 158 Application connection table full” on page 158 Authentication failed for the above object” on page 158 Cannot access remote post office; retrying” on page 159 Cannot access remote post office; user ID switch is missing” on page 159 Cannot find the help file” on page 159 Client/server login failed; no user ID supplied” on page 159 Configured address may not match actual address” on page 159 Database language has been updated; please rebuild this database” on page 160 Disk is full; turning disk logging off’ on page 160 Error creating...” on page 160 Error creating file; turning disk logging off” on page 160 Error initializing communications protocol” on page 161 Error initializing HTTP” on page 161 Error listening for connection” on page 161 Error opening listener port” on page 161 Error putting item in gueue” on page 161 Error writing to file; turning disk logging off’ on page 161 Failed to redirect user; missing host configuration” on page 162 File I/O error” on page 162 Host refused connection” on page 162 HTTP port nn is already in use” on page 162 Internal UDP port is unusable” on page 162 Listen port already in use” on page 163 Low disk space for OuickFinder indexing” on page 163 Machine appears to have TCP/IP incorrectly configured” on page 163 Not enough disk space for OuickFinder indexing” on page 163 Not enough memory to complete operation” on page 163 One or more connections to a remote storage area have been lost and could not be reestablished” on page 164 “GWPOA: “GWPOA: “GWPOA: “GWPOA: “GWPOA: Physical connection table full” on page 164 Possibly damaged blob in database” on page 164 Possibly dangerous message; temporarily suspending dispatcher” on page 164 Reached inbound connections limit” on page 165 StartServiceCtrlDispatcher failed when attempting to start Windows agent service” on page 165 Post Office Agent Error Messages 157 “GWPOA: The Windows agent service fails to set service status; service stopped” on page 165 “GWPOA: The Windows agent service fails to initialize memory system; service stopped” on page 165 “GWPOA: Timed out waiting for end-of-file confirmation” on page 165 “GWPOA: Transport header build failed” on page 166 “GWPOA: Unable to add additional message handler; maximum reached” on page 166 “GWPOA: Unable to change all configuration options” on page 166 “GWPOA: Unable to load viewer” on page 166 “GWPOA: Unable to remove document storage area” on page 166 “GWPOA: Windows NT Version 3.50; TCP/IP may not function” on page 167 GWPOA: Admin database for post office could not be recovered Source: Explanation: Possible Cause: Action: GroupWise® Post Office Agent; admin thread. An attempt to recover the post office database (wphost.db) has failed. The post office database reguires repair beyond that which can be done while in use. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWPOA: Administrator record not found in database Source: Explanation: Possible Cause: Action: Action: GroupWise Post Office Agent; admin thread. The POA admin thread can send a message to an administrator in case of database errors. However, no administrator has been designated. No GroupWise administrator has been set up yet. Set up a GroupWise administrator to receive messages about database errors. See “Notifying the GroupWise Administrator” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Use the /noerrormail switch when starting the POA to turn off administrator messages. GWPOA: Application connection table full Source: Explanation: Possible Cause: Action: GroupWise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication and it has run out of application connections. The POA is very busy. Increase the number of application connections configured for the POA. See “Adjusting the Number of Connections for Client/Server Processing” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Then exit and restart the POA GWPOA: Authentication failed for the above object Source: Explanation: Possible Cause: Action: GroupWise Post Office Agent; admin thread. The POA admin thread attempted to process a record that has the wrong authentication key for the current GroupWise system. The record did not originate in the current GroupWise system, which is a possible security violation. Someone is trying to tamper with your GroupWise system. Check your system security measures. 158 GroupWise 6.5 Troubleshooting 1: Error Messages GWPOA: Cannot access remote post office; retrying Source: Explanation: Possible Cause: Action: GroupWise Post Office Agent. The POA can no longer access its post office. The server where the post office is located is currently down. Wait for the server to come back up, or contact the administrator of that server. GWPOA: Cannot access remote post office; user ID switch is missing Source: Explanation: Possible Cause: Action: Action: Group Wise Post Office Agent. The POA cannot access its post office because it cannot log in to the server where the post office is located. The POA has not been started with the /user or /dn switch. Include the /user and /password, or /dn switches when the POA needs to access a post office on a remote server. See “Using POA Startup Switches” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object. GWPOA: Cannot find the help file Source: Explanation: Action: Group Wise Post Office Agent for Windows. The Help file for the agent is not available. For the name of the Help file the agent is trying to use, see “Agent Installation Directories” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. GWPOA: Client/server login failed; no user ID supplied Source: Explanation: Possible Cause: Action: GroupWise Post Office Agent. The POA cannot communicate with aGroupWise client process that is requesting services because the client is not providing a user ID. The GroupWise client was not started with the needed user ID information. Use the /@u startup switch to make sure the client has the correct user ID information. See “Client” in the GroupWise 6.5 Administration Guide. GWPOA: Configured address may not match actual address Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication, but a mismatch of IP addresses has been detected. DNS is not currently available, so the POA is unable to resolve a host name into its IP address. Make sure DNS is functioning correctly. Or specify the IP address instead ofthe host name when configuring the POA. The POA was started with the wrong /name switch setting, so that it is associated with the wrong configuration information. Make sure the /name switch setting specifies the correct POA configuration. Post Office Agent Error Messages 159 Possible Cause: Action: TCP/IP is not set up correctly on the server where the POA is running. Make sure TCP/IP is set up correctly. GWPOA: Database language has been updated; please rebuild this database Source: Explanation: Action: GroupWise Post Office Agent; admin thread. The post office database (wphost.db) needs to be rebuilt because the language has been changed, which changes the sort order of the users listed in the database. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWPOA: Disk is full; turning disk logging off Source: Explanation: Action: Action: GroupWise Post Office Agent. Logging information to disk has been turned off because there is insufficient disk space to continue writing to the agent log file. See “Using POA Log Files” in “Post Office Agent” in the Group Wise 6.5 Administration Guide. Free up disk space. The agent should resume disk logging after disk space is available. To ensure that disk logging has resumed, check the Logging Level setting in the Log Settings page for the agent in ConsoleOne®. Specify a different location for log files where sufficient disk space is available. GWPOA: Error creating... Source: Explanation: Possible Cause: Action: GroupWise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication. The TCP agent might display a large number of error messages that begin with "Error creating...". Insufficient memory. See “GWPOA: Not enough memory to complete operation” on page 163. GWPOA: Error creating file; turning disk logging off Source: Explanation: Possible Cause: Action: Action: Action: Group Wise agents. Logging information to disk has been turned off because the agent cannot create a new log file. The agent cannot create a file in the location specified by the Log File Path setting on the Log Settings page for the agent in ConsoleOne or specified on the command line using the /log startup switch. See “Using POA Log Files” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Make sure the location exists or specify a more appropriate location. Make sure the agent has rights to create files in the specified location. Start the POA including the /rights switch to determine the specific problem the POA is encountering. Make sure there is available disk space in the specified location. 160 GroupWise 6.5 Troubleshooting 1: Error Messages GWPOA: Error initializing communications protocol Source: Explanation: Possible Cause: Action: Group Wise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication but is unable to establish TCP/IP communication. TCP/IP is not set up correctly on the server where the POA is running. Make sure TCP/IP is set up correctly. GWPOA: Error initializing HTTP Source: Explanation: Action: Group Wise Post Office Agent. The HTTP port the POA is trying to use for its Web console is not responding correctly. Configure the POA to communicate on a different HTTP port. See “Using the POA Web Console” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. GWPOA: Error listening for connection Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication but is unable to connect. TCP/IP is not set up correctly on the server where the POA is running. Make sure TCP/IP is set up correctly. Insufficient memory. See “GWPOA: Not enough memory to complete operation” on page 163. GWPOA: Error opening listener port Source: Explanation: Action: GroupWise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication, but the port it is configured to listen on is already in use by another program. See “8555 Port in use” on page 25. GWPOA: Error putting item in queue Source: Explanation: Action: Group Wise Post Office Agent; TCP agent. The TCP threads are not keeping up with the current workload. Increase the number of TCP handler threads for the POA. See “Adjusting the Number of Connections for Client/Server Processing” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. GWPOA: Error writing to file; turning disk logging off Source: Explanation: Possible Cause: Group Wise Post Office Agent. Logging of information to disk has been turned off because the agent can no longer write to the current log file. See “Using POA Log Files” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. If the log file is located on a server other than the one where the agent is running, that server might be down. Post Office Agent Error Messages 161 Action: Possible Cause: Action: Wait for the server to come back up, or contact the administrator of that server. When the server comes back up, the agent will resume disk logging. The log file has been damaged so the agent can no longer write to it. Remove the damaged log file and turn disk logging back on in the Log Settings page for the agent in ConsoleOne. The agent will create a new log file. You can also use Cycle Log from the POA agent console to start a new log file. GWPOA: Failed to redirect user; missing host configuration Source: Explanation: Action: Group Wise Post Office Agent. The GroupWise client is attempting to contact the POA in client/server mode, but the POA is not set up for client/server communication. Set up the POA for client/server communication. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. GWPOA: File I/O error Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Post Office Agent. The POA cannot access a required file. The POA cannot read its startup file. Check the existence, integrity, and rights of the POA startup file specified in the command to start the POA. See “Installing and Starting the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. The POA cannot view its log file. Check the existence, integrity, and rights of the POA log file. See “Using POA Log Files” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. GWPOA: Host refused connection Source: Explanation: Action: GroupWise Post Office Agent; message transfer protocol. The POA is configured to communicate with the MTA by way of TCP/IP. The server where the MTA is located has refused the POA’s request for a connection. Check the TCP/IP configuration of the server to which the POA must connect. GWPOA: HTTP port nn is already in use Source: Explanation: Action: Group Wise Post Office Agent. The HTTP port the POA is trying to use for its Web console is already in use by another program. Configure the POA to communicate on a different HTTP port. See “Using the POA Web Console” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. GWPOA: Internal UDP port is unusable Source: Explanation: Possible Cause: Action: Group Wise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication but it cannot access the UDP port of the server where it is trying to run. TCP/IP is not set up correctly on the server where the POA is running. Make sure TCP/IP is set up correctly. 162 GroupWise 6.5 Troubleshooting 1: Error Messages GWPOA: Listen port already in use Source: Explanation: Action: Group Wise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication, but the port it is configured to listen on is already in use by another program. See “8555 Port in use” on page 25. GWPOA: Low disk space for QuickFinder indexing Source: Explanation: Action: GroupWise Post Office Agent. The POA requires at least 20 MB of free disk space to perform QuickFinder™ indexing. This warning appears when disk space drops below 30 MB. The POA performs QuickFinder indexing as specified by the QuickFinder Update Interval setting on the POA Agent Settings page in ConsoleOne or as specified using the /qfinterval startup switch. See “Regulating Indexing” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Free up disk space on the server where the POA is running to eliminate the warning. See “Managing Database Disk Space” in “Databases” in the GroupWise 6.5 Administration Guide. GWPOA: Machine appears to have TCP/IP incorrectly configured Source: Explanation: Possible Cause: Action: Group Wise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication but it is unable to determine the IP address of the server where it is trying to run. TCP/IP is not set up correctly on the server where the POA is running. Make sure TCP/IP is set up correctly, including assignment of an IP address. GWPOA: Not enough disk space for QuickFinder indexing Source: Explanation: Action: Group Wise Post Office Agent. The POA requires at least 20 MB of free disk space to perform QuickFinder indexing. A warning appears when disk space drops below 30 MB. This error appears when free disk space drops below 20 MB. The POA performs QuickFinder indexing as specified by the QuickFinder Update Interval setting on the POA Agent Settings page in ConsoleOne or as specified using the /qfinterval startup switch. See “Regulating Indexing” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Make sure sufficient free disk space is available on the server where the POA is running by the next time the POA needs to perform QuickFinder indexing. GWPOA: Not enough memory to complete operation Source: Explanation: Possible Cause: Action: Action: GroupWise Post Office Agent. Not enough memory is available for the POA to function properly. If the POA cannot start, you might be trying to run the agent in an environment where too few system resources are available. For information about POA memory requirements, see “Group Wise System Requirements” in “Installing GroupWise Agents” in the GroupWise 6.5 Installation Guide. Stop some other programs on the server to free up memory for use by the POA. Add memory to the server to accommodate the POA along with other existing programs. Post Office Agent ErrorMessages 163 Action: Possible Cause: Action: Action: Action: Select a different server to run the POA on, where adeguate resources are available. Ifthe POA starts successfully, then encounters a memory error later during otherwise normal processing, some other program on the server, or another agent thread, might have temporarily used a large guantity of memory. Wait to see if the memory problem resolves itself. The POA will retry its operations and should succeed at a later time, when the other program has released some memory. You can reduce the number of POA threads, which reduces the memory requirements for the POA. You can make the change in ConsoleOne by reducing the Message Handler Threads and/or TCP Handler Threads settings in the POA Agent Settings page. See “Adjusting the Number of POA Threads for Message File Processing” and “Adjusting the Number of Connections for Client/ Server Processing” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Ifthe POA starts successfully but freguently encounters memory errors during later processing, treat the situation as ifthe POA cannot start and see the recommended actions above. GWPOA: One or more connections to a remote storage area have been lost and could not be reestablished Source: Explanation: Possible Cause: Action: Action: Group Wise Post Office Agent. The POA has lost its connection to the server where a document storage area is located. The server where the document storage area is located is down. Wait for the server to come back up. The POA will reconnect automatically when the server is available again. Contact the administrator of that server. GWPOA: Physical connection table full Source: Explanation: Possible Cause: Action: Group Wise Post Office Agent; TCP agent. The POA is configured for TCP/IP communication and it has run out of physical connections. The POA is very busy. Increase the number of physical connections configured for the POA. See “Adjusting the Number of Connections for Client/Server Processing” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Then exit and restart the POA GWPOA: Possibly damaged blob in database Source: Explanation: Possible Cause: Action: Action: Group Wise Post Office Agent During indexing, the POA has encountered a BLOB file that it could not process. The BLOB file is damaged Restore the BLOB file from backup. If the damaged BLOB file cannot be restored, you can delete it to eliminate the error. GWPOA: Possibly dangerous message; temporarily suspending dispatcher Source: Group Wise Post Office Agent 164 GroupWise 6.5 Troubleshooting 1: Error Messages Explanation: Possible Cause: Action: Action: No additional message file processor threads will be started until processing of'the current message file has completed. The current message file is flagged as having caused the POA to shut down in a previous processing attempt. The current message file is damaged. Ifall existing message file processor threads successfully process their message files, the POA will resume normal processing. No action is necessary. If processing of a message file causes the POA to shutdown, do not put message files from the post officexwpcsoutiproblem directory back into the POA input queue. Restart the POA. GWPOA: Reached inbound connections limit Source: Explanation: Action: GroupWise Post Office Agent; message transfer protocol. The POA is configured to communicate with the MTA by way of TCP/IP. The POA has reached the maximum number of inbound connections. None. Connections are automatically released and reopened as processing continues. GWPOA: StartServiceCtrIDispatcher failed when attempting to start Windows agent service Source: Explanation: Possible Cause: Action: Group Wise Post Office Agent for Windows. The Windows POA cannot start its dispatcher thread. The Windows server is not functioning properly. Reboot the Windows server. GWPOA: The Windows agent service fails to set service status; service stopped Source: Explanation: Possible Cause: Action: Group Wise Post Office Agent for Windows. The Windows POA cannot start as a service. The Windows POA cannot communicate with the service control manager (SCM). Reboot the Windows server. GWPOA: The Windows_agent service fails to initialize memory system; service stopped Source: Explanation: Possible Cause: Action: Action: Group Wise Post Office Agent for Windows. The Windows POA cannot start as a service. The Windows POA has insufficient memory resources. Reboot the Windows server. Run fewer programs on the server. GWPOA: Timed out waiting for end-of-file confirmation Source: Explanation: Possible Cause: GroupWise Post Office Agent; message transfer protocol. The POA is configured to communicate with the MTA by way of TCP/IP. The MTA has stopped responding in the middle of a communication. The MTA is running on an overburdened server, so it cannot respond to the POA in a timely manner. Post Office Agent ErrorMessages 165 Action: Action: Possible Cause: Action: Add resources to the MTA server so that the MTA can function properly. Move the MTA to a different server where more resources are available. See “Moving the MTA to a Different Server” in “Message Transfer Agent” in the Group Wise 6.5 Administration Guide. The server where the MTA is running has gone down. Check the status of the MTA server. Reboot if necessary. GWPOA: Transport header build failed Source: Explanation: Possible Cause: Action: Group Wise Post Office Agent; message transfer protocol. The POA is configured to communicate with the MTA by way of TCP/IP. The POA was unable to create a packet of information to send to the MTA. Insufficient memory. See “GWPOA: Not enough memory to complete operation” on page 163. GWPOA: Unable to add additional message handler; maximum reached Source: Explanation: Action: Group Wise Post Office Agent. The maximum number of message handler threads for the POA is 32. You cannot create any more message handler threads for this POA. You can run another POA for the post office on the same server if the server has sufficient resources. You can run another POA for the post office on a different server if your network can handle the additional traffic. See “Configuring a Dedicated Message File Processing POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. GWPOA: Unable to change all configuration options Source: Explanation: Action: Group Wise Post Office Agent. POA configuration settings have been changed in ConsoleOne, but some cannot be put into effect until the POA is restarted. Exit and restart the POA. GWPOA: Unable to load viewer Source: Explanation: Possible Cause: Action: GroupWise Post Office Agent for Windows. The POA cannot run the program used to view agent log files or edit agent startup files. The viewer program is not available on the current path or is incorrectly specified. The default viewer used by the POA is Notepad, which is typically available. You can change the viewer specification by selecting View Log Files in the Windows POA agent console and changing the information in the Viewer field. Check the viewer and path specified in the View Log Files dialog box in the POA agent console. GWPOA: Unable to remove document storage area Source: Group Wise Post Office Agent. 166 GroupWise 6.5 Troubleshooting 1: Error Messages Explanation: The POA cannot delete the document storage area. Possible Cause: The library database (dmsh.db) is damaged, so that the POA cannot read the information necessary to delete the storage area. Action: Repair the library. See “Maintaining Library Databases and Documents” in “Databases” in the GroupWise 6.5 Administration Guide. GWPOA: Windows NT Version 3.50; TCP/IP may not function Source: GroupWise Post Office Agent for Windows. Explanation: The POA might not be able to successfully use the TCP/IP capabilities of Windows NT 3.50. Action: Upgrade to at least NT 3.51. Post Office Agent Error Messages 167 168 GroupWise 6.5 Troubleshooting 1: Error Messages Message Transfer Agent Error Messages “GWMTA: Access denied” on page 170 “GWMTA: Admin database for domain cannot be recovered” on page 171 “GWMTA: Administrator record not found in database” on page 171 “GWMTA: Authentication failure for the above object” on page 171 “GWMTA: Cannot attach to server or volume” on page 171 “GWMTA: Cannot create a new receiver thread” on page 172 “GWMTA: Cannot create/read/write files/directories” on page 172 “GWMTA: Cannot find domain database” on page 172 “GWMTA: Cannot find startup file” on page 173 “GWMTA: Cannot move files” on page 173 “GWMTA: Cannot proceed; incompatible GWENN4.NLM” on page 173 “GWMTA: Cannot proceed; insufficient memory available” on page 173 “GWMTA: Cannot read domain database; insufficient memory” on page 174 “GWMTA: Cannot read post office database; insufficient memory” on page 174 “GWMTA: Cannot route message(s); out of memory” on page 174 “GWMTA: Cannot start server; insufficient memory available” on page 174 “GWMTA: Closed for inbound traffic” on page 174 “GWMTA: Command line parameter /home is required” on page 175 “GWMITA: Configuration error; unsupported 3.1 domain” on page 175 “GWMTA: Could not launch the editor” on page 175 “GWMITA: Database language has been updated; please rebuild this database” on page 175 “GWMTA: Disk full; disk logging turned off” on page 175 “GWMTA: Domain database error; circular transfer domain link” on page 175 “GWMTA: Domain database error; transfer domain not found” on page 176 “GWMTA: Domain database open failed” on page 176 “GWMTA: Domain database read error” on page 176 “GWMTA: Domain now closed” on page 176 “GWMTA: Domain open failed” on page 176 “GWMT4A: Error initializing HTTP” on page 177 “GWMTA: Error validating post office members” on page 177 “GWMITA: Expired en route to destination” on page 177 “GWMTA: File create error; disk logging turned off” on page 177 “GWMTA: File write error; disk logging turned off” on page 178 “GWMTA: File not found” on page 178 “GWMTA: Gateway now closed” on page 178 “GWMTA: Gateway open failed” on page 178 “GWMTA: Host refused connection” on page 178 Message Transfer Agent Error Messages 169 “GWMTA: IDomain now closed” on page 178 “GWMTA: Incompatible GWENVIA.DLL; GWMTA cannot continue” on page 179 “GWMTA: Insufficient disk space” on page 179 “GWMTA: Insufficient memory” on page 179 “GWMTA: Insufficient memory to read/process startup file” on page 180 “GWMTA: Internet mail to address is undeliverable because no default GWIA is configured” on page 180 “GWMTA: Invalid /log parameter” on page 181 “GWMTA: Invalid /work parameter” on page 181 “GWMITA: Link or transport down” on page 181 “GWMTA: Logging permanently suspended; insufficient memory” on page 181 “GWMITA: Login not completed; timeout” on page 182 “GWMTA: Login to directory failed” on page 182 “GWMTA: Maximum number of inbound connections reached” on page 182 “GWMTA: No agent record found” on page 182 “GWMTA: No domain record found” on page 183 “GWMTA: No path configured” on page 183 “GWMTA: No post offices found” on page 183 “GWMTA: No response from peer” on page 183 “GWMTA: No sender IDomain; Internet address lookup not attempted” on page 183 “GWMTA: Path to domain database (/home) is invalid or blocked” on page 184 “GWMTA: Post office database open failed; insufficient memory” on page 184 “GWMTA: Post office database read error” on page 184 “GWMTA: Post office now closed” on page 185 “GWMTA: Post office open failed” on page 185 “GWMITA: Received unsupported request; request ignored” on page 185 “GWMTA: StartServiceCtrlDispatcher failed when attempting to start Windows agent service” on page 185 “GWMTA: Target queue temporarily locked” on page 185 “GWMTA: The Windows agent service fails to set service status; service stopped” on page 186 “GWMTA: The Windows. agent service fails to initialize memory system; service stopped” on page 186 “GWMTA: Timed out waiting for end-of-file confirmation” on page 186 “GWMTA: Unable to initialize message log database” on page 186 U “GWMTA: Unable to open connection; no response” on page 186 “GWMTA: Unable to register with SNMP agent” on page 186 “GWMTA: Unable to retrieve TCP/IP address” on page 187 “GWMTA: Undefined link” on page 187 “GWMTA: Unknown connection header received” on page 187 “GWMTA: U “GWMTA: U “GWMTA: Waiting for busy listen socket to become available” on page 188 nknown destination” on page 187 nsupported 3.1 domain” on page 187 GWMTA: Access denied Source: GroupWise® Message Transfer Agent; last closure reason. 170 GroupWise 6.5 Troubleshooting 1: Error Messages Explanation: Possible Cause: Action: A domain or post office is closed because the MTA cannot access the database (wpdomain.db or wphost.db) at the location. An MTA is already running against the domain database. Do not try to run more than one MTA for a domain. GWMTA: Admin database for domain cannot be recovered Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; admin thread. An attempt to recover the domain database (wpdomain.db) has failed. The domain database requires repair beyond that which can be done while in use. Rebuild the domain database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWMTA: Administrator record not found in database Source: Explanation: Possible Cause: Action: Action: GroupWise Message Transfer Agent; admin thread. The MTA admin thread can send a message to an administrator in case of database errors. However, no administrator has been designated. No Group Wise administrator has been set up yet. Set up a Group Wise administrator to receive messages about database errors. See “Notifying the Domain Administrator” in “Message Transfer Agent” inthe GroupWise 6.5 Administration Guide. Use the /noerrormail switch when starting the MTA to turn off administrator messages. GWMTA: Authentication failure for the above object Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; admin thread. The MTA admin thread attempted to process a record that has the wrong authentication key for the current Group Wise system. The record did not originate in the current Group Wise system, which is a possible security violation. Someone is trying to tamper with your Group Wise system. Check your system security measures. GWMTA: Cannot attach to server or volume Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; last closure reason. A domain or post office is closed because the NetWare® MTA cannot access the server or volume where the domain or post office is located. The domain or post office is located on a different server from where the MTA is running and the MTA has not been configured with user information to enable it to log in. Make sure the MTA startup file includes the /user and /password, or /dn switches, so the MTA can log into the remote server. Make sure the user and password information is correct and current. Make sure the information is formatted correctly. In some configurations, you might need to specify a distinguished name (for example, user.org_unit.org) for the /user switch, rather than just a simply user ID. In some configurations, you might need to include the type (for example, .CN=user.org unit.org). Message Transfer Agent Error Messages 171 Action: Possible Cause: Action: Ifthe MTA still cannot log in to the remote server after appropriate user information has been supplied, start the MTA with /tracelogin-2 to display NetWare® error codes. Look up the error codes at Novell Error Codes (http://www.novell.com/documentation/nwec/index.htm]). The NetWare MTA cannot log into the server where a domain or post office is located because all available NetWare licenses are already in use. Increase the number of licenses on the server. GWMTA: Cannot create a new receiver thread Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; message transfer protocol. The MTA cannot create a new receiver thread. Insufficient memory. See “GWMTA: Insufficient memory” on page 179. GWMTA: Cannot create/read/write files/directories Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Group Wise Message Transfer Agent; last closure reason. A domain or post office is closed because the MTA cannot write files into its output gueue in the closed domain or post office. The user specified with the /user switch in the MTA startup file does not have sufficient rights to create files in the domain or post office directory. Make sure the user the MTA is logging in as has sufficient rights in the domain or post office directory. See “Creating a NetWare Account for Agent Access (Optional)” in “Installing Group Wise Agents” in the GroupWise 6.5 Installation Guide. The MTA cannot write message files across a mapped or UNC link into the MTA input gueue in a closed domain (domain\wpcsin directory) or a closed post office (post officetwpcsout directory) because the directory is inaccessible or damaged. Make sure the input gueue directory exists and that the MTA has sufficient rights to create files there. If necessary, and if the input queue subdirectories are empty, you can rename the original input queue directory and then manually recreate it, along with its required subdirectories. The server where the closed domain or post office is located does not have sufficient disk space for the MTA to create message files. Free up disk space. NetWare Note: On a NetWare server, you might need to purge deleted files to free up disk space. The name of the domain directory contains more than 8 characters. Rename the domain directory. The MTA currently does not support long names. Also update the domain directory path in ConsoleOne®. The network type specified for the domain is incorrect. Check the network type selected for the domain. In ConsoleOne, right-click the Domain object, then click Properties. Make sure the Network Type field is correct for the MTA running for the domain. GWMTA: Cannot find domain database Source: GroupWise Message Transfer Agent. 172 GroupWise 6.5 Troubleshooting 1: Error Messages Explanation: Possible Cause: Action: The MTA cannot access a domain database (wpdomain.db) in the directory specified by the /home switch. The MTA has been able to access the directory specified by the /home switch, but it cannot locate a valid domain database in that directory. Make sure the location provided by the /home startup switch specifies a valid domain directory. See “Using MTA Startup Switches” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. GWMTA: Cannot find startup file Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA cannot start because it cannot locate or read its startup file. The name of the startup file as provided in the command to start the MTA is incorrect. Make sure you are providing the name of the startup file correctly. See “Installing and Starting the MTA” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. The startup file is not located on the current path. Specify the full path to the startup file in the command to start the MTA. GWMTA: Cannot move files Source: Explanation: Explanation: Action: GroupWise Message Transfer Agent; last closure reason. The MTA cannot move message files from its input queue (domain\wpcsin or post_office\wpcsin) to its in progress" queue (gwinprog). Insufficient disk space on the server where the mslocal directory structure is located. Free up disk space so the MTA has sufficient space to process message files. GWMTA: Cannot proceed; incompatible GWENN4.NLM Source: Explanation: Possible Cause: Action: Possible Cause: Action: NetWare GroupWise Message Transfer Agent. The MTA cannot start because the agent engine (gwenn4.nlm) is not compatible with the MTA itself (gwmta.nlm). Some agent files have been updated but the update is not complete. When updating the agents, make sure all agent files are installed. For a complete list of files, see “Agent Installation Directories” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. The agent engine (gwenn4.nlm) was not unloaded prior to updating the agent software. The agent software cannot be successfully updated if the agent engine is still loaded. After exiting all the agents, unload the gwenn4.nlm, then perform the update. See the “Updating Secondary Domains” in “Updating Your GroupWise 6.x System to Version 6.5” inthe GroupWise 6.5 Installation Guide. GWMTA: Cannot proceed; insufficient memory available Source: Action: GroupWise Message Transfer Agent. See “GWMTA: Insufficient memory” on page 179. Message Transfer Agent Error Messages 173 GWMTA: Cannot read domain database; insufficient memory Source: GroupWise Message Transfer Agent. Explanation: The MTA cannot access its domain database (wpdomain.db). Possible Cause: Insufficient memory. Action: See “GWMTA: Insufficient memory” on page 179. Possible Cause: The domain database has been damaged. Action: Rebuild the domain database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWMTA: Cannot read post office database; insufficient memory Source: GroupWise Message Transfer Agent. Explanation: The MTA cannot access the post office database (wphost.db). Possible Cause: Insufficient memory. Action: See “GWMTA: Insufficient memory” on page 179. Possible Cause: The post office database has been damaged. Action: Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWMTA: Cannot route message(s); out of memory Source: GroupWise Message Transfer Agent. Action: See “GWMTA: Insufficient memory” on page 179. GWMTA: Cannot start server; insufficient memory available Source: GroupWise Message Transfer Agent. Action: See “GWMTA: Insufficient memory” on page 179. GWMTA: Closed for inbound traffic Source: GroupWise Message Transfer Agent. Explanation: The MTA is not accepting inbound connections on its TCP/IP link. Possible Cause: The MTA has been manually suspended. Action: Resume the MTA for the domain. See “Suspending/Resuming MTA Processing for a Location” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. Possible Cause: If you are running multiple MTAs on the same server, the same TCP port might be in use by more than one MTA. NetWare Note: On a NetWare server, you would see the message "Waiting for busy listen socket to become available." Action: Check the setup of the MTAs. Make sure each MTA is using a unique port. See “Configuring the MTA for TCP/IP” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. 174 GroupWise 6.5 Troubleshooting 1: Error Messages GWMTA: Command line parameter /home is reguired Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Message Transfer Agent. The MTA cannot start without a /home switch specifying the domain directory. The /home switch has not been provided in the command to start the MTA. Add the /home switch to the command to start the MTA. See “Using MTA Startup Switches” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. The agent was not able to access the startup file where the /home switch was specified. Make sure the startup file exists. GWMTA: Configuration error; unsupported 3.1 domain Source: Action: GroupWise Message Transfer Agent. See “GWMTA: Unsupported 3.1 domain” on page 187 GWMTA: Could not launch the editor Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent for Windows. The MTA cannot run the program used to view agent log files or edit agent startup files. The viewer program is not available on the current path or is incorrectly specified. The default viewer used by the agents is Notepad, which is typically available. You can change the viewer specification by selecting View Log Files in the agent window and changing the information in the Viewer field. Check the viewer and path specified in the View Log Files dialog box in the agent window. GWMTA: Database language has been updated; please rebuild this database Source: Explanation: Action: GroupWise Message Transfer Agent; admin thread. The database needs to be rebuilt because the language has been changed, which changes the sort order of the users listed in the database. Rebuild the database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWMTA: Disk full; disk logging turned off Source: Explanation: Action: Action: Group Wise Message Transfer Agent. Logging information to disk has been turned off because there is insufficient disk space to continue writing to the agent log file. Free up disk space. The agent should resume disk logging after disk space is available. To ensure that disk logging has resumed, check the Logging Level setting in the Log Settings page for the MTA in ConsoleOne. See “Using MTA Log Files” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. Specify a different location for log files where sufficient disk space is available. GWMTA: Domain database error; circular transfer domain link Source: Group Wise Message Transfer Agent. Message Transfer Agent Error Messages 175 Explanation: Possible Cause: Action: The MTA cannot route a message to the domain it is addressed to because available indirect links create a circular reference. Links between domains in your Group Wise system are not set up correctly. Check, and if necessary, adjust the indirect links between domains in your Group Wise system. See “Editing a Domain Link” in “Domains” in the GroupWise 6.5 Administration Guide. GWMTA: Domain database error; transfer domain not found Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA cannot locate the domain to which a message is addressed, nor can it locate an indirect link to that domain. Links between domains in your Group Wise system are not set up correctly. Check, and if necessary adjust, the indirect links between domains in your Group Wise system. See “Link Configuration between Domains and Post Offices” in “Domains” in the GroupWise 6.5 Administration Guide. GWMTA: Domain database open failed Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent. The MTA cannot access the domain database (wpdomain.db). The domain database has been damaged. Rebuild the domain database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWMTA: Domain database read error Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA cannot access its domain database (wpdomain.db). The domain database has been damaged. $ Rebuild the domain database. See “Rebuilding Domain or Post Office Databases” in “Databases’ in the GroupWise 6.5 Administration Guide. GWMTA: Domain now closed Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA has lost its connection to a domain with which it could previously communicate. The server where the domain is located is currently down. Wait for the server to come back up, or contact the administrator of that server. If using TCP/IP communication between domains, TCP/IP might be down. Make sure TCP/IP is running in both domains. GWMTA: Domain open failed Source: Explanation: GroupWise Message Transfer Agent. The MTA in the local domain cannot contact the MTA in a different domain in your GroupWise system. 176 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Possible Cause: Action: Links between the domains are not set up correctly. Check the links between the domains. See “Editing a Domain Link” in “Domains” in the Group Wise 6.5 Administration Guide. The local MTA cannot access the MTA input gueue in the other domain. Check the directory structure of the closed domain. See “Domain Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. GWMTA: Error initializing HTTP Source: Explanation: Action: Group Wise Message Transfer Agent. The HTTP port the MTA is trying to use for its Web console is not responding correctly. Configure the MTA to communicate on a different HTTP port. See “Using the MTA Web Console” in “Message Transfer Agent” in the Group Wise 6.5 Administration Guide. GWMTA: Error validating post office members Source: Explanation: Action: Possible Cause: Action: GroupWise Message Transfer Agent, Novell? eDirectory™ user synchronization. When attempting eDirectory user synchronization, the MTA could not access the user information stored in eDirectory. Look up the NetWare error code that accompanies this error at Novell Error Codes (http:// www.novell.com/documentation/nwec/index.html). The MTA does not have sufficient rights to access the user information in eDirectory. Make sure the MTA is properly set up to perform eDirectory user synchronization. See “Using eDirectory User Synchronization” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. GWMTA: Expired en route to destination Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA was unable to deliver a message because it passed through the maximum of 15 hops without reaching its destination. Links between domains are not set up correctly. Check the links between domains. Look for a more efficient route. See “Link Configuration between Domains and Post Offices” in “Domains” in the GroupWise 6.5 Administration Guide. GWMTA: File create error; disk logging turned off Source: Explanation: Possible Cause: Action: Action: Action: GroupWise Message Transfer Agent. Logging information to disk has been turned off because the MTA cannot create a new log file. The agent cannot create a file in the location specified by the Log File Path setting on the Log Settings page for the agent in ConsoleOne or specified on the command line using the /log startup switch. See “Using MTA Log Files” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. Make sure the location exists or specify another location. Make sure the agent has rights to create files in the specified location. Make sure there is available disk space in the specified location. Message Transfer Agent Error Messages 177 GWMTA: File write error; disk logging turned off Source: GroupWise agents. Explanation: Logging information to disk has been turned off because the agent can no longer write to the current log file. Possible Cause: Ifthe log file is located on a server other than the one where the agent is running, that server might be down. Action: Wait for the server to come back up, or contact the administrator of that server. When the server comes back up, the agent will resume disk logging. Possible Cause: The log file has been damaged so the agent can no longer write to it. Action: Remove the damaged log file and turn disk logging back on in the Log Settings page for the agent in ConsoleOne. See “Using MTA Log Files” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. The agent will create a new log file. You can also use Cycle Log from the MTA agent console to start a new log file. See “Cycling the MTA Log File” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. GWMTA: File not found Source: GroupWise Message Transfer Agent; agent console Explanation: From the MTA agent console, you are trying to edit or view either the MTA log file or startup file and the MTA cannot access it. Action: Verify the existence and rights to the file. GWMTA: Gateway now closed Source: GroupWise Message Transfer Agent. Explanation: The MTA has lost its connection to a gateway with which it could previously communicate Possible Cause: The server where the gateway is located is currently down. Action: Wait for the server to come back up, or contact the administrator of that server. GWMTA: Gateway open failed Source: GroupWise Message Transfer Agent. Explanation: The MTA cannot contact a gateway to which a message needs to be routed. Possible Cause: The MTA cannot access the gateway input queue under the wpgate directory of the domain. Action: Check the directory structure of the closed Internet gateway. GWMTA: Host refused connection Source: GroupWise Message Transfer Agent. Explanation: The MTA is configured to communicate with another MTA or a POA by way of TCP/IP. The server where the other MTA or the POA is located has refused the MTA’s request for a connection. Action: Check the TCP/IP configuration of the server to which the MTA must connect. GWMTA: IDomain now closed Source: GroupWise Message Transfer Agent. 178 GroupWise 6.5 Troubleshooting 1: Error Messages Explanation: Possible Cause: Action: Action: The MTA has lost its connection to a domain across the Internet with which it could previously communicate. The server where the domain is located is currently down. Wait for the server to come back up, or contact the administrator of that server. Make sure the Internet link between domains is set up correctly. See “Internet Agent” in the GroupWise 6.5 Administration Guide. GWMTA: Incompatible GWENV1A.DLL; GWMTA cannot continue Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent for Windows. The MTA cannot start because the agent engine (gwenvla.exe) is not compatible with the MTA itself (gwmta.exe). Some agent files have been updated but the update is not complete. When updating the agents, make sure all agent files are installed. For a complete list, see “Agent Installation Directories” in Group Wise 6.5 Troubleshooting 3: Message Flow and Directory Structure. GWMTA: Insufficient disk space Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA does not have sufficient disk space to write files into its input gueues or holding gueues. The MTA requires at least 1 MB of free disk space to run. One or more locations are closed, resulting in a backlog of messages in the MTA holding gueues in the directory. Resolve the problems with the closed facilities so that normal message flow resumes. See “MTA Status Box Shows a Closed Location” in GroupWise 6.5 Troubleshooting 2: Solutions to Common Problems. Other programs running the same server with the MTA have used up all available disk space. Free up disk space so the MTA can continue processing messages. Check the MTA log file to see which gueue the MTA can no longer write to so you know where more disk space is reguired. See “Using MTA Log Files” in “Message Transfer Agent” in the Group Wise 6.5 Administration Guide. The MTA cannot write message files across a mapped or UNC link into the MTA input gueue in a closed domain (domain\wpcsin directory) or a closed post office (post_office\wpcsin directory) because the directory is damaged. Ifthe input gueue subdirectories are empty, you can rename the original input gueue directory and then manually recreate it, along with its reguired subdirectories. GWMTA: Insufficient memory Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. Not enough memory is available for the MTA to function properly. Ifthe MTA cannot start, you might be trying to run the MTA in an environment where too few system resources are available. For requirements, see “GroupWise System Requirements” in “Installing GroupWise Agents” n the GroupWise 6.5 Installation Guide. Message Transfer Agent Error Messages 179 Action: Action: Action: Possible Cause: Action: Action: Stop some other programs on the server to free up memory for use by the MTA. Add memory to the server to accommodate the MTA along with other existing programs. Select a different server to run the MTA on, where adequate resources are available. See “Moving the MTA to a Different Server” in “Message Transfer Agent” inthe GroupWise 6.5 Administration Guide. Ifthe MTA starts successfully, then encounters a memory error later during otherwise normal processing, some other program on the server, or another agent thread, might have temporarily used a large quantity of memory. Wait to see if the memory problem resolves itself. The MTA will retry its operation and should succeed at a later time, when the other program has released some memory. Ifthe MTA starts successfully but frequently encounters memory errors during later processing, treat the situation as ifthe MTA cannot start and see the recommended actions above. GWMTA: Insufficient memory to read/process startup file Source: Possible Cause: Action: GroupWise Message Transfer Agent. Insufficient memory. See “GWMTA: Insufficient memory” on page 179. GWMTA: Insufficient resources to accept inbound connection Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA cannot start a receiver thread. Insufficient memory. If the problem does not resolve itself in a short time, see “GWMTA: Insufficient memory” on page 179. GWMTA: Insufficient system resources Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA was unable to start another thread. Insufficient memory. If the problem does not resolve itself in a short time, see “GWMTA: Insufficient memory” on page 179. GWMTA: Internet mail to address is undeliverable because no default GWIA is configured Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. A message addressed to a user across the Internet cannot be delivered. A default GroupWise Internet Agent has not been configured. Designate a default Internet Agent. See “Internet-Style Addressing” in “System” in the GroupWise 6.5 Administration Guide. 180 GroupWise 6.5 Troubleshooting 1: Error Messages GWMTA: Invalid /log parameter Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Group Wise Message Transfer Agent. The MTA cannot use the location specified by the /log startup switch to store its log files. The location specified by the /log startup switch does not exist. Check, and if necessary change, the location specified by the /log startup switch when starting the MTA. If the /log switch is not specified, it defaults to the mslocal directory in the directory specified by the /work switch. The location specified by the /log startup switch is on a server that is currently not available. Check the status ofthe server where the specified directory is located. Wait for the server to come back up or contact the administrator of'that server. It is recommended that the /log switch be set to a location local to where the MTA is running to avoid this problem. GWMTA: Invalid /work parameter Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: GroupWise Message Transfer Agent. The MTA cannot use the location specified by the /work startup switch for its mslocal directory. The location specified by the /work startup switch does not exist. Check, and if necessary change, the location specified by the /work startup switch when starting the MTA. Ifthe /work switch is not specified, it defaults to the domain directory. See “Using MTA Startup Switches” in “Message Transfer Agent” in the Group Wise 6.5 Administration Guide. The location specified by the /work startup switch is on a server that is currently not available. Check the status ofthe server where the specified directory is located. Wait for the server to come back up or contact the administrator of'that server. It is recommended that the /work switch be set to a location local to where the MTA is running to avoid this problem. GWMTA: Link or transport down Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA is using TCP/IP to communicate with an MTA or POA and the other agent is not responding. The MTA in the other domain is not properly set up for TCP/IP communication. Check the setup ofthe MTA in the other domain. See “Using TCP/IP Links between Domains” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. The POA in the post office is not properly set up for TCP/IP communication. Check the setup ofthe POA. See “Using TCP/IP Links between a Domain and its Post Offices” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. GWMTA: Logging permanently suspended; insufficient memory Source: Explanation: GroupWise Message Transfer Agent. The MTA could not start a new thread for disk logging. Therefore, disk logging has been turned off. Message Transfer Agent Error Messages 181 Possible Cause: Action: Action: Insufficient memory. See “GWMTA: Insufficient memory” on page 179. After sufficient memory is available, turn disk logging back on in the Log Settings page for the agent in ConsoleOne. See “Using MTA Log Files” in “Message Transfer Agent” in the Group Wise 6.5 Administration Guide. GWMTA: Login not completed; timeout Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; message transfer protocol. An MTA or POA started to reguest TCP/IP communication from the MTA, but stopped responding in the middle of the login process. The server where the other agent was running went down. Check the status of the other server. Reboot if necessary. GWMTA: Login to directory failed Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: GroupWise Message Transfer Agent. The MTA cannot communicate with another domain or post office because it cannot access the server where the domain or post office is located. The /user and /password switches do not provide the correct information for the MTA to log in to the server. Check the settings for the /user and /password switches in the command that starts the MTA. Make sure you can log in to the server using the user name and password the MTA is trying to use. The server where the domain or post office is located is currently down. Wait for the server to come back up or contact the administrator of that server. See also “GWMTA: Cannot attach to server or volume” on page 171. GWMTA: Maximum number of inbound connections reached Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA could not start another thread for an inbound connection. The maximum number of inbound connections as specified by the /tcpinbound startup switch has been reached. The default is 40 inbound connections. Increase the setting of the /tcpinbound switch to allow for more inbound connections. There is no maximum number of inbound connections. They are limited only by available system resources. See “Adjusting the Number of MTA TCP/IP Connections” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. GWMTA: No agent record found Source: Explanation: Possible Cause: Group Wise Message Transfer Agent. The MTA object in the eDirectory tree is missing. When a domain is created, an MTA object is automatically created for it. It might have gotten deleted. 182 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Possible Cause: Action: Check for the MTA object in the domain. Make sure it is configured correctly. See “Configuring the MTA in ConsoleOne” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. The domain database (wpdomain.db) is damaged. Check and, if necessary, repair the domain database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWMTA: No domain record found Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA cannot find the domain record in the domain database (wpdomain.db). The domain database is damaged. Rebuild the domain database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. GWMTA: No path configured Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. Path information for links between domains is missing. Links between domains are not set up correctly. Check the links between domain. See “Editing a Domain Link” in “Domains” inthe GroupWise 6.5 Administration Guide. GWMTA: No post offices found Source: Explanation: Action: GroupWise Message Transfer Agent; eDirectory user synchronization. The MTA has been configured to perform eDirectory user synchronization for adomain which has no post offices and, hence, no users; for example, a routing domain. Remove the domain from the list of domains for which eDirectory user synchronization should be performed. See “Using eDirectory User Synchronization” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. GWMTA: No response from peer Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent; message transfer protocol. The MTA is attempting to communicate with another MTA or a POA by way of TCP/IP, but the other agent does not answer. The server where the other MTA or the POA is located is down. Check the status of the other server. Reboot if necessary. GWMTA: No sender IDomain; Internet address lookup not attempted Source: Explanation: Possible Cause: GroupWise Message Transfer Agent. The address the MTA is trying to resolve does not contain [Domain information. The MTA is configured for GWMTP between GroupWise systems, but the link is not set up properly. Message Transfer Agent Error Messages 183 Action: Action: Correct any problems in the setup of'links between the two systems. See “Using Dynamic Internet Links” in “Connecting to GroupWise 5.x and 6.x Systems” in the Group Wise 6.5 Multi-System Administration Guideguide. Ifthe message is destined for a non-Group Wise system across the Internet, it will be routed through the Group Wise Internet Agent. No action is required, provided a preferred Internet Agent has been designated. See “Internet-Style Addressing” in “System” in the GroupWise 6.5 Administration Guide. GWMTA: Path to domain database (/home) is invalid or blocked Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: GroupWise Message Transfer Agent. The MTA cannot access the domain database (wpdomain.db) in the directory specified by the / home switch. The location specified by the /home startup switch does not exist. Check, and if necessary change, the location specified by the /home startup switch when starting the MTA. It must specify the domain directory. See “Using MTA Startup Switches” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. The location specified by the /home startup switch is on a server that is currently not available. Check the status ofthe server where the specified directory is located. Wait for the server to come back up or contact the administrator of that server. If running the MTA on a Windows server, the location might be on a server that is not currently mapped. Make sure the server where the MTA is running has a drive mapped to the domain directory on the server where the domain is located if it is using a mapped link. See “GWMTA: Cannot attach to server or volume” on page 171. GWMTA: Post office database open failed; insufficient memory Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Message Transfer Agent. The MTA cannot access one of its post office databases (wphost.db). Insufficient memory. See “GWMTA: Insufficient memory” on page 179. The post office database has been damaged. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWMTA: Post office database read error Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA cannot access the post office database (wphost.db). The post office database has been damaged. Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 184 GroupWise 6.5 Troubleshooting 1: Error Messages GWMTA: Post office now closed Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Message Transfer Agent. The MTA has lost its connection to a post office with which is could previously communicate. The server where the post office is located is currently down. Wait for the server to come back up, or contact the administrator of that server. Ifusing TCP/IP communtcation between post offices, TCP/IP might be down. Make sure TCP/IP is running on the servers where the post offices are located. GWMTA: Post office open failed Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA cannot contact the POA in one ofthe local post offices. The MTA cannot access the POA input queue in the post office. Check the directory structure of the closed post office. See “Post Office Directory” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. GWMTA: Received unsupported request; request ignored Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA received an administrative message from GroupWise Administrator that it could not respond to. GroupWise Administrator has been updated, but the GroupWise agent software has not yet been updated. Install the latest version of the GroupWise agent software. See the “Installing the GroupWise 6.5 Software” in “Update” in the GroupWise 6.5 Installation Guide. GWMTA: StartServiceCtrlDispatcher failed when attempting to start Windows agent service Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent for Windows. The Windows MTA cannot start its dispatcher thread. The Windows server 1s not functioning properly. Reboot the Windows server. GWMTA: Target gueue temporarily locked Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA is in the process of clearing out a backlog of messages and is not accepting any additional messages into its gueues. The MTA processes existing messages first, before processing new messages, so that messages arrive in the order in which they were sent. The backlog of messages might have been caused by one or more closed facilities in the domain. Wait until the backlog clears, then the MTA will resume its regular processing of new messages. Backlogged messages are stored in subdirectories of the mslocal directory. Message Transfer Agent Error Messages 185 GWMTA: The Windows agent service fails to set service status; service stopped Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent for Windows. The Windows MTA cannot start as an Windows service. The Windows MTA cannot communicate with the Windows service control manager (SCM). Reboot the Windows server. GWMTA: The Windows agent service fails to initialize memory system; service stopped Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent for Windows. The Windows MTA cannot start as an Windows service. The Windows server has insufficient memory resources available. Reboot the Windows server. Run fewer programs on the Windows server. GWMTA: Timed out waiting for end-of-file confirmation Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent. The MTA is in the process of clearing out a backlog of messages and is not accepting any additional messages into its gueues. The MTA processes existing messages first, before processing new messages, so that messages arrive in the order in which they were sent. The backlog of messages might have been caused by one or more closed facilities in the domain. Wait until the backlog clears, then the MTA will resume its regular processing of new messages. Backlogged messages are stored in subdirectories of the mslocal directory. GWMTA: Unable to initialize message log database Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; message transfer protocol. The MTA was unable to create the database where it stores information about messages waiting for processing in its in progress (gwinprog) queue. the msglog subdirectory of mslocal cannot be created. Insufficient disk space. Free up disk space on the server where the MTA runs. GWMTA: Unable to open connection; no response Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; message transfer protocol. The MTA is attempting to communicate with another MTA or a POA by way of TCP/IP, but the other agent does not answer. The server where the other MTA or the POA is located is down. Check the status of the other server. Reboot if necessary. GWMTA: Unable to register with SNMP agent Source: Explanation: Possible Cause: Action: GroupWise agents. The MTA is unable to contact the SNMP agent on the server where the agent is running. SNMP has not been installed and set up properly on the server. Install SNMP as reguired by the server operating system. 186 GroupWise 6.5 Troubleshooting 1: Error Messages GWMTA: Unable to retrieve TCP/IP address Source: Explanation: Possible Cause: Action: Group Wise Message Transfer Agent. The MTA is configured for GWMTP between GroupWise systems, but the MTA cannot find the IDomain name of the destination system GWMTP is not properly set up between the two Group Wise systems. Correct any problems in the setup of'links between the two systems. See “Using Dynamic Internet Links” in “Connecting to Group Wise 5.x and 6.x Systems” in the Group Wise 6.5 Multi-System Administration Guide. GWMTA: Undefined link Source: Explanation: Action: GroupWise Message Transfer Agent; last closure reason. MTAs cannot communicate because no link has been established between them. Configure a link between the MTAs. See “Changing the Link Protocol between Domains” in “Configuring the MTA” in the GroupWise 6.5 Administration Guide. GWMTA: Unknown connection header received Source: Explanation: Possible Cause: Action: GroupWise Message Transfer Agent; message transfer protocol. The MTA received a request for a TCP/IP connection from a process other than a GroupWise agent. Some non-GroupWise program on the server where the MTA is running is configured to send packets to the port the MTA is configured to listen on. Check the network address information of the MTA. See “Configuring the MTA for TCP/IP” in “Configuring the MTA” in the GroupWise 6.5 Administration Guide. Make sure no other programs on the server besides GroupWise agents are configured to use this port. GWMTA: Unknown destination Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: GroupWise Message Transfer Agent. The MTA is unable to route a message because it does not recognize the domain to which it is addressed. The sender manually typed in an invalid address. Have the user select the recipient from the Address Book, then resend the message. During a reconfiguration of your system, a user has addressed a message to a location that either no longer exists or does not exist yet, because the reconfiguration information has not yet replicated throughout the GroupWise system. Wait until replication is complete. The MTA will retry the operation. The message has been damaged so that the destination information is no longer readable. Remove the damaged message from the MTA input queue so it can process subsequent messages. Have the user resend the message. GWMTA: Unsupported 3.1 domain Source: GroupWise Message Transfer Agent. Message Transfer Agent Error Messages 187 Explanation: The Group Wise 6.x MTA cannot run in a WP Office 3.1 domain. Action: Run the WP Office 3.1 Message Server in the 3.1 domain. To communicate between WP Office 3.1 and Group Wise 6, a Group Wise 4.1 domain is required. You cannot upgrade directly from WP Office 3.1 to Group Wise 6. To retain users' mail and appointments, you would need to upgrade to GroupWise 4.1 first. GWMTA: Waiting for busy listen socket to become available Source: GroupWise Message Transfer Agent; message transfer protocol. Explanation: The TCP port the MTA is configured to listen on is already in use by another program. Possible Cause: Another MTA is already running on the server where you are trying to start this MTA. Action: Configure this MTA to use a different TCP port. See “Using TCP/IP Links between Domains” in “Configuring the MTA” in the GroupWise 6.5 Administration Guide. 188 GroupWise 6.5 Troubleshooting 1: Error Messages Internet Agent Error Messages Some error and informational messages you might receive when using the Internet Agent originate from the program engine or from SMTP when the program makes connections with hosts, and from other sources as well. This section includes the error messages generated by the Internet Agent. Variables, such as strings or numbers, are shown in italics and are represented by the following: + ASCII strings are represented by xxx, yyy, or ZZZ * Decimal characters are represented by nnn + Hexadecimal characters are represented by hhh “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: “GWIA: Command task could not be added to message body, rc =xxxx” on page 190 Configuration data is missing from the database” on page 190 ConvertPerfect Error while converting attachment file filename” on page 190 Currently unhandled command value, xxxx, was received by the gateway” on page 190 Database initialization error: xxxx” on page 190 Database open error: xxxx” on page 190 Deferred delivery file I/O error--encryption error” on page 190 Deferred delivery file I/O error-memory error” on page 191 Deferred delivery file I/O error-message undeliverable” on page 191 Deferred file, filename, has been moved to the PROBLEM directory” on page 191 File close error on file filename in module xxxx” on page 191 File creation error on file filename in module xxxx” on page 191 File open error on file filename in module xxxx” on page 191 File read error on file filename in module xxxx” on page 191 File write error on file filename in module xxxx” on page 192 Gateway that uses this directory is not yet defined” on page 192 Gateway Configuration Database could not be found” on page 192 Memory exhausted” on page 192 Memory exhausted while processing an Administrator Command” on page 192 Message File open failed” on page 192 Message re-gueuing failed. The message must be deleted” on page 192 Message transport session open error: xxxx” on page 193 Processing inbound message...” on page 193 Processing outbound command...” on page 193 > “GWIA: Processing outbound message...” on page 193 “GWIA: “GWIA: “GWIA: “GWIA: Scratch-pad file creation error: xxxx” on page 193 Scratch-pad file write error: filename” on page 193 Unable to find TCPIP Kernel” on page 194 Unable to listen on SMTP port” on page 194 Internet Agent Error Messages 189 GWIA: Command task could not be added to message body, rc =xxxx Source: Explanation: Action: Group Wise” Internet Agent. A file output error occurred, probably because of a full disk or an inaccessible directory. If re = D109, check access rights and privileges in the wpcsin directory. or If rc = D907, check access rights and privileges in the wpcsin directory. GWIA: Configuration data is missing from the database Source: Explanation: Action: Group Wise Internet Agent. The domain database (wpdomain.db) is damaged. Rebuild the database using ConsoleOne®. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWIA: ConvertPerfect Error while converting attachment file filename Source: Explanation: Action: Group Wise Internet Agent. The user sent the message using the Convert Attachment feature of the Advanced Send Option, which invokes ConvertPerfect. ConvertPerfect might not know how to convert this type of file, the file could not be decrypted, or a file I/O error occurred. This problem might generate a different error message than the one listed above. None. GWIA: Currently unhandled command value, xxxx, was received by the gateway Source: Explanation: Action: Group Wise Internet Agent. An unrecognized command was received from ConsoleOne. Resend the command. GWIA: Database initialization error: xxxx Source: Explanation: Action: Group Wise Internet Agent. The Internet Agent database management code could not be initialized You might need to rebuild the domain database (wpdomain.db) for the domain where the Internet Agent is installed. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. GWIA: Database open error: xxxx Source: Explanation: Action: Group Wise Internet Agent. The domain database path could not be created, or the database did not open. Make sure that the domain database (wpdomain.db) is in the domain directory. GWIA: Deferred delivery file I/O error--encryption error Source: GroupWise Internet Agent. 190 GroupWise 6.5 Troubleshooting 1: Error Messages Explanation: An encrypted non-queue file was moved to the gwhold directory. Action: Do not put any files in gwhold, remove any files not named with a HEX time stamp, and restart the Internet Agent. GWIA: Deferred delivery file I/O error-memory error Source: GroupWise Internet Agent. Explanation: The Internet Agent server ran out of memory. Action: Free more memory. GWIA: Deferred delivery file I/O error-message undeliverable Source: GroupWise Internet Agent. Explanation: The message could not be written to disk in the gfiles directory. Action: Check to see if the disk is full, and check access to the directory. GWIA: Deferred file, filename, has been moved to the PROBLEM directory Source: GroupWise Internet Agent. Explanation: After the Internet Agent retry schedule expired, the message was moved to the problem directory. The destination host was temporarily down (it sent back a 400-level SMTP reply code) so the program could not transfer the message. Action: Contact the postmaster for the destination host to make sure the host is up. Have the user resend the message. GWIA: File close error on file filename in module xxxx Source: GroupWise Internet Agent. Explanation: A close of the named file resulted in an error. Action: Check if some other process on the server is holding the file open. Check for network problems. GWIA: File creation error on file filename in module xxxx Source: GroupWise Internet Agent. Explanation: An open of the named file resulted in an error. Action: Check access in the named directory. GWIA: File open error on file filename in module xxxx Source: GroupWise Internet Agent. Explanation: An open of the named file resulted in an error. Action: Check access to named file and directory, and check access to file. GWIA: File read error on file filename in module xxxx Source: GroupWise Internet Agent. Explanation: A read of the named file resulted in an error. Action: | Check access to named file. Internet Agent Error Messages 191 GWIA: File write error on file filename in module xxxx Source: GroupWise Internet Agent. Explanation: A write to the named file resulted in an error. Action: Check access in named directory, and check to see if the disk is full. GWIA: Gateway that uses this directory is not yet defined Source: GroupWise Internet Agent. Explanation: The Internet Agent has been installed, but it is not yet configured. Action: Configure the Internet Agent in ConsoleOne. See “Internet Agent” in the GroupWise 6.5 Administration Guide. GWIA: Gateway Configuration Database could not be found Source: GroupWise Internet Agent. Explanation: The directory where the domain database (wpdomain.db) resides cannot be found, given the Internet Agent’s default directory and the Internet Agent startup options. Action: Use the Internet Agent directory startup option /work to reference the directory below wpgate in the domain where the Internet Agent executable file resides, or simply invoke the executable from that directory. Check network rights. GWIA: Memory exhausted Source: GroupWise Internet Agent. Explanation: The Internet Agent was not able to allocate sufficient memory. Action: Free up more memory. GWIA: Memory exhausted while processing an Administrator Command Source: GroupWise Internet Agent. Explanation: The Internet Agent ran out of memory while processing a command sent to the Internet Agent by ConsoleOne. Action: Free up more memory. GWIA: Message File open failed Source: GroupWise Internet Agent. Explanation: The Internet Agent could not open a message file. Action: The message file is moved to the problem directory in the domain directory. GWIA: Message re-queuing failed. The message must be deleted Source: GroupWise Internet Agent. Explanation: A message could not be put into or removed from the delayed delivery and the retry queue maintained under the gwhold directory because of a disk or a memory error. Action: Check access to the gwhold and qfiles subdirectories. 192 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Check to see if the disk is full. Action: Free more memory. GWIA: Message transport session open error: XXXX Source: GroupWise Internet Agent. Explanation: This is almost always caused by a memory error. Action: Free up memory. GWIA: Processing inbound message... Source: GroupWise Internet Agent. Explanation: This is an informational message. A message is being received by the Internet Agent from the foreign system. Action: None. GWIA: Processing outbound command... Source: GroupWise Internet Agent. Explanation: This is an informational message. ConsoleOne has sent a command to the Internet Agent. Commands are STATE, REOUEST STATS, REBOOT, and DIRECTORY SYNCHRONIZATION. Action: None. GWIA: Processing outbound message... Source: GroupWise Internet Agent. Explanation: This is an informational message. A message is being received by the Internet Agent from the Group Wise system. Action: None. GWIA: Scratch-pad file creation error: xxxx Source: GroupWise Internet Agent. Explanation: The Internet Agent settings file, SET, could not be created. Action: Check access (write or create) to the 000.prc directory. Action: | Check to see if the disk is full. GWIA: Scratch-pad file write error: filename Source: GroupWise Internet Agent. Explanation: The Internet Agent settings file, SET, could not be written. Action: Check access (write or create) to the 000.prc directory. Action: check to see if the disk is full. Internet Agent Error Messages 193 GWIA: Unable to find TCPIP Kernel Source: GroupWise Internet Agent. Explanation: The Internet Agent must find the TCP/IP kernel already loaded or the Internet Agent automatically loads the TCP/IP kernel. Ifthe TCP/IP kernel is not or cannot be loaded automatically, this error results. Action: Check to see that the TCP/IP kernel is installed and configured. GWIA: Unable to listen on SMTP port Source: GroupWise Internet Agent. Explanation: The TCP/IP kernel is not installed correctly or the Internet Agent is unable to take control of port 25 (SMTP port number). Other processes might have control of port 25, thereby preventing the Internet Agent from taking control of port 25. Action: | Unload the TCP/IP kernel then reload it. If another process has control of port 25, unloading the TCP/IP kernel will show it. 194 GroupWise 6.5 Troubleshooting 1: Error Messages “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: “WEBACC: WebAccess Agent Error Messages CMC encountered a problem accessing the GroupWise domain” on page 196 CMC was not able to access this GroupWise gateway directory” on page 196 CMC was not able to establish a connection to the post office” on page 196 Conversation timed out” on page 197 Could not start logging thread” on page 197 Error accessing directory” on page 197 Error accessing startup file” on page 197 File I/O error” on page 197 GWINTER NLM cannot initialize screen” on page 198 GWINTER NLM initialization error: Invalid GWENN4.NLM loaded” on page 198 Hash value changed” on page 198 If necessary, the system will attempt a forced shutdown ...” on page 198 Invalid command line syntax” on page 198 Invalid log level” on page 199 Invalid startup parameter” on page 199 Invalid startup parameter file” on page 199 Invalid startup parameter value” on page 199 Logging: Disk is full - turning file logging off’ on page 199 Logging: Error creating file - turning file logging off” on page 199 Logging: Error writing to file - turning file logging off’ on page 200 Login failed” on page 200 Login rejected: No valid password specified” on page 200 Login rejected: No valid userid specified” on page 200 Login rejected: Password is incorrect” on page 200 No gateway alias was specified in NW Admin” on page 201 No gateway directory was specified” on page 201 No message is currently open” on page 201 No NetWare password was specified” on page 201 No NetWare user ID was specified” on page 201 No UNC path specified for the post office” on page 202 Not able to bind to specified port” on page 202 Not able to open configuration file” on page 202 Not enough memory to complete operation” on page 202 Request aborted while waiting on locked conversation” on page 202 Request rejected because all threads are busy” on page 203 Startup file not found” on page 203 TCP socket accept failed” on page 203 WebAccess Agent Error Messages 195 “WEBACC: The post office is closed” on page 203 “WEBACC: The system is busy, please try again later” on page 203 “WEBACC: Unable to establish a connection to the default log path” on page 203 “WEBACC: Unable to establish a connection to the log path” on page 204 “WEBACC: Unable to find the specified user” on page 204 “WEBACC: Unknown keyword:” on page 204 WEBACC: CMC encountered a problem accessing the GroupWise domain Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise” WebAccess Agent The WebAccess Agent could not access the Group Wise domain in which its gateway directory is located. The WebAccess Agent was not started with the /ph switch. Start the WebAccess Agent by using the /ph switch. For example, gwinter /ph- j:\advert\wpgate\webac60a. For more information, see “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. The WebAccess Agent lost its connection to the domain directory or does not have sufficient rights in the directory structure. Reestablish the connection to the domain directory and make sure the WebAccess Agent has sufficient rights. See “WebAccess Security Requirements” in “Installing GroupWise WebAccess” in the GroupWise 6.5 Installation Guide. WEBACC: CMC was not able to access this GroupWise gateway directory Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent could not access its gateway directory in domain directory (domain\wpgate\webac60a, where domain is the domain directory and webac60a is the gateway directory). The WebAccess Agent does not have sufficient rights in the domain directory structure. Make sure the WebAccess Agent has sufficient rights. See “WebAccess Security Requirements” in “Installing GroupWise WebAccess” in the GroupWise 6.5 Installation Guide. WEBACC: CMC was not able to establish a connection to the post office Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent could not connect to the WebAccess user's post office. The WebAccess Agent lost its direct connection (UNC path or mapped drive) to the post office directory or does not have sufficient rights in the directory structure. Reestablish the connection to the post office directory and make sure the WebAccess Agent has sufficient rights. See “WebAccess Security Requirements” in “Installing GroupWise WebAccess’ in the GroupWise 6.5 Installation Guide. The WebAccess Agent lost its TCP/IP connection to the Post Office Agent (POA). 5 Make sure the Post Office Agent is up and running and that TCP/IP is configured properly on the servers running the WebAccess Agent and Post Office Agent. See “Managing Access to Post Offices” in “WebAccess” in the Group Wise 6.5 Administration Guide. 196 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: The WebAccess Agent's post office link information is not defined correctly in Novell? eDirectory™. Check the post office link information. See “Modifying Links to Post Offices” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Conversation timed out Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent automatically logs a user out of GroupWise if he or she does not use GroupWise WebAccess for a certain period of time (the timeout interval). This message indicates that the GroupWise WebAccess user's session has timed out. The GroupWise WebAccess user did not perform any actions in GroupWise WebAccess during the timeout interval. Have the user log in again. Lengthen the timeout interval. See “Creating a Class of Service” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Could not start logging thread Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent uses a separate thread other than the regular worker threads for logging. The WebAccess Agent could not open the logging thread. Low memory resources. Free up memory or add additional memory. WEBACC: Error accessing directory Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent could not access the specified directory. The WebAccess A gent lost its connection to the server where the directory resides or does not have sufficient rights to the directory. Reestablish the connection to the server and make sure the WebAccess Agent has sufficient rights to the directory. See “WebAccess Security Requirements” in “Installing GroupWise WebAccess” in the GroupWise 6.5 Installation Guide. WEBACC: Error accessing startup file Source: Explanation: Possible Cause: Action: Action: GroupWise WebAccess Agent The WebAccess Agent could not access the startup file specified by the @filename switch. The WebAccess Agent does not have the rights needed to access the startup file or the startup file does not exist in the specified location. Make sure the WebAccess Agent has rights to the startup file. Make sure the startup file is in the same directory as the WebAccess Agent program or that filename includes the full path to the file. WEBACC: File I/O error Source: GroupWise WebAccess Agent WebAccess Agent ErrorMessages 197 Explanation: Possible Cause: Action: The WebAccess Agent could not view a log file. The WebAccess Agent does not have access to log file directory, or does not have rights to the file. Make sure the WebAccess Agent has access to the log file directory and that it has rights to view the file. WEBACC: GWINTER NLM cannot initialize screen Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent cannot display its agent console. Insufficient memory. Free up memory or add additional memory. WEBACC: GWINTER NLM initialization error: Invalid GWENN4.NLM loaded Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent Group Wise Agent Engine (gwenn4.nlm) that is currently loaded is the incorrect version for the WebAccess Agent. Another Group Wise agent loaded an earlier version of gwenn4.nlm. Unload all Group Wise agents that are running on the server. Start Group Wise WebAccess and restart the other Group Wise agents. Make sure the other Group Wise agents are version 6. If necessary, reinstall the Group Wise WebAccess software to install the correct version of gwenn4.nlm. WEBACC: Hash value changed Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent Possible security violation. A user bookmarked a Group Wise WebAccess location then attempted to access it directly from another server. Have the user log in through the Group Wise WebAccess login screen. WEBACC: If necessary, the system will attempt a forced shutdown ... Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent In one minute, the WebAccess Agent will attempt to shut down even if WebAccess users are still logged in. The WebAccess Agent has been shut down, but one or more worker threads are still processing user reguests. None. WEBACC: Invalid command line syntax Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The specified syntax is invalid. The wrong startup switch syntax was used when attempting to start the WebAccess Agent. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. 198 GroupWise 6.5 Troubleshooting 1: Error Messages WEBACC: Invalid log level Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent The specified log level is not a valid log level. The log level specified by the /loglevel startup switch is not valid. Use one ofthe valid log levels: normal, verbose, or diagnostic. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the Group Wise 6.5 Administration Guide. WEBACC: Invalid startup parameter Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The specified startup switch is not a valid switch. A startup switch used on the command line or in the startup file is not valid. Retype the command line or edit the startup file to include valid switches only. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Invalid startup parameter file Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The specified file is not a valid startup file. The file is not a text file or does not contain any startup switches. Save the file as a text file or enter valid startup switches in the file. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Invalid startup parameter value Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The value for the specified startup switch is not valid. An invalid value was entered with the startup switch on the command line or in the startup file. Enter a valid value. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Logging: Disk is full - turning file logging off Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The disk where the log files are stored is full. File logging will be turned off. The disk is full. Delete files to increase available disk space. Allocate more disk space. Specify a different location for the log files. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Logging: Error creating file - turning file logging off Source: Explanation: GroupWise WebAccess Agent The WebAccess Agent could not create the log file, so disk logging is being turned off. WebAccess Agent Error Messages 199 Possible Cause: Action: The WebAccess Agent does not have rights to create files in the log file directory. Provide the WebAccess Agent with rights to create files in the log file directory or specify a different location for the log files. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the Group Wise 6.5 Administration Guide. Check the disk to make sure that there is sufficient space available to create the file. WEBACC: Logging: Error writing to file - turning file logging off Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent The WebAccess Agent could not write information to the log file, so logging is being turned off. The WebAccess Agent does not have rights to write to files in the log file directory or the disk is full. Provide the WebAccess Agent with rights to write to files in the log file directory or specify a different location for the log files. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the Group Wise 6.5 Administration Guide. WEBACC: Login failed Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent A WebAccess user attempted to log in and failed. The user did not enter a valid Group Wise user ID or password. Make sure the user knows his or her Group Wise user ID. Make sure the user has a password set on his or her mailbox and knows the password. WEBACC: Login rejected: No valid password specified Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent A Group Wise WebAccess user could not log in because he or she did not enter a valid password. The user did not enter a password when logging in. Make sure the user knows his or her mailbox password and enters it when logging in. WEBACC: Login rejected: No valid userid specified Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent A GroupWise WebAccess user could not log in because he or she did not enter a valid Group Wise user ID. The user did not enter a GroupWise user ID or full name when logging in. Make sure the user knows his or her GroupWise user ID and enters it when logging in. Users can also enter their full names as they appear in eDirectory and the GroupWise Address Book. WEBACC: Login rejected: Password is incorrect Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The password specified during login is incorrect. The user entered the wrong password. Make sure the user knows his or her mailbox password and enters it when logging in. Passwords are case-sensitive. 200 GroupWise 6.5 Troubleshooting 1: Error Messages WEBACC: No gateway alias was specified in NW Admin Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The gateway alias type is not defined. The gateway alias was not specified in ConsoleOne® during setup. Specify a gateway alias type. In ConsoleOne, double-click the WebAccess object, enter an alias in the Gateway Alias Type field, then click OK. The alias can be the same name as the gateway. WEBACC: No gateway directory was specified Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent must know the path to its gateway home directory. This path is specified by the /ph startup switch. The /ph startup switch was not used on the command line or in the strtweb.ncf or strtweb.bat file. Include the startup switch. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: No message is currently open Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent This is an internal diagnostic message. Unknown. If the problem persists, contact the Novell Support (http://support.novell.com). WEBACC: No NetWare password was specified Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The GroupWise WebAccess Agent requires an account and password that lets it log in to eDirectory or NetWare® servers so that it can access the domain directory and post office directories. The /password startup switch was not used on the command line or does not exist in the strtweb.ncf file. Use the /password startup switch when starting the WebAccess Agent from the command line or edit the strtweb.ncf file to add the switch. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: No NetWare user ID was specified Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The GroupWise WebAccess Agent requires an account and password that lets it log in to eDirectory or NetWare servers so that it can access the domain directory and post office directories. The /user startup switch was not used on the command line or does not exist in the strtweb.ncf file. Use the /user startup switch when starting the WebAccess Agent from the command line or edit the strtweb.ncf file to add the switch. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the GroupWise 6.5 Administration Guide. WebAccess Agent Error Messages 201 WEBACC: No UNC path specified for the post office Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent is attempting direct access to a post office and no UNC path is specified. The UNC path is not defined in the post office link information. In ConsoleOne, specify a UNC path or mapped drive to the post office. See “Modifying Links to Post Offices” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Not able to bind to specified port Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent could not bind to the TCP/IP port it uses to listen for messages from the GroupWise WebAccess CGI Extension. Another program is using the port. Resolve the port conflict by changing the port used by the other program or the port used by the WebAccess Agent. To change the WebAccess Agent's port, see in “WebAccess” in the Group Wise 6.5 Administration Guide. WEBACC: Not able to open configuration file Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent could not open the comint.cfg file located in its gateway home directory (domain\wpgate\webac60a, where domain is the domain directory and webac60a is the gateway home directory). The WebAccess Agent reads configuration information from this file. The file has been deleted or has a problem. Use ConsoleOne to reenter the configuration information. See “Configuring the WebAccess Agent” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Not enough memory to complete operation Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent could not perform the operation because of insufficient memory. Insufficient memory. Free up memory or add additional memory. WEBACC: Request aborted while waiting on locked conversation Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent During a conversation (or session), GroupWise WebAccess issues a request whenever the user performs an action in WebAccess. When the WebAccess Agent receives a request, it locks the conversation so that it can process the request. While the conversation is locked, other requests can accumulate. This message indicates a request that was waiting on the locked conversation has timed out. The request for the locked conversation took longer than allowed. Have the GroupWise WebAccess user perform the action again (for example, resend the message). 202 = GroupWise 6.5 Troubleshooting 1: Error Messages WEBACC: Request rejected because all threads are busy Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent The WebAccess Agent could not process a request from a WebAccess user because no threads were available. Heavy WebAccess usage for the number of threads allocated to the WebAccess Agent. Ifthis error occurs often, increase the number ofthreads. See “Modifying WebAccess Settings” in “WebAccess” in the Group Wise 6.5 Administration Guide. WEBACC: Startup file not found Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent could not find the startup file specified by the @filename startup switch. The startup file is not in the same directory as the WebAccess Agent and filename does not include the complete path to the file. Move the startup file to the same directory as the WebAccess Agent or include the full path in the filename (for example @j:\startup\webstart.txt). WEBACC: TCP socket accept failed Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent The Group Wise WebAccess CGI Extension tried to start a new session with the WebAccess Agent, but the WebAccess Agent could not handle another session. Insufficient memory. Free up memory or add additional memory. WEBACC: The post office is closed Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent While processing a reguest for a user, the WebAccess Agent could not access the user's post office. Logging in to the post office has been disabled through ConsoleOne. Enable the post office. See “Disabling a Post Office” in “Post Offices” in the Group Wise 6.5 Administration Guide. WEBACC: The system is busy, please try again later Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent A user tried to log in to GroupWise WebAccess, but the WebAccess Agent could not handle another user. All worker threads are currently being used. If the problem persists, increase the number of threads. See “Modifying WebAccess Settings” in “WebAccess” in the GroupWise 6.5 Administration Guide. WEBACC: Unable to establish a connection to the default log path Source: Explanation: GroupWise WebAccess Agent The WebAccess Agent could not access the specified log file directory. WebAccess Agent Error Messages 203 Possible Cause: Action: The WebAccess Agent does not have rights to the directory or does not have access to the file SETVET. Make sure the WebAccess Agent's user account provides the correct access and rights, or specify a different log file directory using the /log switch. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the Group Wise 6.5 Administration Guide. WEBACC: Unable to establish a connection to the log path Source: Explanation: Possible Cause: Action: Group Wise WebAccess Agent The WebAccess Agent cannot access the log file directory. The WebAccess Agent does not have rights to the directory or does not have access to the file SETVET. Make sure the WebAccess Agent's user account provides the correct access and rights, or specify a different log file directory using the /log switch. See “Using WebAccess Agent Startup Switches” in “WebAccess” in the Group Wise 6.5 Administration Guide. WEBACC: Unable to find the specified user Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: GroupWise WebAccess Agent The WebAccess Agent cannot find the user in the GroupWise database. When logging in, the user entered an incorrect or invalid user ID. Have the user enter a valid user ID or full username (as defined in eDirectory or the GroupWise Address Book) when logging in. Have the user try logging in using the full GroupWise username (domain.post_office.userID. The WebAccess servlet has encountered a problem with the username. Check the WebAccess Application log for additional error messages. On NetWare and Windows, the WebAccess Application log is located in /novell/webaccess/logs. On Linux, it is located in / opt/novell/groupwise/webaccess/logs. WEBACC: Unknown keyword: Source: Explanation: Possible Cause: Action: GroupWise WebAccess Agent When communicating, the WebAccess Agent and WebAccess CGI Extension exchange keywords. This message indicates that the keyword given by the WebAccess CGI Extension is not known by the WebAccess Agent. The comint.cfg file used by the WebAccess Agent is out of sync with the commgr.cfg file used by the WebAccess CGI Extension. The WebAccess Agent, WebAccess CGI Extension, HTML templates, and Java applets are not the same version. In ConsoleOne, reenter the configuration information so that the comint.cfg file and commgr.cfg file will be resaved. See “Configuring the WebAccess Agent” in “WebAccess” in the GroupWise 6.5 Administration Guide. If the problem persists, reinstall the GroupWise WebAccess software. See “Installing Group Wise WebAccess” in the GroupWise 6.5 Installation Guide. 204 GroupWise 6.5 Troubleshooting 1: Error Messages Monitor Agent and Application Error Messages “GWMON: “GWMON: “GWMON: “GWMON: “GWMON: “GWMON: “GWMON: “GWMON: page 207 GroupWise Monitor Agent is not listening” on page 205 No route to GroupWise Monitor Agent” on page 205 Path to domain database (/home) is invalid or blocked” on page 205 Request timed out waiting for response from Group Wise Monitor Agent” on page 206 The URL to connect to the Group Wise Monitor Agent is invalid” on page 206 Unable to communicate with GroupWise Monitor Agent” on page 206 Unable to connect to the MTA at IP_address:port” on page 207 Unable to resolve GroupWise Monitor Agent’s host name to a valid IP address” on GWMON: GroupWise Monitor Agent is not listening Source: GroupWise® Monitor Application. Possible Cause: The Monitor Agent is not running. Action: Restart the Monitor Agent. See “Starting the Monitor Agent” in “Monitor” in the GroupWise 6.5 Administration Guide. Possible Cause: The Monitor Agent is listening on a different port than the one the Monitor Application is using to communicate with it. Action: | Check the gwmonitor.cfg file to make sure it provides the correct IP address and port number for the Monitor Agent. Correct the information as needed. GWMON: No route to GroupWise Monitor Agent Source: GroupWise Monitor Application. Possible Cause: Your firewall is preventing the Monitor Application from communicating with the Monitor Agent. Action: Adjust the configuration of your firewall to accommodate communication between the Monitor Application and the Monitor Agent. Possible Cause: A router between the Monitor Application and the Monitor Agent is down. Action: Resolve any network problems that are preventing GroupWise Monitor from functioning. GWMON: Path to domain database (/home) is invalid or blocked Source: GroupWise Monitor Agent. Explanation: The Monitor Agent cannot access the domain database (wpdomain.db) in the directory specified by the /home switch. Possible Cause: The location specified by the /home startup switch does not exist. Monitor Agent and Application Error Messages 205 Action: Possible Cause: Action: Possible Cause: Action: Check, and if necessary change, the location specified by the /home startup switch when starting the MTA. It must specify the domain directory. See “Using Monitor Agent Switches” in “Monitor” in the Group Wise 6.5 Administration Guide. The location specified by the /home startup switch is on a server that is currently not available. Check the status of the server where the specified directory is located. Wait for the server to come back up or contact the administrator of'that server. The location might be on a server that is not currently mapped. Make sure the server where the Monitor Agent is running has a drive mapped to the domain directory on the server where the domain is located if it is using a mapped link. GWMON: Reguest timed out waiting for response from GroupWise Monitor Agent Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Group Wise Monitor Application. The Monitor Application has been able to communicate successfully with the Monitor Agent, but the Monitor Agent has stopped responding. The server where the Monitor Agent is running has gone down. Resolve any network problems that are preventing GroupWise Monitor from functioning. The server where the Monitor Agent is running is overburdened or has insufficient system resources available, so that the Monitor Agent cannot respond to the Monitor Application in a timely manner. Make sure that the server where the Monitor Agent is running meets Monitor system requirements. See “Deciding Where to Install the GroupWise Monitor Components” in “Installing GroupWise Monitor” in the GroupWise 6.5 Installation Guide. The Monitor Agent has gone down. Restart the Monitor Agent. See “Starting the Monitor Agent” in “Monitor” in the Group Wise 6.5 Administration Guide. GWMON: The URL to connect to the GroupWise Monitor Agent is invalid Source: Possible Cause: Action: GroupWise Monitor Application. The Monitor Agent IP address and port number is not correct in the gwmonitor.cfg file. Check the gwmonitor.cfg file to make sure it provides the correct IP address and port number for the Monitor Agent. Correct the information as needed. GWMON: Unable to communicate with GroupWise Monitor Agent Source: Possible Cause: Action: Possible Cause: Possible Cause: Action: Possible Cause: GroupWise Monitor Application. The Monitor Agent is not running. Start the Monitor Agent. See “Starting the Monitor Agent” in “Monitor” inthe GroupWise 6.5 Administration Guide. The server where the Monitor Agent is running has gone down. A router between the Monitor Application and the Monitor Agent is down. Resolve any network problems that are preventing GroupWise Monitor from functioning. Your firewall is preventing the Monitor Application from communicating with the Monitor Agent. 206 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Adjust the configuration of your firewall to accommodate communication between the Monitor Application and the Monitor Agent. GWMON: Unable to connect to the MTA at /P address:port Source: GroupWise Monitor Agent. Explanation: The Monitor Agent cannot connect to the MTA at the IP address and port you specified when prompted. Action: Double-check the IP address and port number of the MTA that you want the Monitor Agent to communicate with. Action: Make sure that the MTA is running with HTTP enabled. See “Using the MTA Web Console” in “Message Transfer Agent” in the Group Wise 6.5 Administration Guide. GWMON: Unable to resolve GroupWise Monitor Agent's host name to a valid IP address Source: GroupWise Monitor Application. Possible Cause: The Monitor Agent host name is not correct in the gwmonitor.cfg file. Action: | Check the gwmonitor.cfg file to make sure it provides the correct IP address and port number for the Monitor Agent. Correct the information as needed. Monitor Agent and Application Error Messages 207 208 = GroupWise 6.5 Troubleshooting 1: Error Messages Administration Error Messages The Group Wise” Administrator snap-in to ConsoleOne* is used to create and manage Group Wise objects. Group Wise Check is a standalone version of the Mailbox/Library Maintenance feature found in ConsoleOne. This part of Troubleshooting 1: Error Messages helps you resolve error messages that might occur when you are using the GroupWise Administrator snap-in to ConsoleOne and error codes that might occur when you run GroupWise Check. + “GroupWise Administrator Snap-In to ConsoleOne Error Messages” on page 211 + “GroupWise Check Error Codes” on page 219 + “GroupWise Time Stamp Utility Error Messages” on page 235 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) Administration Error Messages 209 210 GroupWise 6.5 Troubleshooting 1: Error Messages GroupWise Administrator Snap-In to ConsoleOne Error Messages “0001 Cannot load resource” on page 212 “0002 Schema not properly defined” on page 212 “0003 Required DLL has incorrect version” on page 212 “0004 Required DLL missing” on page 212 “0005 Cannot read required information from NDS” on page 212 “0006 Group Wise object missing required information” on page 213 “0007 Cannot read required information from GroupWise database” on page 213 “0008 Cannot delete subordinate objects” on page 213 “0009 Cannot obtain UNC path” on page 213 “0013 Out of memory” on page 213 “0019 Cannot map local drive to network resource” on page 213 “001D Cannot add non-Group Wise account to library membership” on page 213 “0021 Gateway setup file not found” on page 214 “0022 Cannot assign non-Group Wise user as administrator” on page 214 “002D Pending move” on page 214 “002E Pending delete” on page 214 “0031 Cannot delete post office that owns GroupWise objects” on page 214 “0032 Cannot delete domain that owns GroupWise objects” on page 215 “0033 Cannot delete post office that owns Group Wise objects” on page 215 “0035 Cannot read GroupWise information for object” on page 215 “0036 Cannot access object in different GroupWise system” on page 215 “0038 Owning object (domain/post office) not found in NDS” on page 215 “0039 Invalid UNC path” on page 216 “0041 Cannot authenticate” on page 216 “0042 Cannot authenticate to requested tree” on page 216 “0045 Domain database not found” on page 216 “0049 Cannot move user from 6.x post office to 4.x post office” on page 216 “0053 Parent domain database not found” on page 216 “0054 Invalid drive specification” on page 216 “0056 Non-networked drive” on page 217 “0057 Cannot create another agent of this type in this context” on page 217 “0059 Cannot create another GroupWise object” on page 217 “0065 Cannot open domain database” on page 217 “0069 Outbound MTA platform undefined” on page 217 “00A2 Cannot set rights on software distribution directory” on page 217 “0102 Password incorrect” on page 218 GroupWise Administrator Snap-In to ConsoleOne Error Messages 211 0001 Cannot load resource Source: Explanation: Possible Cause: Action: Group Wise” Administrator; general snap-in. Unable to load resource DLL. Invalid NWLANGUAGE environment specification. Make sure the NetWare* client is set up properly on the workstation where you are running ConsoleOne*. 0002 Schema not properly defined Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Administrator; general snap-in. Schema error. The Group Wise schema extensions are not present. When you install Group Wise, the tree you are currently logged in to is extended. After installation, you run ConsoleOne and change to a tree that has not been extended. Log in to the tree you want extended, then rerun the installation (install.exe from the root of the distribution CD) to extend the schema on the second tree. See “Setting Up a Basic GroupWise System on NetWare or Windows” in the GroupWise 6.5 Installation Guide. GroupWise installation did not complete successfully. Run Install from the root directory ofthe GroupWise CD. See “Setting Up a Basic GroupWise System on NetWare or Windows” in the GroupWise 6.5 Installation Guide. 0003 Reguired DLL has incorrect version Source: Explanation: Possible Cause: Action: Group Wise Administrator; general snap-in. DLL version mismatch. An improper update of the Group Wise Administrator snap-in might have been loaded from the Novell Technical Support. Rerun Group Wise Install (install.exe from the root of the distribution CD) or acquire the latest GroupWise Administrator snap-in from the Novell Support. For technical services, see Novell Support (http://support.novell.com). 0004 Required DLL missing Source: Explanation: Possible Cause: Action: GroupWise Administrator; general snap-in. One of the GroupWise Administrator snap-in DLL programs is missing. You are attempting to run ConsoleOne on a workstation that does not have GroupWise Administrator snap-in installed. Run ConsoleOne on a workstation where the GroupWise Administrator snap-in has already been installed. 0005 Cannot read required information from NDS Source: Explanation: Possible Cause: Action: GroupWise Administrator; general snap-in. GroupWise is unable to read necessary information from NDS®. You have insufficient rights to read this information. Make sure you have sufficient rights to administer the objects in this GroupWise domain. If you have not been assigned sufficient rights, contact the NetWare system administrator. 212 GroupWise 6.5 Troubleshooting 1: Error Messages 0006 GroupWise object missing reguired information Source: GroupWise Administrator; general snap-in. Explanation: Invalid object state. The information for the NDS object is in an inconsistent state for Group Wise to use. Action: Fill in the missing information by grafting the objects. For information about grafting, see “GW / eDirectory Association” in “System” in the GroupWise 6.5 Administration Guide. 0007 Cannot read required information from GroupWise database Source: GroupWise Administrator; general snap-in. Explanation: Unable to read the required information from the GroupWise database. Possible Cause: Replication is in progress and has encountered inconsistent data. Action: Make sure there are no pending operations. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide. Then rebuild the database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 0008 Cannot delete subordinate objects Source: GroupWise Administrator; general snap-in. Explanation: Error deleting subordinate objects. Possible Cause: You do not have rights to delete the subordinate objects. Action: Make sure you have access and delete rights to the objects you are attempting to delete. 0009 Cannot obtain UNC path Source: GroupWise Administrator; general snap-in. Explanation: UNC path not available. Action: Make sure you are logged in to the appropriate network and you have rights to the location. 0013 Out of memory Source: GroupWise Administrator; database management. Explanation: Out of memory error. Action: Free up memory, then try the operation again. 0019 Cannot map local drive to network resource Source: GroupWise Administrator; connection ID. Explanation: GroupWise is unable to map a local drive to the network resource. Action: | Make sure the UNC specification is correct, that you have drives available to map, and that you have access to the network resource requested. 001D Cannot add non-GroupWise account to library membership Source: GroupWise Administrator; document management. Explanation: You cannot grant library membership to a user that does not have a Group Wise account. GroupWise Administrator Snap-In to ConsoleOne Error Messages 213 Action: Add the user to Group Wise. See “Creating Group Wise Accounts” in “Users” in the Group Wise 6.5 Administration Guide. 0021 Gateway setup file not found Source: GroupWise Administrator; gateway setup. Explanation: A file required to run the gateway-specific setup was missing. Possible Cause: The gateway installation was incomplete. Action: Reinstall the gateway. For a list of gateways, see GroupWise 6.x Gateways (http:// www.novell.com/documentation/gw6xgate/index.html). GroupWise 5.5 gateways can be used with GroupWise 6. 0022 Cannot assign non-GroupWise user as administrator Source: GroupWise Administrator; gateway setup. Explanation: The gateway administrator must be either a GroupWise user or a GroupWise distribution list. Action: Select a valid Group Wise user or distribution list as the gateway administrator. For a list of gateways, see GroupWise 6.x Gateways (http://www.novell.com/documentation/gw6xgate/ index.html). GroupWise 5.5 gateways can be used with GroupWise 6.5. 002D Pending move Source: GroupWise Administrator; association. Explanation: The record has been moved; however, GroupWise replication is still in progress. The record cannot be modified at this time. Action: Wait for replication to complete, then retry the record modification. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide. 002E Pending delete Source: GroupWise Administrator; association. Explanation: The record has been moved; however, GroupWise replication is still in progress. The record cannot be deleted at this time. Action: Wait for the replication to complete, then retry the operation. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide. 0031 Cannot delete post office that owns GroupWise objects Source: GroupWise Administrator; delete visitor. Explanation: You cannot delete this post office until all subordinate objects have been moved or deleted. Possible Cause: The post office still owns one or more Agent objects. Action: Delete any Agent objects using ConsoleOne. Possible Cause: The post office still has users, resources, distribution lists, libraries, or library storage areas assigned to it. Action: Move or delete each subordinate object in the post office. See “Deleting a Post Office” in “Post Offices” GroupWise 6.5 Administration Guide. 214 GroupWise 6.5 Troubleshooting 1: Error Messages 0032 Cannot delete domain that owns GroupWise objects Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Administrator; delete visitor. You cannot delete this domain until all subordinate objects have been moved or deleted. The domain still owns one or more Agent objects. Delete any Agent objects. The domain still has post offices assigned to it. Move or delete the post offices. See “Deleting a Post Office” in “Post Offices” and “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. 0033 Cannot delete post office that owns GroupWise objects Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise Administrator; delete visitor. Cannot delete post office because it still has subordinate GroupWise objects. The post office still owns one or more agent objects. Delete any agent objects from the browser window. The post office still has users, resources, distribution lists, libraries, or library storage areas assigned to it. Move or delete each subordinate object in the post office, then delete the post office. See “Deleting a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. 0035 Cannot read GroupWise information for object Source: Explanation: Possible Cause: Action: GroupWise Administrator; association. Record not read. GroupWise replication is still in progress and the data has become inconsistent. Wait for the replication to complete, then rebuild the database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 0036 Cannot access object in different GroupWise system Source: Possible Cause: Action: GroupWise Administrator; association. You are accessing an object in NDS that belongs to a different GroupWise system than the one you are connected to. Connect to the appropriate Group Wise system. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. 0038 Owning object (domain/post office) not found in NDS Source: Explanation: Possible Cause: Action: GroupWise Administrator; association. Object does not exist in NDS. An invalid DN was entered for the domain or post office that owns this object. Enter a valid DN. GroupWise Administrator Snap-In to ConsoleOne Error Messages 215 0039 Invalid UNC path Source: GroupWise Administrator; UNC path validator. Explanation: The UNC path entered does not specify a valid network resource. Action: Enter a correct UNC path. 0041 Cannot authenticate Source: GroupWise Administrator; NDS operation. Explanation: The NetWare login DLL file was not found. GroupWise was unable to authenticate. Possible Cause: Your NetWare client installation was incomplete. Action: Reinstall the NetWare client. 0042 Cannot authenticate to requested tree Source: GroupWise Administrator; NDS operation. Explanation: | GroupWise was unable to authenticate to the requested tree. Action: Make sure you have proper rights. Contact the NetWare system administrator. 0045 Domain database not found Source: GroupWise Administrator; class definition. Explanation: You are not currently connected to a GroupWise domain database (wpdomain.db). The requested operation cannot be completed. Action: Connect to an existing GroupWise domain. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. 0049 Cannot move user from 6.x post office to 4.x post office Source: GroupWise Administrator; 6.x to 4.x move. Explanation: GroupWise does not support moving users from a GroupWise 6.x post office to a GroupWise 4.x post office. Action: You might want to consider migrating your 4.1 system to GroupWise 5. 0053 Parent domain database not found Source: GroupWise Administrator; visitor base. Explanation: GroupWise was unable to locate the domain database (wpdomain.db) for the requested action. The network resource is unavailable. Action: Retry the operation. 0054 Invalid drive specification Source: GroupWise Administrator; visitor base. Explanation: | GroupWise is unable to determine a local path from the drive specification. Action: Enter a valid path. 216 GroupWise 6.5 Troubleshooting 1: Error Messages 0056 Non-networked drive Source: Explanation: Action: Group Wise Administrator; visitor base. You are attempting to create a Group Wise domain or post office on a non-networked location that might become unavailable. You should create domains and post offices where network users will have permanent access to them. 0057 Cannot create another agent of this type in this context Source: Explanation: Action: Group Wise Administrator; visitor base. Agents are limited based on context. For example, only one MTA per domain can exist. The maximum number of this agent type already exist in this context. You cannot create another agent of this type in the selected context. 0059 Cannot create another GroupWise object Source: Explanation: Action: GroupWise Administrator; visitor base. You are running a limited evaluation version of GroupWise. This GroupWise system is limited to one domain and two post offices, with a maximum of three users on each post office. You can upgrade this evaluation software by purchasing and installing the shipping version of Group Wise. 0065 Cannot open domain database Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise Administrator; system-wide operations. The domain database (wpdomain.db) from which GroupWise Administrator is reading information has become unavailable. The original database will continue to be used until ConsoleOne is restarted. The server where the domain database is located has gone down so the drive mapping is no longer valid. Check the status of the server. The domain database is damaged. Check and, if necessary, repair the domain database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 0069 Outbound MTA platform undefined Source: Explanation: Possible Cause: Action: GroupWise Administrator; link tool. Information in the Link Configuration Tool is displayed based on the domain's MTA platform. MTA settings error. The default outbound MTA platform is NetWare®. Set the outbound MTA platform to the appropriate platform type. See “Configuring the MTA” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide. 00A2 Cannot set rights on software distribution directory Source: GroupWise Administrator; automatic rights. GroupWise Administrator Snap-In to ConsoleOne Error Messages 217 Explanation: | GroupWise Administrator could not automatically set the correct rights to the software distribution directory. Possible Cause: The software distribution directory is located on a server located in a different tree from the post office. Action: Create a software distribution directory in the same tree as the post office. See “Creating a Software Distribution Directory” in “System” in the Group Wise 6.5 Administration Guide. 0102 Password incorrect Source: GroupWise Administrator; temporary password. Explanation: Passwords do not match. Action: Enter the correct password. 218 GroupWise 6.5 Troubleshooting 1: Error Messages GroupWise Check Error Codes “01 Memory initialization error” on page 220 “02 WPHOST.DB database read error” on page 220 “03 Record read error” on page 221 “04 User record has no DS HOST NAME” on page 221 “05 User record has no DS OBJ TYPE” on page 221 “06 User record has no DS FID” on page 221 “07 User record has no DS USER NETID” on page 221 “08 User database read error” on page 221 “09 Message database read error” on page 222 “10 Message record read error” on page 222 “11 Unable to start database transaction” on page 222 “12 Record failed commit” on page 222 “13 Record failed modify” on page 222 “14 Record delete failed commit” on page 223 “15 Record failed delete” on page 223 “16 User does not exist in post office” on page 224 “17 Post office does not exist in domain” on page 224 “18 Message database open error” on page 224 “19 WPHOST.DB database open error” on page 224 “20 User record has no DS DOMAIN NAME” on page 224 “21 Unable to decrypt database” on page 224 “23 Unable to rename file for rebuild backup” on page 225 “24 Path modify error” on page 225 “25 Database create error” on page 225 “26 Database rebuild error” on page 225 “28 User file already exists or current file inaccessible” on page 226 “29 User database close error” on page 226 “30 User database not found” on page 226 “31 Exclusive access denied to user database” on page 226 “32 User database open error” on page 227 “33 Error initializing database engine code” on page 227 “34 Unable to get post office information” on page 227 “35 Memory allocation error” on page 227 “36 Message database not found” on page 227 “37 Exclusive access denied to message database” on page 227 “38 Error writing message record as user outbox item” on page 228 “39 Error writing message record as user inbox item” on page 228 GroupWise Check ErrorCodes 219 “41 All substitute filenames used for rename of database” on page 228 “42 Invalid database; truncated to nn bytes” on page 228 “43 Dictionary file missing; cannot continue” on page 228 “44 Database invalid due to security breach” on page 229 “47 Error in library sync with host” on page 229 “48 Orphaned OuickFinder index file” on page 229 “49 Invalid QuickFinder index file” on page 229 “50 Orphaned blob file” on page 229 “51 Invalid blob file” on page 229 “52 Blob file missing trailer” on page 230 “53 Blob file truncated to 0 bytes” on page 230 “61 Error adding system document type definition” on page 230 “62 Error reading system document type definition” on page 230 “63 Unable to update during check error code” on page 230 “64 Unable to complete verify during check error code” on page 230 “65 Unable to add default system document types” on page 231 “66 Unable to correct document display name” on page 231 “67 Unable to correct element without version object” on page 231 “68 Unable to synchronize document security” on page 231 “69 Unable to correct document without version object” on page 231 “70 Unable to correct version without document” on page 231 “71 Unable to correct version without element” on page 232 “72 Invalid user specified for orphan document reassignment” on page 232 “73 Unable to remove document storage area” on page 232 “74 Unable to move all blobs; storage area cannot be removed” on page 232 “75 Unable to move blob” on page 232 “76 Error accessing document content” on page 233 “77 Error accessing blob for official version distribution list” on page 233 “78 Error accessing blob for current version distribution list” on page 233 “79 Error accessing blob for version distribution list” on page 233 01 Memory initialization error Source: Group Wise? Check utility (GWCheck). Explanation: Insufficient memory to run GWCheck. Action: Run GWCheck where adequate memory is available. 02 WPHOST.DB database read error Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot access the post office database (wphost.db) for Address Book information. Action: In ConsoleOne®, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the Group Wise 6.5 Administration Guide. Action: For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 220 = GroupWise 6.5 Troubleshooting 1: Error Messages 03 Record read error Source: Explanation: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot read records from the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. 04 User record has no DS_HOST_NAME Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck encountered an invalid user record in the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 05 User record has no DS_OBJ_TYPE Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck encountered an invalid user record in the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 06 User record has no DS_FID Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck encountered an invalid user record in the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 07 User record has no DS_USER_NETID Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck encountered an invalid user record in the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 08 User database read error Source: Explanation: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot read records from the specified user database (userxxx.db). Perform a structural analyze/fix on the user database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. GroupWise Check Error Codes 221 09 Message database read error Source: Explanation: Action: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot read records from the specified message database (msgnn.db). Perform a structural analyze/fix on the message database by supplying the name of the message database in the User/Resource field. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If the message database cannot be repaired, manually restore it from backup. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 10 Message record read error Source: Explanation: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot read a specific record in a message database (msgnn.db). Perform a structural analyze/fix on the message database by supplying the name of the message database in the User/Resource field. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. If the message database cannot be repaired, manually restore it from backup. See “Restoring Group Wise Databases from Backup” in “Databases” in the Group Wise 6.5 Administration Guide. 11 Unable to start database transaction Source: Explanation: Action: Action: Action: Group Wise Check utility (GWCheck). The specified database is locked or otherwise inaccessible. Retry. There might have been a timing problem with another database user. See if another program, such as the POA, has the database open with exclusive access and has hung with the database open. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 12 Record failed commit Source: Explanation: Action: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot write a modified record back to the database. Retry. There might have been a timing problem with another database user. See if another program, such as the POA, has the database open with exclusive access and has hung with the database open. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 13 Record failed modify Source: Explanation: Possible Cause: Group Wise Check utility (GWCheck). GWCheck cannot write a modified record back to the database. The record is unavailable. Another user has the record locked. 222 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Action: Possible Cause: Action: Action: Action: Retry. There might have been a timing problem with another database user. See ifanother program, such as the POA, has the database open with exclusive access and has hung with the database open. The record is damaged. Perform a structural analyze/fix on the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Ifthe database cannot be repaired, manually restore it from backup. See “Restoring GroupWise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. 14 Record delete failed commit Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot delete a record from the database. The record is unavailable. Retry. There might have been a timing problem with another database user. See ifanother program, such as the POA, has the database open with exclusive access and has hung with the database open. The record is damaged. Perform a structural analyze/fix on the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Ifthe database cannot be repaired, manually restore it from backup. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. 15 Record failed delete Source: Explanation: Possible Cause: Action: Action: Possible Cause: Action: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot delete arecord from the database. The record is unavailable. Retry. There might have been a timing problem with another database user. See ifanother program, such as the POA, has the database open with exclusive access and has hung with the database open. The record is damaged. Perform a structural analyze/fix on the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Ifthe database cannot be repaired, restore it from backup. See “Restoring GroupWise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. GroupWise Check Error Codes 223 16 User does not exist in post office Source: Explanation: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot locate the specified user ID. Make sure you typed the user ID correctly in the User/Resource field in GWCheck. Ifthe user ID is typed correctly, make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides. 17 Post office does not exist in domain Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck cannot locate the specified post office. Make sure you provided the correct information for the post office in the Database Path and Post Office Name fields. 18 Message database open error Source: Explanation: Action: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot open the specified message database (msgnn.db). Perform a structural analyze/fix on the message database by supplying the name of'the message database in the User/Resource field. See “Maintaining User/Resource and Message Databases” in “Databases” in the Group Wise 6.5 Administration Guide. Ifthe message database cannot be repaired, manually restore it from backup. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 19 WPHOST.DB database open error Source: Explanation: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot open the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 20 User record has no DS_DOMAIN_NAME Source: Explanation: Action: Group Wise Check utility (GWCheck). GWCheck encountered an invalid user record in the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 21 Unable to decrypt database Source: Explanation: Action: Group Wise Check utility (GWCheck). GWCheck encountered an invalid user record in the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 224 GroupWise 6.5 Troubleshooting 1: Error Messages 23 Unable to rename file for rebuild backup Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot create a backup copy of the existing database. All valid backup database filenames have already been used. Check for existing backup databases with extensions .dba through .dbz. If all 26 backup extensions have been used, delete old backup databases so valid backup extensions are available. Insufficient disk space. Free up disk space by deleting unneeded files. Insufficient rights. Make sure you have write access to the directory where the database being repaired is located. 24 Path modify error Source: Explanation: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot create a needed directory path. Check rights and available disk space. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 25 Database create error Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot create a new user database (userxxx.db). Insufficient disk space. Free up disk space by deleting unneeded files. Insufficient rights. Make sure you have write access to the directory where the database being repaired is located. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 26 Database rebuild error Source: Explanation: Possible Cause: Action: Possible Cause: Action: Possible Cause: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot rebuild the database. Insufficient disk space. Free up disk space by deleting unneeded files. Insufficient rights. Make sure you have write access to the directory where the database being repaired is located. All valid backup database filenames have already been used. Check for existing backup databases with extensions .dba through .dbz. If all 26 backup extensions have been used, delete old backup databases so valid backup extensions are available. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. GroupWise Check ErrorCodes 225 28 Userfile already exists or current file inaccessible Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot create a backup copy of the existing database. Insufficient disk space. Free up disk space by deleting unneeded files. Insufficient rights. Make sure you have write access to the directory where the database being repaired is located. 29 User database close error Source: Explanation: Possible Cause: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot close the specified user database (userxxx.db). Insufficient rights. Make sure you have write access to the directory where the repaired database will be written. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. 30 User database not found Source: Explanation: Possible Cause: Action: Possible Cause: Action: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot locate the specified user database (userxxx.db) to check. You specified the user incorrectly. Make sure you typed the user name correctly in the User/Resource field in GWCheck. The user database is missing from the post office. Re-create the user database. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. Restore the user database from backup. If the user name is typed correctly, make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides. 31 Exclusive access denied to user database Source: Explanation: Possible Cause: Action: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot get sufficient access to the specified user database (userxxx.db). Insufficient rights. Make sure you have write access to the user database. Retry. There might have been a timing problem with another database user. See ifanother program, such as the POA, has the database open with exclusive access and has hung with the database open. 226 GroupWise 6.5 Troubleshooting 1: Error Messages 32 User database open error Source: Explanation: Action: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot open the specified user database (userxxx.db). Retry. There might have been a timing problem with another database user. See if another program, such as the POA, has the database open with exclusive access and has hung with the database open. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 33 Error initializing database engine code Source: Explanation: Possible Cause: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot initialize the database engine code. Insufficient rights. Make sure you have write access to the database to repair. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 34 Unable to get post office information Source: Explanation: Action: Action: Group Wise Check utility (GWCheck). GWCheck cannot read information from the post office database (wphost.db). In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “Group Wise Engine Error Codes” on page 9. 35 Memory allocation error Source: Explanation: Action: Group Wise Check utility (GWCheck). Insufficient memory to run GWCheck. Run GWCheck where adequate memory is available. 36 Message database not found Source: Explanation: Action: Group Wise Check utility (GWCheck). GWCheck cannot locate the specified message database (msgnn.db). Restore the message database from backup. 37 Exclusive access denied to message database Source: Explanation: Possible Cause: Action: GroupWise Check utility (GWCheck). GWCheck cannot get sufficient access to the specified message database (msgnn.db). Insufficient rights. Make sure you have write access to the directory where the message database is located. GroupWise Check Error Codes 227 Action: Action: Retry. There might have been a timing problem with another database user. See ifanother program, such as the POA, has the database open with exclusive access and has hung with the database open. 38 Error writing message record as user outbox item Source: Explanation: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot add a message as a received item in a user's mailbox. Perform a structural analyze/fix on the user's message database by supplying the name of the message database in the User/Resource field. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. 39 Error writing message record as user inbox item Source: Explanation: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot add a message as a sent item in a user's mailbox. Perform a structural analyze/fix on the user's message database by supplying the name of the message database in the User/Resource field. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. For additional information, look up the associated engine error code in “GroupWise Engine Error Codes” on page 9. 41 All substitute filenames used for rename of database Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck uses file extensions .dba through .dbz for backup copies of databases. All valid backup database names have already been used. Delete old backup databases so valid backup extensions are available. 42 Invalid database; truncated to nn bytes Source: Explanation: Action: Action: Action: GroupWise Check utility (GWCheck). The database has been modified externally to an illegal size. Perform a structural rebuild on the user database. See “Performing a Structural Rebuild ofa User Database” in “Databases” in the GroupWise 6.5 Administration Guide. Perform a structural rebuild on the user's message database by supplying the name ofthe message database in the User/Resource field. See “Analyzing and Fixing User and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide. Restore the database from backup. 43 Dictionary file missing; cannot continue Source: Explanation: GroupWise Check utility (GWCheck). The specified database dictionary (.dc) file is missing from the post office. 228 GroupWise 6.5 Troubleshooting 1: Error Messages Action: Copy the missing *.dc file from the po subdirectory of the software distribution directory to the post office directory. See “Software Distribution Directory” and “Post Office Directory” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. 44 Database invalid due to security breach Source: Explanation: Possible Cause: Possible Cause: Action: GroupWise Check utility (GWCheck). GWCheck cannot open the specified database because it contains an invalid verification record. The database has been modified in some unauthorized way. The database has been copied from another post office. Restore the original database from backup. 47 Error in library sync with host Source: Explanation: Possible Cause: Action: Possible Cause: Action: GroupWise Check utility (GWCheck). GWCheck synchronizes information in the library database (dmsh.db) with information in the post office database (wphost.db). The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. The post office database is damaged. In ConsoleOne, rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide. 48 Orphaned QuickFinder index file Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck encountered a QuickFinder™ index file that was not associated with any library. None. GWCheck deleted the extraneous index file. 49 Invalid QuickFinder index file Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck encountered an invalid QuickFinder index file. None. GWCheck deleted the invalid index file. 50 Orphaned blob file Source: Explanation: Action: 51 Invalid blob file Source: Explanation: Action: GroupWise Check utility (GWCheck). GWCheck encountered a BLOB file that was not associated with any library. None. GWCheck deleted the extraneous BLOB file. GroupWise Check utility (GWCheck). GWCheck encountered an invalid BLOB file. None. GWCheck deleted the invalid BLOB file. GroupWise Check Error Codes 229 52 Blob file missing trailer Source: GroupWise Check utility (GWCheck). Explanation: GWCheck encountered a BLOB file that did not have a trailer. Action: None. GWCheck deleted the invalid BLOB file. 53 Blob file truncated to 0 bytes Source: GroupWise Check utility (GWCheck). Explanation: The specified BLOB file has been modified externally to an illegal size. Action: Restore the original BLOB file from backup. 61 Error adding system document type definition Source: | GroupWise Check utility (GWCheck). Explanation: GWCheck cannot add the specified document type definition to the library database (dmsh.db) in the post office. Possible Cause: The library database is damaged. Action: Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 62 Error reading system document type definition Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot read the specified document type definition in the library database (dmsh.db) in the post office. Possible Cause: The library database is damaged. Action: Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 63 Unable to update during check error code Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot write changes to the library database (dmsh.db) in the post office. Possible Cause: The library database is damaged. Action: Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 64 Unable to complete verify during check error code Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot verify the library database (dmsh.db) in the post office. Possible Cause: The library database is damaged. Action: Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 230 GroupWise 6.5 Troubleshooting 1: Error Messages 65 Unable to add default system document types Source: Explanation: Possible Cause: Action: GroupWise Check utility (GWCheck). GWCheck cannot add default document types to the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 66 Unable to correct document display name Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot modify the specified document display name in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 67 Unable to correct element without version object Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot correct the specified element because version information was missing in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 68 Unable to synchronize document security Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot synchronize security information for the specified document in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 69 Unable to correct document without version object Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot correct the specified document because the version information was missing in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 70 Unable to correct version without document Source: Group Wise Check utility (GWCheck). GroupWise Check ErrorCodes 231 Explanation: Possible Cause: Action: GWCheck cannot correct the version information because the specified document was missing in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the Group Wise 6.5 Administration Guide. 71 Unable to correct version without element Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot correct the version information for a document because the specified element was missing in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 72 Invalid user specified for orphan document reassignment Source: Explanation: Action: Action: GroupWise Check utility (GWCheck). GWCheck cannot locate the user ID specified in the New Author field in GWCheck. Make sure you typed the user name correctly in the New Author field. If the user name is typed correctly, make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides. 73 Unable to remove document storage area Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot delete the specified document storage area. Insufficient rights. Make sure you have rights to the directory where the document storage area is located. 74 Unable to move all blobs; storage area cannot be removed Source: Explanation: Possible Cause: Action: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot delete the specified storage area because BLOBs still exist in it. Insufficient disk space. Make sure there is free disk space in the directory where you are trying to move the BLOBs to. Insufficient rights. Make sure you have rights to the directory where the document storage area is located. 75 Unable to move blob Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot move the specified BLOB file. Insufficient disk space. Make sure there is free disk space in the directory where you are trying to move the BLOBs to. 232 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: Insufficient rights. Make sure you have rights to the directory where the document storage area is located. 76 Error accessing document content Source: Explanation: Possible Cause: Action: GroupWise Check utility (GWCheck). GWCheck cannot read the content of the specified document. The library database (dmsh.db) is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 77 Error accessing blob for official version distribution list Source: Explanation: Possible Cause: Action: GroupWise Check utility (GWCheck). GWCheck cannot access the specified BLOB file containing the official version distribution list for a document in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 78 Error accessing blob for current version distribution list Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot access the specified BLOB file containing the official current distribution list for a document in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. 79 Error accessing blob for version distribution list Source: Explanation: Possible Cause: Action: Group Wise Check utility (GWCheck). GWCheck cannot access the specified BLOB file containing the distribution list for a document in the library database (dmsh.db) in the post office. The library database is damaged. Perform a structural analyze/fix on the library. See “Analyzing and Fixing Library and Document Information” in “Databases” in the GroupWise 6.5 Administration Guide. GroupWise Check Error Codes 233 234 GroupWise 6.5 Troubleshooting 1: Error Messages GroupWise Time Stamp Utility Error Messages GWTMSTMP: Error setting time stamp GWTMSTMP: Invalid user database GWTMSTMP: Invalid user ID GWTMSTMP: User login error GWTMSTMP: Error setting time stamp Source: GroupWise Time Stamp utility. Explanation: The Time Stamp utility could not write the date/time stamp information into the user database. Possible Cause: The user database is locked by another process. Action: Run the Time Stamp utility again. Possible Cause: The user database is damaged. Action: Run GroupWise Check (GWCheck) to repair the user database. See “GroupWise Check” in “Databases” in the GroupWise 6.5 Administration Guide GWTMSTMP: Invalid user database Source: GroupWise Time Stamp utility. Explanation: The Time Stamp utility could not process the user database you are running it on. Possible Cause: The file you specified using the /userdb switch is not a proper user database. Action: Make sure you specified a valid userxxx.db file. GWTMSTMP: Invalid user ID Source: GroupWise Time Stamp utility. Explanation: The Time Stamp utility cannot identify a user database for the user ID you provided when you started it. Possible Cause: The GroupWise user iD you specified using the /@u switch is not a valid Group Wise user. Action: Double-check the GroupWise user ID and provide a valid one. GWTMSTMP: User login error Source: GroupWise Time Stamp utility. Explanation: The Time Stamp utility cannot log in to the specified post office as the specified user. Possible Cause: The user ID provided with the /@u switch does not exist in the post office specified with the /ph switch. GroupWise Time Stamp Utility Error Messages 235 Action: Correct either the user information or the post office information that you have provided. Possible Cause: The user database is damaged. Action: Run GroupWise Check (GWCheck) to repair the user database. See “Group Wise Check” in “Databases” in the GroupWise 6.5 Administration Guide 236 GroupWise 6.5 Troubleshooting 1: Error Messages Client Error Messages This part of Troubleshooting 1: Error Messages helps you resolve Group Wise” client and Remote error messages. + “Windows Client Error Messages” on page 239 + “Remote Windows Client Error Messages” on page 241 + “Cross-Platform Client Error Messages” on page 247 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) Client Error Messages 237 238 GroupWise 6.5 Troubleshooting 1: Error Messages Windows Client Error Messages Users might encounter two types of errors while using the Group Wise” Windows client: + “Errors the User Can Resolve” on page 239 + “Errors the Administrator Must Resolve” on page 239 Errors the User Can Resolve Explanation: When a GroupWise Windows client error can be fixed immediately by the user, the error message includes instructions. Action: The user resolves the problem independently. Errors the Administrator Must Resolve Explanation: When a GroupWise Windows client error cannot be resolved by the user, it is typically accompanied by a GroupWise engine error code. See “GroupWise Engine Error Codes” on page 9. Action: Look up the error code in “GroupWise Engine Error Codes” on page 9, then resolve the problem for the user. Windows Client Error Messages 239 240 = GroupWise 6.5 Troubleshooting 1: Error Messages Remote Windows Client Error Messages A previous reguest to retrieve items has not been completed Cannot access your Master Mailbox Cannot find the post office Cannot find the post office in the specified path Cannot find your remote Mailbox folder Cannot log in to the gateway. Check the gateway login ID... Cannot log in to the gateway. Check the gateway login password... LDAP failure detected Reguired information is missing from the connection Some setup files are missing The following information necessary to run GroupWise against... The master Group Wise system is unable to process a request... The master GroupWise system is unable to process your current... This item uses a custom view that was not retrieved... This transmission cannot be completed due to network problems Unable to create folder {filename.ext} could not be opened as a modem script file {filename.ext} failed to open A previous request to retrieve items has not been completed Source: Possible Cause: Action: GroupWise® Windows client; Remote. 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 will be returned from the previous request, resulting in wasted transmission time and, possibly, long-distance charges. 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: Possible Cause: Action: GroupWise Windows client; Remote. 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. Run GroupWise before leaving your office, then set apassword on your Master Mailbox. Remote Windows Client Error Messages 241 Action: Action: If you are already away, have someone at your office set a password for you. Then, specify that password in Remote Options. The administrator can reset the password for a user in ConsoleOne®. See “Creating or Changing a Mailbox Password” in “Users” in the GroupWise 6.5 Administration Guide. Notify the user of the new password. Cannot find the post office Source: Possible Cause: Action: Action: Action: Group Wise Windows client; Remote. The application is unable to use the provided network connection path. The path might be entered incorrectly or there might be network changes. Verify that the specified network connection path is valid and points to a GroupWise master system post office. Check the setting of the /ph startup switch used to start the GroupWise client. In ConsoleOne, right-click the Post Office object > 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: Possible Cause: Action: GroupWise Windows client; Remote. The path to your post office, as specified in your network connection, doesn't exist. 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 > 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: Possible Cause: Action: GroupWise Windows client; Remote. The folder specified in Hit the Road or with the /ps startup switch on the command line doesn't exist. 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: Possible Cause: Action: GroupWise Windows client; Remote. The gateway login ID specified in the modem connection doesn't match the login ID of the gateway the modem is dialing. Verify the gateway login ID in the modem connection definition is correct. In ConsoleOne, double-click the Domain object where the gateway is located > double-click the Gateway object. On the GroupWise Remote Profiles page, select the profile that is not working > click Edit > verify the login ID displayed in the Remote Profile dialog box > correct it if necessary. 242 GroupWise 6.5 Troubleshooting 1: Error Messages Cannot log in to the gateway. Check the gateway login password... Source: Possible Cause: Action: Group Wise Windows client; Remote. 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. Verify the gateway password in the modem connection definition is correct. In ConsoleOne, double-click the Domain object where the gateway is located > double-click the Gateway object. On the Group Wise Remote Profiles page, select the profile that is not working > click Edit. Verify the password displayed in the Remote Profile dialog box and correct it if necessary. LDAP failure detected Source: Explanation: Possible Cause: Action: Group Wise Windows client; Remote. A GroupWise client user is using LDAP to authenticate to Group Wise but Group Wise is unable to authenticate. The LDAP server is down. 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 Group Wise 6.5 Administration Guide. Reguired information is missing from the connection Source: Possible Cause: Action: Group Wise Windows client; Remote. The connection definition is incomplete. 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 > double-click the Gateway object. On the GroupWise Remote Profiles page, select the profile that is not working > 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 Remote Profiles page, select the profile that is not working > click Edit. Verify the login ID displayed in the Remote Profile dialog box. Gateway Passowrd for Modem Connections: To check the gateway password in ConsoleOne, double-click the Domain object where the gateway is located > double-click the Gateway object. On the GroupWise Remote Profiles page, select the profile that is not working > 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 inConsoleOne, right-click the Post Office object > 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 > click Properties. In the Network Address box, click Edit. Verify the IP address and TCP port displayed in the Edit Network Address dialog box. Remote Windows Client Error Messages 243 Some setup files are missing Source: Possible Cause: Action: Group Wise Windows client; Remote. Some of the files needed to run Group Wise Remote against your Remote mailbox are missing. These files might have been deleted inadvertently. Reinstall Group Wise on your computer. See “Installing the Group Wise Windows and Cross- Platform Clients” in the Group Wise 6.5 Installation Guide. The following information necessary to run GroupWise against... Action: Possible Cause: Action: Group Wise Windows client; Remote. 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 Group Wise Remote against your Remote mailbox after a new installation. 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 > 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 > double-click the Gateway object. Verify the information displayed on the GroupWise Remote Profiles page. The master GroupWise system is unable to process a request... Source: Possible Cause: Action: GroupWise Windows client; Remote. Transmission errors damaged a response file from the master GroupWise system. 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: Possible Cause: Action: Action: GroupWise Windows client; Remote. Your master GroupWise system encountered an error while processing your requests. Your master system might have a problem. Send another request to the master GroupWise system. Record the conditions under which you encountered the error. For technical services, see Novell Technical Support (http://support.novell.com). This item uses a custom view that was not retrieved... Source: GroupWise Windows client; Remote. 244 GroupWise 6.5 Troubleshooting 1: Error Messages Possible Cause: Action: The view file of an item you want to read is too large to download as specified in the Retrieve Options dialog box. In your Remote mailbox, right-click the item > click Retrieve Selected Items. Or, click Remote > Send/Retrieve > Advanced > click the Size Limits tab increase the maximum size for attachments. This transmission cannot be completed due to network problems Source: Possible Cause: Action: Action: Group Wise Windows client; Remote. This is caused by general failures in the network connection. Make sure your network software is operating correctly. You might also need to exit and restart Windows. Record the conditions under which you encountered the error. For technical services, see Novell Technical Support (http://support.novell.com). Unable to create folder Source: Possible Cause: Action: Group Wise Windows client; Remote. 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. 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: Possible Cause: Action: Group Wise Windows client; Remote. The file you specified to open is not ina script file format. If you want your script file to have the specified filename and overwrite the existing file, open the Modem Connection dialog box > click Edit Script > enter the script information > click Save. Otherwise, select a different script filename (filename.ext) failed to open Source: Possible Cause: Action: Group Wise Windows client; Remote. This usually occurs because the script file is in use by another application or access to the file is restricted. Select a different filename, or open the Modem Connection dialog box > click Edit Script > enter the script information > click Save As. Remote Windows Client Error Messages 245 246 GroupWise 6.5 Troubleshooting 1: Error Messages Cross-Platform Client Error Messages Users might encounter two general types of errors while using the Group Wise” Cross-Platform client: + “Errors the User Can Resolve” on page 239 + “Errors the Administrator Must Resolve” on page 239 In addition, there are a few error messages specific to the Cross-Platform client: Can’t export to file Error during updating mailbox Failed to create directory Errors the User Can Resolve Explanation: When a GroupWise Cross-Platform client error can be fixed immediately by the user, the error message includes instructions. Action: The user resolves the problem independently. Errors the Administrator Must Resolve Explanation: When a GroupWise Cross-Platform client error cannot be resolved by the user, it is typically accompanied by a Group Wise engine error code. See “Group Wise Engine Error Codes” on page 9. Action: Look up the error code in “GroupWise Engine Error Codes” on page 9, then resolve the problem for the user. Can’t export to file Source: GroupWise Cross-Platform client; Linux or Macintosh. Possible Cause: You have tried to save a message or attachment in a location where you do not have sufficient rights to perform the action. Action: Choose a different directory. Action: Obtain rights to the desired directory. Error during updating mailbox Source: GroupWise Cross-Platform client; Linux or Macintosh. Possible Cause: The Cross-Platform client cannot update your Caching mailbox because there is a problem with your Caching mailbox. Action: Use GroupWise Check to repair your Caching mailbox. See “Starting GWCheck on a Linux Workstation” in “Databases” in the GroupWise 6.5 Administration Guide. NOTE: GroupWlse Check is not currently available for Macintosh users. Cross-Platform Client Error Messages 247 Failed to create directory Source: GroupWise Cross-Platform client; Linux or Macintosh. Possible Cause: You have tried to create a Caching mailbox or an archive in a location where you do not have sufficient rights to perform the action. Action: Choose a different directory. Action: Obtain rights to the desired directory. 248 GroupWise 6.5 Troubleshooting 1: Error Messages Documentation Updates This section lists updates to Group Wise 6.5 Troubleshooting 1: Error Messages that have been made since the inttial release of GroupWise® 6.5. The information will help you to keep current on documentation updates and, in some cases, software updates (such as a Support Pack release). The information is grouped according to the date when GroupWise 6.5 Troubleshooting 1: Error Messages was republished. Within each dated section, the updates are listed by the names of the main table of contents sections. GroupWise 6.5 Troubleshooting 1: Error Messages has been updated on the following dates: + “September 19, 2005 (GroupWise 6.5 SP5)” on page 249 + “February 28, 2005 (GroupWise 6.5 SP4)” on page 249 + “August 23, 2004 (GroupWise 6.5 for Linux)” on page 250 + “October 31, 2003” on page 250 + “July 1, 2003 (SP1)” on page 250 September 19, 2005 (GroupWise 6.5 SP5) Location Change Engine Errors 920C Added a new engine error code. February 28, 2005 (GroupWise 6.5 SP4) Location Change Engine Errors 8201 Added two new solutions to this engine error code. 8567 Added a new engine error code. Agent Error Messages WEBACC: Unable to find Added two new solutions to this error message. the specified user Documentation Updates 249 Location Administration Error Messages “GroupWise Time Stamp Utility Error Messages” on page 235 Change Added error messages for the GroupWise Time Stamp utility. August 23, 2004 (GroupWise 6.5 for Linux) Location Engine Errors 8573 AD01, AD06, AD08, AD09, ADOC, AD10, AD11, AD20, AD21, AD25, AD29, AD2E, AD2F C003, C005 D078, DB60 DB29 Client Errors “Cross-Platform Client Error Messages” on page 247 October 31, 2003 Location Engine Errors C067 July 1, 2003 (SP1) Location Engine Errors Change Added one engine error code in the 8xxx range. Added 13 engine error codes in the Axxx range. Added two engine error codes in the Cxxx range. Added two engine error codes in the Dxxx range. Added asterisk (*) to the list of characters that are invalid in GroupWise object names. Added Cross-Platform client error messages. Change Emphasized that the suggestion to delete users’ archive directories applies only to new users who have not yet been able to archive anything. Change 250 GroupWise 6.5 Troubleshooting 1: Error Messages Location 8568, 8569, 8570, 8572, 891A, 891B, 891C, 891D 9007 and 9008 C081 D072, D073, D074, D075, D076, D077, and DB59 D069 and D109 GroupWise Engine Error Codes Change Added new 6.5 engine error codes in the 8xxx range. Added new 6.5 engine error codes in the 9xxx range. Updated the information about an existing error code in the Cxxx range Added new 6.5 engine error codes in the Dxxx range. Updated the information about some existing error codes in the Dxxx range. The following updates were made to the Group Wise Engine Error Codes section of Troubleshooting 1: Error Messages: Documentation Updates 251 252 GroupWise 6.5 Troubleshooting 1: Error Messages