Novell GROUPWISE 7 - TROUBLESHOOTING 1 Troubleshooting Manual

Error messages

page of 284

/ 284
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual

Novell

GroupWise

A p r i l 1 6 , 2 0 0 7

T R O U B L E S H O O T I N G 1 :

E R R O R M E S S A G E S

w w w . n o v e l l . c o m

Table of Contents

Need help?

Do you have a question about the GROUPWISE 7 - TROUBLESHOOTING 1 and is the answer not in the manual?

Questions and answers

Summary of Contents for Novell GROUPWISE 7 - TROUBLESHOOTING 1

Page 1 Novell GroupWise ® w w w . n o v e l l . c o m T R O U B L E S H O O T I N G 1 : A p r i l 1 6 , 2 0 0 7...
Page 2 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.
Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
Page 5: Table Of Contents
Contents About This Guide Part I GroupWise Engine Error Codes 1 0xxx Engine Error Codes 2 8xxx Engine Error Codes 81xx Errors ............. . . 15 82xx Errors .
Page 6 C07x Errors ............. . . 76 C08x Errors .
Page 7 F01x Errors ............. . 164 F02x Errors .
Page 8 A Documentation Updates April 16, 2007 (GroupWise 7 SP2) ..........283 June 15, 2006 (GroupWise 7 SP1).
Page 9: About This Guide
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 of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.
Page 10 Troubleshooting 3: Message Flow and Directory Structure GroupWise Client User Guides GroupWise Client Frequently Asked Questions (FAQ) 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 ( , etc.) denotes a Novell trademark.
Page 11: Part I Groupwise Engine Error Codes
“Exxx Engine Error Codes” on page 143 “Fxxx Engine Error Codes” on page 163 Other sources of assistance include ® Novell Support (http://www.novell.com/support) Novell Support Knowledgebase (http://www.novell.com/support/supportcentral) GroupWise 7 Support Forums (http://support.novell.com/forums/2gw.html) Novell GroupWise Support Community (http://www.novell.com/support/ browse.do?WidgetName=BROWSE_PRODUCT&BROWSE_PRODUCT.TaxoName=SG_Su pportGoals&NodeType=leaf&NodeName=GroupWise&TaxoName=SG_SupportGoals&BRO WSE_PRODUCT.isProductTaxonomy=true&BROWSE_PRODUCT.NodeId=SG_GROUPWI SE_1_1&BROWSE_PRODUCT.NodeType=leaf&BROWSE_PRODUCT.thisPageUrl=%2Fpr oduct%2Fproducts.do&NodeId=SG_GROUPWISE_1_1&id=m1&AppContext=AC_SiteCent ral) GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)
Page 12 GroupWise 7 Troubleshooting 1: Error Messages...
Page 13: 0Xxx Engine Error Codes
0xxx Engine Error Codes “0002 Unexpected error” on page 13 “0003 Encryption password failed verification process” on page 13 “0004 Encryption password too long” on page 13 “0005 Unexpected error” on page 13 “0006 Unexpected error” on page 13 “0007 Unexpected error” on page 13 “0008 Unexpected error”...
Page 14 0008 Unexpected error Source: GroupWise engine; encryption. Action: See “000x Unexpected error” on page 14 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. GroupWise 7 Troubleshooting 1: Error Messages...
Page 15: 8Xxx Engine Error Codes
8xxx Engine Error Codes “81xx Errors” on page 15 “82xx Errors” on page 16 “85xx Errors” on page 27 “88xx Errors” on page 31 “89xx Errors” on page 32 “8Bxx Errors” on page 42 “8Cxx Errors” on page 42 “8Fxx Errors” on page 42 “8xxx Unexpected Error”...
Page 16: 82Xx Errors
Action: After exiting all the agents, unload the agent engine (gwenn5.nlm), then perform the update. See “Updating Your GroupWise 6.x System to Version 7” in “Update” in the GroupWise 7 Installation Guide. Possible Cause: If this error occurs when starting the GroupWise client, the user might have exceeded the limit of viewable 65,000 items per folder.
Page 17 “8214 Unsupported encryption level” on page 26 “8215 Path root error” on page 27 “8219 Cannot connect to remote network resource” on page 27 “821A Access to a critical file denied” on page 27 8200 File I/O error Source: GroupWise engine; file input/output. Explanation: Generic file I/O error.
Page 18 Possible Cause: If this error occurs for a user who has previously been able to access ® GroupWise successfully, the user’s Novell eDirectory object might have become damaged. Action: Delete the user object from eDirectory, then re-create it. Do not delete the user’s GroupWise account, because this would delete the user’s mailbox as...
Page 19 Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator. Possible Cause: Another program might already have the required file open with exclusive access. Action: 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.
Page 20 8204 Disk full Source: GroupWise engine; file input/output. Explanation: Disk full. Possible Cause: There is no space left on a disk when writing and/or creating a file. Action: Create space on disk by deleting unwanted or unnecessary files. Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner.
Page 21 rename it. See also “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 7 Administration Guide. Possible Cause: 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”...
Page 22 Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 7 Administration Guide. 8208 Cannot modify file Source: GroupWise engine; file input/output. Explanation: File modify error. Possible Cause: Cannot move or rename the file. An error occurred when renaming or moving a file to another location.
Page 23 Action: Verify that 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 GroupWise > Post Offices. Check the properties of each Post Office object to make sure that the post office directory for each post office exists.
Page 24 Possible Cause: A directory required for the normal flow of GroupWise messages could be missing. Action: See “Message Transfer/Storage Directories” in “Directory Structure Diagrams” in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure. Verify the existence, ownership, and rights of the directories involved with message flow (domain, post office, and MTA local directory).
Page 25 Possible Cause: An attempt to lock a file failed. Action: Verify that the file is not currently locked by another process that has terminated. Possible Cause: You cannot open the specified file because another user might have the file open. Action: Ask the other user to close the file.
Page 26 Update to the latest version of GroupWise. To check the date of the GroupWise client you are using, click Help > About GroupWise. For technical services and file updates, see Novell Support (http://support.novell.com).
Page 27: 85Xx Errors
Action: 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 check whether or not it is locked.
Page 28 Action: Configure TCP/IP on the server correctly. If this error occurs on a NetWare server, make sure you have the latest version of the TCPIP NLM. For technical services and file updates, see Novell Support (http://support.novell.com). Action: Reboot the server.
Page 29 Action: Exit and restart GroupWise when the machine is back up. 8555 Port in use Source: GroupWise engine; general communication. Explanation: Port in use. Possible Cause: 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.
Page 30 8567 Data not in BCEF format Source: GroupWise engine; general communication. Explanation: A packet of information received by an agent was not in the expected format. Possible Cause: The packet was damaged somewhere between the source and the destination of the data.
Page 31: 88Xx Errors
8571 SOAP port already in use Source: GroupWise engine; general communication. Explanation: The SOAP port used by the POA to communicate with SOAP clients is already in use by another program on the server. Possible Cause: You are trying to run two POAs on the same server and you have not given them unique SOAP port numbers.
Page 32: 89Xx Errors
Action: See “8xxx Unexpected error” on page 880C Unexpected error Source: GroupWise engine; inter- or intra-process communication Action: See “8xxx Unexpected error” on page 2.5 89xx Errors “8901 Cannot use TCP/IP services” on page 33 “8902 Cannot load TCP/IP services” on page 33 “8903 Cannot use TCP/IP services”...
Page 33 “8926 Unknown host” on page 41 “8927 Host not reachable” on page 41 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.
Page 34 numeric format (172.16.5.18), rather than as a host name that requires resolution, when setting the /ipa switch. Action: 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.
Page 35 Possible Cause: If this error occurs from the POA, the server where the POA runs might not have the most current version of TCP/IP. Action: Install the latest TCP/IP. For technical services and file updates, see Novell Support (http://support.novell.com). 8912 Cannot read on connection; timed out Source: GroupWise engine;...
Page 36 Possible Cause: 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. Action: Restart the GroupWise client when the machine is back up. Possible Cause: If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages might be restarting.
Page 37 8917 TCP/IP name lookup failed Source: GroupWise engine; TCP/IP communication. Explanation: A GroupWise agent or client cannot ping the specified IP address. Possible Cause: The agent or client was passed an invalid IP address. Action: Ping the IP address manually to see if it responds. If it does not respond, correct the problem with the server associated with that IP address.
Page 38 Explanation: You have configured an agent for SSL, but the agent cannot locate the SSL certificate. Possible Cause: In ConsoleOne, you enabled SSL on the Agent object Network Address page but did not provide the certificate information on the SSL Settings page. Action: Finish configuring the agent for SSL.
Page 39 “Securing the Domain with SSL Connections to the MTA” in “Message Transfer Agent” “Securing Internet Agent Connections with SSL” in “Internet Agent” “Securing WebAccess Agent Connections with SSL” in “WebAccess” 891E Insufficient memory for SSL Source: GroupWise engine; TCP/IP communication. Explanation: A GroupWise agent failed to establish an SSL connection because insufficient memory is available for creating the connection.
Page 40 Possible Cause: Both servers might have identical certificate files. Action: Obtain a new certificate file for one of the servers. See “Server Certificates and Encryption” in “Security Administration” in the GroupWise 7 Administration Guide. 8922 SSL connect failure Source: GroupWise engine; TCP/IP communication. Explanation: A GroupWise agent cannot establish an SSL connection because the other server failed to connect.
Page 41 Explanation: An agent that is configured for TCP/IP attempted to contact another agent and the connection was refused. Possible Cause: The agent is not communicating on the right TCP port number. Action: Determine the configuration of the target agent and make sure the initiating agent is using the correct port number.
Page 42: 8Bxx Errors
Action: Make sure that all routers are running. 2.6 8Bxx Errors “8B02 Unexpected error” on page 42 8B02 Unexpected error Source: GroupWise engine; named memory. Action: See “8xxx Unexpected error” on page 2.7 8Cxx Errors “8C04 Unexpected error” on page 42 “8C09 Unexpected error”...
Page 43: 8Xxx Unexpected Error
“Using MTA Startup Switches” in “Message Transfer Agent” in the GroupWise 7 Administration Guide. 2.9 8xxx Unexpected Error “8xxx Unexpected error” on page 43 8xxx Unexpected error Source: GroupWise engine. Explanation: An engine error has occurred for which GroupWise does not have a specific error message.
Page 44 GroupWise 7 Troubleshooting 1: Error Messages...
Page 45: 9Xxx Engine Error Codes
9xxx Engine Error Codes “90xx Errors” on page 45 “93xx Errors” on page 45 “9xxx Unexpected Error” on page 46 3.1 90xx Errors “9007 Client not set up for SSL” on page 45 “9008 Server does not support SSL” on page 45 9007 Client not set up for SSL ®...
Page 46: 9Xxx Unexpected Error
9302 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 9304 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error” on page 9305 Unexpected error Source: GroupWise engine; loadable language resource. Action: See “9xxx Unexpected error”...
Page 47: Axxx Engine Error Codes
Axxx Engine Error Codes “A0xx Errors” on page 47 “A5xx Errors” on page 47 “A6xx Errors” on page 47 “A8xx Errors” on page 48 “AAxx Errors” on page 49 “ACxx Errors” on page 49 “ADxx Errors” on page 50 “Axxx Unexpected Error” on page 54 4.1 A0xx Errors “A001 Unexpected error”...
Page 48: A8Xx Errors
A602 Unexpected error Source: GroupWise engine; data list management. Action: See “Axxx Unexpected error” on page 4.4 A8xx Errors “A801 Auto-Date formula too long” on page 48 “A802 Auto-Date formula has incorrect syntax” on page 48 “A803 Auto-Date formula not specified” on page 48 “A804 Auto-Date formula generates too many occurrences”...
Page 49: Aaxx Errors
Possible Cause: 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. Action: If the user does not want to see the warning, the range over which the given Auto-Date spans needs to be shortened.
Page 50: Adxx Errors
AC03 Zipped file damaged Source: GroupWise engine; zip/compression. Explanation: The zipped file failed a checksum test. Action: None. GroupWise cannot unzip the file. 4.7 ADxx Errors “AD01 No LDAP Support” on page 50 “AD06 The LDAP server information passed in is not valid” on page 50 “AD08 No username or password specified for logging into the LDAP server”...
Page 51 Explanation: The Installation program cannot communicate with the LDAP server because it is using incorrect information. Possible Cause: 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.
Page 52 AD10 SSL certificate was not found Source: Internet Agent Installation program or WebAccess Installation program on Linux Explanation: You selected to use an SSL connection with the LDAP server, but the Installation program cannot establish an SSL connection. Possible Cause: You did not provide the correct SSL certificate file information to the Installation program.
Page 53 Possible Cause: The eDirectory schema has not yet been extended to accommodate GroupWise objects. Action: Extend the schema, as described in “Check eDirectory Schema” in “System” in the GroupWise 7 Administration Guide. Action: Run the Installation program again, as described in “Setting Up a Basic GroupWise System”...
Page 54: Axxx Unexpected Error
AD2E A dynamic memory allocation function failed when calling an LDAP function Source: Internet Agent Installation program or WebAccess Installation program on Linux Explanation: The Installation program cannot function in the current environment. Possible Cause: Insufficient memory. Action: Stop some programs that are running on the server in order to free up some memory.
Page 55: Bxxx Engine Error Codes
Bxxx Engine Error Codes “B300 File transmission failed” on page 55 “B309 Port already in use” on page 55 “B30A No peer listening for connection” on page 55 B300 File transmission failed ® Source: GroupWise engine; Message Transfer Protocol. Explanation: The POA was not able to transfer a message file to the MTA. Possible Cause: The MTA restarted during transmission of the file.
Page 56 Action: Reconfigure the MTA for TCP/IP links. See “Changing the Link Protocol between Domains” in “Message Transfer Agent” in the GroupWise 7 Administration Guide. GroupWise 7 Troubleshooting 1: Error Messages...
Page 57: Cxxx Engine Error Codes
Cxxx Engine Error Codes “C00x Errors” on page 57 “C01x Errors” on page 60 “C02x Errors” on page 62 “C03x Errors” on page 66 “C04x Errors” on page 68 “C05x Errors” on page 71 “C06x Errors” on page 74 “C07x Errors” on page 76 “C08x Errors”...
Page 58 Action: 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 GroupWise View but not have a Novell eDirectory object created for it. Connect to the secondary domain. See “Connecting to a...
Page 59 C009 Database error Source: GroupWise engine; database services. Action: “C0xx Database error (Support assistance recommended)” on page C00A Database error Source: GroupWise engine; database services. Action: “C0xx Database error (Support assistance recommended)” on page C00B Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (general database repair strategies)”...
Page 60: C01X Errors
“Moving GroupWise Accounts” in “Users” in the GroupWise 7 Administration Guide. Possible Cause: If this error occurs when rebuilding a database, you might not be connected to the correct GroupWise system. Action: Connect to the GroupWise system where the database is located. See “Connecting to a Domain”...
Page 61 C010 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page C011 Database being modified Source: GroupWise engine; database services. Explanation: Read encountered a modified block. Possible Cause: A read operation encountered a block in the database that was being modified by another user.
Page 62: C02X Errors
C017 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page C018 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page C019 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)”...
Page 63 “C023 Database error” on page 64 “C024 Database dictionary damaged” on page 64 “C026 Database error” on page 65 “C027 Database error” on page 65 “C028 Database error” on page 65 “C029 Database version unsupported” on page 65 “C02A Cannot access database dictionary file” on page 65 “C02B Database error”...
Page 64 Action: The Microsoft Gateway for NetWare is not intended as a full service router for NetWare services. Use a more robust connection to the post office. Action: 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: GroupWise engine;...
Page 65 Action: Make sure the file exists in the post office directory. If it does ngwguard.dc not, copy it from the subdirectory of your software distribution directory. For the specific locations of this file, see “Post Office Directory” and “Software Distribution Directory”...
Page 66: C03X Errors
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 “C0xx Database error (database dictionary file)” on page C02C Database error Source: GroupWise engine;...
Page 67 Possible Cause: GroupWise cannot access the database because it was created using a newer version of GroupWise. Action: 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: GroupWise engine; database services.
Page 68: C04X Errors
C03F Database error Source: GroupWise engine; database services. Explanation: GroupWise tried to open a file that could not be recognized as a valid GroupWise database. Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases”...
Page 69 “C04C Database error” on page 70 “C04D Memory error” on page 70 “C04E Database error” on page 70 “C04F Database checksum error” on page 70 C040 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page C042 Database being modified Source: GroupWise engine;...
Page 70 Action: See “C0xx Database error (general database repair strategies)” on page C047 Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (Support assistance recommended)” on page C048 Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page C04A Unexpected error Source: GroupWise engine;...
Page 71: C05X Errors
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.
Page 72 Guide. Action: Restore the original ngwguard.db file from backup. If the original guardian database is not available, seek assistance. For technical services, see Novell Support (http://support.novell.com). Possible Cause: A user was moved to a different post office and then moved back to the original post office.
Page 73 deleted when the user was moved out, the POA cannot create the new user database. Action: Delete the residual user database, then move the user back into the post office. “Moving GroupWise Accounts” in “Users” in the GroupWise 7 Administration Guide.
Page 74: C06X Errors
6.7 C06x Errors “C060 Unexpected error” on page 74 “C061 Unexpected error” on page 74 “C062 Unexpected error” on page 74 “C063 Database error” on page 74 “C066 Unexpected error” on page 74 “C067 Database error” on page 74 “C068 Database error” on page 75 “C069 Database error”...
Page 75 Possible Cause: The post office database (wphost.db) has been damaged. Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 7 Administration Guide. Possible Cause: If this error occurs when a new user starts the GroupWise client, there might be a problem with the user database (userxxx.db).
Page 76: C07X Errors
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 7 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.
Page 77 “C078 Unexpected error” on page 77 “C079 Unexpected error” on page 77 “C07A Unexpected error” on page 78 “C07B Database error” on page 78 “C07C Unexpected error” on page 78 “C07D Unexpected error” on page 78 “C07E Unexpected error” on page 78 “C07F Unexpected error”...
Page 78: C08X Errors
Action: See “C0xx Unexpected error” on page C07A Unexpected error Source: GroupWise engine; database services. Action: See “C0xx Unexpected error” on page C07B Database error Source: GroupWise engine; database services. Action: See “C0xx Database error (general database repair strategies)” on page C07C Unexpected error Source: GroupWise engine;...
Page 79 Action: Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 7 Administration Guide. C081 Attachment missing Source: GroupWise engine; database services. Explanation: An attachment file that should be available under in the post office offiles directory is missing.
Page 80: C0Xx Unexpected Error
Action: If this error occurs on a message database (msgnnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 7 Administration Guide. Action: If the damaged database cannot be repaired successfully, restore it from backup.
Page 81: Dxxx Engine Error Codes
Dxxx Engine Error Codes “D00x Errors” on page 81 “D01x Errors” on page 84 “D02x Errors” on page 86 “D03x Errors” on page 89 “D04x Errors” on page 90 “D05x Errors” on page 92 “D06x Errors” on page 95 “D07x Errors” on page 98 “D10x Errors”...
Page 82 “D006 Unexpected error” on page 82 “D009 Cannot use group name in distribution list” on page 82 “D00A Syntax error in address” on page 83 “D00B Missing closing quotation mark (")” on page 83 “D00C Unexpected error” on page 83 “D00D Cannot match parentheses”...
Page 83 Possible Cause: A group name was entered in the distribution list for a routed item. Groups are not supported in a workflow step. Action: Delete the group name, then provide the names of the individual users in the group. D00A Syntax error in address Source: GroupWise engine.
Page 84: D01X Errors
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.
Page 85 personal groups could be made into public distribution lists and selected manually when replying to all users. D018 Unexpected error Source: GroupWise engine. Action: See “Dxxx Unexpected error” on page 141 D019 Password incorrect Source: GroupWise engine. Explanation: Invalid password. Action: Type the correct password.
Page 86: D02X Errors
Possible Cause: 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. Action: Check and repair the databases of the master mailbox. See “Maintaining User/ Resource and Message Databases”...
Page 87 D020 Rule caused infinite loop Source: GroupWise engine. Explanation: Rule hop count exceeded. Possible Cause: The execution of a rule has caused a message to be sent, which caused the execution of a rule, and so on. To prevent the possibility of infinite looping, the rule execution has been terminated.
Page 88 Action: Check the priority subdirectories of the directory in the post \wpcsout\ofs 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: GroupWise engine.
Page 89: D03X Errors
D02F Database error Source: GroupWise engine. Explanation: No document record number (DRN) for status. Possible Cause: The domain database (wpdomain.db) or post office database (wphost.db) might be damaged. Action: Rebuild the post office database. See “Rebuilding Domain or Post Office Databases”...
Page 90: D04X Errors
“D041 No recipients in post office” on page 90 “D043 Inconsistent distribution list” on page 90 “D044 Auto-rebuild disabled” on page 91 “D049 Error reported from Novell NDS” on page 91 “D04A Unexpected error” on page 91 “D04B Unexpected error” on page 91 “D04F Unexpected error”...
Page 91 Action: 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: GroupWise engine. ® Explanation: The GroupWise Administrator snap-in to ConsoleOne was unable to retrieve ®...
Page 92: D05X Errors
7.6 D05x Errors “D050 Cannot connect to specified post office” on page 92 “D051 Cannot connect to specified post office” on page 92 “D054 Cannot connect to specified post office” on page 93 “D055 Cannot connect to specified post office” on page 93 “D057 Cannot connect to any post office”...
Page 93 D054 Cannot connect to specified post office Source: GroupWise engine. Explanation: Missing path for direct mode connection. Possible Cause: 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. Action: Set up the path for the specified post office in the post office Identification page in ConsoleOne.
Page 94 Possible Cause: A user is running the latest version of the GroupWise client, but the post office has not yet been updated. Action: Update the post office. See “Update” in the GroupWise 7 Installation Guide. Possible Cause: The post office has been updated, but the latest version of the POA has not yet been installed and started.
Page 95: D06X Errors
Possible Cause: 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. Action: Update the information in users’ /ipa and /ipp switch settings with the current IP address information.
Page 96 “D065 Attempt to purge item that has not been backed up” on page 96 “D066 Attempt to purge an item from a user that has not been backed up” on page 97 “D069 Attempt to open invalid backup location” on page 97 “D06B LDAP failure detected”...
Page 97 Administration Guide. See also “GroupWise Time Stamp Utility” in “Databases” in the GroupWise 7 Administration Guide. D066 Attempt to purge an item from a user that has not been backed up Source: GroupWise engine. Explanation: Client Cleanup options are set so that items cannot be purged from users’ mailboxes until they have been backed up.
Page 98: D07X Errors
D06E Lockout of older GroupWise clients being enforced Source: GroupWise engine. Explanation: The POA is not allowing GroupWise client users with older versions of the client software to access the post office. Possible Cause: The administrator does not want older versions of the GroupWise client to access the post office.
Page 99 D072 Changing the LDAP password has been disabled Source: GroupWise engine. Explanation: 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. Action: Enable LDAP password changes in ConsoleOne. See “Providing LDAP Authentication for GroupWise Users”...
Page 100 D076 Missing trusted application name Source: GroupWise engine. Explanation: A trusted application tried to log in to the POA and was not successful because no application name was provided. Possible Cause: The trusted application is not providing an application name. Action: Add an application name to the trusted application.
Page 101: D10X Errors
Action: The GroupWise administrator can make the mailbox size limit larger, as described in “Setting Mailbox Size Limits” in “Post Offices” in the GroupWise 7 Administration Guide. D07C Invalid content in user’s rule Source: GroupWise engine. Explanation: A rule cannot be executed because it does not work. Possible Cause: The user has constructed the rule incorrectly.
Page 102 Action: If using startup switches, check the /ph switch to make sure the path to the post office is correct. Action: Start the GroupWise client using the /@u or /la startup option to specify the GroupWise user ID. Possible Cause: The user is not yet set up as a GroupWise user. Action: Set the user up as a GroupWise user.
Page 103 Action: Rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 7 Administration Guide. Possible Cause: If this error occurs in systems where new users are added from multiple administrator workstations, preferences might be set differently on different administrator workstations.
Page 104 D104 Ambiguous post office Source: GroupWise engine; database interface. Explanation: The post office is ambiguous. Possible Cause: There are multiple post offices in the same domain. Action: The GroupWise client pops up a list so the user can correct the ambiguity manually.
Page 105 D108 Unexpected error Source: GroupWise engine; database interface. Action: See “Dxxx Unexpected error” on page 141. D109 Bad parameter Source: GroupWise engine; database interface. Explanation: A GroupWise program passed invalid information to another GroupWise program. Possible Cause: The user’s mailbox contains a damaged message. Action: Run a structural rebuild on the user database (userxxx.db) and message database (msgnnn.db).
Page 106: D11X Errors
D10C Unexpected error Source: GroupWise engine; database interface. Action: See “Dxxx Unexpected error” on page 141. 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.
Page 107 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.
Page 108 D118 Database error Source: GroupWise engine; database interface. Explanation: Field not found. Possible Cause: Unable to find the field in the database. Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases”...
Page 109: D12X Errors
D11D GroupWise version newer than database Source: GroupWise engine; database interface. Explanation: New program version. Possible Cause: The GroupWise client has been installed on a workstation where the GroupWise demo that comes with the PerfectOffice Suite 3.0 had already been installed.
Page 110: D50X Errors
Possible Cause: 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. Action: Check for the existence of the temporary directory on the user workstation. Action: Check for available disk space.
Page 111: D70X Errors
Possible Cause: An agent has attempted to send a message to the defined administrator; however, no administrator record was found in the database. Action: To receive these messages, define an administrator for the domain. See “Notifying the Domain Administrator” in “Message Transfer Agent”...
Page 112 D701 Unexpected error Source: GroupWise engine; directory services access. Action: See “Dxxx Unexpected error” on page 141. D704 Unexpected error Source: GroupWise engine; directory services access. Action: See “Dxxx Unexpected error” on page 141. D705 Unexpected error Source: GroupWise engine; directory services access. Action: See “Dxxx Unexpected error”...
Page 113: D71X Errors
Action: See “Dxxx Unexpected error” on page 141. D70A Memory error Source: GroupWise engine; directory services access. Explanation: Memory error. Possible Cause: Unable to lock or allocate memory. Action: The GroupWise client user should exit and restart GroupWise. D70B Database inconsistency detected Source: GroupWise engine;...
Page 114 “D714 User database temporarily disabled” on page 115 “D715 User has failed in too many login attempts, login disabled” on page 115 “D716 The System Address Book needs to be refreshed” on page 115 D710 Incompatible platform Source: GroupWise engine; directory services access. Explanation: Requested platform path not found.
Page 115 Action: Make sure the file exists in the post office directory. If it does ngwguard.dc not, copy it from the subdirectory of your software distribution directory. For the specific locations of this file, see “Post Office Directory” and “Software Distribution Directory”...
Page 116: D9Xx Errors
7.16 D9xx Errors “D901 Unexpected error” on page 116 “D902 Unexpected error” on page 116 “D904 Unexpected error” on page 116 “D90A Unexpected error” on page 116 “D90B Unexpected error” on page 116 “D912 Cannot process message file” on page 116 D901 Unexpected error Source: GroupWise engine;...
Page 117: Da0X Errors
7.17 DA0x Errors “DA0C Incorrect DLL version” on page 117 “DA0D Cannot create directory in post office” on page 117 “DA0E Path to post office database not specified” on page 117 DA0C Incorrect DLL version Source: GroupWise engine; Post Office Agent. Explanation: Wrong DLL.
Page 118: Da1X Errors
7.18 DA1x Errors “DA10 Cannot read post office configuration information” on page 118 “DA12 Invalid application configuration name” on page 118 “DA13 /name switch required” on page 118 “DA17 /user and /password switches required for this configuration” on page 119 DA10 Cannot read post office configuration information Source: GroupWise engine;...
Page 119: Db0X Errors
DA17 /user and /password switches required for this configuration Source: GroupWise engine; Post Office Agent. Explanation: The /user /password switches are required when the POA must log into a remote server. Possible Cause: 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.
Page 120 Action: None. DB02 Database access error Source: GroupWise engine; administration engine. Explanation: Database access error. Possible Cause: Cannot complete the requested operation because the database is being updated. Action: Retry the operation later. If you still cannot access the database, check file activity using your network administration utilities.
Page 121 Explanation: Non-unique name. Possible Cause: The specified name (object.po.domain) conflicts with an existing user, resource, group, or nickname. Action: Specify a new, unique name. DB09 User owns resource Source: GroupWise engine; administration engine. Explanation: User owns a resource. Possible Cause: The specified user cannot be deleted or moved because he or she owns a resource.
Page 122: Db1X Errors
DB0C Cannot close database Source: GroupWise engine; administration engine. Explanation: Error closing database. Possible Cause: An error was encountered while attempting to close the database. Action: Check the network connection to the database location. DB0E Insufficient memory to initialize database Source: GroupWise engine;...
Page 123 DB10 Post office not found Source: GroupWise engine; administration engine. Explanation: Post office not found. Possible Cause: Cannot find the specified post office. Action: 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.
Page 124 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”...
Page 125: Db2X Errors
Action: If the 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”...
Page 126 Explanation: A link between domains is invalid. Action: Select a valid link type and link protocol for the domain link. See “Editing a Domain Link” in “Domains” in the GroupWise 7 Administration Guide. DB25 Duplicate domain name Source: GroupWise engine; administration engine. Explanation: Duplicate domain name.
Page 127 Action: Define Lotus Notes users in a foreign domain. See “Connecting to Non- GroupWise Messaging Systems” in the GroupWise 7 Multi-System Administration Guide. DB2A Invalid name Source: GroupWise engine; administration engine. Explanation: Invalid name. Possible Cause: An invalid or restricted name has been specified. Action: Enter a valid name.
Page 128: Db3X Errors
Action: Check the specified gateway directory path and make sure the requested gateway is installed. For a list of gateways, see GroupWise Gateways (http:// www.novell.com/documentation/gwgateways). DB31 Required field missing or empty Source: GroupWise engine; administration engine. Explanation: A required field is missing or empty.
Page 129 Action: Check the record for a missing required field. DB33 Cannot open all post offices Source: GroupWise engine; administration engine. Explanation: Unable to open all post offices. Possible Cause: There are more post offices defined than the operating system file handles allow.
Page 130 DB38 Cannot delete domain that has post offices Source: GroupWise engine; administration engine. Explanation: Post offices exist for this domain. Possible Cause: An attempt was made to delete a domain that has post offices assigned to it. Action: Move the post offices to another domain. See “Moving a Post Office”...
Page 131: Db4X Errors
Possible Cause: An exclusive open for a domain to be merged or released failed because the domain is already in use. Action: Have all administrators exit the domain database (wpdomain.db) before running the merge or release. Action: Stop the MTA in the domain to be merged or released. DB3D Database sorting language changed Source: GroupWise engine;...
Page 132 DB41 Database does not match domain or post office Source: GroupWise engine; administration engine. Explanation: Incorrect database path Possible Cause: The database found at the specified path does not match the specified domain/ post office name. Action: Enter the correct path. DB42 Information lost during recovery Source: GroupWise engine;...
Page 133 Action: Make sure the software distribution directory has been created in your GroupWise system. See “Software Directory Management” in “System” in the GroupWise 7 Administration Guide “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.
Page 134 Action: 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”...
Page 135: Db5X Errors
7.24 DB5x Errors “DB50 Access to this library has been enabled by WebPublisher” on page 135 “DB51 Required network address information is missing” on page 135 “DB52 Required path information is missing” on page 136 “DB53 No message transfer POA has been selected” on page 136 “DB55 No POA is available for client/server”...
Page 136 DB52 Required path information is missing Source: GroupWise engine; administration engine. Explanation: An action cannot be completed because of insufficient configuration information. Possible Cause: A domain or post office has not been properly configured with the path to the directory where the domain or post office is located. Action: Check the UNC path information provided for the domain or post offices.
Page 137: Db6X Errors
Action: Choose a different name for the new user. Check for existing names first. See “Email Address Lookup” in “System” in the GroupWise 7 Administration Guide. DB58 Specified e-mail address conflicts with an address from a post office alias record Source: GroupWise engine;...
Page 138: Dexx Errors
DB61 The signature information is too large Source: GroupWise engine; administration engine. Explanation: ConsoleOne cannot save the global signature you have created because it exceeds 2.43 MB. Possible Cause: You have tried to create a global signature that is larger than 2.43 MB. Action: Remove some text or objects from the global signature.
Page 139: Dfxx Errors
7.27 DFxx Errors “DF10 Required file or directory missing” on page 139 “DF15 Records lost during rebuild” on page 139 “DF17 Cannot create required directory” on page 140 “DF1C Document storage area definitions are not identical” on page 140 “DF27 Invalid NGWCHECK.DB database migration level” on page 140 “DF28 Failure using the NGWCHECK.DB database”...
Page 140 Action: 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 7 Administration Guide. DF17 Cannot create required directory Source: GroupWise engine;...
Page 141: Dxxx Unexpected Error
7.28 Dxxx Unexpected Error “Dxxx Unexpected error” on page 141 Dxxx 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 Dxxx Engine Error Codes 141...
Page 142 142 GroupWise 7 Troubleshooting 1: Error Messages...
Page 143: Exxx Engine Error Codes
Exxx Engine Error Codes “E50x Errors” on page 143 “E51x Errors” on page 145 “E52x Errors” on page 147 “E7xx Errors” on page 149 “E80x Errors” on page 149 “E81x Errors” on page 151 “E82x Errors” on page 152 “E84x Errors” on page 153 “EA0x Errors”...
Page 144 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.
Page 145: E51X Errors
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 7 Administration Guide. Action: Create the new library on another post office. E50E Unexpected error Source: GroupWise engine;...
Page 146 E513 Unexpected error Source: GroupWise engine; document management. Action: See “Exxx Unexpected error” on page 161. E514 Document version must be checked out and in by same user Source: GroupWise engine; document management. Explanation: User IDs do not match. Possible Cause: 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.
Page 147: E52X Errors
Explanation: The user has exceeded his or her limit of disk space in the library. Possible Cause: The user is trying to add or modify a document and has run out of space in the library. Action: The user must delete some documents or versions in order to free up disk space.
Page 148 Action: Close the document. Possible Cause: The document is archived. Action: Restore the document. See “Restoring Archived Documents” in “Libraries and Documents” in the GroupWise 7 Administration Guide. E525 Cannot delete lookup table; it is not empty Source: GroupWise engine; document management. Explanation: Lookup table not empty.
Page 149: E7Xx Errors
Action: Create a new library. See “Creating and Managing Libraries” in “Libraries and Documents” in the GroupWise 7 Administration Guide. E52A Document not available Source: GroupWise engine; document management. Explanation: The document cannot be restored because it is no longer available on disk. Possible Cause: The document has been moved from the library archive to a backup medium.
Page 150 “E804 Unexpected error” on page 150 “E805 Unexpected error” on page 150 “E806 Unexpected error” on page 150 “E807 Unexpected error” on page 150 “E808 Unexpected error” on page 150 “E809 Unexpected error” on page 150 “E80C Unexpected error” on page 151 “E80D Unexpected error”...
Page 151: E81X Errors
Action: See “Exxx Unexpected error” on page 161. E80C Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 161. E80D Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 161. E80F Unexpected error Source: GroupWise engine;...
Page 152: E82X Errors
E814 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 161. E815 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 161. E816 Insufficient rights to perform operation Source: GroupWise engine; object framework. Explanation: Security access denied.
Page 153: E84X Errors
Action: See “Exxx Unexpected error” on page 161. E823 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 161. E824 Unexpected error Source: GroupWise engine; object framework. Action: See “Exxx Unexpected error” on page 161. E82B Unexpected error Source: GroupWise engine;...
Page 154 Therefore, the item cannot be found. Action: Call getItemsRequest and compare the uid from that call to the uid that you used when the error was generated. For more information, see: uid element (http://developer.novell.com/documentation/gwsoap/ gwwbserv/data/b7o81jm.html#b7o81jm) getItemsRequest (http://developer.novell.com/documentation/gwsoap/ gwwbserv/data/b7m3i5v.html) EA03 Handling of SOAP protocol is not enabled Source: GroupWise engine;...
Page 155 Possible Cause: The current value of the cursor is not valid. Action: Create a cursor before attempting to position or read from it. For more information, see: Cursors (http://developer.novell.com/documentation/gwsoap/gwwbserv/ data/b7m3i3x.html#b7m40qk) createCursorRequest method (http://developer.novell.com/ documentation/gwsoap/gwwbserv/data/b7m3i4n.html) positionCursorRequest method (http://developer.novell.com/ documentation/gwsoap/gwwbserv/data/b7m3i7f.html) readCursorRequest method (http://developer.novell.com/documentation/ gwsoap/gwwbserv/data/b7m3i7l.html)
Page 156 Possible Cause: Your application passes in a uid that does not have the container appended to the end. Action: Call getItemsRequest and compare the uid from that call to the uid that you used when the error was generated. For more information, see: Item element (http://developer.novell.com/documentation/gwsoap/ gwwbserv/data/b7o672m.html) uid element (http://developer.novell.com/documentation/gwsoap/ gwwbserv/data/b7o81jm.html) getItemsRequest method (http://developer.novell.com/documentation/ gwsoap/gwwbserv/data/b7m3i5v.html)
Page 157 SOAP client user. Action: Accepted items are marked as accepted. Check the status of an item before trying to accept it. For more information, see: acceptRequest method (http://developer.novell.com/documentation/ gwsoap/gwwbserv/data/b7m3i49.html) EA0B Item not acceptable/declinable Source: GroupWise engine; SOAP protocol.
Page 158: Ea1X Errors
Possible Cause: Your application did not provide a usable key. Possible Cause: The key string is empty. Action: Check the configureEventsRequest to see if it is passing a valid key element. For more information, see: Event object (http://developer.novell.com/documentation/gwsoap/ gwwbevnt/data/b713j3k.html) configureEventsRequest method (http://developer.novell.com/ documentation/gwsoap/gwwbevnt/data/b713j3w.html) EA0F Missing cursor Source: GroupWise engine;...
Page 159 Possible Cause: Your application does not use a loginResponse to obtain a session string before calling a method that requires a session string. Action: Make sure you use the login method to obtain a session string. For more information, see: session object (http://developer.novell.com/documentation/gwsoap/ gwwbserv/data/b7o64ii.html) EA11 Maximum event read threads Source: GroupWise engine; SOAP protocol.
Page 160 Possible Cause: The user resides in a different post office than your application specified in the login. Action: Redirect the user to the correct post office. For more information, see: loginRequest method and loginResponse (http://developer.novell.com/ ndk/doc/gwsoap/soap_enu/data/brx8x54.html#brx8x54) EA15 The method called is not supported on this container Source: GroupWise engine; SOAP protocol.
Page 161: Exxx Unexpected Error
Possible Cause: Your application fails to specify a start date on a recurring item. Possible Cause: Your application specifies an end date that is earlier than the start date. Action: Specify a valid date/type range. For more information, see: startDate object (http://developer.novell.com/documentation/gwsoap/ gwwbserv/data/b7o64ij.html) endDate object (http://developer.novell.com/documentation/gwsoap/ gwwbserv/data/b8jm8wu.html) EA18 Searching over the entire mailbox requires a filter Source: GroupWise engine;...
Page 162 162 GroupWise 7 Troubleshooting 1: Error Messages...
Page 163: Fxxx Engine Error Codes
Fxxx Engine Error Codes “F00x Errors” on page 163 “F01x Errors” on page 164 “F02x Errors” on page 166 “F03x Errors” on page 167 “F04x Errors” on page 168 “F05x Errors” on page 169 “F06x Errors” on page 170 “F07x Errors” on page 172 “F08x Errors”...
Page 164: F01X Errors
F008 Missing parenthesis in search command Source: GroupWise engine; QuickFinder. Action: See “F0xx Query syntax error” on page 180. F009 Missing operator in search command Source: GroupWise engine; QuickFinder. Action: See “F0xx Query syntax error” on page 180. F00A Switch at end of search command ignored Source: GroupWise engine;...
Page 165 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”...
Page 166: F02X Errors
Action: See “F0xx Query syntax error” on page 180. F01B Unknown field in search command Source: GroupWise engine; QuickFinder. Action: See “F0xx Query syntax error” on page 180. F01C Ambiguous field; supply more characters Source: GroupWise engine; QuickFinder. Action: See “F0xx Query syntax error”...
Page 167: F03X Errors
Action: See “F0xx Query syntax error” on page 180. F022 Missing switch after'/' Source: GroupWise engine; QuickFinder. Action: See “F0xx Query syntax error” on page 180. F023 Word missing between operators Source: GroupWise engine; QuickFinder. Action: See “F0xx Query syntax error” on page 180.
Page 168: F04X Errors
F037 Memory error Source: GroupWise engine; QuickFinder. Action: See “F0xx Memory error” on page 181. F03E Memory error Source: GroupWise engine; QuickFinder. Action: See “F0xx Memory error” on page 181. 9.5 F04x Errors “F045 Unexpected error” on page 168 “F046 File I/O error” on page 168 “F047 File I/O error”...
Page 169: F05X Errors
F04A File I/O error Source: GroupWise engine; QuickFinder. Action: See “F0xx File I/O error” on page 180. F04C File I/O error Source: GroupWise engine; QuickFinder. Action: See “F0xx File I/O error” on page 180. F04D File I/O error Source: GroupWise engine; QuickFinder. Action: See “F0xx File I/O error”...
Page 170: F06X Errors
Action: See “F0xx Memory error” on page 181. 9.7 F06x Errors “F060 Database error” on page 170 “F061 Database error” on page 170 “F062 Database error” on page 170 “F063 Database error” on page 170 “F064 Database error” on page 170 “F065 Database error”...
Page 171 F065 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F066 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F067 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)”...
Page 172: F07X Errors
F06F Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. 9.8 F07x Errors “F070 Database error” on page 172 “F071 Database error” on page 172 “F072 Database error” on page 172 “F073 Database error” on page 172 “F074 Database error”...
Page 173 F074 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F075 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F076 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)”...
Page 174: F08X Errors
F07E Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F07F Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. 9.9 F08x Errors “F080 Database error” on page 174 “F082 Database error”...
Page 175 F085 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F086 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F087 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)”...
Page 176: F09X Errors
9.10 F09x Errors “F090 Database error” on page 176 “F091 Database error” on page 176 “F092 Database error” on page 176 “F093 Database error” on page 176 “F094 Database error” on page 176 “F095 Database error” on page 176 “F096 Database error” on page 177 “F097 Database error”...
Page 177: F0Ax Errors
F096 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F097 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F098 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)”...
Page 178 “F0BE Database error” on page 178 “F0BF Database error” on page 178 F0B2 Memory error Source: GroupWise engine; QuickFinder. Action: See “F0xx Memory error” on page 181. F0B5 File I/O error Source: GroupWise engine; QuickFinder. Action: See “F0xx File I/O error” on page 180.
Page 179: F0Cx Errors
9.13 F0Cx Errors “F0C0 Database error” on page 179 “F0C2 Database error” on page 179 “F0C4 Database error” on page 179 F0C0 Database error Source: GroupWise engine; QuickFinder. Action: See “F0xx Database error (index)” on page 181. F0C2 Database error Source: GroupWise engine;...
Page 180: F0Xx Errors
F104 Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server” on page 182. F105 Cannot connect to remote server Source: GroupWise engine; NetWare remote server connection table. Action: See “F1xx Cannot connect to remote server”...
Page 181 Action: Rebuild the index of the database where the error occurs. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 7 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.
Page 182: F1Xx Cannot Connect Error
9.16 F1xx Cannot Connect Error “F1xx Cannot connect to remote server” on page 182 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.
Page 183: Part Ii Agent Error Messages
Chapter 13, “WebAccess Agent Error Messages,” on page 225 Chapter 14, “Monitor Agent and Application Error Messages,” on page 237 Other sources of assistance include: ® Novell Support (http://www.novell.com/support) Novell Support Knowledgebase (http://www.novell.com/support/supportcentral) GroupWise 7 Support Forums (http://support.novell.com/forums/2gw.html) Novell GroupWise Support Community (http://www.novell.com/support/ browse.do?WidgetName=BROWSE_PRODUCT&BROWSE_PRODUCT.TaxoName=SG_Su pportGoals&NodeType=leaf&NodeName=GroupWise&TaxoName=SG_SupportGoals&BRO WSE_PRODUCT.isProductTaxonomy=true&BROWSE_PRODUCT.NodeId=SG_GROUPWI SE_1_1&BROWSE_PRODUCT.NodeType=leaf&BROWSE_PRODUCT.thisPageUrl=%2Fpr oduct%2Fproducts.do&NodeId=SG_GROUPWISE_1_1&id=m1&AppContext=AC_SiteCent ral) GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)
Page 184 184 GroupWise 7 Troubleshooting 1: Error Messages...
Page 185: Post Office Agent Error Messages
Post Office Agent Error Messages “GWPOA: Admin database for post_office could not be recovered” on page 186 “GWPOA: Administrator record not found in database” on page 186 “GWPOA: Application connection table full” on page 186 “GWPOA: Authentication failed for the above object” on page 187 “GWPOA: Cannot access remote post office;...
Page 186 “GWPOA: Running the agent with conflicting effective users” on page 194 “GWPOA: StartServiceCtrlDispatcher failed when attempting to start Windows_agent service” on page 194 “GWPOA: The Windows_agent service fails to set service status; service stopped” on page 194 “GWPOA: The Windows_agent service fails to initialize memory system; service stopped” on page 194 “GWPOA: Timed out waiting for end-of-file confirmation”...
Page 187 GWPOA: Authentication failed for the above object Source: GroupWise Post Office Agent; admin thread. Explanation: The POA admin thread attempted to process a record that has the wrong authentication key for the current GroupWise system. Possible Cause: The record did not originate in the current GroupWise system, which is a possible security violation.
Page 188 GWPOA: Configured address may not match actual address Source: GroupWise Post Office Agent; TCP agent. Explanation: The POA is configured for TCP/IP communication, but a mismatch of IP addresses has been detected. Possible Cause: DNS is not currently available, so the POA is unable to resolve a host name into its IP address.
Page 189 GWPOA: Error creating file; turning disk logging off Source: GroupWise agents. Explanation: Logging information to disk has been turned off because the agent cannot create a new log file. Possible Cause: 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...
Page 190 Action: See “8555 Port in use” on page GWPOA: Error putting item in queue Source: GroupWise Post Office Agent; TCP agent. Explanation: The TCP threads are not keeping up with the current workload. Action: Increase the number of TCP handler threads for the POA. See “Adjusting the Number of Connections for Client/Server Processing”...
Page 191 GWPOA: Host refused connection Source: GroupWise Post Office Agent; message transfer protocol. Explanation: 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.
Page 192 Explanation: 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. Possible Cause: TCP/IP is not set up correctly on the server where the POA is running. Action: Make sure TCP/IP is set up correctly, including assignment of an IP address.
Page 193 Action: If the POA starts successfully but frequently encounters memory errors during later processing, treat the situation as if the 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: GroupWise Post Office Agent.
Page 194 Action: If processing of a message file causes the POA to shutdown, do not put message files from the directory back post_office\wpcsout\problem into the POA input queue. Restart the POA. GWPOA: Reached inbound connections limit Source: GroupWise Post Office Agent; message transfer protocol. Explanation: The POA is configured to communicate with the MTA by way of TCP/IP.
Page 195 Action: Reboot the Windows server. Action: Run fewer programs on the server. GWPOA: Timed out waiting for end-of-file confirmation Source: GroupWise Post Office Agent; message transfer protocol. Explanation: 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.
Page 196 GWPOA: Unable to load viewer Source: GroupWise Post Office Agent for Windows. Explanation: The POA cannot run the program used to view agent log files or edit agent startup files. Possible Cause: The viewer program is not available on the current path or is incorrectly specified.
Page 197: Message Transfer Agent Error Messages
Message Transfer Agent Error Messages “GWMTA: Access denied” on page 199 “GWMTA: Admin database for domain cannot be recovered” on page 199 “GWMTA: Administrator record not found in database” on page 199 “GWMTA: Authentication failure for the above object” on page 199 “GWMTA: Cannot attach to server or volume”...
Page 198 “GWMTA: Gateway now closed” on page 207 “GWMTA: Gateway open failed” on page 207 “GWMTA: Host refused connection” on page 207 “GWMTA: IDomain now closed” on page 208 “GWMTA: Incompatible GWENV1A.DLL; GWMTA cannot continue” on page 208 “GWMTA: Insufficient disk space” on page 208 “GWMTA: Insufficient memory”...
Page 199 “GWMTA: Timed out waiting for end-of-file confirmation” on page 216 “GWMTA: Unable to initialize message log database” on page 216 “GWMTA: Unable to open connection; no response” on page 216 “GWMTA: Unable to register with SNMP agent” on page 217 “GWMTA: Unable to retrieve TCP/IP address”...
Page 200 /tracelogin-2 to display NetWare error codes. Look up the error codes at Novell Error Codes (http:// www.novell.com/documentation/nwec/index.html). Possible Cause: 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.
Page 201 Possible Cause: The MTA cannot write message files across a mapped or UNC link into the MTA input queue in a closed domain (domain\wpcsin directory) or a closed post office (post_office\wpcsout directory) because the directory is inaccessible or damaged. Action: Make sure the input queue directory exists and that the MTA has sufficient rights to create files there.
Page 202 GWMTA: Cannot move files Source: GroupWise Message Transfer Agent; last closure reason. Explanation: The MTA cannot move message files from its input queue (domain\wpcsin or post_office\wpcsin) to its in progress" queue (gwinprog). Explanation: Insufficient disk space on the server where the directory structure is mslocal located.
Page 203 Action: See “GWMTA: Insufficient memory” on page 209. 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 7 Administration Guide. GWMTA: Cannot route message(s); out of memory Source: GroupWise Message Transfer Agent.
Page 204 Explanation: The MTA cannot run the program used to view agent log files or edit agent startup files. Possible Cause: The viewer program is not available on the current path or is incorrectly specified. Action: 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.
Page 205 Action: Check, and if necessary adjust, the indirect links between domains in your GroupWise system. See “Link Configuration between Domains and Post Offices” in “Domains” in the GroupWise 7 Administration Guide. GWMTA: Domain database open failed Source: GroupWise Message Transfer Agent. Explanation: The MTA cannot access the domain database (wpdomain.db).
Page 206 Agent” in the GroupWise 7 Administration Guide. GWMTA: Error validating post office members ® Source: GroupWise Message Transfer Agent, Novell eDirectory user synchronization. Explanation: When attempting eDirectory user synchronization, the MTA could not access the user information stored in eDirectory.
Page 207 Explanation: Logging information to disk has been turned off because the agent can no longer write to the current log file. Possible Cause: If the log file is located on a server other than the one where the agent is running, that server might be down.
Page 208 GWMTA: IDomain now closed Source: GroupWise Message Transfer Agent. Explanation: The MTA has lost its connection to a domain across the Internet with which it could previously communicate. Possible Cause: The server where the domain is located is currently down. Action: Wait for the server to come back up, or contact the administrator of that server.
Page 209 GWMTA: Insufficient memory Source: GroupWise Message Transfer Agent. Explanation: Not enough memory is available for the MTA to function properly. Possible Cause: If the MTA cannot start, you might be trying to run the MTA in an environment where too few system resources are available. Action: For requirements, see “GroupWise System Requirements”...
Page 210 Action: If the problem does not resolve itself in a short time, see “GWMTA: Insufficient memory” on page 209. GWMTA: Internet mail to address is undeliverable because no default GWIA is configured Source: GroupWise Message Transfer Agent. Explanation: A message addressed to a user across the Internet cannot be delivered. Possible Cause: A default GroupWise Internet Agent has not been configured.
Page 211 GWMTA: Link or transport down Source: GroupWise Message Transfer Agent. Explanation: The MTA is using TCP/IP to communicate with an MTA or POA and the other agent is not responding. Possible Cause: The MTA in the other domain is not properly set up for TCP/IP communication.
Page 212 Action: Wait for the server to come back up or contact the administrator of that server. Action: See also “GWMTA: Cannot attach to server or volume” on page 200. GWMTA: Maximum number of inbound connections reached Source: GroupWise Message Transfer Agent. Explanation: The MTA could not start another thread for an inbound connection.
Page 213 GWMTA: No post offices found Source: GroupWise Message Transfer Agent; eDirectory user synchronization. Explanation: The MTA has been configured to perform eDirectory user synchronization for a domain which has no post offices and, hence, no users; for example, a routing domain. Action: Remove the domain from the list of domains for which eDirectory user synchronization should be performed.
Page 214 Action: 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. Possible Cause: If running the MTA on a Windows server, the location might be on a server that is not currently mapped.
Page 215 Action: Check the directory structure of the closed post office. See “Post Office Directory” in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure. GWMTA: Received unsupported request; request ignored Source: GroupWise Message Transfer Agent. Explanation: The MTA received an administrative message from GroupWise Administrator that it could not respond to.
Page 216 Action: Wait until the backlog clears, then the MTA will resume its regular processing of new messages. Backlogged messages are stored in subdirectories of the directory. mslocal GWMTA: The Windows_agent service fails to set service status; service stopped Source: GroupWise Message Transfer Agent for Windows. Explanation: The Windows MTA cannot start as a Windows service.
Page 217 Possible Cause: The server where the other MTA or the POA is located is down. Action: Check the status of the other server. Reboot if necessary. GWMTA: Unable to register with SNMP agent Source: GroupWise agents. Explanation: The MTA is unable to contact the SNMP agent on the server where the agent is running.
Page 218 Possible Cause: The sender manually typed in an invalid address. Action: Have the user select the recipient from the Address Book, then resend the message. Possible Cause: 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.
Page 219: Internet Agent 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...
Page 220 “GWIA: Running the agent with conflicting effective users” on page 223 “GWIA: Scratch-pad file creation error: xxxx” on page 224 “GWIA: Scratch-pad file write error: filename” on page 224 “GWIA: Unable to find TCPIP Kernel” on page 224 “GWIA: Unable to listen on SMTP port” on page 224 GWIA: Command task could not be added to message body, rc =xxxx ®...
Page 221 GWIA: Database open error: xxxx Source: GroupWise Internet Agent. Explanation: The domain database path could not be created, or the database did not open. Action: 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.
Page 222 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 the named file and directory, and check access to the file. GWIA: File read error on file filename in module xxxx Source: GroupWise Internet Agent.
Page 223 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 directory in the domain directory. problem GWIA: Message re-queuing failed. The message must be deleted Source: GroupWise Internet Agent.
Page 224 Explanation: You are starting the Internet Agent as a user that is different from the user the Internet Agent is configured to run as. The user specified in the uid.conf file does not match the user specified in the uid.run file. Possible Cause: The user specified in the uid.conf file has been manually edited.
Page 225: Webaccess Agent Error Messages
WebAccess Agent Error Messages “WEBACC: CMC encountered a problem accessing the GroupWise domain” on page 226 “WEBACC: CMC was not able to access this GroupWise gateway directory” on page 226 “WEBACC: CMC was not able to establish a connection to the post office” on page 226 “WEBACC: Conversation timed out”...
Page 226 “WEBACC: Request rejected because all threads are busy” on page 234 “WEBACC: Running the agent with conflicting effective users” on page 234 “WEBACC: Startup file not found” on page 234 “WEBACC: TCP socket accept failed” on page 234 “WEBACC: The post office is closed” on page 234 “WEBACC: The system is busy, please try again later”...
Page 227 Offices” in “WebAccess” in the GroupWise 7 Administration Guide. Possible Cause: The WebAccess Agent’s post office link information is not defined correctly in ® Novell eDirectory Action: Check the post office link information. See “Modifying Links to Post Offices” in “WebAccess” in the GroupWise 7 Administration Guide.
Page 228 Action: Reestablish the connection to the server and make sure the WebAccess Agent has sufficient rights to the directory. See “WebAccess Security Requirements” “Installing GroupWise WebAccess” in the GroupWise 7 Installation Guide. WEBACC: Error accessing startup file Source: GroupWise WebAccess Agent Explanation: The WebAccess Agent could not access the startup file specified by the @filename switch.
Page 229 Possible Cause: A user bookmarked a GroupWise WebAccess location then attempted to access it directly from another server. Action: Have the user log in through the GroupWise WebAccess login screen. WEBACC: If necessary, the system will attempt a forced shutdown ... Source: GroupWise WebAccess Agent Explanation: In one minute, the WebAccess Agent will attempt to shut down even if WebAccess users are still logged in.
Page 230 Action: Save the file as a text file or enter valid startup switches in the file. See “Using WebAccess Startup Switches” in “WebAccess” in the GroupWise 7 Administration Guide. WEBACC: Invalid startup parameter value Source: GroupWise WebAccess Agent Explanation: The value for the specified startup switch is not valid. Possible Cause: An invalid value was entered with the startup switch on the command line or in the startup file.
Page 231 WEBACC: Login failed Source: GroupWise WebAccess Agent Explanation: A WebAccess user attempted to log in and failed. Possible Cause: The user did not enter a valid GroupWise user ID or password. Action: Make sure the user knows his or her GroupWise user ID. Make sure the user has a password set on his or her mailbox and knows the password.
Page 232 Source: GroupWise WebAccess Agent Explanation: This is an internal diagnostic message. Possible Cause: Unknown. Action: If the problem persists, contact the Novell Support (http://www.novell.com/ support). WEBACC: No NetWare password was specified Source: GroupWise WebAccess Agent Explanation: The GroupWise WebAccess Agent requires an account and password that lets ®...
Page 233 Action: In ConsoleOne, specify a UNC path or mapped drive to the post office. See “Modifying Links to Post Offices” in “WebAccess” in the GroupWise 7 Administration Guide. WEBACC: Not able to bind to specified port Source: GroupWise WebAccess Agent Explanation: The WebAccess Agent could not bind to the TCP/IP port it uses to listen for messages from the GroupWise WebAccess CGI Extension.
Page 234 WEBACC: Request rejected because all threads are busy Source: GroupWise WebAccess Agent Explanation: The WebAccess Agent could not process a request from a WebAccess user because no threads were available. Possible Cause: Heavy WebAccess usage for the number of threads allocated to the WebAccess Agent.
Page 235 Explanation: While processing a request for a user, the WebAccess Agent could not access the user’s post office. Possible Cause: Logging in to the post office has been disabled through ConsoleOne. Action: Enable the post office. See “Disabling a Post Office”...
Page 236 (domain.post_office.userID. Possible Cause: The WebAccess servlet has encountered a problem with the username. Action: Check the WebAccess Application log for additional error messages. The location of the log file varies by platform. NetWare /novell/webaccess/logs Windows: Linux: /opt/novell/groupwise/webaccess/logs WEBACC: Unknown keyword:...
Page 237: Monitor Agent And Application Error Messages
Monitor Agent and Application Error Messages “GWMON: GroupWise Monitor Agent is not listening” on page 237 “GWMON: No route to GroupWise Monitor Agent” on page 237 “GWMON: Path to domain database (/home) is invalid or blocked” on page 237 “GWMON: Request timed out waiting for response from GroupWise Monitor Agent” on page 238 “GWMON: The URL to connect to the GroupWise Monitor Agent is invalid”...
Page 238 Possible Cause: The location specified by the /home startup switch does not exist. 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”...
Page 239 Possible Cause: The Monitor Agent is not running. Action: Start the Monitor Agent. See “Starting the Monitor Agent” in “Monitor” in the GroupWise 7 Administration Guide. Possible Cause: The server where the Monitor Agent is running has gone down. 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.
Page 240 240 GroupWise 7 Troubleshooting 1: Error Messages...
Page 241: Part Iii Administration Error Messages
Chapter 16, “GroupWise Check Error Codes,” on page 251 Chapter 17, “GroupWise Time Stamp Utility Error Messages,” on page 269 Other sources of assistance include: ® Novell Support (http://www.novell.com/support) Novell Support Knowledgebase (http://www.novell.com/support/supportcentral) GroupWise 7 Support Forums (http://support.novell.com/forums/2gw.html) Novell GroupWise Support Community (http://www.novell.com/support/ browse.do?WidgetName=BROWSE_PRODUCT&BROWSE_PRODUCT.TaxoName=SG_Su pportGoals&NodeType=leaf&NodeName=GroupWise&TaxoName=SG_SupportGoals&BRO WSE_PRODUCT.isProductTaxonomy=true&BROWSE_PRODUCT.NodeId=SG_GROUPWI SE_1_1&BROWSE_PRODUCT.NodeType=leaf&BROWSE_PRODUCT.thisPageUrl=%2Fpr oduct%2Fproducts.do&NodeId=SG_GROUPWISE_1_1&id=m1&AppContext=AC_SiteCent ral) GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)
Page 242 242 GroupWise 7 Troubleshooting 1: Error Messages...
Page 243: Groupwise Administrator Snap-In To Consoleone Error Messages
GroupWise Administrator Snap-In to ConsoleOne Error Messages “0001 Cannot load resource” on page 244 “0002 Schema not properly defined” on page 244 “0003 Required DLL has incorrect version” on page 244 “0004 Required DLL missing” on page 244 “0005 Cannot read required information from NDS” on page 245 “0006 GroupWise object missing required information”...
Page 244 Source: GroupWise Administrator; general snap-in. Explanation: DLL version mismatch. Possible Cause: An improper update of the GroupWise Administrator snap-in might have been loaded from Novell Support. Action: Rerun GroupWise Install or acquire the latest GroupWise Administrator snap- in from Novell Support Novell Support (http://www.novell.com/support).
Page 245 Explanation: GroupWise is unable to read necessary information from eDirectory (the current product name of Novell Directory Services). Possible Cause: You have insufficient rights to read this information. Action: Make sure you have sufficient rights to administer the objects in this GroupWise domain.
Page 246 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 the GroupWise Gateways Documentation Web site (http://www.novell.com/documentation/ gwgateways). 0022 Cannot assign non-GroupWise user as administrator Source: GroupWise Administrator; gateway setup.
Page 247 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 ”...
Page 248 0038 Owning object (domain/post office) not found in NDS Source: GroupWise Administrator; association. Explanation: Object does not exist in eDirectory (the current product name of Novell Directory Services). Possible Cause: An invalid distinguished name (DN) was entered for the domain or post office that owns this object.
Page 249 Explanation: You are not currently connected to a GroupWise domain database ( ). The requested operation cannot be completed. wpdomain.db Action: Connect to an existing GroupWise domain. See “ Connecting to a Domain ” in “ Domains ” in the GroupWise 7 Administration Guide 0049 Cannot move user from 6.x post office to 4.x post office Source: GroupWise Administrator;...
Page 250 Action: You can upgrade this evaluation software by purchasing and installing the shipping version of GroupWise. 0065 Cannot open domain database Source: GroupWise Administrator; system-wide operations. Explanation: The domain database ( ) from which GroupWise wpdomain.db Administrator is reading information has become unavailable. The original database will continue to be used until ConsoleOne is restarted.
Page 251: Groupwise Check Error Codes
GroupWise Check Error Codes GWCheck generates two sets of numeric codes: error codes and problem codes. Both sets of codes are in the same numeric range, but error codes are clearly labeled as errors, for example, “Error 9”. The GWCheck problem codes are not documented because there is nothing you as an administrator need to do about the problems GWCheck is reporting.
Page 252 “32 User database open error” on page 260 “33 Error initializing database engine code” on page 260 “34 Unable to get post office information” on page 260 “35 Memory allocation error” on page 260 “36 Message database not found” on page 261 “37 Exclusive access denied to message database”...
Page 253 01 Memory initialization error ® Source: GroupWise 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 ( ) for Address wphost.db Book information.
Page 254 Explanation: GWCheck encountered an invalid user record in the post office database ( wphost.db Action: In ConsoleOne, rebuild the post office database. See “ Rebuilding Domain or Post Office Databases ” in “ Databases ” in the GroupWise 7 Administration Guide 07 User record has no DS_USER_NETID Source: GroupWise Check utility (GWCheck).
Page 255 User/Resource and Message Databases ” in “ Databases ” in the GroupWise 7 Administration Guide Action: If the message database cannot be repaired, manually restore it from backup. See “ Restoring GroupWise Databases from Backup ” in “ Databases ” in the GroupWise 7 Administration Guide 11 Unable to start database transaction Source: GroupWise Check utility (GWCheck).
Page 256 14 Record delete failed commit Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot delete a record from the database. Possible Cause: The record is unavailable. Action: Retry. There might have been a timing problem with another database user. Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.
Page 257 17 Post office does not exist in domain Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot locate the specified post office. Action: 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: GroupWise Check utility (GWCheck).
Page 258 23 Unable to rename file for rebuild backup Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot create a backup copy of the existing database. Possible Cause: All valid backup database filenames have already been used. Action: 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.
Page 259 Possible Cause: All valid backup database filenames have already been used. Action: 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. Action: For additional information, look up the associated engine error code in Part I, “GroupWise Engine Error Codes,”...
Page 260 31 Exclusive access denied to user database Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot get sufficient access to the specified user database ( user xxx.db Possible Cause: Insufficient rights. Action: Make sure you have write access to the user database. Action: Retry.
Page 261 Action: Run GWCheck where adequate memory is available. 36 Message database not found Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot locate the specified message database ( msg nnn.db Action: Restore the message database from backup. 37 Exclusive access denied to message database Source: GroupWise Check utility (GWCheck).
Page 262 Action: Delete old backup databases so valid backup extensions are available. 42 Invalid database; truncated to nn bytes Source: GroupWise Check utility (GWCheck). Explanation: The database has been modified externally to an illegal size. Action: Perform a structural rebuild on the user database. See “ Performing a Structural Rebuild of a User Database ”...
Page 263 48 Orphaned QuickFinder index file Source: GroupWise Check utility (GWCheck). Explanation: GWCheck encountered a QuickFinder index file that was not associated with any library. Action: None. GWCheck deleted the extraneous index file. 49 Invalid QuickFinder index file Source: GroupWise Check utility (GWCheck). Explanation: GWCheck encountered an invalid QuickFinder index file.
Page 264 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 ( ) in the post office. dmsh.db Possible Cause: The library database is damaged. Action: Perform a structural analyze/fix on the library. See “ Analyzing and Fixing Library and Document Information ”...
Page 265 Action: Perform a structural analyze/fix on the library. See “ Analyzing and Fixing Library and Document Information ” in “ Databases ” in the GroupWise 7 Administration Guide 67 Unable to correct element without version object Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot correct the specified element because version information was missing in the library database ( ) in the post office.
Page 266 Explanation: GWCheck cannot correct the version information for a document because the specified element was missing in the library database ( ) in the post dmsh.db 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 ”...
Page 267 Possible Cause: Insufficient rights. Action: Make sure you have rights to the directory where the document storage area is located. 76 Error accessing document content Source: GroupWise Check utility (GWCheck). Explanation: GWCheck cannot read the content of the specified document. Possible Cause: The library database ( ) is damaged.
Page 268 268 GroupWise 7 Troubleshooting 1: Error Messages...
Page 269: Groupwise Time Stamp Utility Error Messages
GroupWise Time Stamp Utility Error Messages “GWTMSTMP: Error setting time stamp” on page 269 “GWTMSTMP: Invalid user database” on page 269 “GWTMSTMP: Invalid user ID” on page 269 “GWTMSTMP: User login error” on page 269 GWTMSTMP: Error setting time stamp ®...
Page 270 Possible Cause: The user ID provided with the switch does not exist in the post office specified with the switch. 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.
Page 271: Part Iv Client Error Messages
Chapter 19, “Remote Mode Windows Client Error Messages,” on page 275 Chapter 20, “Cross-Platform Client Error Messages,” on page 281 Other sources of assistance include: ® Novell Support (http://www.novell.com/support) Novell Support Knowledgebase (http://www.novell.com/support/supportcentral) GroupWise 7 Support Forums (http://support.novell.com/forums/2gw.html) Novell GroupWise Support Community (http://www.novell.com/support/ browse.do?WidgetName=BROWSE_PRODUCT&BROWSE_PRODUCT.TaxoName=SG_Su pportGoals&NodeType=leaf&NodeName=GroupWise&TaxoName=SG_SupportGoals&BRO WSE_PRODUCT.isProductTaxonomy=true&BROWSE_PRODUCT.NodeId=SG_GROUPWI SE_1_1&BROWSE_PRODUCT.NodeType=leaf&BROWSE_PRODUCT.thisPageUrl=%2Fpr oduct%2Fproducts.do&NodeId=SG_GROUPWISE_1_1&id=m1&AppContext=AC_SiteCent ral) GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)
Page 272 272 GroupWise 7 Troubleshooting 1: Error Messages...
Page 273: Windows Client Error Messages
Windows Client Error Messages ® Users might encounter two types of errors while using the GroupWise Windows client: “Errors the User Can Resolve” on page 273 “Errors the Administrator Must Resolve” on page 273 Errors the User Can Resolve Explanation: When a GroupWise Windows client error can be fixed immediately by the user, the error message includes instructions.
Page 274 274 GroupWise 7 Troubleshooting 1: Error Messages...
Page 275: Remote Mode Windows Client Error Messages
Remote Mode Windows Client Error Messages “A previous request to retrieve items has not been completed” on page 275 “Cannot access your Master Mailbox” on page 275 “Cannot find the post office” on page 276 “Cannot find the post office in the specified path” on page 276 “Cannot find your remote Mailbox folder”...
Page 276 Action: Run GroupWise before leaving your office, then set a password on your Master Mailbox. Action: If you are already away, have someone at your office set a password for you. Then, specify that password in Remote Options. ® Action: The administrator can reset the password for a user in ConsoleOne .
Page 277 Action: Verify that the gateway login ID in the modem connection definition is correct. In ConsoleOne, double-click the Domain object where the gateway is located, then double-click the Gateway object. On the GroupWise client Profiles page, select the profile that is not working, then click Edit. Verify the login ID displayed in the Remote Profile dialog box.
Page 278 is located, then double-click the Gateway object. On the GroupWise client Profiles page, select the profile that is not working, then click Edit. Verify the password displayed in the Remote Profile dialog box. Path to Post Office for Network Connections: To check the path to the post office in ConsoleOne, right-click the Post Office object, then click Properties.
Page 279 Action: Send another request to the master GroupWise system. Action: Record the conditions under which you encountered the error. For technical services, see Novell Support (http://www.novell.com/support). This item uses a custom view that was not retrieved... Source: GroupWise Windows client; Remote mode.
Page 280 Specify the script information, then click Save. Otherwise, select a different script filename {filename.ext} failed to open Source: GroupWise Windows client; Remote mode. Possible Cause: This usually occurs because the script file is in use by another application or access to the file is restricted. Action: Select a different filename, or open the Modem Connection dialog box.
Page 281: Cross-Platform Client Error Messages
Cross-Platform Client Error Messages Section 20.1, “General GroupWise Client Errors,” on page 281 Section 20.2, “Cross-Platform Client Errors,” on page 281 20.1 General GroupWise Client Errors ® As with the Windows client, users might encounter two types of errors while using the GroupWise Cross-Platform client: “Errors the User Can Resolve”...
Page 282 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 “Using GWCheck Linux”...
Page 283 Documentation Updates This section lists updates to GroupWise 7 Troubleshooting 1: Error Messages that have been made ® since the initial release of GroupWise 7. The information helps 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 the GroupWise 7 Troubleshooting 1: Error Messages was republished.
Page 284 223 “WEBACC: Running the Added a new error message. agent with conflicting effective users” on page 234 Entire Guide Page design reformatted to comply with revised Novell documentation standards. 284 GroupWise 7 Troubleshooting 1: Error Messages...

This manual is also suitable for:

Groupwise 7

Novell GROUPWISE 7 - TROUBLESHOOTING 1 Troubleshooting Manual

Quick Links

Need help?

Questions and answers

Related Manuals for Novell GROUPWISE 7 - TROUBLESHOOTING 1

Summary of Contents for Novell GROUPWISE 7 - TROUBLESHOOTING 1

This manual is also suitable for:

Table of Contents