Home

GroupWise 7 Troubleshooting 1: Error Messages

1. Enhancing Domain Security 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 891C Bad SSL certificate Source Explanation Possible Cause Action Possible Cause Action Group Wise engine TCP IP communication You have configured an agent for SSL but the agent cannot read the SSL certificate The SSL certificate is not in the required format Obtain an SSL certificate in the proper format See Encryption and Certificates in Security Administration in the GroupWise 7 Administration Guide The SSL certificate has been damaged Replace the bad SSL certificate with a valid SSL certificate 891D Bad SSL private key or password Source Group Wise engine TCP IP communication 8xxx Engine Error Codes 37 Explanation Possible Cause Action Possible Cause Action You have configured an agent for SSL but the agent cannot read the private key file or the password The SSL certificate that accompanies the private key file is not in the required format Obtain an SSL certificate in the proper format See Encryption and Certificates in Security Administration in the GroupWise 7 Administration Guide The password you provided on the agent object SSL Settings page in ConsoleOne does not match the password in t
2. Action To enable TCP IP communication configure the POA for ConsoleOne See Using Client Server Access to the Post Office in Configuring the POA in the GroupWise 7 Administration Guide To disable TCP IP communication use the notcpip switch when starting the POA See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide You are trying to run two POAs on the same server in client server mode and you have not given them unique TCP port numbers Check the TCP port for each POA object See Using Client Server Access to the Post Office in Configuring the POA in the GroupWise 7 Administration Guide Change the TCP port for one of the POAs You are trying to run two POAs on the same server in client server mode and you haven t created a second POA object in ConsoleOne In ConsoleOne create a second POA object in the post office Make sure you give it a unique TCP port number different from what the first POA is using Use the name switch when starting each POA You might want to create a separate startup file for each POA See Creating a POA Object in eDirectory in Post Office Agent in the GroupWise 7 Administration Guide 8562 Client server request packet contained invalid identifier Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Group Wise engine general communication Client server req
3. Action GroupWise engine document management Transport to a server failed The system was unable to contact a needed server Make sure the needed server is up and that all transport hardware is functioning correctly E529 All document blob areas full Source Explanation Possible Cause GroupWise engine document management All BLOB areas are full All of the areas that hold binary large objects BLOBs are full so the system was unable to create a new BLOB 144 GroupWise 7 Troubleshooting 1 Error Messages 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 Action Move the document back into the library so it is available to users See Restoring Archived Documents in Libraries and Documents in the GroupWise 7 Administration Guide To see where the document belongs right click the document reference in the GroupWise client then click Properties Click Version then check the current location and current filename information 8 4 E7xx Errors e E700 Invalid Address Book record on page 145 E716 Personal Address Book memory error on page 145
4. Action See COxx Unexpected error on page 78 C07D Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 C07E Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 C07F Unexpected error Source Group Wise engine database services Action See COxx Unexpected error on page 78 6 9 C08x Errors C080 Index not found on page 76 C081 Attachment missing on page 77 COxx Database error Support assistance recommended on page 77 COxx Database error general database repair strategies on page 77 COxx Database error database dictionary file on page 78 C0xx Memory error on page 78 COxx Unexpected error on page 78 C080 Index not found Source GroupWise engine database services Explanation A QuickFinder index is missing Action Repair the indexes in the post office database wohost db See Rebuilding Database Indexes in Databases in the GroupWise 7 Administration Guide 76 GroupWise 7 Troubleshooting 1 Error Messages 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 of files in the post of
5. GroupWise engine The password is too long Passwords can contain a maximum of 64 characters Type a password with fewer than 64 characters D01B Access to GroupWise denied Source Explanation Possible Cause Action Possible Cause Action Group Wise engine Access to the user database reguired for this operation has not been granted You are trying to proxy to a user s mailbox or perform an action as a proxy on another user s mailbox but the mailbox owner has not granted you sufficient rights Ask the owner to grant you the necessary rights The user should add your user ID to his or her access list to grant proxy access Look up proxy rights and access in GroupWise client Help You are trying to perform an action in a shared folder but you do not have rights to perform the reguested operation Ask the owner of the shared folder to grant you the necessary rights Look up shared folders in Group Wise client Help D01C Remote mail error Source Explanation Group Wise engine Invalid remote mail request Dxxx Engine Error Codes Possible Cause Action Action Action Remote mail error This error is displayed whenever a more specific error is not available The most common cause is a request for items that have already been deleted Check and repair the databases of the master mailbox See Maintaining User Resource and Message Databases in Databases in t
6. The TCP port the MTA is configured to listen on is already in use by another program Another MTA is already running on the server where you are trying to start this MTA Configure this MTA to use a different TCP port See Using TCP IP Links between Domains in Configuring the MTA in the GroupWise 7 Administration Guide 214 GroupWise 7 Troubleshooting 1 Error Messages Internet Agent Error Messages Some error and informational messages you might receive when using the Internet Agent originate from the program engine or from SMTP when the program makes connections with hosts and from other sources as well This section includes the error messages generated by the Internet Agent Variables such as strings or numbers are shown in italics and are represented by the following ASCII strings are represented by xxx yyy or zzz Decimal characters are represented by nnn Hexadecimal characters are represented by hhh This section contains information on the following Internet Agent errors GWIA Command task could not be added to message body rc xxxx on page 216 GWIA Configuration data is missing from the database on page 216 GWIA ConvertPerfect Error while converting attachment file filename on page 216 GWIA Currently unhandled command value xxxx was received by the gateway on page 216 GWIA Database initialization error xxxx on page 216 GWIA Database open error xxxx on pag
7. on page 73 e CO6D Database error on page 74 e CO6E Unexpected error on page 74 e C06F Store number mismatch on page 74 C060 Unexpected error Source Group Wise engine database services Action See COxx Unexpected error on page 78 C061 Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 C062 Unexpected error Source GroupWise engine database services Action See COxx Unexpected error on page 78 C063 Database error Source GroupWise engine database services Action See COxx Database error Support assistance recommended on page 77 C066 Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 C067 Database error Source GroupWise engine database services Explanation Invalid store number 72 GroupWise 7 Troubleshooting 1 Error Messages 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 Action Perform a structural rebuild on the user See Performing a Structural Rebuild of a User Database in Databases in
8. 8916 Cannot use TCP IP services on page 36 8917 TCP IP name lookup failed on page 36 8918 UDP send failed on page 36 8919 Attempt to bind to a non existent IP address on page 36 891A TCP IP data is not ready for reading on page 37 e 891B No SSL certificate supplied on page 37 e 891C Bad SSL certificate on page 37 891D Bad SSL private key or password on page 37 e 891E Insufficient memory for SSL on page 38 e 891F Invalid SSL certificate on page 38 e 8920 SSL certificate and private key do not match on page 39 8921 SSL accept failure on page 39 8922 SSL connect failure on page 39 8923 Insufficient memory for SSL on page 39 8924 SSL handshake timeout failure on page 40 e 8925 Connection refused on page 40 8926 Unknown host on page 40 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 Possible Cause Cannot load WINSOCK Windows only or the WINSOCK that did load is not supported DNS is not loaded and you are trying to resolve DNS names 32 GroupWise 7 Troubleshooting 1 Error Messages Action Correctly configure TCP IP on the server 8902 Cannot load TCP IP services Source
9. C03D Unexpected error on page 65 C03F Database error on page 66 C032 Database error Source Group Wise engine database services Action See COxx Database error general database repair strategies on page 77 64 GroupWise 7 Troubleshooting 1 Error Messages C033 Database error Source GroupWise engine database services Action See C0Oxx Database error general database repair strategies on page 77 C034 Database error Source GroupWise engine database services Action See COxx Database error database dictionary file on page 78 C035 Database error Source GroupWise engine database services Action See COxx Database error general database repair strategies on page 77 C037 Memory error Source GroupWise engine database services Action See C0xx Memory error on page 78 C038 Memory error Source GroupWise engine database services Action See C0xx Memory error on page 78 CO3A Database requires newer version Source GroupWise engine database services Explanation Newer database error 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 Group Wise software For technical services and file updates see Novell Support http support novell com C03B Database error Source GroupWise engine database services Action See COxx D
10. Check the directory structure of the closed Internet gateway GWMTA Host refused connection Source Explanation Action Group Wise Message Transfer Agent The MTA is configured to communicate with another MTA or a POA by way of TCP IP The server where the other MTA or the POA is located has refused the MTA s request for a connection Check the TCP IP configuration of the server to which the MTA must connect Message Transfer Agent Error Messages 203 GWMTA IDomain now closed Source Explanation Possible Cause Action Action Group Wise Message Transfer Agent The MTA has lost its connection to a domain across the Internet with which it could previously communicate The server where the domain is located is currently down Wait for the server to come back up or contact the administrator of that server Make sure the Internet link between domains is set up correctly See Internet Agent in the GroupWise 7 Administration Guide GWMTA Incompatible GWENV1A DLL GWMTA cannot continue Source Explanation Possible Cause Action GroupWise Message Transfer Agent for Windows The MTA cannot start because the agent engine gwenvla exe is not compatible with the MTA itself gwmta exe Some agent files have been updated but the update is not complete When updating the agents make sure all agent files are installed For a complete list see Agent Installation Directories in G
11. E7xx Errors on page 145 E80x Errors on page 145 E81x Errors on page 147 E82x Errors on page 148 E84x Errors on page 149 EAOx Errors on page 149 EA 1x Errors on page 154 Exxx Unexpected Error on page 157 8 1 E50x Errors E501 Document version not available on page 139 E503 Unexpected error on page 140 E507 Unexpected error on page 140 E508 Unexpected error on page 140 E50A Unexpected error on page 140 E50B Unexpected error on page 140 E50C Unexpected error on page 140 E50D Maximum number of libraries per post office reached on page 140 E50E Unexpected error on page 141 E501 Document version not available Source Group Wise engine document management Explanation Document version not available Possible Cause The document is currently in use Action Have the user who retrieved the document version close it Possible Cause The document is currently checked out Action Havethe user who checked it out check it back in Look up documents checking in in Group Wise client Help Exxx Engine Error Codes 139 Possible Cause Action 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 lib
12. FO6A Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 FO6B Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 FO6C Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FO6D Database error Source GroupWise engine OuickFinder Action See F0xx Database error index on page 177 FO6E Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 Fxxx Engine Error Codes 167 FO6F Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 9 8 F07x Errors e F070 Database error on page 168 F071 Database error on page 168 F072 Database error on page 168 F073 Database error on page 168 F074 Database error on page 169 F075 Database error on page 169 F076 Database error on page 169 F077 Database error on page 169 F078 Database error on page 169 F079 Database error on page 169 F07A Database error on page 169 F07B Database error on page 169 F07C Database error on page 169 F07D Database error on page 169 FOTE Database error on page 170 F07F Database error on page 170 F070 Database er
13. Group Wise engine Message Transfer Protocol The POA is attempting to communicate with the MTA by way of TCP IP but the MTA is not responding The MTA is not running Start the MTA The server where the MTA is running is overloaded so the MTA cannot respond to the POA in a timely manner Check the load on the server where the MTA is running If necessary stop some other programs or upgrade the server so adequate resources are available for the MTA to function properly The MTA is not configured for TCP IP links Bxxx Engine ErrorCodes 53 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 54 GroupWise 7 Troubleshooting 1 Error Messages Cxxx Engine Error Codes 6 C00x Errors on page 55 C01x Errors on page 58 C02x Errors on page 60 C03x Errors on page 64 C04x Errors on page 66 C05x Errors on page 69 C06x Errors on page 72 C07x Errors on page 74 C08x Errors on page 76 C0xx Unexpected Error on page 78 1 C00x Errors C003 Invalid object name has been passed in on page 55 C005 Invalid container has been selected for the GW objects on page 56 C006 Record key or key reference not found on page 56 C007 Database error on page 56 C008 Database error on page 56 C009 Database error on page 57 COOA Databa
14. Post Office Agent in the GroupWise 7 Administration Guide NetWare Note On a NetWare server make sure the grpwise ncf file contains the correct information The ngwguard dc file is missing from the post office directory Copy the ngwguard dc file from another post office or from the po subdirectory of the software distribution directory Mailbox Library Maintenance or GWCheck has been run more that 26 times in less than 2 weeks so all possible temporary file names are already used and a new backup file cannot be created Check for backup user databases userxxx db files with extensions dba through dbz If found move these backup databases to another directory then try Mailbox Library Maintenance or GWCheck again Ifno userxxx db file exists that is only backup files exist rename the most recent backup for example userxxx dbz to userxxx db The post office has been created in the root directory of a NetWare volume 136 GroupWise 7 Troubleshooting 1 Error Messages Action Move all post office directories and files into a subdirectory off the root See Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Adjust the path to the post office in the post office Identification page in ConsoleOne DF15 Records lost during rebuild Source GroupWise engine mailbox library maintenance Explanation The POA has been unable to rebuil
15. The MTA cannot access its domain database wpdomain db The domain database has been damaged Rebuild the domain database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA Domain now closed Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA has lost its connection to a domain with which it could previously communicate The server where the domain is located is currently down Wait for the server to come back up or contact the administrator of that server If using TCP IP communication between domains TCP IP might be down Make sure TCP IP is running in both domains GWMTA Domain open failed Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA in the local domain cannot contact the MTA in a different domain in your GroupWise system Links between the domains are not set up correctly Check the links between the domains See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide The local MTA cannot access the MTA input queue in the other domain Check the directory structure of the closed domain See Domain Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure GWMTA Error initializing HTTP S
16. The link to the post office has been lost Reestablish the link to the post office See Strategies for Message Delivery Problems in GroupWise 7 Troubleshooting 2 Solutions to Common Problems DB34 Time zone definition not found Source Explanation Possible Cause Action Group Wise engine administration engine No time zone defined Unable to find a time zone definition for the current domain or post office Select a time zone in the Identification page for the current domain or post office in ConsoleOne See Time Zones in System in the GroupWise 7 Administration Guide DB35 No pending operation for record Source Explanation Possible Cause Action Group Wise engine administration engine No pending operation for record The pending operation has been completed Refresh the list of pending operations See Pending Operations in System in the GroupWise 7 Administration Guide 126 GroupWise 7 Troubleshooting 1 Error Messages DB37 Cannot delete current domain Source Explanation Action Action Group Wise engine administration engine Cannot delete the current domain Connect to the primary domain See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide Then delete the secondary domain from the primary domain See Deleting a Domain in Domains in the GroupWise 7 Administration Guide If the current domain is the prim
17. The server where the other MTA or the POA is located is down Check the status of the other server Reboot if necessary GWMTA No sender IDomain Internet address lookup not attempted Source Explanation Possible Cause Action Action Group Wise Message Transfer Agent The address the MTA is trying to resolve does not contain Domain information The MTA is configured for GWMTP between GroupWise systems but the link is not set up properly Correct any problems in the setup of links between the two systems See Using Dynamic Internet Links in Connecting to GroupWise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide If the message is destined for a non Group Wise system across the Internet it will be routed through the GroupWise Internet Agent No action is required provided a preferred Internet Agent has been designated See Configuring Internet Addressing in System in the GroupWise 7 Administration Guide GWMTA Path to domain database home is invalid or blocked Source Explanation Possible Cause Action Possible Cause Group Wise Message Transfer Agent The MTA cannot access the domain database wpdomain db in the directory specified by the home switch The location specified by the home startup switch does not exist Check and if necessary change the location specified by the home startup switch when starting the MTA It must
18. in the GroupWise 7 Administration Guide Action Run GWCheck on the library See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide Possible Cause A user tried to start the GroupWise client as a resource that is using the u userID startup switch and specifying a resource rather than a user Action None You cannot start the GroupWise client as a resource You must use a valid user ID Exxx Engine Error Codes 141 E513 Unexpected error Source Action GroupWise engine document management See Exxx Unexpected error on page 157 E514 Document version must be checked out and in by same user Source Explanation Possible Cause Action GroupWise engine document management User IDs do not match The user is attempting to check in or close a document version using a different user ID than the one used to check it out A document version must be checked in or closed by same user who checked it out or opened it Log in to GroupWise as the user who checked out or opened the document version then check in or close the document Look up documents checking in in GroupWise client Help You can find out who originally checked out or opened the document by checking its activity log Look up activity logs in Group Wise client Help E515 Cannot delete last version of document Source Explanation Action GroupWise engine document mana
19. on page 177 Fxxx Engine Error Codes 171 9 10 F09x Errors F090 Database error on page 172 F091 Database error on page 172 F092 Database error on page 172 F093 Database error on page 172 F094 Database error on page 172 F095 Database error on page 172 F096 Database error on page 173 F097 Database error on page 173 F098 Database error on page 173 F099 Database error on page 173 FO9A Database error on page 173 FO9B Memory error on page 173 F090 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F091 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F092 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F093 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F094 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F095 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 172 GroupWise 7 Troubleshooting 1 Error Messages F096 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F097 Data
20. positionCursor method http developer novell com ndk doc gwsoap soap_enu data brx94t1 html brx94t1 readCursor method http developer novell com ndk doc gwsoap soap_enu data brx9f6t html brx9f6t destroyCursor method http developer novell com ndk doc gwsoap soap_enu data brx8dol html brx8dol 8 10 EA1x Errors e EA10 Missing session string on page 155 EA11 Maximum event read threads on page 155 EA13 Redirect user to different post office on page 155 EA15 The method called is not supported on this container on page 156 EA16 The specified contentType is not supported with this call on page 156 154 GroupWise 7 Troubleshooting 1 Error Messages e EA17 The specified date time range is invalid on page 156 e EA18 Searching over the entire mailbox requires a filter on page 156 EA10 Missing session string Source Explanation Possible Cause Action Possible Cause Action GroupWise engine SOAP protocol A session string identifies a user and his or her GroupWise data This information is missing The POA has timed out the session after 30 minutes Your application needs to log in again for that user Your application does not use a loginResponse to obtain a session string before calling a method that requires a session string Make sure you use the login method to obtain a session string For more information see session definition http developer
21. s expiration date See Expiring a Group Wise Account in Users in the GroupWise 7 Administration Guide D024 Rule cannot forward reply accept or delegate personal item Source Explanation Action Group Wise engine Action not valid for personal item Edit the conditions of the rule so that personal items are not included Look up rules in Group Wise client Help D025 Users not specified Source Explanation Possible Cause Action Possible Cause Group Wise engine No users specified No users have been specified in the distribution list Type the names of users or select users from the Address Book to include in the distribution list If this message occurs from the POA it might be attempting to process a damaged message file Dxxx Engine Error Codes 85 Action Check the priority subdirectories of the wpcsout ofs directory in the post office Check the POA log to determine the offending message file Delete the offending message file so that subsequent messages can be processed D026 Missing opening brace in distribution list Source Explanation Possible Cause Action Group Wise engine No opening brace Mismatched braces in the distribution list While processing the To CC and BC addresses in a message the end of the input buffer was reached before finding the closing brace Check the address for incorrect use of braces then resend the message D027 Missi
22. 124 GroupWise 7 Troubleshooting 1 Error Messages DB2E Link record not found Source GroupWise engine administration engine Explanation No link record exists Possible Cause No link record has been defined between an external domain to be merged and any local domain Action Define a link record between an external domain to be merged and any local domain See Merging with GroupWise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide DB2F Correct database type not found Source GroupWise engine administration engine Explanation No database exists Possible Cause Specified database type does not exist in the specified directory Action Check the domain path In ConsoleOne browse to and right click the Domain object then click Properties Action Check the setting of the home switch in the MTA startup file See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide 7 22 DB3x Errors DB30 Gateway directory not found on page 125 e DB31 Required field missing or empty on page 126 DB32 Required field missing on page 126 DB33 Cannot open all post offices on page 126 DB34 Time zone definition not found on page 126 DB35 No pending operation for record on page 126 DB37 Cannot delete current domain on page 127 DB38 Cannot delete domain that has post offices on page 127
23. Choose a different directory Action Obtain rights to the desired directory 278 GroupWise 7 Troubleshooting 1 Error Messages 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 will help you to keep current on documentation updates and in some cases software updates such as a Support Pack release The information is grouped according to the date when the GroupWise 7 Troubleshooting 1 Error Messages was republished Within each dated section the updates are listed by the names of the main table of contents sections GroupWise 7 Troubleshooting 1 Error Messages has been updated on the following dates e Section A 1 June 15 2006 on page 279 A 1 June 15 2006 Location Change Engine Error Codes C03F Database error on Added a new action for use in Caching mode page 66 DB63 Following a database Added a new error code rebuild the ownership of the target file has been changed The file uid run must be deleted manually on page 135 Agent Error Messages GWPOA Running the Added a new error message agent with conflicting effective users on page 190 GWMTA Running the Added a new error message agent with conflicting effective users on page 211 GWIA Running the agent Added anew error message with conflicting effective users on page 219 W
24. DB39 Domain database not found on page 127 e DB3A Cannot delete domain that has links on page 127 DB3B Remote management message sent on page 128 DB3C Domain database in use on page 128 DB3D Database sorting language changed on page 128 e DB3F Cannot delete required field on page 128 DB30 Gateway directory not found Source Group Wise engine administration engine Explanation Gateway directory does not exist Dxxx Engine Error Codes 125 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 Group Wise engine administration engine Explanation A required field is missing or empty Action Provide a value for the required field s DB32 Required field missing Source Explanation Action Group Wise engine administration engine A required field is missing Check the record for a missing required field DB33 Cannot open all post offices Source Explanation Possible Cause Action Possible Cause Action Group Wise engine administration engine Unable to open all post offices There are more post offices defined than the operating system file handles allow All directory synchronized commands will be performed through the MTA for the closed post offices
25. Explanation Possible Cause Action Action GroupWise engine TCP IP communication TCP IP load failed because a required file was missing Unable to load TCP IP services because one or more of the required files is missing winsock d11 wsoc32 d11 ortcpip nlm Make sure that you have the reguired files and that they are in the search path Correctly configure TCP IP on the server 8903 Cannot use TCP IP services Source Action GroupWise engine TCP IP communication See 8901 Cannot use TCP IP services on page 32 8906 Cannot use TCP IP services Source Action GroupWise engine TCP IP communication See 8901 Cannot use TCP IP services on page 32 8907 Cannot use TCP IP services Source Action GroupWise engine TCP IP communication See 8901 Cannot use TCP IP services on page 32 8908 Cannot connect to specified address Source Explanation Possible Cause Action Action Action Possible Cause Action Action GroupWise engine TCP IP communication Connection to the specified address failed Unable to load TCP IP services because one or more of the required files is missing winsock dll wsoc32 d11 ortcpip nlm Make sure that you have the required files and that they are in the search path Correctly configure TCP IP on the server Make sure you are using a current IP stack If you must use an older IP stack try specifying the IP address i
26. GWPOA Machine appears to have TCP IP incorrectly configured Source GroupWise Post Office Agent TCP agent Post Office Agent Error Messages 187 Explanation Possible Cause Action The POA is configured for TCP IP communication but it is unable to determine the IP address of the server where it is trying to run TCP IP is not set up correctly on the server where the POA is running Make sure TCP IP is set up correctly including assignment of an IP address GWPOA Not enough disk space for QuickFinder indexing Source Explanation Action Group Wise Post Office Agent The POA requires at least 20 MB of free disk space to perform QuickFinder indexing A warning appears when disk space drops below 30 MB This error appears when free disk space drops below 20 MB The POA performs QuickFinder indexing as specified by the QuickFinder Update Interval setting on the POA Agent Settings page in ConsoleOne or as specified using the qfinterval startup switch See Regulating Indexing in Post Office Agent in the GroupWise 7 Administration Guide Make sure sufficient free disk space is available on the server where the POA is running by the next time the POA needs to perform QuickFinder indexing GWPOA Not enough memory to complete operation Source Explanation Possible Cause Action Action Action Possible Cause Action Action 188 GroupWise 7 Troubleshooting 1 Group Wise Post Offi
27. GroupWise engine database services Explanation Generic database error Action Check and if necessary repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Cxxx Engine Error Codes 77 Action Action 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 If the damaged database cannot be repaired successfully restore it from backup If a damaged user database cannot be repaired or restored it can be rebuilt First archive all personal appointments tasks and notes Make a backup copy of the user database Then re create the user database See Re creating a User Database in Databases in the GroupWise 7 Administration Guide C0xx Database error database dictionary file Source Explanation Action GroupWise engine database services Problem with a database dictionary dc file Copy the ngwguard dc file from the po subdirectory of the software distribution directory to the post office directory For the specific locations of the file see Software Distribution Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and D
28. GroupWise engine object framework Action See Exxx Unexpected error on page 157 E82C Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E82E Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E82F Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 8 8 E84x Errors e E848 Unexpected error on page 149 E848 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 8 9 EAOx Errors EA02 The item is not found in the container portion of the uid on page 150 e EA03 Handling of SOAP protocol is not enabled on page 150 e EA04 The response is too large on page 150 e EA05 Invalid cursor on page 151 e EA06 Invalid session string on page 151 Exxx Engine Error Codes 149 EA07 Container string is missing on page 151 EA08 Display name is missing on page 152 EA09 User structure still busy on page 152 EAOA Item already accepted on page 152 EAOB Item not acceptable declinable on page 153 EAOC The method called is not supported on page 153 EAOE Key is invalid on page 154 EAOF Missing cursor on page 154 EA02 The item is not found in the container portion of the uid Source Explanation
29. Possible Cause If this error occurs as the GroupWise client starts the user might have specified an archive path that does not exist Action In the GroupWise client verify the path to the archive directory exists and the user has sufficient rights to create and modify files there Look up archive directory in GroupWise client Help 8219 Cannot connect to remote network resource Source GroupWise engine file input output Explanation The POA cannot access a document storage area located on a remote server Possible Cause If this error occurs when running the Windows agents the user s user name and password on the server where the POA is running are different from the user name and password on the server where the document storage area is located Action Use the same user name and password on the server where the POA is running and the server where the document storage area is located Action Use the user and password switches to provide the login information for the server where the document storage area is located See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide Action In ConsoleOne specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object 821A Access to a critical file denied Source GroupWise engine file input output Explanation The POA cannot access a required file Possible Cause Th
30. Relational integrity problem The user database userxxx db and or message database msgnnn db is damaged Check and if necessary repair the database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide A user tried to read an attachment for which the corresponding file has already been deleted from the of files directory in the post office None unless you want to restore the contents of the offiles directory from a backup D108 Unexpected error Source Action GroupWise engine database interface See Dxxx Unexpected error on page 138 D109 Bad parameter Source Explanation Possible Cause Action Possible Cause Action Action Possible Cause Action Group Wise engine database interface A Group Wise program passed invalid information to another GroupWise program The user s mailbox contains a damaged message Run a structural rebuild on the user database user xxx db and message database msgnnn db See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide A delay in Directory replication is preventing the user from logging in to the Group Wise client Start the client using the u switch to bypass eDirectory authenti
31. See FOxx Unexpected error on page 177 FOBA Database error Source GroupWise engine OuickFinder Action See FOxx Database error index on page 177 FOBB Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FOBC Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 FOBD Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FOBE Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FOBF Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 174 GroupWise 7 Troubleshooting 1 Error Messages 9 13 FOCx Errors e FOCO Database error on page 175 e FOC2 Database error on page 175 F0C4 Database error on page 175 FOCO Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FOC2 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F0C4 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 9 14 F10x Errors e F101 Cannot connect to remote server on page 175 e F102 Cannot connect to remote server on
32. See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide GWCheck provides additional repair options compared to the Repair Mailbox feature in the GroupWise client If this error occurs from the POA the POA might not have access to a required location Start the POA including the rights switch to determine the specific problem the POA is encountering See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide On a NetWare server deleted files must be purged to free up the disk space they occupy If the purge is not done the deleted file space is not reused causing insufficient disk space to create the path 8xxx Engine Error Codes 25 Action Purge deleted files to reclaim the disk space Add more disk space to the volume See Managing Database Disk Space in Databases in the GroupWise 7 Administration Guide 8211 Cannot rename file Source Explanation Possible Cause Action Possible Cause Action GroupWise engine file input output File rename failed Attempt by the file system to rename a file failed Make sure the specified filename is unique A directory required for the normal flow of GroupWise messages might be missing See Message Transfer Storage Directories in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Verify the existenc
33. 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 The read is unable to continue because transaction logging has been disabled for the database Action Perform the operation again This is a temporary condition and usually corrects itself As a general rule transaction logging should never be disabled on Group Wise databases Action If transaction logging has been disabled on the database the only way to re enable it is to rebuild the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide C012 Database error Source GroupWise engine database services Action See C0xx Database error general database repair strategies on page 77 C013 Index full Source GroupWise engine database services Explanation B tree is full Possible Cause One of the B trees in the database is full which means either an index area or a record area in the database is full Action Delete some items from the mailbox messages trash and so on to free up space in the database C014 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C015 Database error Source GroupWise eng
34. The LDAP server is down Action Contact the administrator of the LDAP server For more information about using LDAP for authentication see Providing LDAP Authentication for GroupWise Users in Post Office Agent in the GroupWise 7 Administration Guide Required information is missing from the connection Source GroupWise Windows client Remote mode Possible Cause The connection definition is incomplete Action Verify the required information Phone Number for Modem Connections To check the phone number in ConsoleOne double click the Domain object where the gateway is located then double click the Gateway object On the GroupWise client Profiles page select the profile that is not working then click Edit Verify the phone number displayed in the Remote Profile dialog box Gateway Login ID for Modem Connections To check the gateway login ID in ConsoleOne double click the Domain object where the gateway is located then double click the Gateway object On the GroupWise client Profiles page select the profile that is not working then click Edit Verify the login ID displayed in the Remote Profile dialog box Gateway Password for Modem Connections To check the gateway password in ConsoleOne double click the Domain object where the gateway Remote Mode Windows Client Error Messages 273 is located then double click the Gateway object On the Group Wise client Profiles page select the profile that is not working the
35. access and has hung with the database open For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 33 Error initializing database engine code Source Explanation Possible Cause Action Action Group Wise Check utility GWCheck GWCheck cannot initialize the database engine code Insufficient rights Make sure you have write access to the database to repair For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 34 Unable to get post office information Source Explanation Action Action Group Wise Check utility GWCheck GWCheck cannot read information from the post office database wphost db In ConsoleOne rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 35 Memory allocation error Source Explanation Action Group Wise Check utility GWCheck Insufficient memory to run GWCheck Run GWCheck where adequate memory is available 256 GroupWise 7 Troubleshooting 1 Error Messages 36 Message database not found Source GroupWise Check utility GWCheck Explanation GWCheck cannot locate the specified message database m
36. and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide 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 Possible Cause The ngwguard db file has been damaged Action Check the size of the ngwguard rfl file roll forward log If it is less than 24 KB it is considered empty Make backup copies of the ngwguard db ngwguard rfl and ngwguard fbk files Delete the ngwguard db file then copy ngwguard fbk to ngwguard db Be sure to copy it do not rename it See Information Stored in the Post Office in Post Office Agent in the GroupWise 7 Administration Guide Possible Cause If this error occurs when administering GroupWise a domain database wedomain db or post office database wphost db might be damaged Cxxx Engine Error Codes Action Action Possible Cause Action Action Possible Cause Action Action Action Action Possible Cause Action Action Validate and rebuild the domain or post office database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide If this error occurs from the POA after you have already rebuilt databases restart the POA If this error occurs in the GroupWise
37. developer novell com ndk doc gwsoap soap_enu data bs3al2a html bs3al2a EA18 Searching over the entire mailbox requires a filter Source Explanation 156 GroupWise 7 Troubleshooting 1 GroupWise engine SOAP protocol Because a GroupWise mailbox can be very large the process of searching the entire mailbox should be limited either by a filter or by restricting the search to a particular container in the mailbox Error Messages Possible Cause Your application is attempting to search an entire mailbox without limiting the search using either a filter or a container Action Supply a filter For more information see e Filter element http developer novell com ndk doc gwsoap soap_enu data brw415r html brw415r Action Supply a container 8 11 Exxx Unexpected Error e Exxx Unexpected error on page 157 Exxx Unexpected error Source GroupWise engine Explanation An engine error has occurred for which GroupWise does not have a specific error message Action Exit and then restart the GroupWise client Exxx Engine Error Codes 157 158 GroupWise 7 Troubleshooting 1 Error Messages Fxxx Engine Error Codes F00x Errors on page 159 FO1x Errors on page 160 F02x Errors on page 162 F03x Errors on page 163 F04x Errors on page 164 F05x Errors on page 165 F06x Errors on page 166 F07x Errors on page 168 F08x Errors on page 170 F09x
38. in Databases in the GroupWise 7 Administration Guide GroupWise Check Error Codes 263 264 GroupWise 7 Troubleshooting 1 Error Messages GroupWise Time Stamp Utility Error Messages GWTMSTMP Error setting time stamp on page 265 GWTMSTMP Invalid user database on page 265 GWTMSTMP Invalid user ID on page 265 GWTMSTMP User login error on page 265 GWTMSTMP Error setting time stamp Source Explanation Possible Cause Action Possible Cause Action GroupWise Time Stamp utility The Time Stamp utility could not write the date time stamp information into the user database The user database is locked by another process Run the Time Stamp utility again The user database is damaged Run GroupWise Check GWCheck to repair the user database See Group Wise Check in Databases in the GroupWise 7 Administration Guide GWTMSTMP Invalid user database Source Explanation Possible Cause Action Group Wise Time Stamp utility The Time Stamp utility could not process the user database you are running it on The file you specified using the userdb switch is not a proper user database Make sure you specified a valid userxxx db file GWTMSTNP Invalid user ID Source Explanation Possible Cause Action Group Wise Time Stamp utility The Time Stamp utility cannot identify a user database for the user ID you provided when you started it Th
39. missile or chemical biological weaponry end uses Please refer to www novell com info exports for more information on exporting Novell software Novell assumes no responsibility for your failure to obtain any necessary export approvals Copyright 1993 2006 Novell Inc All rights reserved No part of this publication may be reproduced photocopied stored on a retrieval system or transmitted without the express written consent of the publisher Novell Inc has intellectual property rights relating to technology embodied in the product that is described in this document In particular and without limitation these intellectual property rights may include one or more of the U S patents listed at http www novell com company legal patents and one or more additional patents or pending patent applications in the U S and in other countries Novell Inc 404 Wyman Street Suite 500 Waltham MA 02451 U S A www novell com Online Documentation To access the online documentation for this and other Novell products and to get updates see www novell com documentation 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 Contents About This Guide Part GroupWise Engine Error Codes Oxxx Engine Error Codes 8xxx Engine Error Codes
40. on page 49 ADOC No connection could be made to the LDAP server on page 49 AD10 SSL certificate was not found on page 50 AD11 SSL could not be initialized on page 50 AD20 The attribute specified in the request does not exist in the entry on page 50 AD21 The attribute specified in the request does not exist in the LDAP server s schema on page 50 AD25 The object DN passed in is invalid because the target object cannot be found on page 51 AD29 The security TLS versus plain surrounding this request is not valid for the request on page 51 AD2D The LDAP server is busy unavailable has timed out or is down on page 51 AD2E A dynamic memory allocation function failed when calling an LDAP function on page 52 AD2F The LDAP server cannot process the request because of server defined restrictions on page 52 AD01 No LDAP Support Source Internet Agent Installation program or WebAccess Installation program on Linux Explanation The Linux GroupWise Installation program requires that LDAP be running the on server during installation This requirement is not being met Possible Cause LDAP is not available on the Linux server where you are trying to install the Internet Agent or WebAccess Agent Action Set up LDAP on the Linux server Action Install the Internet Agent or WebAccess Agent on a Linux server where LDAP is already set up AD06 The LDAP server information passed
41. repair the message database nsgnnn db See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide 7 13 D50x Errors e D506 Security violation on page 107 D507 Administrator record not found in database on page 108 D508 Transaction failed on page 108 D506 Security violation Source Explanation Possible Cause Action Possible Cause GroupWise engine administration services No authentication An administration command was received that did not contain the proper authentication This command might have originated outside the system or the administration database wpdomain db or wphost db at the destination domain post office has been replaced with an invalid version Monitor and log the source of the command Rebuild the domain or post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide If this error occurs after a configuration change for example after changing which domain is the primary domain of your GroupWise system the Dxxx Engine Error Codes 107 Action Action Possible Cause Action configuration change might not have replicated throughout the system in time to support a following change for example adding a user Wait for replication to complete then synchronize the object that caused the error See Synchronizing Datab
42. 16 User does not exist in post office on page 252 17 Post office does not exist in domain on page 252 18 Message database open error on page 253 19 WPHOST DB database open error on page 253 20 User record has no DS DOMAIN NAME on page 253 21 Unable to decrypt database on page 253 23 Unable to rename file for rebuild backup on page 253 24 Path modify error on page 254 25 Database create error on page 254 26 Database rebuild error on page 254 28 User file already exists or current file inaccessible on page 255 29 User database close error on page 255 30 User database not found on page 255 31 Exclusive access denied to user database on page 255 GroupWise Check Error Codes 247 32 User database open error on page 256 e 33 Error initializing database engine code on page 256 e 34 Unable to get post office information on page 256 35 Memory allocation error on page 256 e 36 Message database not found on page 257 37 Exclusive access denied to message database on page 257 38 Error writing message record as user outbox item on page 257 39 Error writing message record as user inbox item on page 257 41 All substitute filenames used for rename of database on page 257 e 42 Invalid database truncated to nn bytes on page 258 43 Dictionary file missing cannot continue on pa
43. 2 1 2 2 2 3 2 4 2 5 2 6 2 7 2 8 2 9 8xxx Unexpected Emon ns nn EA eA a eee eS 9xxx Engine Error Codes 3 1 3 2 3 3 Oxxx Unexpected EMOR 2 55 4 snd ee Brain ea eG ele ee eS Axxx Engine Error Codes 4 1 4 2 4 3 4 4 4 5 4 6 4 7 4 8 AXX Unexpected Emon ereen kh a he os cate Be kel kaua Ee ed Bxxx Engine Error Codes Cxxx Engine Error Codes 6 1 6 2 6 3 6 4 6 5 6 6 6 7 11 13 15 15 16 27 31 31 41 41 42 42 43 43 43 44 45 45 45 45 46 47 47 48 52 53 6 6 8 C07x Errors 6 9 C08x Errors 6 10 COxx Unexpected Errok ry rir He Me eRe Ee een De 7 Dxxx Engine Error Codes 7 1 DOOx Errors 7 2 D01x Errors 73 DO2x Errors 74 D03x Errors 75 D04x Errors 76 DO5x Errors 7 7 D06x Errors 7 8 D07x Errors 7 9 D10x Errors 7 10 D11x Errors 7 11 D12x Errors 7 12 D20x Errors 7 13 D50x Errors 7 14 D70x Errors 7 15 D71x Errors 7 16 D9xx Errors TAL DAX EMOS cr sie 24 sus cteie gar a gaggle ls ta a ee Aale ae i T18 DATXKEIOFS E ae wes eect eae tes gain eres Dan a ae hotels bees St PO oe eee C19 DBOXX EMOS nu mt ites Narnia Mar Naar SS hotdog atte hat helist 48 tahin 1 20 DBIX EMOS 1 48 Gh ele ty Se De rs EE ae hn eed 21 DB2XErf rfst ae as Wik tes gol ative Gaeta asta oot fice ta en alana sues geh F222 DBS EMOS IH ale EEG Be GS ae 1 23 gt DBABGEFTO S 1 14 ee dass kka a et ne re Rei heb Lede ek 1 24 DB5XETIOrS in ics ects Kree ML ei vias 1 25 DBO GE
44. 3 Message Flow and Directory Structure Check the ownership of the Group Wise databases If necessary change the ownership to a valid user such as the system administrator Another program might already have the required file open with exclusive access 18 GroupWise 7 Troubleshooting 1 Error Messages Action Action Possible Cause 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 Use backup software that interacts properly with GroupWise file locking as described in Target Service Agents in Databases in the GroupWise 7 Administration Guide The Group Wise client has been installed on the local drive so the program can still run but the network connection to the post office has been lost When the network connection to the post office is reestablished the Group Wise client will function normally again Reboot the server If the post office still cannot be accessed resolve those network problems 8202 Cannot access required file Source Explanation Possible Cause Action Possible Cause Action Group Wise engine file input output Bad file handle GroupWise is no longer able to access a required file Exit and then restart the GroupWise program that displayed the error An invalid or old closed file handle was passed to a file I O function Perform the action again If the s
45. 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 DB62 The software area is being referenced Source GroupWise engine administration engine Explanation The software distribution area is still in use by one or more post offices Possible Cause You are trying to delete a software distribution area that is still in use Action Configure the post offices to use other software distribution directories In ConsoleOne display the Post Office Settings property page of each Post Office object then select a different software distribution directory When no post offices reference the software distribution directory it can be deleted DB63 Following a database rebuild the ownership of the target file has been changed The file uid run must be deleted manually Source GroupWise engine administration engine Explanation After it rebuilds a domain or post office database ConsoleOne tries to delete the uid run file that specifies the user that the agent runs as so that user information can be reestablished from the uid conf file Possible Cause ConsoleOne was unable to delete the uid run file Action Delete the uid run file from the domain or post office directory The agent generates a new one based on the uid conf file when it starts running against the rebuilt database 7 26 DExx Errors e DE02 Cannot perform delay
46. 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 Possible Cause The WebAccess Agent has been shut down but one or more worker threads are still processing user reguests Action None WEBACC Invalid command line syntax Source GroupWise WebAccess Agent Explanation The specified syntax is invalid Possible Cause The wrong startup switch syntax was used when attempting to start the WebAccess Agent Action See Using WebAccess Startup Switches in WebAccess in the Group Wise 7 Administration Guide WEBACC Invalid log level Source GroupWise WebAccess Agent Explanation The specified log level is not a valid log level Possible Cause The log level specified by the loglevel startup switch is not valid Action Use one of the valid log levels normal verbose or diagnostic See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC Invalid startup parameter Source GroupWise WebAccess Agent Explanation The specified startup switch is not a valid switch Possible Cause A startup switch used on the command line or in the startup file is not valid Action Retype the command line or edit the startup file to include valid switches
47. Action Make sure the POA process has the required network rights See Creating a NetWare Account for Agent Access Optional in Installing GroupWise Agents in the GroupWise 7 Installation Guide 114 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause The post office has been created in the root directory of a NetWare volume Action Move all post office directories and files into a subdirectory off the root See Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Adjust the path to the post office in the post office Identification page in ConsoleOne DAOE Path to post office database not specified Source GroupWise engine Post Office Agent Explanation No post office path Possible Cause The path to the post office database wphost db was not specified Action Use the home startup switch to specify the location of the post office database See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide 7 18 DA1x Errors e DA10 Cannot read post office configuration information on page 115 e DA12 Invalid application configuration name on page 115 e DA13 name switch required on page 116 e DA17 user and password switches required for this configuration on page 116 DA10 Cannot read post office configuration information Source GroupWise engine Post Office Age
48. Agent The maximum number of message handler threads for the POA is 32 You cannot create any more message handler threads for this POA You can run another POA for the post office on the same server if the server has sufficient resources You can run another POA for the post office on a different server if your network can handle the additional traffic See Configuring a Dedicated Message File Processing POA in Post Office Agent in the GroupWise 7 Administration Guide GWPOA Unable to change all configuration options Source Explanation Action Group Wise Post Office Agent POA configuration settings have been changed in ConsoleOne but some cannot be put into effect until the POA is restarted Exit and restart the POA Post Office Agent Error Messages 191 GWPOA Unable to load viewer Source Explanation Possible Cause Action Group Wise Post Office Agent for Windows The POA cannot run the program used to view agent log files or edit agent startup files The viewer program is not available on the current path or is incorrectly specified The default viewer used by the POA is Notepad which is typically available You can change the viewer specification by selecting View Log Files in the Windows POA agent console and changing the information in the Viewer field Check the viewer and path specified in the View Log Files dialog box in the POA agent console GWPOA Unable to remove doc
49. Agent in the GroupWise 7 Administration Guide If this error occurs when creating a post office you might not be connected to the domain in which you are trying to create the post office 8xxx Engine Error Codes 17 Action Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Action Action Possible Cause Action Possible Cause Action Possible Cause Connect to the domain where you want the post office located See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide If this error occurs when trying to access the account of a new user some required files might be missing from the post office directory See Post Office Directory in Directory Structure Diagrams in Group Wise 7 Troubleshooting 3 Message Flow and Directory Structure Make sure all required files are present in the post office directory especially the dc files which are required for creating new user and message databases If dc files are missing copy them from another post office or from the po subdirectory of the software distribution directory 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 Delete the user object from eDirectory then re create it Do not delete the user s GroupWise account because this would delete t
50. Agent lost its connection to the domain directory or does not have sufficient rights in the directory structure Reestablish the connection to the domain directory and make sure the WebAccess Agent has sufficient rights See WebAccess Security Requirements in Installing GroupWise WebAccess in the Group Wise 7 Installation Guide WEBACC CMC was not able to access this GroupWise gateway directory Source Explanation Possible Cause Action Group Wise WebAccess Agent The WebAccess Agent could not access its gateway directory in domain directory domain wpgate webac70a where domain is the domain directory and webac 70a is the gateway directory The WebAccess Agent does not have sufficient rights in the domain directory structure Make sure the WebAccess Agent has sufficient rights See WebAccess Security Requirements in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide WEBACC CMC was not able to establish a connection to the post office Source Explanation GroupWise WebAccess Agent The WebAccess Agent could not connect to the WebAccess user s post office 222 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Possible Cause Action Possible Cause Action The WebAccess Agent lost its direct connection UNC path or mapped drive to the post office directory or does not have sufficient rights in the directory structure Reestabl
51. Also see Managing Library Access in Libraries and Documents in the GroupWise 7 Administration Guide E818 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 8 7 E82x Errors E820 Invalid attribute value on page 148 E821 Unexpected error on page 148 E823 Unexpected error on page 149 E824 Unexpected error on page 149 E82B Unexpected error on page 149 E82C Unexpected error on page 149 E82E Unexpected error on page 149 E82F Unexpected error on page 149 E820 Invalid attribute value Source GroupWise engine object framework Explanation Validation error when creating or updating a document Possible Cause The user supplied a value for a document property that does not match the valid values specified by the corresponding lookup table For example the value was too large or too small Action Retry the operation with valid values for document properties E821 Unexpected error Source GroupWise engine object framework 148 GroupWise 7 Troubleshooting 1 Error Messages Action See Exxx Unexpected error on page 157 E823 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E824 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E82B Unexpected error Source
52. Braces ASCII characters 0 13 If this error occurs when trying to synchronize users through the GroupWise Gateway to Lotus Notes users might be defined under the gateway rather than in a foreign domain Define Lotus Notes users in a foreign domain See Connecting to Non Group Wise Messaging Systems in the GroupWise 7 Multi System Administration Guide DB2A Invalid name Source Explanation Possible Cause Action Group Wise engine administration engine Invalid name An invalid or restricted name has been specified Enter a valid name DB2B Non unique entry Source Explanation Possible Cause Action Group Wise engine administration engine Non unique entry A new entry conflicts with an existing entry in an index that must be unique This can occur with a user s network ID Check the network ID for uniqueness on the post office where the user will reside DB2C Invalid post office database Source Explanation Action Group Wise engine administration engine Invalid post office database wphost db Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide DB2D Platform error Source Explanation Possible Cause Action Group Wise engine administration engine Wrong platform No valid path could be found for the current platform type Enter a path for the current platform
53. Cause Action GroupWise Post Office Agent admin thread An attempt to recover the post office database wphost db has failed The post office database requires repair beyond what can be done while in use Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWPOA Administrator record not found in database Source Explanation Possible Cause Action Action GroupWise Post Office Agent admin thread The POA admin thread can send a message to an administrator in case of database errors However no administrator has been designated No Group Wise administrator has been set up yet Set up a GroupWise administrator to receive messages about database errors See Notifying the GroupWise Administrator in Post Office Agent in the GroupWise 7 Administration Guide Use the noerrormail switch when starting the POA to turn off administrator messages GWPOA Application connection table full Source Explanation Possible Cause Action 182 GroupWise 7 Troubleshooting 1 Group Wise Post Office Agent TCP agent The POA is configured for TCP IP communication and it has run out of application connections The POA is very busy Increase the number of application connections configured for the POA See Adjusting the Number of Connections for Client Server Processing in Post Office Agent
54. Cause The Monitor Agent is not running Action Restart the Monitor Agent See Starting the Monitor Agent in Monitor in the GroupWise 7 Administration Guide Possible Cause The Monitor Agent is listening on a different port than the one the Monitor Application is using to communicate with it Action Check the gwmonitor cfg file to make sure it provides the correct IP address and port number for the Monitor Agent Correct the information as needed GWMON No route to GroupWise Monitor Agent Source GroupWise Monitor Application Possible Cause Your firewall is preventing the Monitor Application from communicating with the Monitor Agent Action Adjust the configuration of your firewall to accommodate communication between the Monitor Application and the Monitor Agent Possible Cause A router between the Monitor Application and the Monitor Agent is down Action Resolve any network problems that are preventing GroupWise Monitor from functioning GWMON Path to domain database home is invalid or blocked Source GroupWise Monitor Agent Explanation The Monitor Agent cannot access the domain database wodomain db in the directory specified by the home switch Monitor Agent and Application Error Messages 233 Possible Cause Action Possible Cause Action Possible Cause Action The location specified by the home startup switch does not exist Check and if necessary change the location specif
55. Domain Link in Domains in the Group Wise 7 Administration Guide DB25 Duplicate domain name Source GroupWise engine administration engine Explanation Duplicate domain name Possible Cause The name of the external domain being merged conflicts with the name of an existing local domain The names of all primary and secondary domains must be unique in both systems when merging systems Action Remove one of the duplicate domains See Deleting a Domain in Domains in the GroupWise 7 Administration Guide DB26 Secondary domains exist Source GroupWise engine administration engine Explanation Secondary domains exist Possible Cause Multiple local domains were found in an external domain being merged Action Release all secondary domains from the domain to be merged or release the domain to be merged from its owning primary domain See Merging with Group Wise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide DB29 Invalid character Source GroupWise engine administration engine Explanation Invalid character Possible Cause Invalid character in a domain post office or object name Action Check the contents of the name strings for invalid characters Do not use any of the following characters in GroupWise object names Space Period Dxxx Engine Error Codes 123 Possible Cause Action At sign Asterisk Comma Colon Double quote Parentheses
56. E700 Invalid Address Book record Source GroupWise engine Personal Address Book Explanation The POA could not access a user s Personal Address Book Possible Cause The POA is attempting to perform nightly user upkeep for a new user that has not yet used the GroupWise client which means that the Personal Address Book does not yet exist Action None After the user starts the GroupWise client and sends or receives a message the Personal Address Book will be created and the POA will no longer encounter the problem Action Ifthe error persists when the Personal Address Book already exists see 8101 Memory error on page 15 E716 Personal Address Book memory error Source GroupWise engine Personal Address Book Explanation An action involving the Personal Address Book could not be performed due to insufficient memory Action Exit some programs so that more memory is available Action Restart the workstation where the error is occurring 8 5 E80x Errors E801 Unexpected error on page 146 e E803 Unexpected error on page 146 Exxx Engine Error Codes 145 E804 Unexpected error on page 146 e E805 Unexpected error on page 146 e E806 Unexpected error on page 146 e E807 Unexpected error on page 146 e E808 Unexpected error on page 146 E809 Unexpected error on page 146 E80C Unexpected error on page 147 e E80D Unexpected error on page 147 E80F U
57. Errors on page 172 FOAx Errors on page 173 FOBx Errors on page 173 FOCx Errors on page 175 F10x Errors on page 175 FOxx Errors on page 176 F1xx Cannot Connect Error on page 178 9 1 F00x Errors F000 Memory error on page 159 F007 End of command reached unexpectedly on page 159 F008 Missing parenthesis in search command on page 160 F009 Missing operator in search command on page 160 FOOA Switch at end of search command ignored on page 160 FOOB Unknown switch in search command on page 160 F00C Ambiguous switch supply more characters on page 160 F000 Memory error Source Group Wise engine QuickFinder Action See FOxx Memory error on page 177 F007 End of command reached unexpectedly Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 Fxxx Engine Error Codes 159 F008 Missing parenthesis in search command Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 F009 Missing operator in search command Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 FOOA Switch at end of search command ignored Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 FOOB Unknown switch in search command Source GroupWise engine QuickFinder Action See FOxx Qu
58. Group Wise engine See Dxxx Unexpected error on page 138 Dxxx Engine Error Codes 89 7 6 DO5x Errors D050 Cannot connect to specified post office on page 90 D051 Cannot connect to specified post office on page 90 D054 Cannot connect to specified post office on page 91 e D055 Cannot connect to specified post office on page 91 D057 Cannot connect to any post office on page 91 D058 Version mismatch on GroupWise client POA post office on page 91 D059 Recursion limit exceeded during delivery on page 92 e DOSA User database access denied on page 92 DOSD Post office intruder lockout is enforced on page 93 DOSE Message size exceeds limit on page 93 DOSF Box size limit exceeded on page 93 D050 Cannot connect to specified post office Source Explanation Possible Cause Action Possible Cause Action Action Action Group Wise engine No TCP IP services The Group Wise client cannot connect to the specified post office in client server mode because an IP address has not been provided The POA ina remote post office is required for cross post office proxy and library access Set up the IP address for the POA See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide The Group Wise client cannot connect to the specified post office in cl
59. GroupWise 7 Administration Guide D062 Busy Search denied for external Internet user Source Explanation Action Group Wise engine The local GroupWise system is configured so that users outside the local Group Wise system cannot perform Busy Searches on local users To permit Busy Search access by external users enable Allow External Busy Search See System Preferences in System in the GroupWise 7 Administration Guide D065 Attempt to purge item that has not been backed up Source Explanation Action Group Wise engine Client Cleanup options are set so that items cannot be purged from users mailboxes until they have been backed up A user has tried to purge an item that has not yet been backed up You can allow users to purge items that have not yet been backed up See Environment Options Cleanup in Users in the GroupWise 7 94 GroupWise 7 Troubleshooting 1 Error Messages 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 Explanation Action GroupWise engine Client Cleanup options are set so that items cannot be purged from users mailboxes until they have been backed up A process has tried to purge an item that has not yet been backed up You can allow purging of items that have not yet been backed up See
60. GroupWise 7 Troubleshooting 1 GroupWise engine general communication The SOAP port used by the POA to communicate with SOAP clients is already in use by another program on the server You are trying to run two POAs on the same server and you have not given them unique SOAP port numbers Check the SOAP port for each POA See Supporting SOAP Clients in Configuring the POA in the GroupWise 7 Administration Guide Change the SOAP port for one of the POAs Error Messages 8572 CAP port already in use Source GroupWise engine general communication Explanation The CAP port used by the POA to communicate with CAP 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 CAP port numbers Action Check the CAP port for each POA object See Supporting CAP Clients in Configuring the POA in the GroupWise 7 Administration Guide Change the CAP port for one of the POAs 8573 LDAP port already in use Source GroupWise engine general communication Explanation The LDAP port used by the POA 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 LDAP port numbers Action Check the LDAP port for each POA object See Providing LDAP Authentication for GroupWise Users in Configuring the POA in the GroupW
61. GroupWise 7 Troubleshooting 1 Error Messages Action Action Reboot the Windows server Run fewer programs on the server GWPOA Timed out waiting for end of file confirmation Source Explanation Possible Cause Action Action Possible Cause Action Group Wise Post Office Agent message transfer protocol The POA is configured to communicate with the MTA by way of TCP IP The MTA has stopped responding in the middle of a communication The MTA is running on an overburdened server so it cannot respond to the POA in a timely manner Add resources to the MTA server so that the MTA can function properly Move the MTA to a different server where more resources are available See Moving the MTA to a Different Server in Message Transfer Agent in the GroupWise 7 Administration Guide The server where the MTA is running has gone down Check the status of the MTA server Reboot if necessary GWPOA Transport header build failed Source Explanation Possible Cause Action Group Wise Post Office Agent message transfer protocol The POA is configured to communicate with the MTA by way of TCP IP The POA was unable to create a packet of information to send to the MTA Insufficient memory See GWPOA Not enough memory to complete operation on page 188 GWPOA Unable to add additional message handler maximum reached Source Explanation Action Group Wise Post Office
62. Guide 0032 Cannot delete domain that owns GroupWise objects Source Explanation Possible Cause Action Possible Cause Action GroupWise Administrator delete visitor You cannot delete this domain until all subordinate objects have been moved or deleted The domain still owns one or more Agent objects Delete any Agent objects The domain still has post offices assigned to it Move or delete the post offices See Deleting a Post Office in Post Offices and Deleting a Domain in Domains in the GroupWise 7 Administration Guide 0033 Cannot delete post office that owns GroupWise objects Source Explanation Possible Cause Action Possible Cause Action GroupWise Administrator delete visitor Cannot delete post office because it still has subordinate GroupWise objects The post office still owns one or more agent objects Delete any agent objects from the browser window The post office still has users resources distribution lists libraries or library storage areas assigned to it Move or delete each subordinate object in the post office then delete the post office See Deleting a Post Office in Post Offices in the GroupWise 7 Administration Guide 0035 Cannot read GroupWise information for object Source Explanation GroupWise Administrator association Record not read GroupWise Administrator Snap In to ConsoleOne Error Messages 243 Possible Cau
63. I O error on page 176 FO4E File not found during QuickFinder indexing Source GroupWise engine QuickFinder Action See FOxx File I O error on page 176 FO4F File I O error Source GroupWise engine QuickFinder Action See FOxx File I O error on page 176 9 6 F05x Errors F050 Database error on page 165 F051 Database error on page 165 F052 Database error on page 165 F056 Database error on page 165 F050 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F051 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F052 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F056 Database error Source GroupWise engine QuickFinder Fxxx Engine Error Codes 165 Action See FOxx Memory error on page 177 9 7 FO6x Errors F060 Database error on page 166 e F061 Database error on page 166 F062 Database error on page 166 F063 Database error on page 166 F064 Database error on page 166 e F065 Database error on page 167 F066 Database error on page 167 F067 Database error on page 167 e F068 Database error on page 167 F069 Database error on page 167 e FO6A Database error on page 167 FO6B Database
64. Ifyou need a new request because of differing date ranges or item filtering click Yes to confirm that an additional request is required Otherwise click No so the outstanding request will be processed completely before another request is issued Cannot access your Master Mailbox Source GroupWise Windows client Remote mode Possible Cause For GroupWise to access your Master Mailbox remotely GroupWise must give your Master Mailbox password to the master GroupWise system Otherwise access is denied without the appropriate password Remote Mode Windows Client Error Messages 271 Action Run GroupWise before leaving your office then set a password on your Master Mailbox Action Ifyou are already away have someone at your office set a password for you Then specify that password in Remote Options Action The administrator can reset the password for a user in ConsoleOne See Creating or Changing a Mailbox Password in Users in the GroupWise 7 Administration Guide Notify the user of the new password Cannot find the post office Source GroupWise Windows client Remote mode Possible Cause The application is unable to use the provided network connection path The path might be entered incorrectly or there might be network changes Action Verify that the specified network connection path is valid and points to a GroupWise master system post office Action Check the setting of the ph startup switch used to start
65. Installation program on Linux The Installation program cannot log in to the LDAP server The password you supplied is no longer valid Update the password information for the user on the LDAP Server object Specify a user whose password has not expired ADOC No connection could be made to the LDAP server Source Explanation Possible Cause Action Possible Cause Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot communicate at all with the LDAP server you specified The LDAP server is down Check the status of the LDAP server and bring it up if necessary Network problems are preventing communication between the Installation program and the LDAP server Use the ping command to attempt to contact the LDAP server If there is no response resolve the network problem Axxx Engine Error Codes 49 AD10 SSL certificate was not found Source Explanation Possible Cause Action Possible Cause Action Internet Agent Installation program or WebAccess Installation program on Linux You selected to use an SSL connection with the LDAP server but the Installation program cannot establish an SSL connection You did not provide the correct SSL certificate file information to the Installation program Review Linux Installation Options LDAP Information and Clustering in Installing the GroupWise Internet Agent or Linux In
66. Installation program or WebAccess Installation program on Linux The Installation program cannot function in the current environment Insufficient memory Stop some programs that are running on the server in order to free up some memory AD2F The LDAP server cannot process the request because of server defined restrictions Source Explanation Possible Cause Possible Cause Possible Cause Possible Cause Action Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot function in the current environment The add entry request violates the server s structure rules The modify attribute request specifies attributes that users cannot modify Password restrictions prevent the action Connection restrictions prevent the action Make sure that the user who is running the installation has sufficient rights to modify objects Make sure that the user who is running the installation does not have any login restrictions 4 8 Axxx Unexpected Error e Axxx Unexpected error on page 52 Axxx Unexpected error Source Explanation Action Group Wise engine An engine error has occurred for which Group Wise does not have a specific error message Exit and then restart the GroupWise client 52 GroupWise 7 Troubleshooting 1 Error Messages Bxxx Engine Error Codes e B300 File transmission failed on page 53 B309 Port already
67. Message Databases in Databases in the GroupWise 7 Administration Guide If the database cannot be repaired manually restore it from backup For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 15 Record failed delete Source Explanation Possible Cause Action Action Possible Cause Action Action Action Group Wise Check utility GWCheck GWCheck cannot delete a record from the database The record is unavailable Retry There might have been a timing problem with another database user See if another program such as the POA has the database open with exclusive access and has hung with the database open The record is damaged Perform a structural analyze fix on the database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide If the database cannot be repaired restore it from backup See Restoring GroupWise Databases from Backup in Databases in the GroupWise 7 Administration Guide For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 16 User does not exist in post office Source Explanation Action Action Group Wise Check utility GWCheck GWCheck cannot locate the specified user ID Make sure you typed the user ID correctly in the User Resource
68. NetWare error codes Look up the error codes at Novell Error Codes http www novell com documentation nwec index html The NetWare MTA cannot log into the server where a domain or post office is located because all available NetWare licenses are already in use Increase the number of licenses on the server GWMTA Cannot create a new receiver thread Source Explanation Possible Cause Action Group Wise Message Transfer Agent message transfer protocol The MTA cannot create a new receiver thread Insufficient memory See GWMTA Insufficient memory on page 205 GWMTA Cannot create read write files directories Source Explanation Possible Cause Action Group Wise Message Transfer Agent last closure reason A domain or post office is closed because the MTA cannot write files into its output queue in the closed domain or post office The user specified with the user switch in the MTA startup file does not have sufficient rights to create files in the domain or post office directory Make sure the user the MTA is logging in as has sufficient rights in the domain or post office directory See Creating a NetWare Account for Agent Access Optional in Installing GroupWise Agents in the GroupWise 7 Installation Guide 196 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Action The MT
69. Not able to open configuration file on page 229 Not enough memory to complete operation on page 229 Request aborted while waiting on locked conversation on page 229 WebAccess Agent Error Messages 221 e WEBACC Request rejected because all threads are busy on page 230 e WEBACC Running the agent with conflicting effective users on page 230 e WEBACC Startup file not found on page 230 e WEBACC TCP socket accept failed on page 230 WEBACC The post office is closed on page 230 e WEBACC The system is busy please try again later on page 231 e WEBACC Unable to establish a connection to the default log path on page 231 e WEBACC Unable to establish a connection to the log path on page 231 e WEBACC Unable to find the specified user on page 231 e WEBACC Unknown keyword on page 232 WEBACC CMC encountered a problem accessing the GroupWise domain Source Explanation Possible Cause Action Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent could not access the GroupWise domain in which its gateway directory is located The WebAccess Agent was not started with the ph switch Start the WebAccess Agent by using the ph switch For example gwinter ph j advert wpgate webac7 0a For more information see Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide The WebAccess
70. Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 71 Unable to correct version without element Source Group Wise Check utility GWCheck GroupWise Check Error Codes 261 Explanation Possible Cause Action GWCheck cannot correct the version information for a document because the specified element was missing in the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 72 Invalid user specified for orphan document reassignment Source Explanation Action Action Group Wise Check utility GWCheck GWCheck cannot locate the user ID specified in the New Author field in GWCheck Make sure you typed the user name correctly in the New Author field Ifthe user name is typed correctly make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides 73 Unable to remove document storage area Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot delete the specified document storage area Insufficient rights Make sure you have rights to the directory where the docu
71. Possible Cause Action Possible Cause Action Possible Cause Action Action Possible Cause Action Possible Cause Action Group Wise engine file input output Drive or path not found Group Wise cannot find the specified drive or path Use Browse to find the correct path The file you are trying to perform an action on does not exist Enter a valid filename If this error occurs shortly after starting the Group Wise client the path to the archive directory might not be correct In the GroupWise client verify that the path to the archive directory exists and that you have sufficient rights to create and modify files Look up archive directory in GroupWise client Help If the path to the archive directory is valid and this is the first time the user has tried to archive items make sure the ngwguard dc file exists in the post office If it is missing the databases required for archiving cannot be created To restore the ngwguard dc file if it is missing copy it from the po directory in the software distribution directory to the post office directory For the locations of these files see Post Office Directory and Software Distribution Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure If this error occurs from the POA the POA might not have access to a required file Start the POA including the rights switch to dete
72. Rights in Security Administration in the GroupWise 7 Administration Guide If this error occurs when trying to add users to a post office or when trying to rebuild a user database a required file might be missing from the post office directory Make sure the ngwguard dc file exists in the post office directory If it does not copy it from the po subdirectory of your software distribution directory For the specific location of this file see Post Office Directory and Software Distribution Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure New user databases userxxx db files and message databases ms gnnn db files cannot be created for new users if this file is missing 820B Path too long Source Explanation Possible Cause Action Possible Cause Action Group Wise engine file input output Path too long The file system cannot build or modify a path because the specified path contains too many characters Shorten the path name to a length that is valid for the operating system If a filename will be appended to the path name include the filename in the total length If this error occurs when you are trying to create a new GroupWise system you might have mapped the drive where you are creating the GroupWise system to an object in the eDirectory tree instead of to the correct volume on the server For example if you used
73. See Moving a Document Storage Area in Libraries and Documents in the GroupWise 7 Administration Guide Next start the POA using the noconfig user and password switches so the POA can start and process the administrative message containing the new storage location without accessing the old storage location Finally exit then restart the POA with its typical configuration 7 19 DBOx Errors DB01 Operation cancelled on page 117 DB02 Database access error on page 117 DB03 Operation pending cannot modify on page 117 DB04 Owner not valid user on page 117 DB05 Invalid path on page 118 DB08 Non unique name on page 118 116 GroupWise 7 Troubleshooting 1 Error Messages DBO9 User owns resource on page 118 DBOA Record not found on page 118 DBOB Required field empty on page 119 DBOC Cannot close database on page 119 DBOE Insufficient memory to initialize database on page 119 DBOF Domain not found on page 119 DB01 Operation cancelled Source Explanation Possible Cause Action Group Wise engine administration engine Operation cancelled Operation cancelled by user None DB02 Database access error Source Explanation Possible Cause Action Action Group Wise engine administration engine Database access error Cannot complete the requested operation because the database is being updated Retry the oper
74. Source Explanation Possible Cause Action GroupWise WebAccess Agent During a conversation or session GroupWise WebAccess issues a request whenever the user performs an action in WebAccess When the WebAccess Agent receives a request it locks the conversation so that it can process the request While the conversation is locked other requests can accumulate This message indicates a request that was waiting on the locked conversation has timed out The request for the locked conversation took longer than allowed Have the GroupWise WebAccess user perform the action again for example resend the message WebAccess Agent Error Messages 229 WEBACC Request rejected because all threads are busy Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent could not process a request from a WebAccess user because no threads were available Heavy WebAccess usage for the number of threads allocated to the WebAccess Agent If this error occurs often increase the number of threads See Modifying WebAccess Settings in WebAccess in the GroupWise 7 Administration Guide WEBACC Running the agent with conflicting effective users Source Explanation Possible Cause Possible Cause Action GroupWise WebAccess Agent for Linux You are starting the WebAccess Agent as a user that is different from the user the WebAccess Agent is configured to run as The user
75. The database you want to repair cannot be accessed You are trying to perform database maintenance on a database that is currently being repaired None Your database maintenance request will be deferred until the build in completed D078 LDAP SSL key file not found Source Explanation Possible Cause Action Group Wise engine The POA is configured to use SSL on its LDAP connection but it cannot locate the SSL key file The SSL key file has not been specified or has been specified incorrectly Provide the full path to a valid SSL key file See Providing LDAP Authentication for GroupWise Users in Post Office Agent in the GroupWise 7 Administration Guide See also Server Certificates and SSL Encryption in Security Administration in the GroupWise 7 Administration Guide D07F Unexpected error Source Action Group Wise engine See Dxxx Unexpected error on page 138 7 9 D10x Errors e D101 User not found on page 99 D102 Ambiguous user ID on page 100 D103 Post office not found during login on page 101 e D104 Ambiguous post office on page 101 D105 Directory Services data missing on page 101 98 GroupWise 7 Troubleshooting 1 Error Messages D106 Database error on page 101 D107 Record not found on page 102 D108 Unexpected error on page 102 D109 Bad parameter on page 102 D10A Unexpected error on page 10
76. User record has no DS_HOST_NAME Source GroupWise Check utility GWCheck 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 05 User record has no DS_OBJ_TYPE Source GroupWise Check utility GWCheck 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 06 User record has no DS_FID Source GroupWise Check utility GWCheck GroupWise Check Error Codes 249 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 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 08 User database read error Source
77. Windows Explorer or Network Neighborhood to map the drive you might have browsed under the tree icon rather than under the server icon Make sure you have mapped the drive where you are creating the Group Wise system to the correct volume on the server not to an object in the eDirectory tree 820E Cannot lock file Source Explanation Possible Cause Action Possible Cause Action Action Group Wise engine file input output File lock error An attempt to lock a file failed Verify that the file is not currently locked by another process that has terminated You cannot open the specified file because another user might have the file open Ask the other user to close the file Retry the action later 24 GroupWise 7 Troubleshooting 1 Error Messages Action Possible Cause Action Possible Cause Action Action If no valid user or process has the file open delete the connection to unlock the file You cannot open the specified file because you might not have rights to open the file Obtain rights to the file If this error occurs from the POA when rebuilding a database a user might still have the database open The POA requires exclusive access to databases when rebuilding them Make sure no users associated with the database to be rebuilt are currently running the GroupWise client If none are and the database is still locked break the connection to unlock the file Exit
78. a server that is currently not available Check the status of the server where the specified directory is located Wait for the server to come back up or contact the administrator of that server It is recommended that the work switch be set to a location local to where the MTA is running to avoid this problem 206 GroupWise 7 Troubleshooting 1 Error Messages GWMTA Link or transport down Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA is using TCP IP to communicate with an MTA or POA and the other agent is not responding The MTA in the other domain is not properly set up for TCP IP communication Check the setup of the MTA in the other domain See Using TCP IP Links between Domains in Message Transfer Agent in the GroupWise 7 Administration Guide The POA in the post office is not properly set up for TCP IP communication Check the setup of the POA See Using TCP IP Links between a Domain and its Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA Logging permanently suspended insufficient memory Source Explanation Possible Cause Action Action Group Wise Message Transfer Agent The MTA could not start a new thread for disk logging Therefore disk logging has been turned off Insufficient memory See GWMTA Insufficient memory on page 205 After suffici
79. and see the recommended actions above GWMTA Insufficient memory to read process startup file Source GroupWise Message Transfer Agent Possible Cause Insufficient memory Action See GWMTA Insufficient memory on page 205 GWMTA Insufficient resources to accept inbound connection Source GroupWise Message Transfer Agent Explanation The MTA cannot start a receiver thread Possible Cause Insufficient memory Action Ifthe problem does not resolve itself in a short time see GWMTA Insufficient memory on page 205 GWMTA Insufficient system resources Source GroupWise Message Transfer Agent Explanation The MTA was unable to start another thread Possible Cause Insufficient memory Message Transfer Agent Error Messages 205 Action If the problem does not resolve itself in a short time see GWMTA Insufficient memory on page 205 GWMTA Internet mail to address is undeliverable because no default GWIA is configured Source Explanation Possible Cause Action Group Wise Message Transfer Agent A message addressed to a user across the Internet cannot be delivered A default GroupWise Internet Agent has not been configured Designate a default Internet Agent See Configuring Internet Addressing in System in the GroupWise 7 Administration Guide GWMTA Invalid log parameter Source Explanation Possible Cause Action Possible Cause Action Action Group Wise
80. are newer than the current database so a recover is needed to update the database The admin thread of the POA or MTA should take care of this recovery automatically If not perform the recovery manually See Recovering Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide DB4E Cannot delete default gateway Source Explanation Possible Cause Group Wise engine administration engine The gateway is used in default routing You are trying to delete a GroupWise Internet Agent object that is used as the default gateway for routing Internet messages Dxxx Engine Error Codes 131 Action Select a different Internet Agent as the default gateway for Internet messages See Configuring Internet Addressing in System in the GroupWise 7 Administration Guide DB4F Cannot delete POA that performs message transfer T DB DB Source GroupWise engine administration engine Explanation The POA is used as the message transfer recipient for its post office Possible Cause You are trying to delete a a POA that is part of the TCP IP link between the post office and domain through which messages arrive in the post office Action Setup a different POA to provide the link to the domain MTA See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide After another POA has been set up to provide the link with the MTA th
81. auto upgrade on the older database 7 11 D12x Errors e D124 Access to user denied on page 106 D124 Access to user denied Source Explanation Possible Cause GroupWise engine database interface Access rights failure A required field was not found Moving a resource causes the resource owner to lose access to the resource 106 GroupWise 7 Troubleshooting 1 Error Messages Action In ConsoleOne browse to and select the Resource object then click Tools gt GroupWise Utilities gt Mailbox Library Maintenance Select Reset Client Options in the Action drop down list 7 12 D20x Errors e D201 Unexpected error on page 107 D202 General printing error on page 107 D201 Unexpected error Source Action Group Wise engine mail calendar import and print services See Dxxx Unexpected error on page 138 D202 General printing error Source Explanation Possible Cause Action Action Possible Cause Action Group Wise engine mail calendar import and print services You have attempted to print an item that is missing information The user workstation is missing its temporary directory or there is insufficient disk space available to create the temporary files needed to print the item Check for the existence of the temporary directory on the user workstation Check for available disk space The link to the item to print has been damaged Check and if necessary
82. cfg file used by the WebAccess Agent is out of sync with the commgr cfg file used by the WebAccess CGI Extension The WebAccess Agent WebAccess CGI Extension HTML templates and Java applets are not the same version Action In ConsoleOne reenter the configuration information so that the comint cfg file and commgr cfg file will be resaved See Configuring the WebAccess Agent in WebAccess in the GroupWise 7 Administration Guide If the problem persists reinstall the GroupWise WebAccess software See Installing GroupWise WebAccess in the GroupWise 7 Installation Guide 232 GroupWise 7 Troubleshooting 1 Error Messages Monitor Agent and Application Error Messages e GWMON GroupWise Monitor Agent is not listening on page 233 e GWMON No route to GroupWise Monitor Agent on page 233 e GWMON Path to domain database home is invalid or blocked on page 233 e GWMON Request timed out waiting for response from Group Wise Monitor Agent on page 234 e GWMON The URL to connect to the Group Wise Monitor Agent is invalid on page 234 e GWMON Unable to communicate with Group Wise Monitor Agent on page 234 e GWMON Unable to connect to the MTA at IP_address port on page 235 e GWMON Unable to resolve GroupWise Monitor Agent s host name to a valid IP address on page 235 GWMON GroupWise Monitor Agent is not listening Source GroupWise Monitor Application Possible
83. client in Remote mode there might be a problem with the structure or content of the Remote mailbox For example copying a GroupWise client installation from one laptop to another might introduce this problem Delete the rofdata directory on the remote computer then request all information from the master mailbox again Reinstall the GroupWise client on the remote computer See the platform specific setup instructions for using Remote mode in Setting Up GroupWise Modes and Accounts in Client in the GroupWise 7 Administration Guide The hard disk where the Group Wise databases are stored is damaged Scan the hard disk for damage Correct any problems with the hard disk Repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide If the database cannot be repaired you must restore it from backup See Restoring GroupWise Databases from Backup in Databases in the GroupWise 7 Administration Guide In ConsoleOne you can set the proper user rights for all users in a post office or for an individual user See GroupWise User Rights in Security Administration in the GroupWise 7 Administration Guide If users are accessing a post office on a NetWare server through a Windows workstation using the Microsoft Gateway for NetWare the gateway might not be providing adequate sup
84. db in the post office Possible Cause The library database is damaged Action Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide GroupWise Check Error Codes 259 62 Error reading system document type definition Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot read the specified document type definition in the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 63 Unable to update during check error code Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot write changes to the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 64 Unable to complete verify during check error code Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot verify the library database dmsh db in the post office The library database is damaged Perform a stru
85. does not exist in the strtweb ncf file Use the password startup switch when starting the WebAccess Agent from the command line or edit the strtweb ncf file to add the switch See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC No NetWare user ID was specified Source Explanation Possible Cause Action GroupWise WebAccess Agent The GroupWise WebAccess Agent requires an account and password that lets it log in to eDirectory or NetWare servers so that it can access the domain directory and post office directories The user startup switch was not used on the command line or does not exist in the strtweb ncf file Use the user startup switch when starting the WebAccess Agent from the command line or edit the strtweb ncf file to add the switch See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC No UNC path specified for the post office Source Explanation Possible Cause GroupWise WebAccess Agent The WebAccess Agent is attempting direct access to a post office and no UNC path is specified The UNC path is not defined in the post office link information 228 GroupWise 7 Troubleshooting 1 Error Messages 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 W
86. does not have rights to the directory or does not have access to the file server Action Make sure the WebAccess Agent s user account provides the correct access and rights or specify a different log file directory using the log switch See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC Unable to find the specified user Source GroupWise WebAccess Agent Explanation The WebAccess Agent cannot find the user in the GroupWise database Possible Cause When logging in the user entered an incorrect or invalid user ID Action Have the user enter a valid user ID or full username as defined in eDirectory or the GroupWise Address Book when logging in WebAccess Agent Error Messages 231 Action Have the user try logging in using the full GroupWise username 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 and Windows Linux opt novell groupwise webaccess logs WEBACC Unknown keyword Source GroupWise WebAccess Agent Explanation When communicating the WebAccess Agent and WebAccess CGI Extension exchange keywords This message indicates that the keyword given by the WebAccess CGI Extension is not known by the WebAccess Agent Possible Cause The comint
87. error on page 167 e F06C Database error on page 167 FO6D Database error on page 167 e FO6E Database error on page 167 e FO6F Database error on page 168 F060 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F061 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F062 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F063 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F064 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 166 GroupWise 7 Troubleshooting 1 Error Messages F065 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F066 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F067 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F068 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F069 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177
88. in is not valid Source Internet Agent Installation program or WebAccess Installation program on Linux 48 GroupWise 7 Troubleshooting 1 Error Messages Explanation Possible Cause Action Action The Installation program cannot communicate with the LDAP server because it is using incorrect information Required LDAP information includes an IP address for the LDAP server a port number a username in LDAP format and a password You have provided incorrect information Review Linux Installation Options LDAP Information and Clustering in Installing the Group Wise Internet Agent or Linux Installation Options LDAP Information and Clustering in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide for details about the information that the Installation program requires then provide the correct information Make sure that the LDAP Server object is correctly configured in ConsoleOne AD08 No username or password specified for logging into the LDAP server Source Explanation Possible Cause Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot log in to the LDAP server You have not supplied a username or password Supply the required information AD09 The password for the LDAP user has expired Source Explanation Possible Cause Action Action Internet Agent Installation program or WebAccess
89. in the GroupWise 7 Administration Guide Then exit and restart the POA Error Messages GWPOA Authentication failed for the above object Source Explanation Possible Cause Action Group Wise Post Office Agent admin thread The POA admin thread attempted to process a record that has the wrong authentication key for the current GroupWise system The record did not originate in the current GroupWise system which is a possible security violation Someone is trying to tamper with your Group Wise system Check your system security measures GWPOA Cannot access remote post office retrying Source Explanation Possible Cause Action GroupWise Post Office Agent The POA can no longer access its post office The server where the post office is located is currently down Wait for the server to come back up or contact the administrator of that server GWPOA Cannot access remote post office user ID switch is missing Source Explanation Possible Cause Action Action Group Wise Post Office Agent The POA cannot access its post office because it cannot log in to the server where the post office is located The POA has not been started with the user or dn switch Include the user and password or dn switches when the POA needs to access a post office on a remote server See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide In ConsoleOne
90. is being received by the Internet Agent from the GroupWise system Action None GWIA Running the agent with conflicting effective users Source GroupWise Internet Agent for Linux Internet Agent Error Messages 219 Explanation Possible Cause Possible Cause Action 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 The user specified in the uid conf file has been manually edited The uid conf file has been deleted Verify that the uid conf file specifies the desired user then delete the uid run file For more information see Running the Linux GroupWise Agents as a Non root User in Installing GroupWise Agents in the GroupWise 7 Installation Guide GWIA Scratch pad file creation error xxxx Source Explanation Action Action Group Wise Internet Agent The Internet Agent settings file SET could not be created Check access write or create to the 000 prc directory Check to see if the disk is full GWIA Scratch pad file write error filename Source Explanation Action Action Group Wise Internet Agent The Internet Agent settings file SET could not be written Check access write or create to the 000 prc directory check to see if the disk is full GWIA Unable to find TCPIP Kernel Source Expl
91. loadable language resource Action See 9xxx Unexpected error on page 44 9307 Unexpected error Source GroupWise engine loadable language resource Action See 9xxx Unexpected error on page 44 9308 Unexpected error Source GroupWise engine loadable language resource Action See 9xxx Unexpected error on page 44 9309 Unexpected error Source GroupWise engine loadable language resource Action See 9xxx Unexpected error on page 44 3 3 9xxx Unexpected Error e Oxxx Unexpected error on page 44 9xxx Unexpected error Source GroupWise engine loadable language resource Explanation An engine error has occurred for which GroupWise does not have a specific error message Action Exit and then restart the GroupWise client 44 GroupWise 7 Troubleshooting 1 Error Messages Axxx Engine Error Codes AOxx Errors on page 45 A5xx Errors on page 45 A6xx Errors on page 45 A8xx Errors on page 46 e AAxx Errors on page 47 e ACxx Errors on page 47 e ADxx Errors on page 48 e Axxx Unexpected Error on page 52 4 1 AQxx Errors e A001 Unexpected error on page 45 A001 Unexpected error Source GroupWise engine sized string manipulation Action See Axxx Unexpected error on page 52 4 2 A5xx Errors e A501 Unexpected error on page 45 e A502 Unexpected error on page 45 e A504 Unexpected error on page 45 A
92. logged out of his or her GroupWise mailbox The POA has timed out the session after 30 minutes Your application needs to log in again for that user For more information see session definition http developer novell com ndk doc gwsoap soap_enu data bs3a3 1o html bs3a3 10 login method http developer novell com ndk doc gwsoap soap_enu data brx8x54 html brx8x54 EA07 Container string is missing Source Explanation Possible Cause GroupWise engine SOAP protocol The container string in a POA request is not found in your application Your application calls a method that requires a container as an argument and you have not provided a container Exxx Engine Error Codes 151 Possible Cause Your application passes in a uid that does not have the container appended to the end Action Call getltemsReguest 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 ndk doc gwsoap soap_enu data brw59el html brw59el uid element http developer novell com ndk doc gwsoap soap_enu data brwiocm html brwiocm getltems method http developer novell com ndk doc gwsoap soap_enu data brx8r5w html brx8r5w ContainerRef element http developer novell com ndk doc gwsoap soap_enu data brw3u9a html brw3u9a Containerltem element http developer novell com ndk doc gwsoap soap_enu data brw3r28 html brw3r28
93. mismatch An improper update ofthe GroupWise Administrator snap in might have been loaded from Novell Support Rerun GroupWise Install or acquire the latest GroupWise Administrator snap in from Novell Support Novell Support http support novell com 0004 Required DLL missing Source Explanation Possible Cause Action GroupWise Administrator general snap in One of the GroupWise Administrator snap in DLL programs is missing You are attempting to run ConsoleOne on a workstation that does not have Group Wise Administrator snap in installed Run ConsoleOne on a workstation where the GroupWise Administrator snap in has already been installed 240 GroupWise 7 Troubleshooting 1 Error Messages 0005 Cannot read required information from NDS Source Explanation Possible Cause Action GroupWise Administrator general snap in Group Wise is unable to read necessary information from eDirectory the current product name of Novell Directory Services You have insufficient rights to read this information Make sure you have sufficient rights to administer the objects in this Group Wise domain If you have not been assigned sufficient rights contact the system administrator 0006 GroupWise object missing required information Source Explanation Action GroupWise Administrator general snap in Invalid object state The information for the eDirectory object is in an inconsistent state for Gr
94. more efficient route See Link Configuration between Domains and Post Offices in Domains in the GroupWise 7 Administration Guide GWMTA File create error disk logging turned off Source Explanation Possible Cause Action Action Action Group Wise Message Transfer Agent Logging information to disk has been turned off because the MTA cannot create a new log file The agent cannot create a file in the location specified by the Log File Path setting on the Log Settings page for the agent in ConsoleOne or specified on the command line using the log startup switch See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide Make sure the location exists or specify another location Make sure the agent has rights to create files in the specified location Make sure there is available disk space in the specified location GWMTA File write error disk logging turned off Source Group Wise agents 202 GroupWise 7 Troubleshooting 1 Error Messages Explanation Possible Cause Action Possible Cause Action Logging information to disk has been turned off because the agent can no longer write to the current log file If the log file is located on a server other than the one where the agent is running that server might be down Wait for the server to come back up or contact the administrator of that server When the server comes back up the age
95. named file GWIA File write error on file filename in module xxxx Source GroupWise Internet Agent Explanation A write to the named file resulted in an error Action Check access in the named directory and check to see if the disk is full GWIA Gateway that uses this directory is not yet defined Source GroupWise Internet Agent Explanation The Internet Agent has been installed but it is not yet configured Action Configure the Internet Agent in ConsoleOne See Internet Agent in the GroupWise 7 Administration Guide GWIA Gateway Configuration Database could not be found Source GroupWise Internet Agent Explanation The directory where the domain database wodomain db resides cannot be found given the Internet Agent s default directory and the Internet Agent startup options Action Use the Internet Agent directory startup option work to reference the directory below wpgate in the domain where the Internet Agent executable file resides or simply invoke the executable from that directory Check network rights GWIA Memory exhausted Source GroupWise Internet Agent Explanation The Internet Agent was not able to allocate sufficient memory Action Free up more memory GWIA Memory exhausted while processing an Administrator Command Source GroupWise Internet Agent Explanation The Internet Agent ran out of memory while processing a command sent to the Internet Agent by ConsoleOne Action Free up mo
96. of date Action Use a supported method For a list of currently supported methods see e Methods http developer novell com ndk doc gwsoap soap_enu data brx9pkk html brx9pkk Exxx Engine Error Codes 153 EAOE Key is invalid Source GroupWise engine SOAP protocol Explanation A key is a unique identifier that is used to create or modify an event configuration Events notify your application when an event has occurred in a user s mailbox for example when an item is deleted Possible Cause Your application did not provide a usable key Possible Cause The key string is empty Action Check the configureEvents request to see if it is passing a valid key element For more information see Event object http developer novell com ndk doc gwevents evnt_enu data buotgsx html buotgsx configureEvents XML reference http developer novell com ndk doc gwevents evnt_enu data buj9p3v html buj9p3v EAOF Missing cursor Source GroupWise engine SOAP protocol Explanation A required cursor string is absent Possible Cause Your application calls a method that requires a cursor but no cursor was provided Action Call createCursor to get a valid cursor before using positionCursor or readCursor For more information see Cursors http developer novell com ndk doc gwsoap soap enu data bwncsce html bwncsce createCursor method http developer novell com ndk doc gwsoap soap_enu data brx85xo html brx85xo
97. on page 68 C040 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C042 Database being modified Source GroupWise engine database services Explanation Read consistent view of record not available Possible Cause A read operation encountered data that was being modified by another concurrent program The read operation needs to see a prior version of the data however no prior version is available This error should be handled by the GroupWise engine in most cases If it finally does come through to the end user it might indicate there is a problem with the database However it might also indicate the update activity on the database is currently very high Action Generally the error is transitory and goes away when the operation is retried Make sure that others are not doing updates to the database and retry the action If the problem persists validate and rebuild the database as necessary See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Action If this error occurs on a message or user database run GWCheck See Standalone Database Maintenance Programs in the GroupWise 7 Administration Guide C043 Database error Source GroupWise engine database services Action See COxx Database error general databa
98. only See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC Invalid startup parameter file Source GroupWise WebAccess Agent Explanation The specified file is not a valid startup file Possible Cause The file is not a text file or does not contain any startup switches WebAccess Agent Error Messages 225 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 Explanation Possible Cause Action GroupWise WebAccess Agent The value for the specified startup switch is not valid An invalid value was entered with the startup switch on the command line or in the startup file Enter a valid value See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC Logging Disk is full turning file logging off Source Explanation Possible Cause Action GroupWise WebAccess Agent The disk where the log files are stored is full File logging will be turned off The disk is full Delete files to increase available disk space Allocate more disk space Specify a different location for the log files See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC Logging Error creating file tu
99. specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object GWPOA Cannot find the help file Source Explanation Action Group Wise Post Office Agent for Windows The Help file for the agent is not available For the name of the Help file the agent is trying to use see Agent Installation Directories in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure GWPOA Client server login failed no user ID supplied Source Explanation Possible Cause Action Group Wise Post Office Agent The POA cannot communicate with a Group Wise client process that is requesting services because the client is not providing a user ID The GroupWise client was not started with the needed user ID information Use the u startup switch to make sure the client has the correct user ID information See Client in the GroupWise 7 Administration Guide Post Office Agent Error Messages 183 GWPOA Configured address may not match actual address Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Group Wise Post Office Agent TCP agent The POA is configured for TCP IP communication but a mismatch of IP addresses has been detected DNS is not currently available so the POA is unable to resolve a host name into its IP address Make sure DNS is functioning correctly Or specify t
100. system if necessary DBOF Domain not found Source Explanation Possible Cause Action Possible Cause Action Group Wise engine administration engine Domain not found Cannot find the specified domain Make sure that the domain exists and that the domain name is correct In ConsoleOne browse to and right click the Domain object then click Properties If this error occurs from the POA the post office database wphost db might be damaged so that valid domain information is not available Check and if necessary repair the database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide Dxxx Engine Error Codes 119 7 20 DB1x Errors DB10 Post office not found on page 120 DB11 Unexpected error on page 120 DB12 Maximum number of objects per post office reached on page 120 DB17 Domain already exists in specified directory on page 120 DB19 Local post office not found on page 121 DBIA Insufficient administrative rights to perform operation on page 121 DBIB Message Transfer Agent not installed on page 121 DBIC Invalid object name on page 121 DBID Cannot delete post office on page 121 DBIF Cannot delete current domain on page 122 DB10 Post office not found Source Explanation Possible Cause Action GroupWise engine administration engine Post office not found Cannot find the s
101. the GroupWise 7 Administration Guide Action Reset the client options for that user See Resetting Client Options to Default Settings in Users in the GroupWise 7 Administration Guide Possible Cause If this error occurs when new users exit GroupWise or try to archive items the archive might be damaged Action Copy a new ngwguard dc file from the po subdirectory of the software distribution directory into the post office directory Delete new users archive directories because they haven t been able to archive anything yet C068 Database error Source GroupWise engine database services Action See COxx Database error general database repair strategies on page 77 C069 Database error Source GroupWise engine database services Action See COxx Database error database dictionary file on page 78 COGA Database error Source Group Wise engine database services Action See C0xx Database error general database repair strategies on page 77 C06B Database error Source GroupWise engine database services Explanation Server not defined Possible Cause The platform specific definition needed by the database to identify the location of the database files is either missing or invalid Action Check and repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Gui
102. the Windows client Explain to the user that he or she must use the WebAccess client Allow the user to use the Windows client See Setting Client Options in Users in the GroupWise 7 Administration Guide 7 8 D07x Errors e D071 LDAP authentication failed because the password has expired on page 96 D072 Changing the LDAP password has been disabled on page 97 D073 Attempting to log in trusted without SSL on page 97 D074 Invalid key for trusted application on page 97 e D075 Invalid IP address for trusted application on page 97 e D076 Missing trusted application name on page 98 D077 The problem file is being rebuilt on page 98 D078 LDAP SSL key file not found on page 98 D07F Unexpected error on page 98 D071 LDAP authentication failed because the password has expired Source Explanation Action 96 GroupWise 7 Troubleshooting 1 GroupWise engine The GroupWise client was attempting to authenticate using LDAP but the user s LDAP password has expired The user needs to contact the administrator ofthe LDAP server and get the password reset Error Messages D072 Changing the LDAP password has been disabled Source Explanation Action Action GroupWise engine A user tried to change his or her LDAP password from the GroupWise client but the administrator has disabled that capability for the user s post office Ena
103. 138 D704 Unexpected error Source GroupWise engine directory services access Action See Dxxx Unexpected error on page 138 D705 Unexpected error Source GroupWise engine directory services access Action See Dxxx Unexpected error on page 138 D706 Unexpected error Source GroupWise engine directory services access Action See Dxxx Unexpected error on page 138 D707 Unexpected error Source GroupWise engine directory services access Action See Dxxx Unexpected error on page 138 D708 Directory entry record not found Source Group Wise engine directory services access Explanation Requested record not found Possible Cause The directory entry record was not found This can occur if multiple processes are updating the database at the same time Dxxx Engine Error Codes 109 Action Cancel the current operation refresh the listing then select again from the available items Possible Cause The database is damaged Action Rebuild the problem database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide Possible Cause The path to the software distribution directory might be incorrect Action Make sure the post office where the problem is occurring has a software distribution directory assigned See Editing Post Office Properties in Post Offices in the GroupWise 7 Administration Guide Action Check the curre
104. 2 D10B Database needs to be repaired on page 103 D10C Unexpected error on page 103 D10D Cannot open any more mailboxes on page 103 Source Explanation Possible Cause Action Action Possible Cause Action Possible Cause Action Possible Cause Action Action Possible Cause Action Possible Cause Action D101 User not found Group Wise engine database interface User not found The Group Wise user ID is not found in the post office database during login If using startup switches check the ph switch to make sure the path to the post office is correct Start the Group Wise client using the u or la startup option to specify the Group Wise user ID The user is not yet set up as a Group Wise user Set the user up as a Group Wise user See Creating GroupWise Accounts in Users in the GroupWise 7 Administration Guide The user ID provided when the user was set up as a GroupWise user is not correct Check the GroupWise user information in ConsoleOne Make sure the common name CN of the user is provided No additional information is needed in the Network ID field User information has not replicated from the domain to the post office the user is trying to access Wait for replication to take place Make sure the MTA is running Check the current scan cycles of the MTA See Adjusting MTA Polling of Input Queues in the Domain Post Offices and Gate
105. 47 e AA04 Unexpected error on page 47 AA01 Unexpected error Source Group Wise engine ASCII strings Action See Axxx Unexpected error on page 52 AA02 Unexpected error Source GroupWise engine ASCII strings Action See Axxx Unexpected error on page 52 AA04 Unexpected error Source GroupWise engine ASCII strings Action See Axxx Unexpected error on page 52 4 6 ACxx Errors e AC01 Zipped file has unsupported version number on page 47 e AC02 Zipped file has incorrect format on page 47 e AC03 Zipped file damaged on page 48 AC01 Zipped file has unsupported version number Source GroupWise engine zip compression Explanation The zipped file has an unsupported version number Action None GroupWise cannot unzip the file AC02 Zipped file has incorrect format Source GroupWise engine zip compression Explanation The zipped file is not formatted correctly Action None GroupWise cannot unzip the file Axxx Engine Error Codes 47 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 ADOI No LDAP Support on page 48 AD06 The LDAP server information passed in is not valid on page 48 e AD08 No username or password specified for logging into the LDAP server on page 49 AD09 The password for the LDAP user has expired
106. 501 Unexpected error Source GroupWise engine data array management Action See Axxx Unexpected error on page 52 A502 Unexpected error Source GroupWise engine data array management Action See Axxx Unexpected error on page 52 A504 Unexpected error Source GroupWise engine data array management Action See Axxx Unexpected error on page 52 4 3 A6xx Errors e A602 Unexpected error on page 46 Axxx Engine Error Codes 45 A602 Unexpected error Source GroupWise engine data list management Action See Axxx Unexpected error on page 52 4 4 A8xx Errors A801 Auto Date formula too long on page 46 A802 Auto Date formula has incorrect syntax on page 46 A803 Auto Date formula not specified on page 46 A804 Auto Date formula generates too many occurrences on page 46 A801 Auto Date formula too long Source GroupWise engine Auto Date Explanation Formula is too long Possible Cause The user either entered formula text that was too large 4 KB is maximum or the user selected from the graphical Auto Date window and the generated formula was too large Action Enter a shorter formula or reduce the number of days selected in the Auto Date window Look up auto dates in GroupWise client Help A802 Auto Date formula has incorrect syntax Source GroupWise engine Auto Date Explanation Formula is invalid Possible Cause The user entered a formula which
107. 77 C04F Database checksum error Source GroupWise engine database services Explanation Checksum error reading database Action Check and if necessary repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide If the error returns check for bad network cards on workstations from which the GroupWise client updates the databases Action If this error occurs on a message database msgnnn db or user database userxxx db run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide 68 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Possible Cause Action Action Possible Cause Action The guardian database ngwguard db is damaged 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 rf1 file See also Information Stored in the Post Office in Post Office Agent in the GroupWise 7 Administration Guide If this error occurs in the GroupWise client in Remote mode there might be a problem with the structure or c
108. 810 Unexpected error on page 147 E811 Unexpected error on page 147 E812 Unexpected error on page 147 e E813 Unexpected error on page 147 E814 Unexpected error on page 148 e E815 Unexpected error on page 148 E816 Insufficient rights to perform operation on page 148 E818 Unexpected error on page 148 E810 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E811 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E812 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E813 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 Exxx Engine Error Codes 147 E814 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E815 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E816 Insufficient rights to perform operation Source GroupWise engine object framework Explanation Security access denied Possible Cause User does not have rights to perform this operation on this object Action Have the document owner grant you rights Look up documents permission to access in GroupWise client Help
109. A 1x Errors on page 115 DBOx Errors on page 116 DB1x Errors on page 120 DB2x Errors on page 122 DB3x Errors on page 125 DB4x Errors on page 128 DB5x Errors on page 132 DB6x Errors on page 134 DExx Errors on page 135 DFxx Errors on page 136 Dxxx Unexpected Error on page 138 7 1 D00x Errors D001 Unexpected error on page 80 D002 Folder not empty on page 80 D004 Database error on page 80 D005 Settings field list is not valid on page 80 Dxxx Engine Error Codes 79 D006 Unexpected error on page 80 D009 Cannot use group name in distribution list on page 80 e DOOA Syntax error in address on page 81 DOOB Missing closing quotation mark on page 81 e DO0C Unexpected error on page 81 DOOD Cannot match parentheses on page 81 e DOOE Distribution list contains nested groups on page 81 e DOOF Remote mail error on page 82 D001 Unexpected error Source GroupWise engine Action See Dxxx Unexpected error on page 138 D002 Folder not empty Source GroupWise engine Explanation Folder not empty Action Delete all items in the folder before attempting to delete it D004 Database error Source GroupWise engine Explanation Database error Attempt to read or modify settings failed Possible Cause The user database userxxx db contains inconsistent information Action Ch
110. A cannot write message files across a mapped or UNC link into the MTA input queue in a closed domain domain wpcsin directory ora closed post office post office wpcsout directory because the directory is inaccessible or damaged Make sure the input queue directory exists and that the MTA has sufficient rights to create files there If necessary and if the input queue subdirectories are empty you can rename the original input queue directory and then manually recreate it along with its required subdirectories The server where the closed domain or post office is located does not have sufficient disk space for the MTA to create message files Free up disk space NetWare Note On a NetWare server you might need to purge deleted files to free up disk space The name of the domain directory contains more than 8 characters Rename the domain directory The MTA currently does not support long names Also update the domain directory path in ConsoleOne The network type specified for the domain is incorrect Check the network type selected for the domain In ConsoleOne right click the Domain object then click Properties Make sure the Network Type field is correct for the MTA running for the domain GWMTA Cannot find domain database Source Explanation Possible Cause Action Group Wise Message Transfer Agent The MTA cannot access a domain database wodomain db in the directory specified by the home switch T
111. Action Possible Cause Action Possible Cause Action Action Possible Cause Action Possible Cause Action 8205 End of file Source Explanation Possible Cause Action Possible Cause Disk full There is no space left on a disk when writing and or creating a file Create space on disk by deleting unwanted or unnecessary files One or more of the GroupWise databases might have an invalid owner or no owner For the locations of GroupWise databases in domains and post offices see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Check the ownership of the Group Wise databases If necessary change the ownership to a valid user such as the system administrator The owner of a GroupWise database has a space restriction on the volume where the database resides and that limit has been reached so that the database cannot grow any larger Check the ownership of these databases and make sure that owner does not have disk space restrictions If disk space is available and database ownership is correct the disk itself might need repair If this error occurs from the POA there might be a problem with its input queue Stop the POA Rename the wpcsout directory in the post office Restart the POA This re creates the wpcsout directory structure for the post office If the POA now runs witho
112. As on the same server the same TCP port might be in use by more than one MTA NetWare Note On a NetWare server you would see the message Waiting for busy listen socket to become available Check the setup of the MTAs Make sure each MTA is using a unique port See Configuring the MTA for TCP IP in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA Command line parameter home is required Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA cannot start without a home switch specifying the domain directory The home switch has not been provided in the command to start the MTA Add the home switch to the command to start the MTA See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide The agent was not able to access the startup file where the home switch was specified Make sure the startup file exists GWMTA Could not launch the editor Source Group Wise Message Transfer Agent for Windows Message Transfer Agent Error Messages 199 Explanation Possible Cause Action The MTA cannot run the program used to view agent log files or edit agent startup files The viewer program is not available on the current path or is incorrectly specified The default viewer used by the agents is Notepad which is typically available You can change the viewer specif
113. EA08 Display name is missing Source GroupWise engine SOAP protocol Explanation A display name is the human readable name of a GroupWise object It is required when creating such objects as a contact or a resource Possible Cause Your application tries to create a GroupWise item that should include a display name without providing the display name Action Make sure you provide the display name when creating the object For more information see displayName definition http developer novell com ndk doc gwsoap soap_enu data bs39q28 html bs39q28 createltem method http developer novell com ndk doc gwsoap soap_enu data brx8867 html brx8867 EA09 User structure still busy Source GroupWise engine SOAP protocol Explanation A user structure contains the data about a user session It cannot be accessed when it is busy Possible Cause Your application is trying to log out ofthe POA when a lengthy activity such as a Busy Search is in progress Action Program your application to wait when this error is encountered The problem typically resolves itself in a short period of time EAOA Item already accepted Source GroupWise engine SOAP protocol 152 GroupWise 7 Troubleshooting 1 Error Messages Explanation The GroupWise item being processed has already been accepted and cannot be accepted again Possible Cause Your application is trying to mark as Accepted a GroupWise item that has already been accepted by the S
114. EBACC Not able to bind to specified port Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent could not bind to the TCP IP port it uses to listen for messages from the GroupWise WebAccess CGI Extension Another program is using the port Resolve the port conflict by changing the port used by the other program or the port used by the WebAccess Agent To change the WebAccess Agent s port see in WebAccess in the GroupWise 7 Administration Guide WEBACC Not able to open configuration file Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent could not open the comint cfg file located in its gateway home directory domain wpgate webac70a where domain is the domain directory and webac 70a is the gateway home directory The WebAccess Agent reads configuration information from this file The file has been deleted or has a problem Use ConsoleOne to reenter the configuration information See Configuring the WebAccess Agent in WebAccess in the GroupWise 7 Administration Guide WEBACC Not enough memory to complete operation Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent could not perform the operation because of insufficient memory Insufficient memory Free up memory or add additional memory WEBACC Request aborted while waiting on locked conversation
115. EBACC Running the Added a new error message agent with conflicting effective users on page 230 Entire Guide Page design reformatted to comply with revised Novell documentation standards Documentation Updates 279
116. Environment Options Cleanup in Users in the GroupWise 7 Administration Guide See also GroupWise Time Stamp Utility in Databases in the GroupWise 7 Administration Guide D069 Attempt to open invalid backup location Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Action Group Wise engine The user attempted to open a backup location that did not contain a valid backup of a GroupWise post office or mailbox The user is unsure of the backup location Make sure users know where their backed up messages have been restored See Restoring Deleted Mailbox Items in Databases in the GroupWise 7 Administration Guide The backup location path includes a directory name that has more than eight characters Rename any long directory names to eight characters maximum then make matching changes to the restore area information in ConsoleOne See Setting Up a Restore Area in Databases in the GroupWise 7 Administration Guide The restore area is in a location where the POA does not have the necessary rights to access it If the restore area is on a different server from where the POA is running provide a username and password for the POA to use to access the remote location You can provide this information in ConsoleOne in the Remote File Server Settings box on the Post Office Settings page of the Post office object or in the POA startu
117. File I O error Source GroupWise WebAccess Agent Explanation The WebAccess Agent could not view a log file Possible Cause The WebAccess Agent does not have access to log file directory or does not have rights to the file Action Make sure the WebAccess Agent has access to the log file directory and that it has rights to view the file WEBACC GWINTER NLM cannot initialize screen Source GroupWise WebAccess Agent Explanation The WebAccess Agent cannot display its agent console Possible Cause Insufficient memory Action Free up memory or add additional memory WEBACC GWINTER NLM initialization error Invalid GWENN5 NLM loaded Source GroupWise WebAccess Agent Explanation GroupWise Agent Engine gwenn5 n1m that is currently loaded is the incorrect version for the WebAccess Agent Possible Cause Another GroupWise agent loaded an earlier version of gqwenn5 nlm Action Unload all GroupWise agents that are running on the server Start GroupWise WebAccess and restart the other GroupWise agents Make sure the other Group Wise agents are version 7 If necessary reinstall the GroupWise WebAccess software to install the correct version of gwenn5 n1m WEBACC Hash value changed Source GroupWise WebAccess Agent Explanation Possible security violation 224 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause A user bookmarked a GroupWise WebAccess location then attempted to access it directly from another server
118. Finder index is located so the QuickFinder process cannot write more information to disk Free up disk space You do not have rights to the location where the QuickFinder index is located Check your access rights In ConsoleOne you can set the proper user rights for all users in a post office or for an individual user See GroupWise User Rights in Security Administration in the GroupWise 7 Administration Guide FOxx Database error Source Explanation Action Action GroupWise engine QuickFinder Generic database error Check and if necessary repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide 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 FOxx Database error index Source Explanation Action GroupWise engine QuickFinder Generic database error Rebuild the index of the database where the error occurs See Rebuilding Database Indexes in Databases in the GroupWise 7 Administration Guide FOxx Memory error Source Explanation Action Action GroupWise engine QuickFinder Generic QuickFinder memory error Exit and restart the GroupWise client Free up more memory befo
119. GroupWise Check utility GWCheck Explanation GWCheck cannot read records from the specified user database userxxx db Action Perform a structural analyze fix on the user database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Action For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 09 Message database read error Source GroupWise Check utility GWCheck Explanation GWCheck cannot read records from the specified message database msgnnn db Action Perform a structural analyze fix on the message database by supplying the name of the message database in the User Resource field See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide Action Ifthe message database cannot be repaired manually restore it from backup Action For additional information look up the associated engine error code in Part I GroupWise Engine Error Codes on page 11 10 Message record read error Source GroupWise Check utility GWCheck Explanation GWCheck cannot read a specific record in a message database msgnnn db Action Perform a structural analyze fix on the message database by supplying the name of the message database in the User Resource field See Maintaining User Resource and Message Databases in Databases i
120. MOMISs er ee tah a teh et Ret KS ASUS MUR 7 26 DExx Errors 7 27 DFxx Errors 7 28 Dxxx Unexp ected ETTOR rl SDs Snes aon E ar a pate 8 Exxx Engine Error Codes 8 1 E50x Errors 8 2 51x Errors 8 3 E52x Errors 84 E7xx Errors 8 5 E80x Errors 8 6 E81x Errors 8 7 82x Errors 8 8 E84x Errors 89 EAOx Errors 8 10 EA1x Errors 8 11 Exo Unexpected Emot ann Ha a ete sen Beta 9 Fxxx Engine Error Codes 9 1 FOOx Errors GroupWise 7 Troubleshooting 1 Error Messages 139 139 141 143 145 145 147 148 149 149 154 157 159 9 2 ROX EROS ic kei aes ele E DE ee oad i A od oo de at ee wd ee 9 3 SEO2X ENOrS a tee Oe ok hee t ca Ee ot le oe Jo al rh 9 4 SFOSX ERMOIS wee ran et eo en tee ce dee ar oes 9 55 SFOAX Enrorsin Sets a os Eee 9 67 ROIX ERRORS A ett ns toad mia E M Sa M cae Peta tae ae he t aaa 9 70 EOOXEMTOLS a A otter alte Ae ok a t al a alad 9 8 FO7X ENOFS 2 ne Dr he t tu aaa 9 95 sFOSX EnrOrs 444 Mats aaa a ka Man 9 10 FOIX EMMONS sree Den M 9 41 CROAK EO E a ints bs bok aie a ht 9 12 WROBX EMONS 3 4 6 2 4 ae te ees eee eee a es aa 9 13 FOCX EMOS 27 20 er yh eer eee Ao eres che Be A Patent be gecko 9 14 FIOS EMOS eae ee pampa eels lacie near 9 15 FOX EMOPS an en re age se dots Bota eee ea a eee eee aoe Sos ee 9 16 F1xx Cannot Connect Error 20 0 eee Part II Agent Error Messages 10 Post Office Agent Error Messages 11 Message Transfer Agent Error Messages 12 Internet Ag
121. Message Transfer Agent The MTA cannot use the location specified by the log startup switch to store its log files The location specified by the log startup switch does not exist Check and if necessary change the location specified by the log startup switch when starting the MTA If the log switch is not specified it defaults to the mslocal directory in the directory specified by the work switch The location specified by the log startup switch is on a server that is currently not available Check the status of the server where the specified directory is located Wait for the server to come back up or contact the administrator of that server It is recommended that the log switch be set to a location local to where the MTA is running to avoid this problem GWMTA Invalid work parameter Source Explanation Possible Cause Action Possible Cause Action Action Group Wise Message Transfer Agent The MTA cannot use the location specified by the work startup switch for its mslocal directory The location specified by the work startup switch does not exist Check and if necessary change the location specified by the work startup switch when starting the MTA If the work switch is not specified it defaults to the domain directory See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide The location specified by the work startup switch is on
122. Novell GroupWise www novell com T TROUBLESHOOTING 1 June 15 2006 ERROR MESSAGES Novell Legal Notices Novell Inc makes no representations or warranties with respect to the contents or use of this documentation and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose Further Novell Inc reserves the right to revise this publication and to make changes to its content at any time without obligation to notify any person or entity of such revisions or changes Further Novell Inc makes no representations or warranties with respect to any software and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose Further Novell Inc reserves the right to make changes to any and all parts of Novell software at any time without any obligation to notify any person or entity of such changes Any products or technical information provided under this Agreement may be subject to U S export controls and the trade laws of other countries You agree to comply with all export control regulations and to obtain any required licenses or classification to export re export or import deliverables You agree not to export or re export to entities on the current U S export exclusion lists or to any embargoed or terrorist countries as specified in the U S export laws You agree to not use deliverables for prohibited nuclear
123. OAP client user Action Accepted items are marked as accepted Check the status of an item before trying to accept it For more information see accept method http developer novell com ndk doc gwsoap soap_enu data brwiukl html brwiukl EAOB Item not acceptable declinable Source GroupWise engine SOAP protocol Explanation The GroupWise item being processed is not eligible for being accepted or declined Possible Cause Your application is trying to accept a GroupWise item that cannot be accepted or declined because it is not the right type of item Action Check the following item status information before trying to accept an item e The item is a calendar item appointment note or task The item is a received item in the Mailbox folder The item is not archived The items is not in the Work in Progress folder The item is not in the Trash folder e Your application has sufficient access rights to the item For more information see accept method http developer novell com ndk doc gwsoap soap_enu data brwiukl html brwiukl e decline method http developer novell com ndk doc gwsoap soap_enu data brx8aih html brx8aih EAOC The method called is not supported Source GroupWise engine SOAP protocol Explanation The action that your application is trying to perform is no longer accepted by the GroupWise SOAP protocol used by the POA Possible Cause Your application contains a method that is out
124. P threads are not keeping up with the current workload Increase the number of TCP handler threads for the POA See Adjusting the Number of Connections for Client Server Processing in Post Office Agent in the GroupWise 7 Administration Guide GWPOA Error writing to file turning disk logging off Source Explanation Possible Cause Action Possible Cause Action Group Wise Post Office Agent Logging of information to disk has been turned off because the agent can no longer write to the current log file See Using POA Log Files in Post Office Agent in the GroupWise 7 Administration Guide If the log file is located on a server other than the one where the agent is running that server might be down Wait for the server to come back up or contact the administrator of that server When the server comes back up the agent will resume disk logging The log file has been damaged so the agent can no longer write to it Remove the damaged log file and turn disk logging back on in the Log Settings page for the agent in ConsoleOne The agent will create a new log file You can also use Cycle Log from the POA agent console to start a new log file GWPOA Failed to redirect user missing host configuration Source Explanation Action Group Wise Post Office Agent The Group Wise client is attempting to contact the POA in client server mode but the POA is not set up for client server communica
125. Possible Cause Possible Cause Action Group Wise engine SOAP protocol Your application looked for a GroupWise item in a particular container a folder or an address book in a GroupWise mailbox and did not find the item Your application calls a method that requires a container as an argument and the item is not in the specified container Your application passes a uid that does not have the container appended to the end Therefore the item cannot be found 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 ndk doc gwsoap soap_enu data brwiocm html brwiocm EA03 Handling of SOAP protocol is not enabled Source Explanation Possible Cause Action Group Wise engine SOAP protocol A SOAP client has attempted to contact the POA and the POA cannot respond successfully The POA is not yet configured for SOAP See Supporting SOAP Clients in Post Office Agent in the GroupWise 7 Administration Guide EA04 The response is too large Source Explanation Possible Cause Action Action GroupWise engine SOAP protocol The POA received a response from your application that is too large for it to process Your application responded to the POA with more than 1 MB of data Refine the SOAP request so that the response is smaller Use the soapsizelimit sta
126. See FOxx Database error index on page 177 F07C Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F07D Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 Fxxx Engine Error Codes 169 F07E Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F07F Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 9 9 F08x Errors F080 Database error on page 170 F082 Database error on page 170 F083 Database error on page 170 F084 Database error on page 170 F085 Database error on page 171 F086 Database error on page 171 F087 Database error on page 171 F088 Database error on page 171 F089 Database error on page 171 FO8A Database error on page 171 FOSB Database error on page 171 FOSD Database error on page 171 e FOSE Database error on page 171 FO8F Database error on page 171 F080 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F082 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F083 Database error Source GroupWise engine QuickFi
127. Undamaged message files can then be returned to their original subdirectories for processing C059 Database file already exists Source Explanation Possible Cause Action Possible Cause Group Wise engine database services GroupWise attempted to create a user file message file or library file but it could not create the file because the file already existed The ngwguard db file has been renamed or deleted When the POA detects the guardian database is missing it creates a new one The original guardian database contained a catalog of dependent databases user messages library and so on The new guardian database lacks this catalog so the POA attempts to create the needed dependent databases but it cannot because they already exist The POA does not overwrite existing files See also Information Stored in the Post Office in Post Office Agent in the GroupWise 7 Administration Guide 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 A user was moved to a different post office and then moved back to the original post office When the user is moved back to the original post office the POA attempts to create the user database If the user database was not 70 GroupWise 7 Troubleshooting 1 Error Messages Action deleted when the user was moved out the POA can
128. Wise Check utility GWCheck GWCheck cannot write a modified record back to the database The record is unavailable Another user has the record locked Retry There might have been a timing problem with another database user See if another program such as the POA has the database open with exclusive access and has hung with the database open The record is damaged Perform a structural analyze fix on the database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide If the database cannot be repaired manually restore it from backup See Restoring GroupWise Databases from Backup in Databases in the GroupWise 7 Administration Guide For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 14 Record delete failed commit Source Group Wise Check utility GWCheck GroupWise Check Error Codes 251 Explanation Possible Cause Action Action Possible Cause Action Action Action GWCheck cannot delete a record from the database The record is unavailable Retry There might have been a timing problem with another database user See if another program such as the POA has the database open with exclusive access and has hung with the database open The record is damaged Perform a structural analyze fix on the database See Maintaining User Resource and
129. a message that exceeded the user s message size limit as set by the administrator The user is not aware that there is a message size limit on his or her mailbox Notify the user of the message size limit so that the user can send messages of appropriate size The administrator has set a message size limit that is too restrictive Increase the message size limit Increase the maximum message size for the user See Send Options Disk Space Management in Users in the GroupWise 7 Administration Guide DO5F Box size limit exceeded Source Explanation Possible Cause Action Possible Cause Action Group Wise engine A user s GroupWise mailbox exceeds the size limit set by the administrator The user is not aware that there is a size limit on his or her mailbox Notify the user of the mailbox size limit so that the user can delete unneeded messages from the mailbox The administrator has set a mailbox size limit that is too restrictive Increase the message size limit Increase the maximum mailbox size for the user See Send Options Disk Space Management in Users in the GroupWise 7 Administration Guide 7 7 DO6x Errors D060 Message size exceeds threshold limit on page 94 D061 Status denied to external Internet user on page 94 D062 Busy Search denied for external Internet user on page 94 Dxxx Engine Error Codes 93 D065 Attempt to purge item that has not
130. abase dictionary dc file is missing from the post office Copy the missing dc file from the po subdirectory of the software distribution directory to the post office directory See Software Distribution Directory and Post Office Directory in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 44 Database invalid due to security breach Source Explanation Possible Cause Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot open the specified database because it contains an invalid verification record The database has been modified in some unauthorized way The database has been copied from another post office Restore the original database from backup 47 Error in library sync with host Source Explanation Possible Cause Action Possible Cause Action Group Wise Check utility GWCheck GWCheck synchronizes information in the library database dmsh db with information in the post office database wphost db The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide The post office database is damaged In ConsoleOne rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide 258 GroupWise 7 Troublesh
131. above object on page 183 GWPOA Cannot access remote post office retrying on page 183 GWPOA Cannot access remote post office user ID switch is missing on page 183 GWPOA Cannot find the help file on page 183 GWPOA Client server login failed no user ID supplied on page 183 GWPOA Configured address may not match actual address on page 184 GWPOA Database language has been updated please rebuild this database on page 184 GWPOA Disk is full turning disk logging off on page 184 GWPOA Error creating on page 184 GWPOA Error creating file turning disk logging off on page 185 GWPOA Error initializing communications protocol on page 185 GWPOA Error initializing HTTP on page 185 GWPOA Error listening for connection on page 185 GWPOA Error opening listener port on page 185 GWPOA Error putting item in queue on page 186 GWPOA Error writing to file turning disk logging off on page 186 GWPOA Failed to redirect user missing host configuration on page 186 GWPOA File I O error on page 186 GWPOA Host refused connection on page 187 GWPOA HTTP port nn is already in use on page 187 GWPOA Internal UDP port is unusable on page 187 GWPOA Listen port already in use on page 187 GWPOA Low disk space for OuickFinder indexing on page 187 GWPOA Machine appears to have TCP IP incorrectly config
132. age Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide D119 Unexpected error Source Action GroupWise engine database interface See Dxxx Unexpected error on page 138 D11B Too many items in mailbox Source Explanation Possible Cause Action Action Action Group Wise engine database interface Too many records There are more than 5 000 items in your mailbox Only the first 5 000 items are displayed When you delete messages additional items are displayed Have users clean out their mailboxes You might want to run a statistics check on the mailboxes Gathering Mailbox Statistics in Databases in the GroupWise 7 Administration Guide Users could move items to different folders Users could archive items See archive items in GroupWise client Help Dxxx Engine Error Codes 105 D11C Cannot use group name Source Explanation Possible Cause Action Possible Cause Action GroupWise engine database interface Groups cannot be listed as users here A group name was used where a user name was expected For example the startup option u group_name was used or a group name was used in a domain where there is no entry in the Address Book for this group Check your Address Book for correct addressing syntax If the
133. alid path specified The specified path exists however it is not a directory Enter a new path or remove the invalid path DB08 Non unigue name Source Explanation Possible Cause Action Group Wise engine administration engine Non unique name The specified name object po domain conflicts with an existing user resource group or nickname Specify a new unique name DBO9 User owns resource Source Explanation Possible Cause Action Action Possible Cause Action Action Group Wise engine administration engine User owns a resource The specified user cannot be deleted or moved because he or she owns a resource Remove the resource See Deleting a Resource in Resources in the GroupWise 7 Administration Guide Reassign the resource to another owner See Changing a Resource s Owner in Resources in the GroupWise 7 Administration Guide If this error occurs after removing resources from a user to be deleted or moved the change might not yet have replicated through the system Wait for replication to occur or manually synchronize the resource s and user See Synchronizing Database Information in Databases in the GroupWise 7 Administration Guide Rebuild the post office database wohost db See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide DBOA Record not found Source Explanat
134. all to accommodate communication between the Monitor Application and the Monitor Agent GWMON Unable to connect to the MTA at P address port Source GroupWise Monitor Agent Explanation The Monitor Agent cannot connect to the MTA at the IP address and port you specified when prompted Action Double check the IP address and port number of the MTA that you want the Monitor Agent to communicate with Action Make sure that the MTA is running with HTTP enabled See Using the MTA Web Console in Message Transfer Agent in the GroupWise 7 Administration Guide GWMON Unable to resolve GroupWise Monitor Agent s host name to a valid IP address Source GroupWise Monitor Application Possible Cause The Monitor Agent host name is not correct in the gwmonitor cfg file Action Check the gwmonitor cfg file to make sure it provides the correct IP address and port number for the Monitor Agent Correct the information as needed Monitor Agent and Application Error Messages 235 236 GroupWise 7 Troubleshooting 1 Error Messages Administration Error Messages The Group Wise Administrator snap in to ConsoleOne is used to create and manage Group Wise objects GroupWise Check is a standalone version of the Mailbox Library Maintenance feature found in ConsoleOne This part of Troubleshooting 1 Error Messages helps you resolve error messages that might occur when you are using the GroupWise Administrator snap in to ConsoleOne and
135. am again as described in Setting Up a Basic GroupWise System in the GroupWise 7 Installation Guide AD21 The attribute specified in the request does not exist in the LDAP server s schema Source Explanation Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object but the LDAP server is not configured for the necessary attribute 50 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Action The eDirectory schema has not yet been extended to accommodate GroupWise objects Extend the schema as described in Check eDirectory Schema in System in the GroupWise 7 Administration Guide Run the Installation program again as described in Setting Up a Basic GroupWise System in the GroupWise 7 Installation Guide AD25 The object DN passed in is invalid because the target object cannot be found Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object but the context you specified does not exist You typed the context incorrectly Browse to and select the context You typed the context correctly but the context does not exist In ConsoleOne create the container object you want to use then browse to an
136. ame error occurs exit and then restart the Group Wise program that displayed the error 8203 Cannot copy file or directory Source Explanation Possible Cause Action Possible Cause Action Action 8204 Disk full Source Group Wise engine file input output Copy error If this error occurs when trying to rebuild a post office database the domain or the post office might not contain the correct files For the required contents of domains and post offices see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Make sure the post office you are trying to rebuild and the domain it belongs to contain the correct files especially dc files If this error occurs in the GroupWise client in Remote mode there might be a problem with the structure or content of the Remote mailbox For example copying a GroupWise client installation from one laptop to another might introduce this problem Delete the rofdata directory on the remote computer then request all information from the master mailbox again Reinstall the GroupWise client on the remote computer See the platform specific setup instructions for using Remote mode in GroupWise Modes in Client in the GroupWise 7 Administration Guide Group Wise engine file input output 8xxx Engine Error Codes 19 Explanation Possible Cause
137. anation Action Group Wise Internet Agent The Internet Agent must find the TCP IP kernel already loaded or the Internet Agent automatically loads the TCP IP kernel If the TCP IP kernel is not or cannot be loaded automatically this error results Check to see that the TCP IP kernel is installed and configured GWIA Unable to listen on SMTP port Source Explanation Action Group Wise Internet Agent The TCP IP kernel is not installed correctly or the Internet Agent is unable to take control of port 25 SMTP port number Other processes might have control of port 25 thereby preventing the Internet Agent from taking control of port 25 Unload the TCP IP kernel then reload it If another process has control of port 25 unloading the TCP IP kernel shows it 220 GroupWise 7 Troubleshooting 1 Error Messages WebAccess Agent Error Messages WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC page 224 WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC WEBACC CMC encountered a problem accessing the GroupWise domain on page 222 CMC was not able to access this GroupWise gateway directory on page 222 CMC was not able to establis
138. are being stored at the post office make sure the docs subdirectory exists for the library If documents are being stored in a remote document storage area make sure that the POA can access the location of the document storage area In ConsoleOne browse to and right click the Library object then click Properties Click GroupWise gt Storage Areas Select a storage area then click Edit Check the location to make sure the required library directory structure exists The structure of a remote document storage area is the same as the gwdms directory in the post office If this error occurs when trying to access a document in a library the BLOB file containing the document might no longer exist You can determine what BLOB file the document was in from the GroupWise client Right click the document reference then click Properties gt Activity Log If filenames are not currently displayed right click the menu bar then click Filename to display the filename in the activity log If the document is needed you can restore the BLOB file from backup See Restoring Archived Documents in Libraries and Documents in the GroupWise 7 Administration Guide If the document is not needed you can delete it from the library to eliminate the error Have the original sender of the message resend the attachment Some applications such as Corel WordPerfect 7 MS Word 95 and Excel 95 need a blank file stored in the c windows shellnew di
139. art logging thread Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent uses a separate thread other than the regular worker threads for logging The WebAccess Agent could not open the logging thread Low memory resources Free up memory or add additional memory WEBACC Error accessing directory Source Explanation Possible Cause GroupWise WebAccess Agent The WebAccess Agent could not access the specified directory The WebAccess Agent lost its connection to the server where the directory resides or does not have sufficient rights to the directory WebAccess Agent Error Messages 223 Action Reestablish the connection to the server and make sure the WebAccess Agent has sufficient rights to the directory See WebAccess Security Requirements in Installing GroupWise WebAccess in the GroupWise 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 Possible Cause The WebAccess Agent does not have the rights needed to access the startup file or the startup file does not exist in the specified location Action Make sure the WebAccess Agent has rights to the startup file Action Make sure the startup file is in the same directory as the WebAccess Agent program or that filename includes the full path to the file WEBACC
140. ary domain you cannot delete it unless you delete all secondary domains first meaning that you want to delete your entire Group Wise system or you designate a different domain as the primary domain See Converting a Secondary Domain to a Primary Domain in Domains in the GroupWise 7 Administration Guide DB38 Cannot delete domain that has post offices Source Explanation Possible Cause Action Action Group Wise engine administration engine Post offices exist for this domain An attempt was made to delete a domain that has post offices assigned to it Move the post offices to another domain See Moving a Post Office in Post Offices in the GroupWise 7 Administration Guide Then delete the domain after it is empty See Deleting a Domain in Domains in the GroupWise 7 Administration Guide Delete the post offices See Deleting a Post Office in Post Offices in the GroupWise 7 Administration Guide Then delete the domain after it is empty See Deleting a Domain in Domains in the GroupWise 7 Administration Guide DB39 Domain database not found Source Explanation Possible Cause Action Possible Cause Action Group Wise engine administration engine Database is not available No domain database wodomain db was found however a recover ddb file was found The database is currently being rebuilt Allow the rebuild operation to finish A database rebu
141. ase See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide Cxxx Engine Error Codes 69 C055 Unexpected error Source Action Group Wise engine database services See COxx Unexpected error on page 78 C057 Database maintenance in progress please exit Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Group Wise engine database services Maintenance in progress error Database maintenance in progress one of the databases is being recovered or rebuilt Exit GroupWise and try again later Depending on the size of the database the maintenance could take from a few seconds to several minutes If the condition continues for an extended period and no GroupWise maintenance is being performed another program might already have the required file open with exclusive access Check the open lock activity on GroupWise databases and other files You might find that a backup program is holding the file open If this error occurs constantly from the POA a damaged message file might be blocking its processing Check the priority subdirectories of the wocsout ofs directory See Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Move message files out to a temporary location until the damaged message file is eliminated
142. ase Information in Databases in the GroupWise 7 Administration Guide If you do not want to wait for replication to complete you can rebuild the secondary domain database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide If this error occurs when synchronizing domains or post offices the databases might be damaged Rebuild the databases then synchronize the databases D507 Administrator record not found in database Source Explanation Possible Cause Action D508 Transaction Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Action Group Wise engine administration services No administrator record found in database An agent has attempted to send a message to the defined administrator however no administrator record was found in the database To receive these messages define an administrator for the domain See Notifying the Domain Administrator in Message Transfer Agent in the GroupWise 7 Administration Guide failed Group Wise engine administration services The transaction failed The database was locked by another process and could not be updated None The message will be retried automatically One or more of the GroupWise databases might have an invalid owner or no owner For the locations of GroupWise databases in domains and post offices see Doma
143. assistance recommended on page 77 C01F Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 6 3 C02x Errors e C020 Database error on page 61 e C021 Database error on page 61 e C022 Database damaged on page 61 60 GroupWise 7 Troubleshooting 1 Error Messages C023 Database error on page 62 C024 Database dictionary damaged on page 62 C026 Database error on page 63 C027 Database error on page 63 C028 Database error on page 63 C029 Database version unsupported on page 63 C02A Cannot access database dictionary file on page 63 C02B Database error on page 64 C02C Database error on page 64 C02D Database error on page 64 C02E Database error on page 64 C02F Database error on page 64 C020 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C021 Database error Source GroupWise engine database services Action See COxx Database error Support assistance recommended on page 77 C022 Database damaged Source GroupWise engine database services Explanation The integrity of an item or structure in the database has been compromised Action Check and if necessary repair the database See Maintaining Domain and Post Office Databases
144. assword Domain Post Office e Connection Definition To check the first five items for a user in ConsoleOne double click the User object then click GroupWise Account The user s full name user ID domain and post office are displayed The user s Group Wise password can be reset if it has been forgotten To check the connection definition in ConsoleOne double click the Domain object where the gateway is located then double click the Gateway object Verify the information displayed on the GroupWise client Profiles page The master GroupWise system is unable to process a request Source GroupWise Windows client Remote mode 274 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Transmission errors damaged a response file from the master GroupWise system Action Send another request to the master GroupWise system to receive a new response file The master GroupWise system is unable to process your current Source GroupWise Windows client Remote mode Possible Cause Your master GroupWise system encountered an error while processing your requests Your master system might have a problem Action Send another request to the master GroupWise system Action Record the conditions under which you encountered the error For technical services see Novell Support http support novell com This item uses a custom view that was not retrieved Source GroupWise Windows client Remote mode Possibl
145. atabase error Support assistance recommended on page 77 C03C Database error Source GroupWise engine database services Action See C0xx Database error general database repair strategies on page 77 C03D Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 Cxxx Engine Error Codes 65 C03F Database error Source Explanation Action Action Action Action Action Possible Cause Action Action Group Wise engine database services GroupWise tried to open a file that could not be recognized as a valid Group Wise database Check and if necessary repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide 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 It can sometimes be helpful to run GWCheck multiple times because as some errors are fixed others are uncovered If the damaged database cannot be repaired successfully restore it from backup If a damaged user database cannot be repaired or restored it can be rebuilt First archive all personal appointments tasks and notes Make a backup copy of the user database Then re creat
146. ation The MTA cannot find the domain record in the domain database wpdomain db Possible Cause The domain database is damaged Action Rebuild the domain database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA No path configured Source GroupWise Message Transfer Agent Explanation Path information for links between domains is missing Possible Cause Links between domains are not set up correctly Action Check the links between domain See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide 208 GroupWise 7 Troubleshooting 1 Error Messages GWMTA No post offices found Source Explanation Action Group Wise Message Transfer Agent eDirectory user synchronization 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 Remove the domain from the list of domains for which eDirectory user synchronization should be performed See Using eDirectory User Synchronization in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA No response from peer Source Explanation Possible Cause Action Group Wise Message Transfer Agent message transfer protocol The MTA is attempting to communicate with another MTA or a POA by way of TCP IP but the other agent does not answer
147. ation later If you still cannot access the database check file activity using your network administration utilities Rebuild the database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide DB03 Operation pending cannot modify Source Explanation Possible Cause Action Group Wise engine administration engine Unsafe record modification This record has a pending operation and cannot be modified A remote operation has been requested for this record Wait for the MTA or POA to complete the pending operation or undo the operation See Pending Operations in System in the GroupWise 7 Administration Guide DB04 Owner not valid user Source Explanation Possible Cause Action Group Wise engine administration engine Invalid owner The owner you specified is not a valid user in the same post office as the resource Select an owner for the resource from among the users in the same post office as the resource See Changing a Resource s Owner in Resources in the GroupWise 7 Administration Guide Dxxx Engine Error Codes 117 Action DB05 Invalid path Source Explanation Possible Cause Action Create a new user in the post office to function as the owner of the resource See Creating GroupWise Accounts in Users in the GroupWise 7 Administration Guide Group Wise engine administration engine Inv
148. base error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F098 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F099 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 FO9A Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F09B Memory error Source GroupWise engine QuickFinder Action See FOxx Memory error on page 177 9 11 FOAx Errors e FOAI Memory error on page 173 FOA1 Memory error Source GroupWise engine QuickFinder Action See F0xx Memory error on page 177 9 12 FOBx Errors FOB2 Memory error on page 174 FOBS File I O error on page 174 FOB9 Unexpected error on page 174 FOBA Database error on page 174 FOBB Database error on page 174 FOBC Database error on page 174 FOBD Database error on page 174 Fxxx Engine Error Codes 173 FOBE Database error on page 174 FOBF Database error on page 174 F0B2 Memory error Source Group Wise engine OuickFinder Action See F0xx Memory error on page 177 F0B5 File I O error Source GroupWise engine OuickFinder Action See FOxx File I O error on page 176 F0B9 Unexpected error Source GroupWise engine OuickFinder Action
149. bases in the GroupWise 7 Administration Guide Start the POA without the norecover startup switch so that the POA can automatically recover any databases where damage is detected D044 Auto rebuild disabled Source Explanation Possible Cause Action Action Group Wise engine Automatic recovery of damaged databases by the POA has been turned off The POA has been started with the norecover startup switch and damage has been detected in a database Repair the database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Start the POA without the norecover startup switch so that the POA can automatically recover any databases where damage is detected D049 Error reported from Novell NDS Source Explanation Possible Cause Action Group Wise engine The GroupWise Administrator snap in to ConsoleOne was unable to retrieve information from Novell eDirectory You might be running ConsoleOne with insufficient Browse Read or Compare rights to the required eDirectory object Check the rights to the GroupWise user post office and agent objects in eDirectory D04A Unexpected error Source Action Group Wise engine See Dxxx Unexpected error on page 138 D04B Unexpected error Source Action Group Wise engine See Dxxx Unexpected error on page 138 D04F Unexpected error Source Action
150. been backed up on page 94 D066 Attempt to purge an item from a user that has not been backed up on page 95 D069 Attempt to open invalid backup location on page 95 D06B LDAP failure detected on page 95 e DO6E Lockout of older GroupWise clients being enforced on page 96 DO6F This GroupWise client doesn t match the user s license on page 96 D060 Message size exceeds threshold limit Source Explanation Possible Cause Action Possible Cause Action Group Wise engine A user s GroupWise mailbox is close to exceeding the size limit set by the administrator The user is not aware that there is a size limit on his or her mailbox Notify the user of the mailbox size limit so that the user can delete unneeded messages from the mailbox The administrator has set a mailbox size limit that is too restrictive Increase the message size limit Increase the maximum mailbox size for the user See Send Options Disk Space Management in Users in the GroupWise 7 Administration Guide D061 Status denied to external Internet user Source Explanation Action Group Wise engine The local GroupWise system is configured so that users outside the local Group Wise system cannot receive status information about messages To permit access to status information by external users enable Allow External Status Tracking See System Preferences in System in the
151. been used 254 GroupWise 7 Troubleshooting 1 Error Messages Action 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 For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 28 User file already exists or current file inaccessible Source Explanation Possible Cause Action Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot create a backup copy of the existing database Insufficient disk space Free up disk space by deleting unneeded files Insufficient rights Make sure you have write access to the directory where the database being repaired is located 29 User database close error Source Explanation Possible Cause Action Action Group Wise Check utility GWCheck GWCheck cannot close the specified user database user xxx db Insufficient rights Make sure you have write access to the directory where the repaired database will be written For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 30 User database not found Source Explanation Possible Cause Action Possible Cause Action Action Action Group Wise Check utility GWCheck GWCheck cannot lo
152. ble LDAP password changes in ConsoleOne See Providing LDAP Authentication for GroupWise Users in Post Office Agent in the GroupWise 7 Administration Guide Show the user what application he or she needs to use to change the LDAP password D073 Attempting to log in trusted without SSL Source Explanation Possible Cause Action Group Wise engine A trusted application tried to log in to the POA and was not successful because an SSL connection could not be established The POA is not configured to support SSL connections Enable SSL for the POA that the trusted application needs to log in to See Enhancing Post Office Security with SSL Connections to the POA in Post Office Agent in the GroupWise 7 Administration Guide D074 Invalid key for trusted application Source Explanation Possible Cause Action Group Wise engine A trusted application tried to log in to the POA and was not successful because the key was invalid The private key offered by the application did the match the private key the POA was configured to accept Verify the private key that the POA is configured to accept See Enhancing Post Office Security with SSL Connections to the POA in Post Office Agent in the GroupWise 7 Administration Guide D075 Invalid IP address for trusted application Source Explanation Possible Cause Action Possible Cause Action Group Wise engine A
153. cate the specified user database user xxx db to check You specified the user incorrectly Make sure you typed the user name correctly in the User Resource field in GWCheck The user database is missing from the post office Re create the user database See Re creating a User Database in Databases in the GroupWise 7 Administration Guide Restore the user database from backup If the user name is typed correctly make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides 31 Exclusive access denied to user database Source Group Wise Check utility GWCheck GroupWise Check Error Codes 255 Explanation Possible Cause Action Action Action GWCheck cannot get sufficient access to the specified user database userxxx db Insufficient rights Make sure you have write access to the user database Retry There might have been a timing problem with another database user See if another program such as the POA has the database open with exclusive access and has hung with the database open 32 User database open error Source Explanation Action Action Action Group Wise Check utility GWCheck GWCheck cannot open the specified user database user xxx db Retry There might have been a timing problem with another database user See if another program such as the POA has the database open with exclusive
154. cation Wait for eDirectory replication to complete The user s Client Options settings have been damaged Reset the user s Client Options setting back to the default See Resetting Client Options to Default Settings in Client in the GroupWise 7 Administration Guide D10A Unexpected error Source Action GroupWise engine database interface See Dxxx Unexpected error on page 138 D10B Database needs to be repaired Source Group Wise engine database interface 102 GroupWise 7 Troubleshooting 1 Error Messages Explanation Possible Cause Action Action Possible Cause Possible Cause Database invalid or damaged A record is no longer valid Validate the database then take the appropriate actions to either recover or rebuild the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide If this error occurs when running the GroupWise client under Windows for Workgroups the user login name might be incorrect Check the user login name on the station where the error occurs In Windows for Workgroups click Main gt Control Panel gt Network gt Login Name The login name must match the user s GroupWise ID D10C Unexpected error So
155. ccess 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 in Post Offices in the GroupWise 7 Administration Guide WEBACC The system is busy please try again later Source GroupWise WebAccess Agent Explanation A user tried to log in to GroupWise WebAccess but the WebAccess Agent could not handle another user Possible Cause All worker threads are currently being used Action Ifthe problem persists increase the number of threads See Modifying WebAccess Settings in WebAccess in the GroupWise 7 Administration Guide WEBACC Unable to establish a connection to the default log path Source GroupWise WebAccess Agent Explanation The WebAccess Agent could not access the specified log file directory Possible Cause The WebAccess Agent does not have rights to the directory or does not have access to the file server Action Make sure the WebAccess Agent s user account provides the correct access and rights or specify a different log file directory using the log switch See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC Unable to establish a connection to the log path Source GroupWise WebAccess Agent Explanation The WebAccess Agent cannot access the log file directory Possible Cause The WebAccess Agent
156. ccess the database wpdomain db orwphost db at the location An MTA is already running against the domain database Do not try to run more than one MTA for a domain GWMTA Admin database for domain cannot be recovered Source Explanation Possible Cause Action GroupWise Message Transfer Agent admin thread An attempt to recover the domain database wodomain db has failed The domain database requires repair beyond what can be done while in use Rebuild the domain database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA Administrator record not found in database Source Explanation Possible Cause Action Action GroupWise Message Transfer Agent admin thread The MTA admin thread can send a message to an administrator in case of database errors However no administrator has been designated No GroupWise administrator has been set up yet Set up a GroupWise administrator to receive messages about database errors See Notifying the Domain Administrator in Message Transfer Agent in the GroupWise 7 Administration Guide Use the noerrormail switch when starting the MTA to turn off administrator messages GWMTA Authentication failure for the above object Source Explanation GroupWise Message Transfer Agent admin thread The MTA admin thread attempted to process a record that has the wrong authentication ke
157. ce Free up disk space by deleting unneeded files Insufficient rights Make sure you have write access to the directory where the database being repaired is located 24 Path modify error Source Explanation Action Action Group Wise Check utility GWCheck GWCheck cannot create a needed directory path Check rights and available disk space For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 25 Database create error Source Explanation Possible Cause Action Possible Cause Action Action Group Wise Check utility GWCheck GWCheck cannot create a new user database userxxx db Insufficient disk space Free up disk space by deleting unneeded files Insufficient rights Make sure you have write access to the directory where the database being repaired is located For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 26 Database rebuild error Source Explanation Possible Cause Action Possible Cause Action Possible Cause Group Wise Check utility GWCheck GWCheck cannot rebuild the database Insufficient disk space Free up disk space by deleting unneeded files Insufficient rights Make sure you have write access to the directory where the database being repaired is located All valid backup database filenames have already
158. ce Agent Not enough memory is available for the POA to function properly If the POA cannot start you might be trying to run the agent in an environment where too few system resources are available For information about POA memory requirements see GroupWise System Requirements in Installing GroupWise Agents in the GroupWise 7 Installation Guide Stop some other programs on the server to free up memory for use by the POA Add memory to the server to accommodate the POA along with other existing programs Select a different server to run the POA on where adequate resources are available If the POA starts successfully then encounters a memory error later during otherwise normal processing some other program on the server or another agent thread might have temporarily used a large quantity of memory Wait to see if the memory problem resolves itself The POA will retry its operations and should succeed at a later time when the other program has released some memory You can reduce the number of POA threads which reduces the memory requirements for the POA You can make the change in ConsoleOne by reducing the Message Handler Threads and or TCP Handler Threads settings in the POA Agent Settings page See Adjusting the Number of POA Threads for Message File Processing and Adjusting the Number of Connections for Client Server Processing in Post Office Agent in the GroupWise 7 Administration Guide Err
159. ce of any document storage areas for libraries associated with the post office To list the available libraries see Editing Post Office Properties in Post Offices in the GroupWise 7 Administration Guide To check the path to a document storage area see Managing Document Storage Areas in Libraries and Documents in the GroupWise 7 Administration Guide Correct any incorrect path then try to start the POA D712 Post office currently disabled Source Explanation Possible Cause Action GroupWise engine directory services access Post office is disabled The system administrator has disabled the post office This is not an error It is a notification by the program of the return value To enable the post office deselect Disable Logins in the post office Identification Dxxx Engine Error Codes 111 Possible Cause Action Action page in ConsoleOne See Disabling a Post Office in Post Offices in the GroupWise 7 Administration Guide If this error occurs when the Disable Logins option is not selected the flag might be set improperly on the post office database After making sure the Disable Logins option is not selected stop and restart the POA See Starting the POA in Post Office Agent in the GroupWise 7 Administration Guide Rebuild the post office database wohost db See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administrat
160. ctural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 65 Unable to add default system document types Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot add default document types to the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 66 Unable to correct document display name Source Explanation Possible Cause Group Wise Check utility GWCheck GWCheck cannot modify the specified document display name in the library database dmsh db in the post office The library database is damaged 260 GroupWise 7 Troubleshooting 1 Error Messages 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 Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot correct the specified element because version information was missing in the library database dmsh db in the post office The library database is damaged Perform a struc
161. d select it in the Installation program You typed an alias rather than a valid distinguished name Check for the correct distinguished name in ConsoleOne AD29 The security TLS versus plain surrounding this request is not valid for the request Source Explanation Possible Cause Action Possible Cause Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object but it does not have the necessary rights in eDirectory The LDAP server is not configured to accept clear text passwords In ConsoleOne configure the LDAP Server object to accept clear text passwords The LDAP server is not properly configured for SSL Configure the LDAP server for SSL and make sure that the correct root certificate is used AD2D The LDAP server is busy unavailable has timed out or is down Source Explanation Action Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program made initial contact with the LDAP server but the LDAP server is no longer responding Therefore the Installation program cannot create an Agent object Resolve the problem with the LDAP server Restart the LDAP server Axxx Engine Error Codes 51 AD2E A dynamic memory allocation function failed when calling an LDAP function Source Explanation Possible Cause Action Internet Agent
162. d a database Possible Cause An administrative message requesting a rebuild in the POA input queue is damaged 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 mailbox library maintenance Explanation The POA cannot create one or more directories required for processing messages Possible Cause The POA has insufficient rights to create the directory Action Make sure the POA has the necessary network rights to access the directories in the post office See Creating a NetWare Account for Agent Access Optional in Installing GroupWise Agents in the GroupWise 7 Installation Guide Action Start the POA including the rights switch to determine the specific problem the POA is encountering See Using POA Startup Switches in Post Office Agent the GroupWise 7 Administration Guide DF1C Document storage area definitions are not identical Source GroupWise engine mailbox library maintenance Explanation The location of the document storage area as stored in the post office database wehost db does not match the guardian database ngwguard db The error message includes the conflicting locations Action Mod
163. de C06C Database error Source GroupWise engine database services Explanation Driver not found Possible Cause The platform specific definition needed by the database to identify the location of the database files is either missing or invalid Cxxx Engine Error Codes 73 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 CO6D Database error Source Explanation Possible Cause Action Group Wise engine database services Bad driver path The platform specific definition needed by the database to identify the location of the database files is either missing or invalid 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 C06E Unexpected error Source Action Group Wise engine database services See C0xx Unexpected error on page 78 C06F Store number mismatch Source Explanation Possible Cause Action Action Possible Cause Action Group Wise engine database services The store number in a database does not match the store number recorded in the store catalog The database is damaged Check and if necessary repair the database See Maintaining User Reso
164. did not follow the correct syntax for Auto Dates Action Enter the correct formula by checking the syntax in your Auto Date formula or using the Dates tab to specify the dates you want to include Look up auto dates in Group Wise client Help A803 Auto Date formula not specified Source GroupWise engine Auto Date Explanation Formula is empty Possible Cause An attempt might have been made to switch from the Auto Date formula mode to graphical mode however no formula was entered Action Enter a formula in the formula window or exit and reenter the send window This generates a default formula which does not give the above error Look up auto dates in Group Wise client Help A804 Auto Date formula generates too many occurrences Source GroupWise engine Auto Date Explanation Auto Date occurrences truncated 46 GroupWise 7 Troubleshooting 1 Error Messages 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 The user can then regenerate additional occurrences for the same Auto Date for another subrange of his or her original range Look up auto dates in GroupWise client Help 4 5 AAxx Errors e AAOI Unexpected error on page 47 e AA02 Unexpected error on page
165. directory Action Check to see if the disk is full and check access to the directory GWIA Deferred file filename has been moved to the PROBLEM directory Source GroupWise Internet Agent Explanation After the Internet Agent retry schedule expired the message was moved to the problem directory The destination host was temporarily down it sent back a 400 level SMTP reply code so the program could not transfer the message Action Contact the postmaster for the destination host to make sure the host is up Have the user resend the message GWIA File close error on file filename in module xxxx Source GroupWise Internet Agent Explanation A close of the named file resulted in an error Action Check if some other process on the server is holding the file open Check for network problems GWIA File creation error on file filename in module xxxx Source GroupWise Internet Agent Explanation An open of the named file resulted in an error Action Check access in the named directory Internet Agent Error Messages 217 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 Explanation A read of the named file resulted in an error Action Check access to the
166. dministrator group name or other object Make sure the specified object ID is correct DB1D Cannot delete post office Source Explanation Possible Cause Action Group Wise engine administration engine Error deleting post office You do not have sufficient rights to perform the operation Make sure you have rights to delete files and directories by checking rights for file and directory removal Dxxx Engine Error Codes 121 Possible Cause The post office directory or files in that directory are in use by another user Action Check the open lock activity on files DB1F Cannot delete current domain Source GroupWise engine administration engine Explanation Error deleting current domain Possible Cause The attempt to delete the current domain failed Action Connect to the primary domain See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide Then delete the secondary domain from the primary domain See Deleting a Domain in Domains in the GroupWise 7 Administration Guide Action Ifthe current domain is the primary domain you cannot delete it unless you delete all secondary domains first meaning that you want to delete your entire Group Wise system or you designate a different domain as the primary domain See Converting a Secondary Domain to a Primary Domain in Domains in the GroupWise 7 Administration Guide 7 21 DB2x Errors DB20 Unexpected erro
167. e An eDirectory distinguished name DN was not specified where one is required Your system is configured in a way that requires the name switch to be specified when starting the POA This post office has been configured to run more than one POA process for it The DN is used by the POA to identify the configuration information and options that it should use when running The name switch should be used in conjunction with one of the DNs specified in the error message DA17 user and password switches required for this configuration Source Explanation Possible Cause Action Action Possible Cause Action GroupWise engine Post Office Agent The user and password switches are required when the POA must log into a remote server The POA needs to log in to a remote server where a document storage area is located but it does not have the necessary user and password information to log in with See Using POA Startup Switches and Installing and Starting the POA in Post Office Agent in the GroupWise 7 Administration Guide In ConsoleOne specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object You have renamed the server where a document storage area is located The POA can no longer access the original document storage area location so the POA cannot start First provide the new location of the document storage area
168. e See Rebuilding Database Indexes in Databases in the GroupWise 7 Administration Guide If rebuilding the index is not sufficient to resolve the problem validate the database then take the appropriate actions to either recover or rebuild the database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide 92 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Action The IP address of the POA has changed but GroupWise client users are still trying to start the client using old ipa and ipp client startup switch settings Update the information in users ipa and ipp switch settings with the current IP address information Remove the ipa and ipp switches and let the client and or the POA resolve the address See Simplifying Client Server Access with a GroupWise Name Server in Post Office Agent in the GroupWise 7 Administration Guide DO5D Post office intruder lockout is enforced Source Explanation Action Group Wise engine The POA has detected a possible intruder The user has been locked out You have several options for handling the situation See Enabling Intruder Detection in Post Office Agent in the GroupWise 7 Administration Guide DO5E Message size exceeds limit Source Explanation Possible Cause Action Possible Cause Action Group Wise engine A user tried to send
169. e ownership and rights of the directories involved with message flow domain post office and MTA local directory 8212 Password incorrect Source Explanation Possible Cause Action Group Wise engine file input output Invalid file password The password entered by the user does not match the one stored in the encrypted file Reenter the password 8214 Unsupported encryption level Source Explanation Possible Cause Action Action Group Wise engine file input output Unsupported encryption level in file Attempted to decrypt a file using an encryption level that is no longer supported The file you are trying to open was created in a newer version of Group Wise and cannot be opened in an older version Update to the latest version of Group Wise To check the date of the GroupWise client you are using click Help gt About GroupWise For technical services and file updates see Novell Support http support novell com Make sure the archive directory is not locked to an unusable location In ConsoleOne browse to and select the post office the user belongs to then click Tools gt GroupWise Utilities gt Client Options gt Environment gt File Location Check the setting in the Archive Directory field and check whether or not it is locked 8215 Path root error Source Explanation GroupWise engine file input output At path root 26 GroupWise 7 Troubleshooting 1 Error Messages
170. e 143 E524 Document not available for synchronization to server on page 143 e E525 Cannot delete lookup table it is not empty on page 144 e E526 Cannot delete lookup table it is in use on page 144 e E527 Cannot create library record already exists on page 144 e E528 Cannot transfer data to server on page 144 E529 All document blob areas full on page 144 e E52A Document not available on page 145 E520 Unexpected error Source GroupWise engine document management Action See Exxx Unexpected error on page 157 E522 Library not empty Source GroupWise engine document management Explanation Library not empty Possible Cause GroupWise cannot perform the requested operation until the library is empty Action Delete all documents from the library Look up documents deleting in Group Wise client Help E523 Document not modified Source GroupWise engine document management Explanation Document not modified Possible Cause The document has not been modified and does not need to be sent to the server Action Make changes to the document then save the document E524 Document not available for synchronization to server Source GroupWise engine document management Explanation Document not available for synchronization Possible Cause The document is currently in use Exxx Engine Error Codes 143 Action Possible Cause Action Close the document The document
171. e 19 8203 Cannot copy file or directory on page 19 8204 Disk full on page 19 8205 End of file on page 20 e 8206 Cannot open file on page 21 e 8207 Cannot locate file on page 21 e 8208 Cannot modify file on page 22 8209 Path not found on page 22 820B Path too long on page 24 e 820E Cannot lock file on page 24 8210 Cannot create path on page 25 e 8211 Cannot rename file on page 26 8212 Password incorrect on page 26 16 GroupWise 7 Troubleshooting 1 Error Messages 8200 File I O error Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action 8214 Unsupported encryption level on page 26 8215 Path root error on page 26 8219 Cannot connect to remote network resource on page 27 821A Access to a critical file denied on page 27 Group Wise engine file input output Generic file I O error Any file I O error that cannot be mapped to a more specific file I O error message A GroupWise database has been damaged so it is unrecognizable as a GroupWise database for example having a size of 0 KB or 2 GB For the locations of GroupWise databases in domains and post offices see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Restore the damaged database
172. e 217 GWIA Deferred delivery file I O error encryption error on page 217 GWIA Deferred delivery file I O error memory error on page 217 GWIA Deferred delivery file I O error message undeliverable on page 217 GWIA Deferred file filename has been moved to the PROBLEM directory on page 217 GWIA File close error on file filename in module xxxx on page 217 GWIA File creation error on file filename in module xxxx on page 217 GWIA File open error on file filename in module xxxx on page 218 GWIA File read error on file filename in module xxxx on page 218 GWIA File write error on file filename in module xxxx on page 218 GWIA Gateway that uses this directory is not yet defined on page 218 GWIA Gateway Configuration Database could not be found on page 218 GWIA Memory exhausted on page 218 GWIA Memory exhausted while processing an Administrator Command on page 218 GWIA Message File open failed on page 219 GWIA Message re gueuing failed The message must be deleted on page 219 GWIA Message transport session open error xxxx on page 219 GWIA Processing inbound message on page 219 GWIA Processing outbound command on page 219 GWIA Processing outbound message on page 219 Internet Agent Error Messages 215 GWIA Running the agent with conflicting effective users on page 219 GWIA Scratch pad file c
173. e 7 Administration Guide DB19 Local post office not found Source Explanation Possible Cause Action Group Wise engine administration engine No local post office record found Group Wise was unable to find a local post office The post office database wphost db might have been damaged Validate the post office database and rebuild if necessary See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide DB1A Insufficient administrative rights to perform operation Source Explanation Possible Cause Action Group Wise engine administration engine No administrative rights to perform action The current domain has no administrative rights to perform the specified action for the selected record Connect to the GroupWise system that owns this record See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide DB1B Message Transfer Agent not installed Source Explanation Possible Cause Action Group Wise engine administration engine The MTA is not installed The MTA is not installed or the MTA record is missing from the database Set up the MTA See Installing GroupWise Agents in the GroupWise 7 Installation Guide DB1C Invalid object name Source Explanation Possible Cause Action Group Wise engine administration engine Invalid object An invalid object name was specified for an a
174. e Cause Action Possible Cause Action You provided a non unique entry in a field that requires a unique entry Provide a new unique value in the field The database is damaged Check and if necessary repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide D70F Unexpected error Source Action Group Wise engine directory services access See Dxxx Unexpected error on page 138 7 15 D71x Errors e D710 Incompatible platform on page 111 D712 Post office currently disabled on page 111 e D713 Database dictionary not found on page 112 e D714 User database temporarily disabled on page 112 D715 User has failed in too many login attempts login disabled on page 112 D716 The System Address Book needs to be refreshed on page 113 D710 Incompatible platform Source Explanation Possible Cause Action Possible Cause Action Group Wise engine directory services access Requested platform path not found In a multiple platform environment a path was requested for a given platform but none was found This is not an error It is a notification by the program of the return value If this error occurs when the POA is trying to start a path to a document storage area might be incorrect Check the location and existen
175. e Cause The view file of an item you want to read is too large to download as specified in the Retrieve Options dialog box Action In your Remote mailbox right click the item then click Retrieve Selected Items Or click Remote gt Send Retrieve gt Advanced then click Size Limits to increase the maximum size for attachments This transmission cannot be completed due to network problems Source GroupWise Windows client Remote mode Possible Cause This is caused by general failures in the network connection Action Make sure your network software is operating correctly You might also need to exit and restart Windows Action Record the conditions under which you encountered the error For technical services see Novell Technical Support http support novell com Unable to create folder Source GroupWise Windows client Remote mode Possible Cause The folder specified in the Hit the Road Wizard or with the ps startup switch cannot be created Either you don t have rights to the specified folder or the path includes more than one folder that does not exist Action Modify the command line in Windows and include a valid path and folder in Hit the Road or with the ps startup switch filename ext could not be opened as a modem script file Source GroupWise Windows client Remote mode Possible Cause The file you specified to open is not in a script file format Action Ifyou want your script file to have the specified file
176. e GroupWise user 1D you specified using the u switch is not a valid Group Wise user Double check the GroupWise user ID and provide a valid one GWTMSTNP User login error Source Explanation Group Wise Time Stamp utility The Time Stamp utility cannot log in to the specified post office as the specified user GroupWise Time Stamp Utility Error Messages 265 Possible Cause Action Possible Cause Action The user ID provided with the u switch does not exist in the post office specified with the ph switch Correct either the user information or the post office information that you have provided The user database is damaged Run GroupWise Check GWCheck to repair the user database See Group Wise Check in Databases in the GroupWise 7 Administration Guide 266 GroupWise 7 Troubleshooting 1 Error Messages Client Error Messages This part of Troubleshooting 1 Error Messages helps you resolve GroupWise Windows client Remote client and Cross Platform client error messages e Chapter 18 Windows Client Error Messages on page 269 Chapter 19 Remote Mode Windows Client Error Messages on page 271 e Chapter 20 Cross Platform Client Error Messages on page 277 Other sources of assistance include Novell Support http support novell com Novell Support Knowledgebase http support novell com search kb index jsp Group Wise 7 Support Forums http support novel
177. e MTA cannot access the post office database wphost db The post office database has been damaged Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA Post office now closed Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA has lost its connection to a post office with which is could previously communicate The server where the post office is located is currently down Wait for the server to come back up or contact the administrator of that server If using TCP IP communication between post offices TCP IP might be down Make sure TCP IP is running on the servers where the post offices are located GWMTA Post office open failed Source Explanation Possible Cause Group Wise Message Transfer Agent The MTA cannot contact the POA in one of the local post offices The MTA cannot access the POA input queue in the post office 210 GroupWise 7 Troubleshooting 1 Error Messages 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 Explanation Possible Cause Action Group Wise Message Transfer Agent The MTA received an administrative message from GroupWi
178. e Message Transfer Agent The MTA is in the process of clearing out a backlog of messages and is not accepting any additional messages into its queues The MTA processes existing messages first before processing new messages so that messages arrive in the order in which they were sent The backlog of messages might have been caused by one or more closed facilities in the domain Message Transfer Agent Error Messages 211 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 mslocal directory 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 Possible Cause The Windows MTA cannot communicate with the Windows service control manager SCM Action Reboot the Windows server GWMTA The Windows agent service fails to initialize memory system service stopped Source GroupWise Message Transfer Agent for Windows Explanation The Windows MTA cannot start as a Windows service Possible Cause The Windows server has insufficient memory resources available Action Reboot the Windows server Run fewer programs on the Windows server GWMTA Timed out waiting for end of file confirmation Source GroupWise Message Transfer Agent Explanation The MTA is in the process of clearing out a back
179. e domain database See Rebuilding Domain or Post Office Databases in Databases in the Group Wise 7 Administration Guide GWMTA Cannot read post office database insufficient memory Source Group Wise Message Transfer Agent Explanation The MTA cannot access the post office database wphost db Possible Cause Insufficient memory 198 GroupWise 7 Troubleshooting 1 Error Messages Action Possible Cause Action See GWMTA Insufficient memory on page 205 The post office database has been damaged 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 Action Group Wise Message Transfer Agent See GWMTA Insufficient memory on page 205 GWMTA Cannot start server insufficient memory available Source Action Group Wise Message Transfer Agent See GWMTA Insufficient memory on page 205 GWMTA Closed for inbound traffic Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA is not accepting inbound connections on its TCP IP link The MTA has been manually suspended Resume the MTA for the domain See Suspending Resuming MTA Processing for a Location in Message Transfer Agent in the GroupWise 7 Administration Guide If you are running multiple MT
180. e original POA can be deleted 24 DB5x Errors DB50 Access to this library has been enabled by WebPublisher on page 132 DB51 Required network address information is missing on page 132 DB52 Required path information is missing on page 133 DB53 No message transfer POA has been selected on page 133 DB55 No POA is available for client server on page 133 DB56 Specified e mail address conflicts with the address of an existing gateway alias on page 133 DB57 Specified e mail address conflicts with the address of an existing user on page 134 DB58 Specified e mail address conflicts with an address from a post office alias record on page 134 DB59 This GroupWise administration version is older than the minimum allowed by the system administrator on page 134 50 Access to this library has been enabled by WebPublisher Source GroupWise engine administration engine Explanation An action cannot be completed because of how the library is configured Possible Cause A library cannot be deleted because it is configured for access by WebPublisher Action Remove the WebPublisher access to the library See Modifying WebPublisher Settings in WebAccess in the GroupWise 7 Administration Guide Then delete the library 51 Required network address information is missing Source GroupWise engine administration engine Explanation An action cannot be completed because of insufficient con
181. e post office database wphost db was missing in the post office Action Restore the wphost db file to the post office Although the conversion does not actually use the old wphost db file it does attempt to access a file by that name in order to rename it COOF Invalid password Source GroupWise engine database services Explanation Invalid password specified on database open Possible Cause If this error occurs when a user has been moved to a different post office the update to the post office database might not have completed Action Move the user back to the original post office Verify the user s password Make sure the agents are running Repeat the move user procedure See Cxxx Engine Error Codes 57 Possible Cause Action Possible Cause Action Action Possible Cause Action Action Moving GroupWise Accounts in Users in the GroupWise 7 Administration Guide If this error occurs when rebuilding a database you might not be connected to the correct GroupWise system Connect to the Group Wise system where the database is located See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide Then perform the rebuild again The password information in the user database user xxx db has been damaged Check and if necessary repair the database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administrati
182. e required file is locked by another program for example a backup program Action Implement a backup process that does not lock files in your live GroupWise system See Backing Up GroupWise Databases in Databases in the GroupWise 7 Administration Guide Action If necessary restart the server to reset all file locks 2 3 85xx Errors 8502 Cannot initialize protocol on page 28 8503 Cannot connect to specified IP address on page 28 8509 Cannot access TCP IP services on page 28 e 850F Connection no longer valid on page 28 e 8555 Port in use on page 28 e 8562 Client server request packet contained invalid identifier on page 29 8563 Client server request packet contained invalid identifier on page 29 8567 Data not in BCEF format on page 29 8568 HTTP port already in use on page 30 8xxx Engine Error Codes 27 8569 SSL login required for this post office on page 30 8570 IMAP port already in use on page 30 8571 SOAP port already in use on page 30 8572 CAP port already in use on page 31 8573 LDAP port already in use on page 31 8502 Cannot initialize protocol Source Explanation Action GroupWise engine general communication Cannot open protocol See 8901 Cannot use TCP IP services on page 32 8503 Cannot connect to specified IP address Source Explanation Action GroupWise engine general commu
183. e software Check the open lock activity on the GroupWise program files If this error occurs from the POA the POA might not have access to a required file Start the POA including the rights switch to determine the specific problem the POA is encountering See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide 8207 Cannot locate file Group Wise engine file input output File seek error A failure occurred when positioning file pointers during an explicit file copy function Cannot open the specified file or directory If this error occurs when a specific user starts the Group Wise client that user database userxxx db might be damaged Check and if necessary repair the database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide 8xxx Engine Error Codes 21 8208 Cannot modify file Source Explanation Possible Cause Action Group Wise engine file input output File modify error Cannot move or rename the file An error occurred when renaming or moving a file to another location Check to see if another file with the same name exists the filename must be unique If so rename that file or move or rename the current file 8209 Path not found Source Explanation
184. e the user database See Re creating a User Database in Databases in the GroupWise 7 Administration Guide If this error occurs in Caching mode delete your Caching mailbox and create a new one as described in the User Guide for your GroupWise client Windows client Setting Up Your Caching Mailbox e Cross Platform client Setting Up Your Caching Mailbox If this error occurs each time the user exits the GroupWise client the archive database might be damaged In the GroupWise client open the archive then use the Repair Mailbox feature to repair the archive See Enabling GroupWise Check in the Windows Client in Client in the GroupWise 7 Administration Guide Run GWCheck on the archive See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide 6 5 C04x Errors e C040 Database error on page 67 C042 Database being modified on page 67 C043 Database error on page 67 C044 Database error on page 67 C045 Unexpected error on page 67 C046 Database error on page 67 C047 Database error on page 68 C048 Unexpected error on page 68 C04A Unexpected error on page 68 C04B Database error on page 68 66 GroupWise 7 Troubleshooting 1 Error Messages C04C Database error on page 68 C04D Memory error on page 68 CO4E Database error on page 68 C04F Database checksum error
185. ebAccess Agent The gateway alias type is not defined The gateway alias was not specified in ConsoleOne during setup Specify a gateway alias type In ConsoleOne double click the WebAccess object enter an alias in the Gateway Alias Type field then click OK The alias can be the same name as the gateway WEBACC No gateway directory was specified Source GroupWise WebAccess Agent WebAccess Agent Error Messages 227 Explanation Possible Cause Action The WebAccess Agent must know the path to its gateway home directory This path is specified by the ph startup switch The ph startup switch was not used on the command line or in the strtweb ncf or strtweb bat file Include the startup switch See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide WEBACC No message is currently open Source Explanation Possible Cause Action GroupWise WebAccess Agent This is an internal diagnostic message Unknown If the problem persists contact the Novell Support http support novell com WEBACC No NetWare password was specified Source Explanation Possible Cause Action GroupWise WebAccess Agent The GroupWise WebAccess Agent requires an account and password that lets it log in to eDirectory or NetWare servers so that it can access the domain directory and post office directories The password startup switch was not used on the command line or
186. eck and if necessary repair the user database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide D005 Settings field list is not valid Source GroupWise engine Possible Cause The post office database wphost db is damaged Action Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide D006 Unexpected error Source GroupWise engine Action See Dxxx Unexpected error on page 138 D009 Cannot use group name in distribution list Source GroupWise engine Explanation A group has been included in a Workflow 80 GroupWise 7 Troubleshooting 1 Error Messages 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 DOOA Syntax error in address Source GroupWise engine Explanation Syntax error Possible Cause A syntax error was detected in the distribution list One of the following conditions exists There is a colon at sign or a period inside a parenthesized list There are parentheses with nothing between them or an opening parenthesis followed by a comma in the distribution list There must be a user ID between the parenthesis and the comma There is a comma followed by a clos
187. ed action request on page 135 e DE05 Unexpected error on page 136 DE02 Cannot perform delayed action request Source GroupWise engine data store and deferment Dxxx Engine Error Codes 135 Explanation Possible Cause Action Error in the defer routine Unable to perform delayed action request Insufficient memory Wait and retry the operation later DE05 Unexpected error Source Action Group Wise engine data store and deferment See Dxxx Unexpected error on page 138 7 27 DFxx Errors DF10 Required file or directory missing on page 136 DF15 Records lost during rebuild on page 137 DF17 Cannot create reguired directory on page 137 DF1C Document storage area definitions are not identical on page 137 DF27 Invalid NGWCHECK DB database migration level on page 137 DF28 Failure using the NGWCHECK DB database on page 138 DF10 Reguired file or directory missing Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Group Wise engine mailbox library maintenance Path error If this error occurs from the POA the path specified by the home switch might be incorrect Check the home setting in the POA startup file Make sure the specified path exists Make sure the path is provided in the format required for the platform on which the POA is running See Using POA Startup Switches in
188. ed error Source GroupWise engine encryption Action See 000x Unexpected error on page 14 0006 Unexpected error Source GroupWise engine encryption Action See 000x Unexpected error on page 14 0007 Unexpected error Source GroupWise engine encryption Action See 000x Unexpected error on page 14 Oxxx Engine Error Codes 13 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 14 GroupWise 7 Troubleshooting 1 Error Messages 8xxx Engine Error Codes 81xx Errors on page 15 82xx Errors on page 16 85xx Errors on page 27 88xx Errors on page 31 e 89xx Errors on page 31 8Bxx Errors on page 41 e 8Cxx Errors on page 41 e 8Fxx Errors on page 42 e 8xxx Unexpected Error on page 42 2 1 81xx Errors e 8101 Memory error on page 15 8101 Memory error Source Explanation Possible Cause Action Possible Cause Action Possible Cause GroupWise engine memory management Memory function failure Invalid memory handle If this error occurs in the NetWare POA there might be insufficient memory on the server for the POA to run On the serv
189. ell com documentation gwgateways 002D Pending move Source GroupWise Administrator association Explanation The record has been moved however GroupWise replication is still in progress The record cannot be modified at this time Action Wait for replication to complete then retry the record modification See Pending Operations in System in the GroupWise 7 Administration Guide 002E Pending delete Source GroupWise Administrator association 242 GroupWise 7 Troubleshooting 1 Error Messages Explanation Action The record has been moved however GroupWise replication is still in progress The record cannot be deleted at this time Wait for the replication to complete then retry the operation See Pending Operations in System in the GroupWise 7 Administration Guide 0031 Cannot delete post office that owns GroupWise objects Source Explanation Possible Cause Action Possible Cause Action GroupWise Administrator delete visitor You cannot delete this post office until all subordinate objects have been moved or deleted The post office still owns one or more Agent objects Delete any Agent objects using ConsoleOne The post office still has users resources distribution lists libraries or library storage areas assigned to it Move or delete each subordinate object in the post office See Deleting a Post Office in Post Offices GroupWise 7 Administration
190. ent Error Messages 13 WebAccess Agent Error Messages 14 Monitor Agent and Application Error Messages Part IIl Administration Error Messages 15 GroupWise Administrator Snap In to ConsoleOne Error Messages 16 GroupWise Check Error Codes 17 GroupWise Time Stamp Utility Error Messages Part IV Client Error Messages 18 Windows Client Error Messages 19 Remote Mode Windows Client Error Messages 20 Cross Platform Client Error Messages 20 1 General GroupWise Client Errors 0 0 0 ee eee eee 20 2 Cross Platform Client Errors 0 0 0c ce teeta 181 193 215 221 233 237 239 247 265 267 269 271 8 A Documentation Updates KA J4n8 19 2006 is wees 2 md ee ee ak bes IR DE ys Bie ss eed GroupWise 7 Troubleshooting 1 Error Messages About This Guide This Novell GroupWise 7 Troubleshooting 1 Error Messages guide covers error messages that appear in ConsoleOne Group Wise agents and GroupWise clients along with possible causes and suggested actions to resolve the problem The guide is divided into the following sections e Group Wise Engine Error Codes on page 11 e Agent Error Messages on page 179 e Administration Error Messages on page 237 e Client Error Messages on page 267 Documentation Updates on page 279 Other sources of troubleshooting assistance include Novell Support http support novell com Novell Support Knowledgebase http suppor
191. ent memory is available turn disk logging back on in the Log Settings page for the agent in ConsoleOne See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA Login not completed timeout Source Explanation Possible Cause Action Group Wise Message Transfer Agent message transfer protocol An MTA or POA started to request TCP IP communication from the MTA but stopped responding in the middle of the login process The server where the other agent was running went down Check the status of the other server Reboot if necessary GWMTA Login to directory failed Source Explanation Possible Cause Action Possible Cause Group Wise Message Transfer Agent The MTA cannot communicate with another domain or post office because it cannot access the server where the domain or post office is located The user and password switches do not provide the correct information for the MTA to log in to the server Check the settings for the user and password switches in the command that starts the MTA Make sure you can log in to the server using the user name and password the MTA is trying to use The server where the domain or post office is located is currently down Message Transfer Agent Error Messages 207 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 vol
192. er box Use a UNC or mapped link between the Internet Agent and the POA rather than a TCP IP link 8909 Cannot use TCP IP services Source Action GroupWise engine TCP IP communication See 8901 Cannot use TCP IP services on page 32 890A Cannot listen on specified port Source Explanation Possible Cause Action GroupWise engine TCP IP communication Listen failed Unable to listen on the specified port It is possible the specified port is in use by another process For example two GroupWise agents might be running on the same server where both were configured for the same port Verify that the IP address and port provided in ConsoleOne are correct See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide 890B Cannot accept incoming connection Source Explanation Possible Cause Action GroupWise engine TCP IP communication Acceptance failed Hardware is overloaded Upgrade the hardware 890F Connection no longer valid Source Explanation Possible Cause Action GroupWise engine TCP IP communication Connection was broken while in use A client or server machine has crashed or the process was forced to close without shutting down The machine might have been exited while connections were active Make sure the POA is running Check the IP address for the POA See Using Client Server Access to the Pos
193. er is attempting to to gain access without having a valid password Try again after the lockout period has passed The default lockout period is 30 minutes Manually enable the user s account See Disabling and Enabling Group Wise Accounts in Users in the GroupWise 7 Administration Guide 112 GroupWise 7 Troubleshooting 1 Error Messages D716 The System Address Book needs to be refreshed Source Explanation Possible Cause Possible Cause Action Group Wise engine directory services access The Address Book updates that the Remote or Caching client is expecting to find in the post office database wphost db are not available For more information see Address Book Delta Sync v7 0 in What s New in Group Wise 7 in the GroupWise 7 Installation Guide The delta records that the client needs have already been removed from the post office database as part of scheduled maintenance to control the size of the post office database You can control how often delta records are removed as described in Controlling Address Book Synchronization for Remote Client Users in System in the GroupWise 7 Administration Guide The post office database has been rebuilt as described in Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide The rebuild process removes all delta sync records Manually download the complete Address Book from the post of
194. er where the POA runs cache buffers should be around 60 If cache buffers drop below 30 there is not enough memory available Unload some other NLM programs or add memory to the server In some cases the insufficient memory condition is temporary GroupWise automatically resends unsuccessful messages so no action might be required Ifthis error occurs in the NetWare POA some current server parameters might be set too low Increase the settings for the following NetWare server parameters e Minimum Packet Receive Buffers e Maximum Directory Cache Buffers e Maximum Services Processes Many factors influence what the proper settings should be for a particular server Make sure each parameter is set to at least 1000 and increase settings from there as needed For more information see Fine Tuning Your NetWare POA Installation in Post Office Agent in the GroupWise 7 Administration Guide If this error occurs in the NetWare agents after updating your Group Wise system you might not have updated the agents properly 8xxx Engine Error Codes 15 Action After exiting all the agents unload the agent engine gwenn5 n1m 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 Group Wise client the user might have exceeded the limit of viewable 65 000 items per folder Remember that Tras
195. error on page 78 C072 Database error Source Group Wise engine database services Explanation Guardian transaction active Possible Cause Attempted to synchronize a dependent database dictionary file However the parent database dictionary file which contains the definitions was locked by another process See Information Stored in the Post Office in Post Office Agent in the Group Wise 7 Administration Guide Action Retry the operation C073 Unexpected error Source Group Wise engine database services Action See C0xx Unexpected error on page 78 C076 Unexpected error Source GroupWise engine database services Action See COxx Unexpected error on page 78 C077 Unexpected error Source GroupWise engine database services Action See COxx Unexpected error on page 78 C078 Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 C079 Unexpected error Source GroupWise engine database services Cxxx Engine Error Codes 75 Action See COxx Unexpected error on page 78 C07A Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 C07B Database error Source Group Wise engine database services Action See C0xx Database error general database repair strategies on page 77 C07C Unexpected error Source Group Wise engine database services
196. error codes that might occur when you run GroupWise Check e Chapter 15 GroupWise Administrator Snap In to ConsoleOne Error Messages on page 239 e Chapter 16 GroupWise Check Error Codes on page 247 e Chapter 17 GroupWise Time Stamp Utility Error Messages on page 265 Other sources of assistance include Novell Support http support novell com Novell Support Knowledgebase http support novell com search kb_index jsp e GroupWise 7 Support Forums http support novell com forums 2gw html e Novell GroupWise Support Community http support novell com products groupwise GroupWise Cool Solutions http www novell com coolsolutions gwmag index html Administration Error Messages 237 238 GroupWise 7 Troubleshooting 1 Error Messages GroupWise Administrator Snap In to ConsoleOne Error Messages e 0001 Cannot load resource on page 240 0002 Schema not properly defined on page 240 e 0003 Required DLL has incorrect version on page 240 e 0004 Required DLL missing on page 240 e 0005 Cannot read required information from NDS on page 241 e 0006 GroupWise object missing required information on page 241 e 0007 Cannot read required information from GroupWise database on page 241 e 0008 Cannot delete subordinate objects on page 241 e 0009 Cannot obtain UNC path on page 241 e 0013 Out of memory on page 241 e 0019 Cannot map local drive to net
197. erver Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 F108 Cannot connect to remote server Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 9 15 FOxx Errors e FOxx Query syntax error on page 176 FOxx File I O error on page 176 FOxx Database error on page 177 FOxx Database error index on page 177 F0xx Memory error on page 177 FOxx Unexpected error on page 177 FOxx Query syntax error Source GroupWise engine QuickFinder Explanation While using the Find feature in the GroupWise client you received a message indicating a problem with the syntax of your search query Action Correct the query syntax then retry the operation Look up find using operators and conditions in GroupWise client Help FOxx 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 176 GroupWise 7 Troubleshooting 1 Error Messages Action Possible Cause Action Possible Cause Action Action Rebuild the index of the database where the error occurs See Rebuilding Database Indexes in Databases in the GroupWise 7 Administration Guide The disk is full where the Quick
198. ery syntax error on page 176 FOOC Ambiguous switch supply more characters Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 9 2 F01x Errors e F010 Search cancelled on page 160 e F012 File I O error on page 161 e F013 Database error on page 161 F014 Database error on page 161 e F016 Database error on page 161 F018 Number contains non numeric characters on page 161 F019 Search switch reguires n on page 161 e FOLA Document summary field name or number required on page 161 FOIB Unknown field in search command on page 162 e FOLIC Ambiguous field supply more characters on page 162 FOID Empty quotation marks not allowed on page 162 FOIE nowildcard and prefix cannot be used together on page 162 e FOIF Invalid syntax in search query on page 162 F010 Search cancelled Source GroupWise engine QuickFinder Explanation Search cancelled Action Search was cancelled at user s request 160 GroupWise 7 Troubleshooting 1 Error Messages F012 File I O error Source GroupWise engine QuickFinder Explanation The QuickFinder process used by the Find feature cannot access a required file Possible Cause The QuickFinder index is damaged Action Rebuild the index of the database where the error occurred See Rebuilding Database Indexes in Databases in the GroupWise 7 Admini
199. es of the wpcsout ofs directory Check the POA log file to determine the offending message file See Using POA Log Files in Post Office Agent in the GroupWise 7 Administration Guide Delete the offending message file so that subsequent messages can be processed 7 17 DA0x Errors e DAOC Incorrect DLL version on page 114 e DAOD Cannot create directory in post office on page 114 e DAOE Path to post office database not specified on page 115 DAOC Incorrect DLL version Source GroupWise engine Post Office Agent Explanation Wrong DLL Possible Cause The DLL being used with the POA executable is either an older or a newer version The DLL cannot be used with the executable Action Make sure the POA executable is the same version as the POA DLL For a list of agent files see Windows Installation Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure DAOD Cannot create directory in post office Source GroupWise engine Post Office Agent Explanation Post office directory structure problem Possible Cause A required post office directory could not be created or one or more database dictionary files is missing Action Make sure all of the database dictionary files are present For file locations see Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure
200. ffice Directory and Software Distribution Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Cxxx Engine Error Codes 63 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 78 C02C Database error Source GroupWise engine database services Action See C0xx Database error database dictionary file on page 78 C02D Database error Source GroupWise engine database services Action See COxx Database error database dictionary file on page 78 CO2E Database error Source GroupWise engine database services Action See C0xx Database error database dictionary file on page 78 C02F Database error Source GroupWise engine database services Action See COxx Database error database dictionary file on page 78 6 4 C03x Errors e C032 Database error on page 64 C033 Database error on page 65 C034 Database error on page 65 C035 Database error on page 65 C037 Memory error on page 65 C038 Memory error on page 65 C03A Database requires newer version on page 65 C03B Database error on page 65 C03C Database error on page 65
201. fice In the Group Wise Windows client open the Address Book then click View gt Retrieve System Address Book 7 16 D9xx Errors D901 Unexpected error on page 113 D902 Unexpected error on page 113 D904 Unexpected error on page 113 e D90A Unexpected error on page 113 D90B Unexpected error on page 114 D912 Cannot process message file on page 114 D901 Unexpected error Source Action Group Wise engine messaging services See Dxxx Unexpected error on page 138 D902 Unexpected error Source Action Group Wise engine messaging services See Dxxx Unexpected error on page 138 D904 Unexpected error Source Action Group Wise engine messaging services See Dxxx Unexpected error on page 138 D90A Unexpected error Source Action Group Wise engine messaging services See Dxxx Unexpected error on page 138 Dxxx Engine Error Codes 113 D90B Unexpected error Source GroupWise engine messaging services Action See Dxxx Unexpected error on page 138 D912 Cannot process message file Source GroupWise engine messaging services Explanation The message file has been opened too many times It has been moved to the problem directory Possible Cause The POA might be attempting to process a damaged message file and is unable to move it to the problem directory Action Check the priority subdirectori
202. fice directory is missing Possible Cause Files have been inadvertently removed from the offiles directory Action Restore the files from backup Possible Cause The post office has been copied to a new location and not all files in the offiles directory were copied successfully Action Make sure that all files from the offiles directory are available in the new location Possible Cause The user has archived the message with the attachment and the archive directory is not currently available Action Check the current archive location In the GroupWise client click Tools gt Options gt Environment gt File Location Possible Cause A document in a GroupWise library is not accessible Action Repair the library See Maintaining Library Databases and Documents in Databases in the GroupWise 7 Administration Guide Under the Analyze Fix action select the following e Verify Library Fix Document Version Element e Verify Document Files e Validate All Document Security COxx Database error Support assistance recommended Source GroupWise engine database services Explanation Generic database error Action Typically database errors in this group require assistance from Support However you might want to try to repair the database yourself before contacting Support See COxx Database error general database repair strategies on page 77 COxx Database error general database repair strategies Source
203. fice database read error on page 210 Post office now closed on page 210 Post office open failed on page 211 Received unsupported request request ignored on page 211 Running the agent with conflicting effective users on page 211 StartServiceCtrlDispatcher failed when attempting to start Windows agent service on page 211 e GWMTA e GWMTA page 212 e GWMTA page 212 Target gueue temporarily locked on page 211 The Windows agent service fails to set service status service stopped on The Windows agent service fails to initialize memory system service stopped on 194 GroupWise 7 Troubleshooting 1 Error Messages e GWMTA Timed out waiting for end of file confirmation on page 212 e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA U U U U U e GWMTA U nable to initialize message log database on page 212 nable to open connection no response on page 213 nable to register with SNMP agent on page 213 nable to retrieve TCP IP address on page 213 ndefined link on page 213 nknown connection header received on page 213 e GWMTA Unknown destination on page 214 e GWMTA Waiting for busy listen socket to become available on page 214 GWMTA Access denied Source Explanation Possible Cause Action Group Wise Message Transfer Agent last closure reason A domain or post office is closed because the MTA cannot a
204. field in GWCheck If the user ID is typed correctly make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides 17 Post office does not exist in domain Source Group Wise Check utility GWCheck 252 GroupWise 7 Troubleshooting 1 Error Messages Explanation Action GWCheck cannot locate the specified post office Make sure you provided the correct information for the post office in the Database Path and Post Office Name fields 18 Message database open error Source Explanation Action Action Action Group Wise Check utility GWCheck GWCheck cannot open the specified message database msgnnn db Perform a structural analyze fix on the message database by supplying the name of the message database in the User Resource field See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide If the message database cannot be repaired manually restore it from backup For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 19 WPHOST DB database open error Source Explanation Action Action Group Wise Check utility GWCheck GWCheck cannot open the post office database wohost db In ConsoleOne rebuild the post office database See Rebuilding Domain or Post Office Databases i
205. figuration information Possible Cause An agent has not been properly configured with an IP address or TCP port 132 GroupWise 7 Troubleshooting 1 Error Messages Action Action Action Action The POA is not properly configured See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide The MTA is not properly configured See Changing the Link Protocol between Domains in Message Transfer Agent in the GroupWise 7 Administration Guide The Internet Agent is not properly configured In ConsoleOne browse to and right click the GWIA object then click Properties Click Post Office Links then correct the link information as needed See Internet Agent in the GroupWise 7 Administration Guide The WebAccess Agent is not properly configured See Managing Access to Post Offices in WebAccess in the GroupWise 7 Administration Guide DB52 Required path information is missing Source Explanation Possible Cause Action Group Wise engine administration engine An action cannot be completed because of insufficient configuration information A domain or post office has not been properly configured with the path to the directory where the domain or post office is located Check the UNC path information provided for the domain or post offices See Editing Domain Properties in Domains or Editing Post Office Propert
206. ge 258 e 44 Database invalid due to security breach on page 258 e 47 Error in library sync with host on page 258 e 48 Orphaned QuickFinder index file on page 259 49 Invalid QuickFinder index file on page 259 e 50 Orphaned blob file on page 259 51 Invalid blob file on page 259 52 Blob file missing trailer on page 259 e 53 Blob file truncated to 0 bytes on page 259 61 Error adding system document type definition on page 259 62 Error reading system document type definition on page 260 e 63 Unable to update during check error code on page 260 64 Unable to complete verify during check error code on page 260 e 65 Unable to add default system document types on page 260 e 66 Unable to correct document display name on page 260 e 67 Unable to correct element without version object on page 261 e 68 Unable to synchronize document security on page 261 e 69 Unable to correct document without version object on page 261 e 70 Unable to correct version without document on page 261 e 71 Unable to correct version without element on page 261 e 72 Invalid user specified for orphan document reassignment on page 262 e 73 Unable to remove document storage area on page 262 e 74 Unable to move all blobs storage area cannot be removed on page 262 e 75 Unable to move blob on page 262 e 76 Error accessing doc
207. gement Cannot delete last version Delete the entire document not just the version Look up documents deleting in GroupWise client Help E516 Unexpected error Source Action GroupWise engine document management See Exxx Unexpected error on page 157 E517 Unexpected error Source Action GroupWise engine document management See Exxx Unexpected error on page 157 E51B Access to feature denied Source Explanation Possible Cause Action GroupWise engine document management Access to requested feature denied The user is attempting to use a document management feature that is not available to this user on this library If the user should be allowed to use this feature grant the appropriate library membership rights See Managing Library Access in Libraries and Documents in the GroupWise 7 Administration Guide E51C Disk space limit exceeded Source GroupWise engine document management 142 GroupWise 7 Troubleshooting 1 Error Messages 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 8 3 E52x Errors e E520 Unexpected error on page 143 E522 Library not empty on page 143 E523 Document not modified on pag
208. h is considered a folder Action Delete items or move them to a different folder Empty the Trash Possible Cause If this error occurs when manually addressing a message to multiple external recipients the user might have typed one or more addresses incorrectly in such a way that the client exceeded available memory trying to resolve the erroneous external addresses For example leaving out the at sign can cause this problem Action Users should select recipients from the Address Book whenever possible If users must type external addresses care should be used to type the addresses correctly especially in cases where the number of recipients is large Possible Cause If this error occurs in the GroupWise client in Remote mode Group Wise might not be installed correctly on the remote computer Action Reinstall GroupWise on the remote computer See the platform specific setup instructions for using Remote mode in GroupWise Modes in Client in the GroupWise 7 Administration Guide Possible Cause This error can occasionally be caused by damaged databases Action Check and if necessary repair databases accessed by the user who is receiving the error See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide 2 2 82xx Errors 8200 File I O error on page 17 e 8201 Access to file denied on page 17 e 8202 Cannot access required file on pag
209. h a connection to the post office on page 222 Conversation timed out on page 223 Could not start logging thread on page 223 Error accessing directory on page 223 Error accessing startup file on page 224 File I O error on page 224 GWINTER NLM cannot initialize screen on page 224 GWINTER NLM initialization error Invalid GWENN5 NLM loaded on Hash value changed on page 224 If necessary the system will attempt a forced shutdown on page 225 Invalid command line syntax on page 225 Invalid log level on page 225 Invalid startup parameter on page 225 Invalid startup parameter file on page 225 Invalid startup parameter value on page 226 Logging Disk is full turning file logging off on page 226 Logging Error creating file turning file logging off on page 226 Logging Error writing to file turning file logging off on page 226 Login failed on page 227 Login rejected No valid password specified on page 227 Login rejected No valid userid specified on page 227 Login rejected Password is incorrect on page 227 No gateway alias was specified in NW Admin on page 227 No gateway directory was specified on page 227 No message is currently open on page 228 No NetWare password was specified on page 228 No NetWare user ID was specified on page 228 No UNC path specified for the post office on page 228 Not able to bind to specified port on page 229
210. h not specified on page 84 D017 Too many users in address Source Explanation Possible Cause Action GroupWise engine Reply buffer full When Reply to All is selected personal groups and public distribution lists are expanded into a complete list of users If the expanded list exceeds 6 KB this error occurs If the reply is sent some of the users included in the original groups might not receive the reply To reply to all the users create a personal group that contains the users and send the reply to that group If replying to these groups is common the 82 GroupWise 7 Troubleshooting 1 Error Messages personal groups could be made into public distribution lists and selected manually when replying to all users D018 Unexpected error Source Action Group Wise engine See Dxxx Unexpected error on page 138 D019 Password incorrect Source Explanation Action Possible Cause Action Action Group Wise engine Invalid password Type the correct password Passwords are case sensitive The password information in the post office database wohost db has been damaged Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide If rebuilding the post office database does not resolve the problem rebuild the domain database wodomain db DO1A Password too long Source Explanation Action
211. has changed Rebuild the database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide DB3F Cannot delete required field Source Explanation Action Group Wise engine administration engine Cannot remove a required field You must supply valid data for all required fields 7 23 DB4x Errors DB40 Cannot delete gateway used in link on page 129 DB41 Database does not match domain or post office on page 129 DB42 Information lost during recovery on page 129 DB43 Maximum number of open post offices reached on page 129 DB45 GroupWise system not found on page 129 DB46 Path too long on page 130 DB47 Invalid area on page 130 DB48 Cannot delete domain that has links on page 130 DB49 Cannot use limited visibility distribution list as administrator on page 130 DB4A External sync message from unknown system on page 131 128 GroupWise 7 Troubleshooting 1 Error Messages DB4B Cannot delete Internet domain name that is still referenced on page 131 DB4D Database recovery required to update database structure on page 131 e DBAE Cannot delete default gateway on page 131 e DB4F Cannot delete POA that performs message transfer on page 132 DB40 Cannot delete gateway used in link Source Explanation Possible Cause Action Group Wise engine administration engine Gateway lin
212. he GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide In Remote mode the GroupWise client should automatically repair any problems with the remote databases If the client is unable to repair the problem you can delete the rofdata directory on the remote computer then request all information from the master mailbox again DO1E Cannot execute rule Source Explanation Possible Cause Action Group Wise engine Invalid rule action An archive rule was given an invalid execution type GroupWise does not allow you to create a rule that automatically archives messages when they are received Edit the rule and select a valid execution type Look up rules in GroupWise client Help DO1F Archive path not specified Source Explanation Possible Cause Action Group Wise engine No archive path No archive path specified in the GroupWise client Specify the archive path before attempting to archive items Look up archive directory setting up in GroupWise client Help 7 3 DO2x Errors e D020 Rule caused infinite loop on page 85 e D021 Cannot deliver message on page 85 D023 User ID expired on page 85 D024 Rule cannot forward reply accept or delegate personal item on page 85 D025 Users not specified on page 85 e D026 Missing opening brace in distribu
213. he IP address instead of the host name when configuring the POA The POA was started with the wrong name switch setting so that it is associated with the wrong configuration information Make sure the name switch setting specifies the correct POA configuration TCP IP is not set up correctly on the server where the POA is running Make sure TCP IP is set up correctly GWPOA Database language has been updated please rebuild this database Source Explanation Action Group Wise Post Office Agent admin thread The post office database wphost db needs to be rebuilt because the language has been changed which changes the sort order of the users listed in the database Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWPOA Disk is full turning disk logging off Source Explanation Action Action Group Wise Post Office Agent Logging information to disk has been turned off because there is insufficient disk space to continue writing to the agent log file See Using POA Log Files in Post Office Agent in the GroupWise 7 Administration Guide Free up disk space The agent should resume disk logging after disk space is available To ensure that disk logging has resumed check the Logging Level setting in the Log Settings page for the agent in ConsoleOne Specify a different location for log files
214. he MTA has been able to access the directory specified by the home switch but it cannot locate a valid domain database in that directory Make sure the location provided by the home startup switch specifies a valid domain directory See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA Cannot find startup file Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA cannot start because it cannot locate or read its startup file The name of the startup file as provided in the command to start the MTA is incorrect Make sure you are providing the name of the startup file correctly See Installing and Starting the MTA in Message Transfer Agent in the GroupWise 7 Administration Guide The startup file is not located on the current path Specify the full path to the startup file in the command to start the MTA Message Transfer Agent Error Messages 197 GWMTA Cannot move files Source Explanation Explanation Action Group Wise Message Transfer Agent last closure reason The MTA cannot move message files from its input queue domain wpcsin or post officeXwpcsin to its in progress queue gwinprog Insufficient disk space on the server where the ms local directory structure is located Free up disk space so the MTA has sufficient space to process message files GWMTA Ca
215. he SSL certificate file or key file might be damaged Obtain a new SSL certificate and key file See Encryption and Certificates in Security Administration in the GroupWise 7 Administration Guide 8925 Connection refused Source Explanation Possible Cause Action Group Wise engine TCP IP communication An agent that is configured for TCP IP attempted to contact another agent and the connection was refused The agent is not communicating on the right TCP port number Determine the configuration of the target agent and make sure the initiating agent is using the correct port number See the following sections of the GroupWise 7 Administration Guide depending on which agent is refusing the connection e Using Client Server Access to the Post Office in Post Office Agent Using TCP IP Links between a Domain and its Post Offices in Message Transfer Agent Changing the Link Protocol between the Internet Agent and the Message Transfer Agent in Internet Agent Changing the WebAccess Agent s Network Address or Port Numbers in WebAccess 8926 Unknown host Source Explanation Possible Cause Action Possible Cause Action Action GroupWise engine TCP IP communication The IP address or DNS hostname cannot be resolved to a host in the network An incorrect IP address was specified Verify the IP address If a DNS hostname was specified the DNS name ser
216. he private key file Correct the password information in ConsoleOne See the following sections of the GroupWise 7 Administration Guide depending on which agent is encountering the problem e Enhancing Post Office Security with SSL Connections to the POA in Post Office Agent Enhancing Domain Security with SSL Connections to the MTA in Message Transfer Agent Securing Internet Agent Connections with SSL in Internet Agent Securing WebAccess Agent Connections with SSL in WebAccess 891E Insufficient memory for SSL Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action GroupWise engine TCP IP communication A GroupWise agent failed to establish an SSL connection because insufficient memory is available for creating the connection Another program was temporarily using a very large amount of memory on the server Wait and try the operation again Too many programs are currently running on the server Stop some programs that are running on the server in order to free up some memory The server where the agent is running has insufficient memory for proper functioning Run the agent on a more powerful server 891F Invalid SSL certificate Source Explanation Possible Cause Action Group Wise engine TCP IP communication A GroupWise agent cannot establish an SSL connection because the SSL certificate file
217. he user s mailbox as well If this error occurs when users exit the Group Wise client the users might have the archive directory set to a location where they do not have sufficient rights In the GroupWise client check the users path to the archive directory Look up archive directory in GroupWise client Help Make sure users have sufficient rights to create and modify files there Or have users change their archive directory to a location where they already have sufficient rights If this error occurs when users exit the GroupWise client the user database userxxx db might be damaged Check and if necessary repair the user database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide If this error occurs when a user is running in Caching mode or Remote mode the user s local databases might be damaged Repair the user s Caching or Remote mailbox See Tools for Analyzing and Correcting Group Wise Client Problems in Client in the GroupWise 7 Administration Guide The Group Wise databases might be owned by an invalid user For the locations of GroupWise databases in domains and post offices see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting
218. ibrary 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 document management Action See Exxx Unexpected error on page 157 8 2 E51x Errors e E511 Document version available on page 141 E512 Invalid user ID on page 141 e E513 Unexpected error on page 142 e E514 Document version must be checked out and in by same user on page 142 e E515 Cannot delete last version of document on page 142 e E516 Unexpected error on page 142 e E517 Unexpected error on page 142 ESIB Access to feature denied on page 142 e ESIC Disk space limit exceeded on page 142 E511 Document version available Source GroupWise engine document management Explanation Version is available Possible Cause The user is attempting to check in a document version that is not checked out or to end access to a version that is not in use Action Do not attempt to check in or end access to a version that is already available E512 Invalid user ID Source GroupWise engine document management Explanation The user ID on a document is not valid Possible Cause User information on the document has been damaged Action Repair the document information in the library See Maintaining Library Databases and Documents in Databases
219. ibution list Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot access the specified BLOB file containing the official version distribution list for a document in the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 78 Error accessing blob for current version distribution list Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot access the specified BLOB file containing the official current distribution list for a document in the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 79 Error accessing blob for version distribution list Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot access the specified BLOB file containing the distribution list for a document in the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information
220. ication by selecting View Log Files in the agent window and changing the information in the Viewer field Check the viewer and path specified in the View Log Files dialog box in the agent window GWMTA Database language has been updated please rebuild this database Source Explanation Action GroupWise Message Transfer Agent admin thread The database needs to be rebuilt because the language has been changed which changes the sort order of the users listed in the database Rebuild the database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA Disk full disk logging turned off Source Explanation Action Action Group Wise Message Transfer Agent Logging information to disk has been turned off because there is insufficient disk space to continue writing to the agent log file Free up disk space The agent should resume disk logging after disk space is available To ensure that disk logging has resumed check the Logging Level setting in the Log Settings page for the MTA in ConsoleOne See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide Specify a different location for log files where sufficient disk space is available GWMTA Domain database error circular transfer domain link Source Explanation Possible Cause Action Group Wise Message Transfer Agent The MTA cannot
221. ide A library database is missing Library databases must be restored from backup They cannot be re created If this message occurs from the POA when starting its indexing cycle a library directory structure might have been deleted without deleting the library object Run GWCheck to perform a structural rebuild on the dmsh db file in the post office then verify the library See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide Then delete the library See Deleting a Library in Libraries and Documents in the GroupWise 7 Administration Guide If this message occurs in the GroupWise client in Remote mode a database might be missing from the Remote mailbox Delete the rofdata directory on the remote computer then request all information from the master mailbox again CO5E Unexpected error Source Action Group Wise engine database services See C0xx Unexpected error on page 78 Cxxx Engine Error Codes 71 6 7 C06x Errors e C060 Unexpected error on page 72 e C061 Unexpected error on page 72 e C062 Unexpected error on page 72 e C063 Database error on page 72 e C066 Unexpected error on page 72 C067 Database error on page 72 e C068 Database error on page 73 e C069 Database error on page 73 e CO6A Database error on page 73 e CO6B Database error on page 73 e C06C Database error
222. ied by the home startup switch when starting the MTA It must specify the domain directory See Using Monitor Agent Switches in Monitor in the GroupWise 7 Administration Guide The location specified by the home startup switch is on a server that is currently not available Check the status of the server where the specified directory is located Wait for the server to come back up or contact the administrator of that server The location might be on a server that is not currently mapped Make sure the server where the Monitor Agent is running has a drive mapped to the domain directory on the server where the domain is located if it is using a mapped link GWMON Request timed out waiting for response from GroupWise Monitor Agent Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Group Wise Monitor Application The Monitor Application has been able to communicate successfully with the Monitor Agent but the Monitor Agent has stopped responding The server where the Monitor Agent is running has gone down Resolve any network problems that are preventing GroupWise Monitor from functioning The server where the Monitor Agent is running is overburdened or has insufficient system resources available so that the Monitor Agent cannot respond to the Monitor Application in a timely manner Make sure that the server where the Monitor Agent is running meets Monitor
223. ient server mode because the POA in that post office is not running The POA ina remote post office is required for cross post office proxy and library access Make sure the POA is running in the remote post office See Monitoring the POA in Post Office Agent in the GroupWise 7 Administration Guide Make sure the POA in the remote post office is configured with the correct IP address and TCP port Make sure the POA in the remote post office is configured to allow TCP IP connections Make sure it has not been started with the notcpip switch D051 Cannot connect to specified post office Source Explanation Possible Cause Action Group Wise engine TCP IP not allowed An attempt to connect to a post office by way of a direct or mapped mode was rejected No IP address information is available to attempt a client server connection The administrator hasn t set up the client server addressing Set up the IP address for the POA See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide 90 GroupWise 7 Troubleshooting 1 Error Messages D054 Cannot connect to specified post office Source Explanation Possible Cause Action Action Action GroupWise engine Missing path for direct mode connection The post office rejected the client server mode connection but is allowing direct mode The path might be set up but not for this platfor
224. ies in Post Offices in the GroupWise 7 Administration Guide DB53 No message transfer POA has been selected Source Explanation Possible Cause Action Group Wise engine administration engine An action cannot be completed because of insufficient configuration information A post office has been configured with a TCP IP link to its domain but no POA has been selected to provide the link to the MTA Configure the link between the POA and the MTA See Editing a Post Office Link in Domains in the GroupWise 7 Administration Guide DB55 No POA is available for client server Source Explanation Possible Cause Action Group Wise engine administration engine An action cannot be completed because of incorrect configuration A post office has been configured for client server access mode but no POA has been configured for client server processing Configure a POA for client server mode See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide DB56 Specified e mail address conflicts with the address of an existing gateway alias Source Group Wise engine administration engine Dxxx Engine Error Codes 133 Possible Cause You are creating or modifying a gateway alias in such a way that its new name conflicts with an existing gateway alias Action Choose a different name for the new gateway alias Check for existing
225. ify the UNC path to the document storage area as needed so that the post office database and the guardian database are both updated with the same current information If the information looks correct as is simply delete and retype one character so that the correct information is written out to all affected databases See Managing Document Storage Areas in Libraries and Documents in the GroupWise 7 Administration Guide DF27 Invalid NGWCHECK DB database migration level Source GroupWise engine mailbox library maintenance Explanation The GWCheck database ngwcheck db contains invalid information Dxxx Engine Error Codes 137 Action Delete the GWCheck database then rerun GWCheck or Mailbox Library Maintenance DF28 Failure using the NGWCHECK DB database Source GroupWise engine mailbox library maintenance Explanation The GWCheck database ngwcheck db cannot be accessed by GWCheck Action Delete the GWCheck database then rerun GWCheck or Mailbox Library Maintenance 7 28 Dxxx Unexpected Error e Dxxx Unexpected error on page 138 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 138 GroupWise 7 Troubleshooting 1 Error Messages Exxx Engine Error Codes E50x Errors on page 139 ES1x Errors on page 141 E52x Errors on page 143
226. ild failed Rename recover ddb to wodomain db in the domain directory then rerun the rebuild See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide DB3A Cannot delete domain that has links Source Explanation Possible Cause Group Wise engine administration engine Domain has indirect links Cannot delete the domain because it is used in indirect routing Dxxx Engine Error Codes 127 Action Reconfigure domain links before deleting the domain See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide DB3B Remote management message sent Source Explanation Action Group Wise engine administration engine Remote management message sent None This is not an error It is a notification by the program that the operation to be performed has been sent to the parent domain DB3C Domain database in use Source Explanation Possible Cause Action Action Group Wise engine administration engine Exclusive open error An exclusive open for a domain to be merged or released failed because the domain is already in use Have all administrators exit the domain database wpdomain db before running the merge or release Stop the MTA in the domain to be merged or released DB3D Database sorting language changed Source Explanation Action Group Wise engine administration engine Database language
227. in Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Check the ownership of the Group Wise databases If necessary change the ownership to a valid user such as the system administrator The database has been damaged If the ownership on the problem database is correct or you are unable to reset it repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide 108 GroupWise 7 Troubleshooting 1 Error Messages 7 14 D70x Errors D701 Unexpected error on page 109 D704 Unexpected error on page 109 D705 Unexpected error on page 109 D706 Unexpected error on page 109 D707 Unexpected error on page 109 D708 Directory entry record not found on page 109 D709 Unexpected error on page 110 D70A Memory error on page 110 D70B Database inconsistency detected on page 110 D70D Unexpected error on page 110 D70E Duplicate entry in database on page 110 D70F Unexpected error on page 111 D701 Unexpected error Source GroupWise engine directory services access Action See Dxxx Unexpected error on page
228. in use on page 53 e B30A No peer listening for connection on page 53 B300 File transmission failed Source Explanation Possible Cause Possible Cause Action GroupWise engine Message Transfer Protocol The POA was not able to transfer a message file to the MTA The MTA restarted during transmission of the file The network experienced a slow down causing the MTA to time out while waiting for the rest of the file None The POA automatically resends the message until the message is sent successfully B309 Port already in use Source Explanation Possible Cause Action Group Wise engine Message Transfer Protocol The specified port is already in use You have set up the POA to communicate with the MTA by way of TCP IP but the TCP port you have chosen for the Message Transfer Protocol MTP link between them is already in use by another program The message transfer port configured for the POA should be the same port number as the MTA is using to listen on Make sure the MTA is set up correctly for TCP IP links Make sure the POA is configured with the message transfer port number matching the port number of the MTA See Changing the Link Protocol between the Post Office and the Domain in Post Office Agent in the GroupWise 7 Administration Guide B30A No peer listening for connection Source Explanation Possible Cause Action Possible Cause Action Possible Cause
229. inal database will continue to be used until ConsoleOne is restarted The server where the domain database is located has gone down so the drive mapping is no longer valid Check the status of the server The domain database is damaged Check and if necessary repair the domain database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide 0069 Outbound MTA platform undefined Source Explanation Possible Cause Action GroupWise Administrator link tool Information in the Link Configuration Tool is displayed based on the domain s MTA platform MTA settings error The default outbound MTA platform is NetWare Set the outbound MTA platform to the appropriate platform type See Configuring the MTA in Message Transfer Agent in the GroupWise 7 Administration Guide 00A2 Cannot set rights on software distribution directory Source Explanation Possible Cause Action GroupWise Administrator automatic rights Group Wise Administrator could not automatically set the correct rights to the software distribution directory The software distribution directory is located on a server located in a different tree from the post office Create a software distribution directory in the same tree as the post office See Creating a Software Distribution Directory in System in the GroupWise 7 Administration Guide 0102 Password i
230. ine database services Action See C0xx Database error Support assistance recommended on page 77 C016 Database error Source GroupWise engine database services Action See COxx Database error Support assistance recommended on page 77 Cxxx Engine Error Codes 59 C017 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C018 Database error Source GroupWise engine database services Action See COxx Database error Support assistance recommended on page 77 C019 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C01A Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C01B Database error Source GroupWise engine database services Action See COxx Database error general database repair strategies on page 77 C01C Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C01D Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C01E Database error Source GroupWise engine database services Action See COxx Database error Support
231. ing parenthesis in the distribution list There must be a user ID between the comma and the parenthesis There is a colon somewhere after a closing parenthesis Action Locate the syntax error in the distribution list A pointer indicates where the error is Correct the syntax error then retry the operation DOOB Missing closing quotation mark Source GroupWise engine Explanation No closing quotation mark Possible Cause A closing quotation mark is missing in a distribution list Action Type the closing quotation mark then retry the operation DOOC Unexpected error Source GroupWise engine Action See Dxxx Unexpected error on page 138 DOOD Cannot match parentheses Source GroupWise engine Explanation Problem with parentheses Possible Cause Cannot match the parentheses in the distribution list While processing the To BC and CC buffers of a send window a problem was found matching up parentheses See also DOOA Syntax error in address on page 81 Action Check the distribution list for incorrect usage of parentheses and resend DOOE Distribution list contains nested groups Source GroupWise engine Explanation Groups are nested too deep Dxxx Engine Error Codes 81 Possible Cause Action 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
232. inistration Guide The Group Wise name server cannot locate any post offices Make sure the network connections to the servers where post offices reside are functioning properly D058 Version mismatch on GroupWise client POA post office Source Explanation Group Wise engine The post office directory with its associated user databases userxxx db and message databases msgnnn db was created by a version of GroupWise that is older than the version of the GroupWise client that is accessing the post office Dxxx Engine Error Codes 91 Possible Cause Action Possible Cause Action A user is running the latest version of the GroupWise client but the post office has not yet been updated Update the post office See Update in the GroupWise 7 Installation Guide The post office has been updated but the latest version of the POA has not yet been installed and started Update the POA See Updating Post Offices in Update in the GroupWise 7 Installation Guide D059 Recursion limit exceeded during delivery Source Explanation Possible Cause Action Group Wise engine The POA received a message that contained more than 36 levels of encapsulation The POA could not deliver the message This can be caused by rule forwarding loops that include one hop to an external user or by some Internet chain letters Check the rule configuration of the GroupWise recipient Disable any rules
233. inistration Guide Change the HTTP port for one of the POAs 8569 SSL login required for this post office Source Explanation Possible Cause Action Action GroupWise engine general communication Starting with GroupWise 6 5 the POA can be configured to require SSL connections with clients Users of clients earlier than GroupWise 6 5 are trying to log in to the post office Have users update their Group Wise client software See Updating Users Group Wise Clients in Update in the GroupWise 7 Installation Guide Configure the POA so that SSL is enabled rather than required so that the older GroupWise clients can connect to the post office See Enhancing Post Office Security with SSL Connections to the POA in Post Office Agent in the GroupWise 7 Administration Guide 8570 IMAP port already in use Source Explanation Possible Cause Action GroupWise engine general communication The IMAP port used by the POA to communicate with IMAP e mail clients is already in use by another program on the server You are trying to run two POAs on the same server and you have not given them unique IMAP port numbers Check the IMAP port for each POA object See Supporting IMAP Clients in Configuring the POA in the GroupWise 7 Administration Guide Change the IMAP port for one of the POAs 8571 SOAP port already in use Source Explanation Possible Cause Action 30
234. ion GroupWise engine database interface The Group Wise user ID is ambiguous There is more than one user with same user ID in the same post office Select the correct user ID in the pop up list or select the user in the Address Book If this error occurs when a user starts the GroupWise client the user s information in the post office database might not be correct Check the information provided for the GroupWise user in ConsoleOne Correct the information as needed See Creating GroupWise Accounts for eDirectory Users in Users in the GroupWise 7 Administration Guide 100 GroupWise 7 Troubleshooting 1 Error Messages Action Even if the information in the user record looks correct make a change somewhere so the record is written out again Action Ifthe problem persists rebuild the post office database wphost db See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide D103 Post office not found during login Source GroupWise engine database interface Explanation Post office not found Action Ifusing startup switches check the ph switch to make sure the path to the post office is correct If it is incorrect enter the correct ph switch Action If the path is correct the post office was not found during parse of the To line buffer In that case find the post office in To line Delete the post office qualifier or select the user from the Addre
235. ion Possible Cause Group Wise engine administration engine Record not found Cannot find a record that was previously in the database The record might have been deleted 118 GroupWise 7 Troubleshooting 1 Error Messages Action Action Action Check Pending Operations to see if the command is still awaiting execution See Pending Operations in System in the GroupWise 7 Administration Guide Retry the command Make sure the record was replicated throughout the system See Synchronizing Database Information in Databases in the GroupWise 7 Administration Guide DBOB Required field empty Source Explanation Possible Cause Action GroupWise engine administration engine Required field empty A required field has no value Supply a value for all required fields DBOC Cannot close database Source Explanation Possible Cause Action Group Wise engine administration engine Error closing database An error was encountered while attempting to close the database Check the network connection to the database location DBOE Insufficient memory to initialize database Source Explanation Possible Cause Action Group Wise engine administration engine Database initialization failure The database failed to initialize because of insufficient memory ConsoleOne requires at least 500 KB of available RAM Check the amount of available memory and reconfigure your
236. ion Guide D713 Database dictionary not found Source Explanation Possible Cause Action Group Wise engine directory services access Dictionary not found A database create request was made and the corresponding database dictionary file was not found Make sure the ngwguard dc file exists in the post office directory If it does not copy it from the po subdirectory of your software distribution directory For the specific locations of this file see Post Office Directory and Software Distribution Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure D714 User database temporarily disabled Source Explanation Possible Cause Action Action Group Wise engine directory services access The administrator has temporarily disabled Group Wise login for a specific user The user is being moved from GroupWise 5 x to 7 Wait for the move to be completed If the problem persists rebuild the user database userxxx db See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide D715 User has failed in too many login attempts login disabled Source Explanation Possible Cause Action Action Group Wise engine directory services access The Intruder Lockout feature is preventing the user from logging in A valid user is using an incorrect password or an intrud
237. ipient information A Remote user sent a message using a personal group that exists in the user s master mailbox but has not been downloaded to Remote Download the personal group D043 Inconsistent distribution list Source Explanation Possible Cause Action 88 GroupWise 7 Troubleshooting 1 Group Wise engine Information in the distribution list does not match information elsewhere in the system Outdated information in a distribution list a damaged distribution list or a damaged message file could cause this error from the POA Check the priority subdirectories of the wpcsout ofs directory in the post office Check the POA log file to determine the offending message file See Using POA Log Files in Post Office Agent in the GroupWise 7 Administration Guide Determine the originator of the offending message Check and if necessary repair the user database user xxx db for that user Error Messages Action Possible Cause Action Action See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide The POA has been started with the norecover startup switch and damage to a user or message database has been detected Repair the database See Maintaining User Resource and Message Databases in Data
238. irectory Structure C0xx Memory error Source Explanation Action GroupWise engine database services Generic memory error Retry the operation that caused the error If it occurs again restart GroupWise If it occurs again it might be necessary to run GroupWise in an environment with more available memory C0xx Unexpected error Source Explanation Action GroupWise engine database services An engine error has occurred for which GroupWise does not have a specific error message Exit and then restart the GroupWise client 6 10 COxx Unexpected Error e COxx Unexpected error on page 78 C0xx Unexpected error Source Explanation Action 78 GroupWise 7 Troubleshooting 1 Group Wise engine database services An engine error has occurred for which GroupWise does not have a specific error message Exit and then restart the GroupWise client Error Messages Dxxx Engine Error Codes D00x Errors on page 79 DO1x Errors on page 82 D02x Errors on page 84 D03x Errors on page 87 D04x Errors on page 88 D05x Errors on page 90 D06x Errors on page 93 D07x Errors on page 96 D10x Errors on page 98 D11x Errors on page 103 D12x Errors on page 106 D20x Errors on page 107 D50x Errors on page 107 D70x Errors on page 109 D71x Errors on page 111 D9xx Errors on page 113 DAOx Errors on page 114 D
239. is archived 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 Explanation Possible Cause Action GroupWise engine document management Lookup table not empty Cannot delete the lookup table because it is not empty Delete all entries from the lookup table then retry the operation See Customizing Document Properties in Libraries and Documents in the GroupWise 7 Administration Guide for information about lookup tables E526 Cannot delete lookup table it is in use Source Explanation Possible Cause Action GroupWise engine document management Lookup table in use by a library The lookup table cannot be deleted because it is being used by a library Remove all library references to the lookup table then retry the operation See Customizing Document Properties in Libraries and Documents in the GroupWise 7 Administration Guide for information about lookup tables E527 Cannot create library record already exists Source Explanation Action GroupWise engine document management Library already exists Use a unique library name to create the library See Creating and Managing Libraries in Libraries and Documents in the GroupWise 7 Administration Guide E528 Cannot transfer data to server Source Explanation Possible Cause
240. is not usable The certificate file is damaged Obtain a usable certificate file See Server Certificates and SSL Encryption in Security Administration in the GroupWise 7 Administration Guide 38 GroupWise 7 Troubleshooting 1 Error Messages 8920 SSL certificate and private key do not match Source Explanation Possible Cause Possible Cause Action GroupWise engine TCP IP communication A GroupWise agent cannot establish an SSL connection because the SSL certificate file and the public key file cannot be used together One of the files is damaged You are trying to use a certificate file and a public key file that were not generated for use together Obtain usable files See Server Certificates and SSL Encryption in Security Administration in the GroupWise 7 Administration Guide 8921 SSL accept failure Source Explanation Possible Cause Action GroupWise engine TCP IP communication A GroupWise agent cannot establish an SSL connection because the handshake negotiation between the two servers failed Both servers might have identical certificate files Obtain a new certificate file for one of the servers See Server Certificates and SSL Encryption in Security Administration in the GroupWise 7 Administration Guide 8922 SSL connect failure Source Explanation Possible Cause Action Possible Cause Action GroupWise engine TCP IP communica
241. ise 7 Administration Guide Change the LDAP port for one of the POAs 2 4 88xx Errors 8809 Unexpected error on page 31 880B Unexpected error on page 31 e 880C Unexpected error on page 31 8809 Unexpected error Source GroupWise engine inter or intra process communication Action See 8xxx Unexpected error on page 42 880B Unexpected error Source GroupWise engine inter or intra process communication Action See 8xxx Unexpected error on page 42 880C Unexpected error Source GroupWise engine inter or intra process communication Action See 8xxx Unexpected error on page 42 2 5 89xx Errors 8901 Cannot use TCP IP services on page 32 8xxx Engine Error Codes 31 e 8902 Cannot load TCP IP services on page 33 e 8903 Cannot use TCP IP services on page 33 e 8906 Cannot use TCP IP services on page 33 8907 Cannot use TCP IP services on page 33 8908 Cannot connect to specified address on page 33 8909 Cannot use TCP IP services on page 34 e 890A Cannot listen on specified port on page 34 e 890B Cannot accept incoming connection on page 34 e 890F Connection no longer valid on page 34 8910 Cannot read on connection on page 35 8911 Cannot write on connection on page 35 8912 Cannot read on connection timed out on page 35 8913 Cannot write on connection timed out on page 35
242. ise system for external synchronization with that system See Exchanging Information Between Systems in Connecting to GroupWise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide The external synchronization record in the domain database has been damaged Delete the external synchronization record In ConsoleOne click Tools gt GroupWise System Operations gt External System Synchronization Select an external system then click Delete gt Close Exit and restart the MTA and POA Re create the external synchronization record See Exchanging Information Between Systems in Connecting to GroupWise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide DB4B Cannot delete Internet domain name that is still referenced Source Explanation Possible Cause Action Group Wise engine administration engine The specified Internet domain name is being referenced in a system domain post office or user You are trying to delete an Internet domain record that is still in use Change or delete the Internet domain association See Configuring Internet Addressing in System in the GroupWise 7 Administration Guide DB4D Database recovery required to update database structure Source Explanation Possible Cause Action Group Wise engine administration engine The database needs to be recovered The database dictionaries dc files
243. ish the connection to the post office directory and make sure the WebAccess Agent has sufficient rights See WebAccess Security Requirements in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide The WebAccess Agent lost its TCP IP connection to the Post Office Agent POA Make sure the Post Office Agent is up and running and that TCP IP is configured properly on the servers running the WebAccess Agent and Post Office Agent See Managing Access to Post Offices in WebAccess in the GroupWise 7 Administration Guide The WebAccess Agent s post office link information is not defined correctly in Novell eDirectory Check the post office link information See Modifying Links to Post Offices in WebAccess in the GroupWise 7 Administration Guide WEBACC Conversation timed out Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent automatically logs a user out of Group Wise if he or she does not use GroupWise WebAccess for a certain period of time the timeout interval This message indicates that the GroupWise WebAccess user s session has timed out The GroupWise WebAccess user did not perform any actions in GroupWise WebAccess during the timeout interval Have the user log in again Lengthen the timeout interval See Creating a Class of Service in WebAccess in the GroupWise 7 Administration Guide WEBACC Could not st
244. ks exist The gateway you are attempting to delete is used in a gateway link Reconfigure the links before deleting the gateway See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide DB41 Database does not match domain or post office Source Explanation Possible Cause Action Group Wise engine administration engine Incorrect database path The database found at the specified path does not match the specified domain post office name Enter the correct path DB42 Information lost during recovery Source Explanation Possible Cause Action Group Wise engine administration engine Information lost Some records were lost during the recover operation You might want to rebuild the database at this time See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide DB43 Maximum number of open post offices reached Source Explanation Possible Cause Action Group Wise engine administration engine Maximum number of post offices are opened You have tried to open too many post offices Close one or more post offices See Disabling a Post Office in Post Offices in the GroupWise 7 Administration Guide DB45 GroupWise system not found Source Explanation Action Action Group Wise engine administration engine No system found Verify the path to the domain database wodomain db Make sure y
245. l com forums 2gw html e Novell Group Wise Support Community http support novell com products groupwise Group Wise Cool Solutions http www novell com coolsolutions gwmag index html Client Error Messages 267 268 GroupWise 7 Troubleshooting 1 Error Messages Windows Client Error Messages Users might encounter two types of errors while using the GroupWise Windows client e Errors the User Can Resolve on page 269 Errors the Administrator Must Resolve on page 269 Errors the User Can Resolve Explanation When a GroupWise Windows client error can be fixed immediately by the user the error message includes instructions Action The user resolves the problem independently Errors the Administrator Must Resolve Explanation When a GroupWise Windows client error cannot be resolved by the user it is typically accompanied by a GroupWise engine error code See GroupWise Engine Error Codes on page 11 Action Look up the error code in GroupWise Engine Error Codes on page 11 then resolve the problem for the user Windows Client Error Messages 269 270 GroupWise 7 Troubleshooting 1 Error Messages Remote Mode Windows Client Error Messages A previous request to retrieve items has not been completed on page 271 Cannot access your Master Mailbox on page 271 Cannot find the post office on page 272 Cannot find the post office in the specified path on page 272 Can
246. lanation The MTA is unable to contact the SNMP agent on the server where the agent is running Possible Cause SNMP has not been installed and set up properly on the server Action Install SNMP as required by the server operating system GWMTA Unable to retrieve TCP IP address Source GroupWise Message Transfer Agent Explanation The MTA is configured for GWMTP between Group Wise systems but the MTA cannot find the Domain name of the destination system Possible Cause GWMTP is not properly set up between the two GroupWise systems Action Correct any problems in the setup of links between the two systems See Using Dynamic Internet Links in Connecting to GroupWise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide GWMTA Undefined link Source GroupWise Message Transfer Agent last closure reason Explanation MTAs cannot communicate because no link has been established between them Action Configure a link between the MTAs See Changing the Link Protocol between Domains in Configuring the MTA in the Group Wise 7 Administration Guide GWMTA Unknown connection header received Source Group Wise Message Transfer Agent message transfer protocol Explanation The MTA received a reguest for a TCP IP connection from a process other than a Group Wise agent Possible Cause Some non GroupWise program on the server where the MTA is running is configured to send packets to the
247. lete Action Reinstall the NetWare client 0042 Cannot authenticate to requested tree Source GroupWise Administrator eDirectory operation Explanation GroupWise was unable to authenticate to the requested tree Action Make sure you have proper rights Contact the system administrator 0045 Domain database not found Source GroupWise Administrator class definition 244 GroupWise 7 Troubleshooting 1 Error Messages Explanation You are not currently connected to a GroupWise domain database wpdomain db The requested operation cannot be completed Action Connect to an existing GroupWise domain See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide 0049 Cannot move user from 6 x post office to 4 x post office Source GroupWise Administrator 6 x to 4 x move Explanation GroupWise does not support moving users from a GroupWise 6 x or 7 post office to a GroupWise 4 x post office Action You might want to consider migrating your 4 1 system to GroupWise 5 0053 Parent domain database not found Source GroupWise Administrator visitor base Explanation GroupWise was unable to locate the domain database wodomain db for the requested action The network resource is unavailable Action Retry the operation 0054 Invalid drive specification Source GroupWise Administrator visitor base Explanation GroupWise is unable to determine a local path from the drive specification Actio
248. log of messages and is not accepting any additional messages into its queues The MTA processes existing messages first before processing new messages so that messages arrive in the order in which they were sent Possible Cause The backlog of messages might have been caused by one or more closed facilities in the domain 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 mslocal directory GWMTA Unable to initialize message log database Source GroupWise Message Transfer Agent message transfer protocol Explanation The MTA was unable to create the database where it stores information about messages waiting for processing in its in progress gwinprog queue the msglog subdirectory of mslocal cannot be created Possible Cause Insufficient disk space Action Free up disk space on the server where the MTA runs GWMTA Unable to open connection no response Source GroupWise Message Transfer Agent message transfer protocol Explanation The MTA is attempting to communicate with another MTA or a POA by way of TCP IP but the other agent does not answer 212 GroupWise 7 Troubleshooting 1 Error Messages 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 Exp
249. ly accompanied by a GroupWise engine error code See GroupWise Engine Error Codes on page 11 Action Look up the error code in GroupWise Engine Error Codes on page 11 then resolve the problem for the user 20 2 Cross Platform Client Errors The following are a few error messages specific to the Cross Platform client e Can t export to file on page 277 Error during updating mailbox on page 278 e Failed to create directory on page 278 Can t export to file Source GroupWise Cross Platform client Linux or Macintosh Possible Cause You have tried to save a message or attachment in a location where you do not have sufficient rights to perform the action Action Choose a different directory Action Obtain rights to the desired directory Cross Platform Client Error Messages 277 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 on Linux in Databases in the GroupWise 7 Administration Guide Failed to create directory Source GroupWise Cross Platform client Linux or Macintosh Possible Cause You have tried to create a Caching mailbox or an archive in a location where you do not have sufficient rights to perform the action Action
250. m Set up the path for the specified post office in the post office Identification page in ConsoleOne To start the GroupWise client in direct mode use the ph switch to provide the path to the post office If you want to use client server mode you can set up an additional POA to handle client server communication See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide D055 Cannot connect to specified post office Source Explanation Possible Cause Action Group Wise engine Cannot use direct mapped connection The post office rejected the direct mode connection but is allowing client server mode Make sure the IP address for the POA is set up correctly See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide D057 Cannot connect to any post office Source Explanation Possible Cause Possible Cause Action Possible Cause Action Group Wise engine TCP IP default address failed An attempt to connect to a post office using the GroupWise IP address defaults NGWNAMESERVER and NGWNAMESERVER2 was unsuccessful No client server or direct information was specified or available Make sure the GroupWise name server is properly set up and running See Simplifying Client Server Access with a GroupWise Name Server in Post Office Agent in the GroupWise 7 Adm
251. ment storage area is located 74 Unable to move all blobs storage area cannot be removed Source Explanation Possible Cause Action Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot delete the specified storage area because BLOBs still exist in it Insufficient disk space Make sure there is free disk space in the directory where you are trying to move the BLOBs to Insufficient rights Make sure you have rights to the directory where the document storage area is located 75 Unable to move blob Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot move the specified BLOB file Insufficient disk space Make sure there is free disk space in the directory where you are trying to move the BLOBs to 262 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Insufficient rights Make sure you have rights to the directory where the document storage area is located 76 Error accessing document content Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot read the content of the specified document The library database dmsh db is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 77 Error accessing blob for official version distr
252. message database in the User Resource field See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Action For additional information look up the associated engine error code in Part I GroupWise Engine Error Codes on page 11 41 All substitute filenames used for rename of database Source GroupWise Check utility GWCheck Explanation GWCheck uses file extensions dba through dbz for backup copies of databases All valid backup database names have already been used Action Delete old backup databases so valid backup extensions are available GroupWise Check Error Codes 257 42 Invalid database truncated to nn bytes Source Explanation Action Action Action Group Wise Check utility GWCheck The database has been modified externally to an illegal size Perform a structural rebuild on the user database See Performing a Structural Rebuild of a User Database in Databases in the GroupWise 7 Administration Guide Perform a structural rebuild on the user s message database by supplying the name of the message database in the User Resource field See Analyzing and Fixing User and Message Databases in Databases in the GroupWise 7 Administration Guide Restore the database from backup 43 Dictionary file missing cannot continue Source Explanation Action Group Wise Check utility GWCheck The specified dat
253. n Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Action Source Explanation Possible Cause Possible Cause Action Action offices see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Check the ownership of the Group Wise databases If necessary change the ownership to a valid user such as the system administrator 8206 Cannot open file Group Wise engine file input output File open error Group Wise cannot copy the specified file During an explicit file copy function failure to create the destination file generates this error If the destination file exists and is read only this error might occur Check destination filename specified and ensure it is unique If this error occurs the first time a user tries to archive messages the user might not have sufficient rights to the archive location Check the user s rights to the archive location Grant the user the rights necessary to create the archive or suggest a location where the user already has sufficient rights to create the archive If this error occurs when updating the GroupWise client software users might be running the client software Perform the update when no one is using the GroupWise client or send a broadcast message asking all users to exit so you can update th
254. n Databases in the GroupWise 7 Administration Guide For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 20 User record has no DS_DOMAIN_NAME Source Explanation Action Group Wise Check utility GWCheck GWCheck encountered an invalid user record in the post office database wphost db In ConsoleOne rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide 21 Unable to decrypt database Source Explanation Action GroupWise Check utility GWCheck GWCheck encountered an invalid user record in the post office database wphost db In ConsoleOne rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide 23 Unable to rename file for rebuild backup Source GroupWise Check utility GWCheck GroupWise Check Error Codes 253 Explanation Possible Cause Action Possible Cause Action Possible Cause Action GWCheck cannot create a backup copy of the existing database All valid backup database filenames have already been used Check for existing backup databases with extensions dba through dbz If all 26 backup extensions have been used delete old backup databases so valid backup extensions are available Insufficient disk spa
255. n Enter a valid path 0056 Non networked drive Source GroupWise Administrator visitor base Explanation You are attempting to create a GroupWise domain or post office on a non networked location that might become unavailable Action You should create domains and post offices where network users will have permanent access to them 0057 Cannot create another agent of this type in this context Source GroupWise Administrator visitor base Explanation Agents are limited based on context For example only one MTA per domain can exist The maximum number of this agent type already exist in this context Action You cannot create another agent of this type in the selected context 0059 Cannot create another GroupWise object Source GroupWise Administrator visitor base Explanation You are running a limited evaluation version of GroupWise This GroupWise system is limited to one domain and two post offices with a maximum of three users on each post office GroupWise Administrator Snap In to ConsoleOne Error Messages 245 Action You can upgrade this evaluation software by purchasing and installing the shipping version of Group Wise 0065 Cannot open domain database Source Explanation Possible Cause Action Possible Cause Action GroupWise Administrator system wide operations The domain database wodoma in db from which GroupWise Administrator is reading information has become unavailable The orig
256. n click Edit Verify the password displayed in the Remote Profile dialog box Path to Post Office for Network Connections To check the path to the post office in ConsoleOne right click the Post Office object then click Properties Verify the path displayed in the post office Identification page IP Address and Port for TCP IP Connections To check the IP address and port in ConsoleOne double click the Post Office object to connect to right click the POA object then click Properties In the Network Address box click Edit Verify the IP address and TCP port displayed in the Edit Network Address dialog box Some setup files are missing Source GroupWise Windows client Remote mode Possible Cause Some of the files needed to run the GroupWise client against your Remote mailbox are missing These files might have been deleted inadvertently Action Reinstall GroupWise on your computer See Installing the GroupWise Windows and Cross Platform Clients in the GroupWise 7 Installation Guide The following information necessary to run GroupWise against Action GroupWise Windows client Remote mode Possible Cause Hit the Road sets up your Remote mailbox with all the needed setup information If you didn t use Hit the Road this message appears the first time you run the GroupWise client against your Remote mailbox after a new installation Action Verify the necessary information Full Name e User ID e Master Mailbox P
257. n dotted numeric format 172 16 5 18 rather than as a host name that requires resolution when setting the ipa switch When using direct mode rather than client server the GroupWise client still requires a valid winsock dll to be available on the search path Make sure a current valid winsock d11 file is available on the workstation where the problem is occurring The GroupWise client cannot establish a TCP IP connection with the POA Check the IP address for the POA See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide Check the status of the POA server and the load on the network 8xxx Engine Error Codes 33 Possible Cause Action Possible Cause Action Action If this error appears in the Message Transfer Status box of the POA the MTA to which it is transferring messages is not running Check the status of the MTA for the domain Restart the MTA if necessary If this error occurs from the GroupWise Internet Agent the Internet Agent might not be able to establish a TCP IP connection to the POA Check the post office link set up for the Internet Agent In ConsoleOne click the domain where the Internet Agent is installed Right click the Internet Agent object then click Properties Click Post Office Links select the post office then click Edit Link Make sure the IP address and TCP port for the POA are specified correctly in the Client Serv
258. n now closed on page 204 Incompatible GWENV1A DLL GWMTA cannot continue on page 204 Insufficient disk space on page 204 Insufficient memory on page 205 Insufficient memory to read process startup file on page 205 Insufficient resources to accept inbound connection on page 205 Insufficient system resources on page 206 e GWMTA Internet mail to address is undeliverable because no default GWIA is configured on page 206 e GWMTA Invalid log parameter on page 206 e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA Invalid work parameter on page 206 Link or transport down on page 207 Logging permanently suspended insufficient memory on page 207 Login not completed timeout on page 207 Login to directory failed on page 207 Maximum number of inbound connections reached on page 208 No agent record found on page 208 No domain record found on page 208 No path configured on page 209 No post offices found on page 209 No response from peer on page 209 No sender IDomain Internet address lookup not attempted on page 209 Path to domain database home is invalid or blocked on page 209 Post office database open failed insufficient memory on page 210 Post of
259. n the GroupWise 7 Administration Guide 250 GroupWise 7 Troubleshooting 1 Error Messages 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 Explanation Action Action Action Group Wise Check utility GWCheck The specified database is locked or otherwise inaccessible Retry There might have been a timing problem with another database user See if another program such as the POA has the database open with exclusive access and has hung with the database open For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 12 Record failed commit Source Explanation Action Action Action Group Wise Check utility GWCheck GWCheck cannot write a modified record back to the database Retry There might have been a timing problem with another database user See if another program such as the POA has the database open with exclusive access and has hung with the database open For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 13 Record failed modify Source Explanation Possible Cause Action Action Possible Cause Action Action Action Group
260. n the GroupWise client the user dragged away all the column headings Restore the column headings Right click the bar where the column headings belong then select the column headings such as From Subject and Date from the drop down list If this error occurs when creating a post office you might not be connected to the correct domain If you try to create a post office in a secondary domain while connected to a different domain you might not have sufficient rights to create the post office correctly It might show up in the GroupWise View but not have a Novell eDirectory object created for it Connect to the secondary domain See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide Then graft the post office into the correct domain See GW eDirectory Association in System in the GroupWise 7 Administration Guide If this error occurs when deleting a Library object representing a remote document storage area the remote document storage area and its directory might have already been deleted In ConsoleOne display the GroupWise View Right click the Library object then click Properties Remove the path to the document storage area that no longer exists Select Store Documents in Post Office then click OK Then delete the library object from the GroupWise View C007 Database error Source Action GroupWise engine database services See COxx Database error Support as
261. name and overwrite the existing file open the Modem Connection dialog box then click Edit Script Remote Mode Windows Client Error Messages 275 Specify the script information then click Save Otherwise select a different script filename filename ext failed to open Source GroupWise Windows client Remote mode Possible Cause This usually occurs because the script file is in use by another application or access to the file is restricted Action Select a different filename or open the Modem Connection dialog box Click Edit Script enter the script information then click Save As 276 GroupWise 7 Troubleshooting 1 Error Messages Cross Platform Client Error Messages e Section 20 1 General GroupWise Client Errors on page 277 e Section 20 2 Cross Platform Client Errors on page 277 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 on page 277 Errors the Administrator Must Resolve on page 277 Errors the User Can Resolve Explanation When a GroupWise Cross Platform client error can be fixed immediately by the user the error message includes instructions Action The user resolves the problem independently Errors the Administrator Must Resolve Explanation When a GroupWise Cross Platform client error cannot be resolved by the user it is typical
262. names first See Email Address Lookup in System in the GroupWise 7 Administration Guide DB57 Specified e mail address conflicts with the address of an existing user Source GroupWise engine administration engine Possible Cause You are creating modifying or moving a user in such a way that its new name conflicts with an existing user name 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 administration engine Possible Cause You are creating or modifying a post office alias in such a way that its new name conflicts with an existing post office alias Action Choose a different name for the new post office alias Check for existing names first See Email Address Lookup in System in the GroupWise 7 Administration Guide DB59 This GroupWise administration version is older than the minimum allowed by the system administrator Source GroupWise engine administration engine Explanation Although you can start ConsoleOne the GroupWise snap ins are out of date Possible Cause In ConsoleOne the Lock Out Older GroupWise Administration Snapins option has been selected under Tools gt GroupWise System Operations gt System Preferences gt Admin Lockout Settings and you are tryi
263. nation Out of memory error Action Free up memory then try the operation again 0019 Cannot map local drive to network resource Source GroupWise Administrator connection ID Explanation GroupWise is unable to map a local drive to the network resource Action Make sure the UNC specification is correct that you have drives available to map and that you have access to the network resource requested 001D Cannot add non GroupWise account to library membership Source GroupWise Administrator document management Explanation You cannot grant library membership to a user that does not have a GroupWise account Action Add the user to GroupWise See Creating GroupWise Accounts in Users in the GroupWise 7 Administration Guide 0021 Gateway setup file not found Source GroupWise Administrator gateway setup Explanation A file required to run the gateway specific setup was missing Possible Cause The gateway installation was incomplete Action Reinstall the gateway For a list of gateways see GroupWise Gateways http www novell com documentation gwgateways 0022 Cannot assign non GroupWise user as administrator Source GroupWise Administrator gateway setup Explanation The gateway administrator must be either a GroupWise user or a GroupWise distribution list Action Select a valid GroupWise user or distribution list as the gateway administrator For a list of gateways see GroupWise Gateways http www nov
264. ncorrect Source Explanation Action GroupWise Administrator temporary password Passwords do not match Enter the correct password 246 GroupWise 7 Troubleshooting 1 Error Messages 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 GWCheck fixes these problems for you This section contains information about the following numeric codes which are GWCheck error codes 01 Memory initialization error on page 249 02 WPHOST DB database read error on page 249 03 Record read error on page 249 04 User record has no DS HOST NAME on page 249 e 05 User record has no DS OBJ TYPE on page 249 e 06 User record has no DS FID on page 249 e 07 User record has no DS USER NETID on page 250 e 08 User database read error on page 250 09 Message database read error on page 250 10 Message record read error on page 250 11 Unable to start database transaction on page 251 12 Record failed commit on page 251 13 Record failed modify on page 251 14 Record delete failed commit on page 251 15 Record failed delete on page 252
265. nder Action See F0xx Database error index on page 177 F084 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 170 GroupWise 7 Troubleshooting 1 Error Messages F085 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F086 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F087 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F088 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F089 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FO8A Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F08B Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 FO8D Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FO8E Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 FO8F Database error Source GroupWise engine QuickFinder Action See F0xx Database error index
266. ne Error Messages 239 e 0069 Outbound MTA platform undefined on page 246 e 00A2 Cannot set rights on software distribution directory on page 246 e 0102 Password incorrect on page 246 0001 Cannot load resource Source Explanation Possible Cause Action GroupWise Administrator general snap in Unable to load resource DLL Invalid NWLANGUAGE environment specification Make sure the NetWare client is set up properly on the workstation where you are running ConsoleOne 0002 Schema not properly defined Source Explanation Possible Cause Action Possible Cause Action GroupWise Administrator general snap in Schema error The GroupWise schema extensions are not present When you install GroupWise the tree you are currently logged in to is extended After installation you run ConsoleOne and change to a tree that has not been extended Log in to the tree you want extended then rerun the installation to extend the schema on the second tree See Setting Up a Basic GroupWise System in the GroupWise 7 Installation Guide GroupWise installation did not complete successfully Run Install from the root directory ofthe GroupWise Administrator CD See Setting Up a Basic GroupWise System in the GroupWise 7 Installation Guide 0003 Required DLL has incorrect version Source Explanation Possible Cause Action GroupWise Administrator general snap in DLL version
267. network error TCP IP services couldn t be used It is possible that TCP IP isn t loaded correctly on the server Group Wise has encountered unusually long timeouts while trying to retrieve names from DNS This probably occurred in Windows where the workstation is not connected to the network Check the network connections for the workstation 8917 TCP IP name lookup failed Source Explanation Possible Cause Action Action GroupWise engine TCP IP communication A GroupWise agent or client cannot ping the specified IP address The agent or client was passed an invalid IP address 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 Determine what the correct IP address should be 8918 UDP send failed Source Explanation Possible Cause Action Group Wise engine TCP IP communication The GroupWise agent cannot write to the specified UDP socket port The server that the agent is running on is not functioning normally Restart the server 8919 Attempt to bind to a non existent IP address Source Explanation Possible Cause Action GroupWise engine TCP IP communication The GroupWise agent cannot locate the specified IP address to set up an exclusive bind on it The agent is configured to bind to an IP address but that IP address is not available on the server where the agent is running Dete
268. nexpected error on page 147 E801 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E803 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E804 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E805 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E806 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E807 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E808 Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E809 Unexpected error Source GroupWise engine object framework 146 GroupWise 7 Troubleshooting 1 Error Messages Action See Exxx Unexpected error on page 157 E80C Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E80D Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 E80F Unexpected error Source GroupWise engine object framework Action See Exxx Unexpected error on page 157 8 6 E81x Errors e E
269. ng closing brace in distribution list Source Explanation Possible Cause Action Group Wise engine No closing brace Mismatched braces in the distribution list While processing the To CC and BC addresses in a message the end of the input buffer was reached before finding the closing brace Check the address for incorrect use of braces then resend the message D028 Lost attachment Source Explanation Possible Cause Action Group Wise engine Attachment could not be associated with a message The attachment pointer was damaged Resend the message D029 Recipient not specified Source Explanation Possible Cause Action Group Wise engine No distribution list for a delegate rule No recipient has been specified in a delegate rule The delegate rule must contain a valid user ID to which to delegate the item This error might indicate the user who sees the message or some other user has an incorrect delegate tule Make sure the delegate rule contains a valid distribution list Look up rules in Group Wise client Help D02A Name for group not specified Source Explanation Possible Cause Action Group Wise engine No group name No name has been specified for the distribution list Enter a unique group name 86 GroupWise 7 Troubleshooting 1 Error Messages DO2F Database error Source Explanation Possible Cause Action Action GroupWise engine No doc
270. ng to run ConsoleOne with a version of the snap ins that is too old Action Update the GroupWise snap ins See ConsoleOne in Installing a Basic GroupWise System in the GroupWise 7 Installation Guide 7 25 DB6x Errors DB60 The LDAP server is being used for eDirectory synchronization on page 134 DB61 The signature information is too large on page 135 DB62 The software area is being referenced on page 135 DB63 Following a database rebuild the ownership of the target file has been changed The file uid run must be deleted manually on page 135 DB60 The LDAP server is being used for eDirectory synchronization Source GroupWise engine administration engine 134 GroupWise 7 Troubleshooting 1 Error Messages Explanation An MTA that performs eDirectory user synchronization obtains its eDirectory information from a server that is also being used in your GroupWise system as an LDAP server Possible Cause You are trying to delete an LDAP server that is being used for eDirectory user synchronization as well as for LDAP Action Reconfigure eDirectory synchronization See Using eDirectory User Synchronization in Message Transfer Agent in the GroupWise 7 Administration Guide Then delete the LDAP server 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
271. nication Cannot open connection to specified address See 8908 Cannot connect to specified address on page 33 8509 Cannot access TCP IP services Source Explanation Possible Cause Action Action GroupWise engine general communication TCP IP bind failed TCP IP is not loaded on the server or is not loaded correctly The TCP port is already in use by another process Configure TCP IP on the server correctly If this error occurs on a NetWare server make sure you have the latest version of the TCPIP NLM For technical services and file updates see Novell Support http support novell com Reboot the server 850F Connection no longer valid Source Explanation Possible Cause Action 8555 Port in use Source Explanation Possible Cause GroupWise engine general communication Connection was broken while in use A client or server machine has crashed or the process was forced to close without shutting down The machine might have been exited while connections were active Exit and restart GroupWise when the machine is back up GroupWise engine general communication Port in use 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 28 GroupWise 7 Troubleshooting 1 Error Messages Action Action Possible Cause Action Possible Cause
272. nnot proceed incompatible GWENN5 NLM Source Explanation Possible Cause Action Possible Cause Action NetWare GroupWise Message Transfer Agent The MTA cannot start because the agent engine gwenn5 n1m is not compatible with the MTA itself gwmta n1m Some agent files have been updated but the update is not complete When updating the agents make sure all agent files are installed For a complete list of files see Agent Installation Directories in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure The agent engine gwenn5 n1m was not unloaded prior to updating the agent software The agent software cannot be successfully updated if the agent engine is still loaded After exiting all the agents unload the gwenn5 n1m then perform the update See the Updating Secondary Domains in Updating Your GroupWise 6 x System to Version 7 in the GroupWise 7 Installation Guide GWMTA Cannot proceed insufficient memory available Source Action Group Wise Message Transfer Agent See GWMTA Insufficient memory on page 205 GWMTA Cannot read domain database insufficient memory Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA cannot access its domain database wpdomain db Insufficient memory See GWMTA Insufficient memory on page 205 The domain database has been damaged Rebuild th
273. not create the new user database Delete the residual user database then move the user back into the post office See Moving GroupWise Accounts in Users in the GroupWise 7 Administration Guide CO5D Cannot open database file Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Action Group Wise engine database services Store file not found GroupWise cannot open a file associated with a multi file database For example one of the dependent databases listed in ngwguard db has been deleted Restore the missing database from backup If this error occurs when users send mail the message database msgnnn db to which the users belong might be missing If the message database cannot be restored from backup perform a structural rebuild on the user s experiencing the problem See Performing a Structural Rebuild of a User Database in Databases in the GroupWise 7 Administration Guide This will create a new empty message database Old messages will no longer be available to the affected users If the message occurs for only a single user that user s user database userxxx db might be missing If the user database cannot be restored from backup re create the user database See Re creating a User Database in Databases in the Group Wise 7 Administration Gu
274. not find your remote Mailbox folder on page 272 Cannot log in to the gateway Check the gateway login ID on page 272 Cannot log in to the gateway Check the gateway login password on page 273 LDAP failure detected on page 273 Required information is missing from the connection on page 273 Some setup files are missing on page 274 The following information necessary to run GroupWise against on page 274 The master Group Wise system is unable to process a request on page 274 The master GroupWise system is unable to process your current on page 275 This item uses a custom view that was not retrieved on page 275 This transmission cannot be completed due to network problems on page 275 Unable to create folder on page 275 filename ext could not be opened as a modem script file on page 275 filename ext failed to open on page 276 A previous request to retrieve items has not been completed Source GroupWise Windows client Remote mode Possible Cause Because requests sent to the master GroupWise system are processed and then returned to your Remote mailbox there are times when your Remote mailbox waits for responses from the master system Ifthis is the case making a new request will duplicate the response that is returned from the previous request resulting in wasted transmission time and possibly long distance charges Action
275. novell com ndk doc gwsoap soap_enu data bs3a3 1o html bs3a3 10 EA11 Maximum event read threads Source Explanation Possible Cause Action GroupWise engine SOAP protocol Your application has started as many event read threads as the POA is configured to service The POA cannot create additional event read threads Your application is issuing more getEvents requests than the POA can respond to Reduce the number of getEvents requests that your application issues at one time For more information see getEvents method http developer novell com ndk doc gwevents evnt_enu data bundmjo html bundmjo EA13 Redirect user to different post office Source Explanation Possible Cause Action GroupWise engine SOAP protocol The specified user does not exist in the specified post office and needs to be redirected in order to log in to GroupWise successfully The user resides in a different post office than your application specified in the login Redirect the user to the correct post office For more information see login method and loginResponse http developer novell com ndk doc gwsoap soap_enu data brx8x54 html brx8x54 Exxx Engine Error Codes 155 EA15 The method called is not supported on this container Source Explanation Possible Cause Action Group Wise engine SOAP protocol The calling method is valid but the container type on which it is being called is not app
276. nt Explanation Error reading post office configuration information Possible Cause An error was detected while reading POA configuration information from the post office database wphost db The post office database might be in an inconsistent state Action Start the POA with noconfig and validate the post office database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide DA12 Invalid application configuration name Source GroupWise engine Post Office Agent Explanation Invalid application name Possible Cause The eDirectory distinguished name DN specified on the command line when starting the POA was invalid The DN might be misspelled Action Specify a valid DN A list of valid DNs for a given post office can be obtained by failing to specify one on the POA command line with the name switch when the system is configured so that one is required You can then choose one from the list A DN must be specified in a system that has been configured to run more than one POA process for a single post office In that case the DN is used by the POA to find configuration information for a specific POA process such as TCP IP address port and other configuration information Dxxx Engine Error Codes 115 DA13 name switch required Source Explanation Possible Cause Possible Cause Action GroupWise engine Post Office Agent Ambiguous application nam
277. nt path to the software distribution directory See Software Directory Management in System in the GroupWise 7 Administration Guide Correct the path as needed Make sure the specified software distribution directory actually exists D709 Unexpected error Source GroupWise engine directory services access Action See Dxxx Unexpected error on page 138 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 Group Wise D70B Database inconsistency detected Source GroupWise engine directory services access Explanation Database invalid or damaged Possible Cause The directory services database wpdomain db or wphost db is inconsistent The identifier used to identify which domain or post office owns this database has been lost Action Ifthe database is a primary domain restore it from backup otherwise rebuild the database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide D70D Unexpected error Source GroupWise engine directory services access Action See Dxxx Unexpected error on page 138 D70E Duplicate entry in database Source GroupWise engine directory services access Explanation Duplicate entry found in database 110 GroupWise 7 Troubleshooting 1 Error Messages Possibl
278. nt will resume disk logging The log file has been damaged so the agent can no longer write to it Remove the damaged log file and turn disk logging back on in the Log Settings page for the agent in ConsoleOne See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide The agent will create a new log file You can also use Cycle Log from the MTA agent console to start a new log file See Cycling the MTA Log File in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA File not found Source Explanation Action Group Wise Message Transfer Agent agent console From the MTA agent console you are trying to edit or view either the MTA log file or startup file and the MTA cannot access it Verify the existence and rights to the file GWMTA Gateway now closed Source Explanation Possible Cause Action Group Wise Message Transfer Agent The MTA has lost its connection to a gateway with which it could previously communicate The server where the gateway is located is currently down Wait for the server to come back up or contact the administrator of that server GWMTA Gateway open failed Source Explanation Possible Cause Action Group Wise Message Transfer Agent The MTA cannot contact a gateway to which a message needs to be routed The MTA cannot access the gateway input queue under the wogate directory of the domain
279. of To line or group Find the user in the To line or Group Either delete the user or find the correct user ID in the Address Book If this error occurs for all users in a post office the post office database might be damaged Rebuild the post office database wohost db See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide If this error occurs in systems where new users are added from multiple administrator workstations preferences might be set differently on different administrator workstations On each workstation where users are added in ConsoleOne click Tools gt GroupWise System Operations gt System Preferences Make sure that the When Creating or Modifying Objects For Network ID Use setting is the same on all workstations If some workstations are set to Full Distinguished Name and some are set to Common Name users will be set up differently depending on which workstation they were created from causing problems when users access Group Wise If this error occurs only when using the GroupWise client in Remote mode the user ID might be specified incorrectly under Remote Options Check the user ID specified in the GroupWise client Look up Remote specifying user and system information in GroupWise client Help Make sure the user ID specified is correct D102 Ambiguous user ID Source Explanation Possible Cause Action Possible Cause Act
280. on Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide If this error occurs in the GroupWise client when accessing archived messages the archive might be damaged In the GroupWise client open the archive then use the Repair Mailbox feature to repair the archive See Enabling GroupWise Check in the Windows Client in Client in the GroupWise 7 Administration Guide Run GWCheck on the user s archive See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide 6 2 C01x Errors C010 Database error on page 59 C011 Database being modified on page 59 C012 Database error on page 59 C013 Index full on page 59 C014 Database error on page 59 C015 Database error on page 59 C016 Database error on page 59 C017 Database error on page 60 C018 Database error on page 60 C019 Database error on page 60 CO1A Database error on page 60 C01B Database error on page 60 CO1C Database error on page 60 COID Database error on page 60 COIE Database error on page 60 C01F Database error on page 60 58 GroupWise 7 Troubleshooting 1 Error Messages C010 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C011 Database being modified
281. on page 198 Cannot proceed insufficient memory available on page 198 Cannot read domain database insufficient memory on page 198 Cannot read post office database insufficient memory on page 198 Cannot route message s out of memory on page 199 Cannot start server insufficient memory available on page 199 Closed for inbound traffic on page 199 Command line parameter home is required on page 199 Could not launch the editor on page 200 Database language has been updated please rebuild this database on page 200 Disk full disk logging turned off on page 200 Domain database error circular transfer domain link on page 200 Domain database error transfer domain not found on page 200 Domain database open failed on page 201 Domain database read error on page 201 Domain now closed on page 201 Domain open failed on page 201 Error initializing HTTP on page 202 Error validating post office members on page 202 Expired en route to destination on page 202 File create error disk logging turned off on page 202 File write error disk logging turned off on page 203 File not found on page 203 Message Transfer Agent Error Messages 193 e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA Gateway now closed on page 203 Gateway open failed on page 203 Host refused connection on page 204 IDomai
282. ontent of the Remote mailbox Delete the rofdata directory on the remote computer then request all information from the master mailbox again Reinstall GroupWise on the remote computer See the platform specific setup instructions for using Remote mode in Setting Up GroupWise Modes and Accounts in Client in the GroupWise 7 Administration Guide If this error occurs in the GroupWise client in the Find Results dialog box the POA has not indexed the documents yet and might not be running Start the POA Check its indexing cycle See Regulating Indexing in Optimizing the POA in the GroupWise 7 Administration Guide After the documents have been indexed the user will be able to use the Find feature in the GroupWise client to access them 6 6 C05x Errors e C050 Transaction aborted on page 69 C055 Unexpected error on page 70 C057 Database maintenance in progress please exit on page 70 C059 Database file already exists on page 70 C05D Cannot open database file on page 71 COSE Unexpected error on page 71 C050 Transaction aborted Source Explanation Possible Cause Action Group Wise engine database services Attempted operation after critical error transaction aborted If this error occurs during domain related activities such as adding users or synchronizing domains the domain database has been damaged Check and if necessary repair the domain datab
283. ooting 1 Error Messages 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 Action None GWCheck deleted the invalid index file 50 Orphaned blob file Source GroupWise Check utility GWCheck Explanation GWCheck encountered a BLOB file that was not associated with any library Action None GWCheck deleted the extraneous BLOB file 51 Invalid blob file Source GroupWise Check utility GWCheck Explanation GWCheck encountered an invalid BLOB file Action None GWCheck deleted the invalid BLOB file 52 Blob file missing trailer Source GroupWise Check utility GWCheck Explanation GWCheck encountered a BLOB file that did not have a trailer Action None GWCheck deleted the invalid BLOB file 53 Blob file truncated to 0 bytes Source GroupWise Check utility GWCheck Explanation The specified BLOB file has been modified externally to an illegal size Action Restore the original BLOB file from backup 61 Error adding system document type definition Source GroupWise Check utility GWCheck Explanation GWCheck cannot add the specified document type definition to the library database dmsh
284. or Messages 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 Explanation Possible Cause Action Action Group Wise Post Office Agent The POA has lost its connection to the server where a document storage area is located The server where the document storage area is located is down Wait for the server to come back up The POA will reconnect automatically when the server is available again Contact the administrator of that server GWPOA Physical connection table full Source Explanation Possible Cause Action Group Wise Post Office Agent TCP agent The POA is configured for TCP IP communication and it has run out of physical connections The POA is very busy Increase the number of physical connections configured for the POA See Adjusting the Number of Connections for Client Server Processing in Post Office Agent in the GroupWise 7 Administration Guide Then exit and restart the POA GWPOA Possibly damaged blob in database Source Explanation Possible Cause Action Action Group Wise Post Office Agent During indexing the POA has encountered a BLOB file that it could not process The BLOB file is damaged Re
285. ormation from the master mailbox again DO3F Database error Source Explanation Possible Cause Group Wise engine No item type The user database userxxx db and or message database msgnnn db for the user have been damaged Dxxx Engine Error Codes 87 Action Action Check and if necessary repair the user and or message databases See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide 7 5 D04x Errors D040 Cannot delete folder used in rule on page 88 D041 No recipients in post office on page 88 D043 Inconsistent distribution list on page 88 e D044 Auto rebuild disabled on page 89 D049 Error reported from Novell NDS on page 89 e D04A Unexpected error on page 89 DO4B Unexpected error on page 89 D04F Unexpected error on page 89 D040 Cannot delete folder used in rule Source Explanation Possible Cause Action GroupWise engine Folder being used in a rule User cannot delete the folder because it is referenced in a rule Change or delete the rule then delete the folder Look up rules in Group Wise client Help D041 No recipients in post office Source Explanation Possible Cause Action Group Wise engine Insufficient rec
286. ort See Using the POA Web Console in Post Office Agent in the GroupWise 7 Administration Guide GWPOA Internal UDP port is unusable Source GroupWise Post Office Agent TCP agent Explanation The POA is configured for TCP IP communication but it cannot access the UDP port 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 GWPOA Listen port already in use Source GroupWise Post Office Agent TCP agent Explanation The POA is configured for TCP IP communication but the port it is configured to listen on is already in use by another program Action See 8555 Port in use on page 28 GWPOA Low disk space for QuickFinder indexing Source GroupWise Post Office Agent Explanation The POA requires at least 20 MB of free disk space to perform QuickFinder indexing This warning appears when disk space drops below 30 MB The POA performs QuickFinder indexing as specified by the QuickFinder Update Interval setting on the POA Agent Settings page in ConsoleOne or as specified using the qfinterval startup switch See Regulating Indexing in Post Office Agent in the GroupWise 7 Administration Guide Action Free up disk space on the server where the POA is running to eliminate the warning See Managing Database Disk Space in Databases in the GroupWise 7 Administration Guide
287. ou are logged in to the server where the GroupWise system resides Dxxx Engine Error Codes 129 DB46 Path too long Source GroupWise engine administration engine Explanation Path too long Action You can map a drive to a lower level DB47 Invalid area Source Explanation Possible Cause Action Group Wise engine administration engine Invalid BLOB area specified ConsoleOne is unable to copy the GroupWise client view files from the software distribution directory into the post office directory structure Make sure the software distribution directory has been created in your GroupWise system See Software Directory Management in System in the GroupWise 7 Administration Guide and Software Distribution Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure DB48 Cannot delete domain that has links Source Explanation Possible Cause Action Possible Cause Action Group Wise engine administration engine System link exists You are trying to delete a domain that is specified as the link domain for an external system Remove the external system or specify a different external domain as the link for the system See Using Direct Links in Connecting to GroupWise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide You are trying to delete a domain that is set up for external system
288. oupWise 7 Troubleshooting 1 Error Messages Action See FOxx Query syntax error on page 176 F022 Missing switch after Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 F023 Word missing between operators Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 F026 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 FO2A Search query must specify words to search for Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 F02D Missing word after operator Source GroupWise engine OuickFinder Action See FOxx Query syntax error on page 176 FO2E Invalid date Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 FO2F Word too long for search Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 9 4 F03x Errors F030 Empty parentheses not allowed on page 163 F037 Memory error on page 164 e FO3E Memory error on page 164 F030 Empty parentheses not allowed Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 Fxxx Engine Error Codes 163 F037 Memory error Source GroupWise engine QuickFinder Action See F0xx Memory error on page 177 FO3E Memory error Source G
289. oupWise to use Fill in the missing information by grafting the objects For information about grafting see GW eDirectory Association in System in the GroupWise 7 Administration Guide 0007 Cannot read required information from GroupWise database Source Explanation Possible Cause Action GroupWise Administrator general snap in Unable to read the required information from the GroupWise database Replication is in progress and has encountered inconsistent data Make sure there are no pending operations See Pending Operations in System in the GroupWise 7 Administration Guide Then rebuild the database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide 0008 Cannot delete subordinate objects Source Explanation Possible Cause Action GroupWise Administrator general snap in Error deleting subordinate objects You do not have rights to delete the subordinate objects Make sure you have access and delete rights to the objects you are attempting to delete 0009 Cannot obtain UNC path Source Explanation Action GroupWise Administrator general snap in UNC path not available Make sure you are logged in to the appropriate network and you have rights to the location 0013 Out of memory Source GroupWise Administrator database management GroupWise Administrator Snap In to ConsoleOne Error Messages 241 Expla
290. ource Group Wise Message Transfer Agent Message Transfer Agent Error Messages 201 Explanation Action The HTTP port the MTA is trying to use for its Web console is not responding correctly Configure the MTA to communicate on a different HTTP port See Using the MTA Web Console in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA Error validating post office members Source Explanation Action Possible Cause Action Group Wise Message Transfer Agent Novell eDirectory user synchronization When attempting eDirectory user synchronization the MTA could not access the user information stored in eDirectory Look up the NetWare error code that accompanies this error at Novell Error Codes http www novell com documentation nwec index html The MTA does not have sufficient rights to access the user information in eDirectory Make sure the MTA is properly set up to perform eDirectory user synchronization See Using eDirectory User Synchronization in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA Expired en route to destination Source Explanation Possible Cause Action Group Wise Message Transfer Agent The MTA was unable to deliver a message because it passed through the maximum of 15 hops without reaching its destination Links between domains are not set up correctly Check the links between domains Look for a
291. p file using the user and password switches If the restore area is on the same server add a trustee assignment to the restore area directory that provides the POA with object file system rights to the directory DO6B LDAP failure detected Source Group Wise engine Explanation GroupWise was unable to authenticate using LDAP Action Make sure your LDAP server is functioning correctly Dxxx Engine Error Codes 95 DOGE Lockout of older GroupWise clients being enforced Source Explanation Possible Cause Action Group Wise engine The POA is not allowing GroupWise client users with older versions of the client software to access the post office The administrator does not want older versions of the Group Wise client to access the post office The client version can be controlled as described in Checking What GroupWise Clients Are in Use in Post Office Agent in the GroupWise 7 Administration Guide GroupWise client users must update their client software before they can access the post office See Updating Users GroupWise Clients in Updating Your GroupWise 6 x System to Version 7 in the GroupWise 7 Installation Guide D06F This GroupWise client doesn t match the user s license Source Explanation Action Action Group Wise engine The GroupWise administrator has restricted client users to the WebAccess client and a user is attempting to access his or her mailbox using
292. page 175 F103 Cannot connect to remote server on page 175 F104 Cannot connect to remote server on page 176 F105 Cannot connect to remote server on page 176 F106 Cannot connect to remote server on page 176 F107 Cannot connect to remote server on page 176 F108 Cannot connect to remote server on page 176 F101 Cannot connect to remote server Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 F102 Cannot connect to remote server Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 F103 Cannot connect to remote server Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 Fxxx Engine Error Codes 175 F104 Cannot connect to remote server Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 F105 Cannot connect to remote server Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 F106 Cannot connect to remote server Source GroupWise engine NetWare remote server connection table Action See F1xx Cannot connect to remote server on page 178 F107 Cannot connect to remote s
293. pecified post office Make sure that the post office exists and that the post office name is correct In ConsoleOne browse to and right click the Post Office object then click Properties DB11 Unexpected error Source Action GroupWise engine administration engine See Dxxx Unexpected error on page 138 DB12 Maximum number of objects per post office reached Source Explanation Possible Cause Action Action Action GroupWise engine administration engine No more file ID combinations exist for the post office The maximum user limit has been reached for this post office The maximum number of FID combinations is approximately 46 000 per post office Delete obsolete users See Removing GroupWise Accounts in Users in the GroupWise 7 Administration Guide Remove unneeded resources See Deleting a Resource in Resources in the GroupWise 7 Administration Guide Create additional post offices See Creating a New Post Office in Post Offices in the GroupWise 7 Administration Guide DB17 Domain already exists in specified directory Source Explanation GroupWise engine administration engine Directory exists 120 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause A domain already exists in the specified directory Action Specify a new domain directory or remove the existing domain See Deleting a Domain in Domains in the GroupWis
294. port for the number of users trying to access the post office 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 Make sure you have all the latest NetWare patches installed If using the Novell IPX IP gateway make sure you have the latest version C023 Database error Source Action GroupWise engine database services See COxx Database error Support assistance recommended on page 77 C024 Database dictionary damaged Source Explanation Possible Cause Group Wise engine database services Database dictionary compromised The database dictionary dc file has been damaged 62 GroupWise 7 Troubleshooting 1 Error Messages Action Make sure the ngwguard dc file exists in the post office directory If it does not copy it from the po subdirectory of your software distribution directory For the specific locations of this file see Post Office Directory and Software Distribution Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Action If this does not solve the problem check and repair the database See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide C026 Database error Source GroupWise engine database services Action See COxx Database error Support a
295. port the MTA is configured to listen on Action Check the network address information of the MTA See Configuring the MTA for TCP IP in Configuring the MTA in the GroupWise 7 Administration Guide Make sure no other programs on the server besides GroupWise agents are configured to use this port GWMTA Unknown destination Source GroupWise Message Transfer Agent Explanation The MTA is unable to route a message because it does not recognize the domain to which it is addressed Message Transfer Agent Error Messages 213 Possible Cause Action Possible Cause Action Possible Cause Action The sender manually typed in an invalid address Have the user select the recipient from the Address Book then resend the message During a reconfiguration of your system a user has addressed a message to a location that either no longer exists or does not exist yet because the reconfiguration information has not yet replicated throughout the Group Wise system Wait until replication is complete The MTA will retry the operation The message has been damaged so that the destination information is no longer readable Remove the damaged message from the MTA input queue so it can process subsequent messages Have the user resend the message GWMTA Waiting for busy listen socket to become available Source Explanation Possible Cause Action GroupWise Message Transfer Agent message transfer protocol
296. r on page 122 DB21 Database inconsistency detected on page 122 DB23 Password incorrect on page 123 DB24 Invalid link on page 123 DB25 Duplicate domain name on page 123 DB26 Secondary domains exist on page 123 DB29 Invalid character on page 123 DB2A Invalid name on page 124 DB2B Non unique entry on page 124 DB2C Invalid post office database on page 124 DB2D Platform error on page 124 DB2E Link record not found on page 125 DB2F Correct database type not found on page 125 DB20 Unexpected error Source GroupWise engine administration engine Action See Dxxx Unexpected error on page 138 DB21 Database inconsistency detected Source GroupWise engine administration engine Explanation Database invalid or damaged Possible Cause The database is invalid 122 GroupWise 7 Troubleshooting 1 Error Messages Action Rebuild the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide DB23 Password incorrect Source GroupWise engine administration engine Explanation Invalid password Action Enter the correct password DB24 Invalid link Source GroupWise engine administration engine Explanation A link between domains is invalid Action Selecta valid link type and link protocol for the domain link See Editing a
297. rary when the user closes the document e A user s workstation went down while the document was open Manually reset the document status Look up document status in Group Wise client Help E503 Unexpected error Source Action GroupWise engine document management See Exxx Unexpected error on page 157 E507 Unexpected error Source Action GroupWise engine document management See Exxx Unexpected error on page 157 E508 Unexpected error Source GroupWise engine document management Action See Exxx Unexpected error on page 157 E50A Unexpected error Source GroupWise engine document management Action See Exxx Unexpected error on page 157 E50B Unexpected error Source Action GroupWise engine document management See Exxx Unexpected error on page 157 E50C Unexpected error Source Action GroupWise engine document management See Exxx Unexpected error on page 157 E50D Maximum number of libraries per post office reached Source Explanation Possible Cause GroupWise engine document management Maximum libraries reached The maximum number of libraries allowed per post office has been reached Each post office can have as many as 256 libraries A user attempted to create the 257th library 140 GroupWise 7 Troubleshooting 1 Error Messages Action Delete any unnecessary libraries on the post office Then create the new l
298. rate actions within a step and items in a cross reference path A trademark symbol z etc denotes a Novell trademark An asterisk denotes a third party trademark When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms the pathname is presented with a backslash Users of platforms that require a forward slash such as Linux should use forward slashes as required by your software When a startup switch can be written with a forward slash for some platforms or a double hyphen for other platforms the startup switch is presented with a forward slash Users of platforms that require a double hyphen such as Linux should use double hyphens as required by your software 10 GroupWise 7 Troubleshooting 1 Error Messages GroupWise Engine Error Codes GroupWise engine code underlies all aspects of GroupWise including the GroupWise client the agents and the GroupWise snap ins to ConsoleOne An engine error code can be displayed from any GroupWise component This part of Troubleshooting 1 Error Messages helps you resolve engine error codes in any Group Wise component For more information see the following sections Oxxx Engine Error Codes on page 13 8xxx Engine Error Codes on page 15 9xxx Engine Error Codes on page 43 Axxx Engine Error Codes on page 45 e Bxxx Engine Error Codes on page 53 e Cxxx Engine Error Codes on page 55 D
299. re memory 218 GroupWise 7 Troubleshooting 1 Error Messages GWIA Message File open failed Source GroupWise Internet Agent Explanation The Internet Agent could not open a message file Action The message file is moved to the problem directory in the domain directory GWIA Message re queuing failed The message must be deleted Source GroupWise Internet Agent Explanation A message could not be put into or removed from the delayed delivery and the retry queue maintained under the gwhold directory because of a disk or a memory error Action Check access to the gwhold and qfiles subdirectories Action Check to see if the disk is full Action Free more memory GWIA Message transport session open error xxxx Source GroupWise Internet Agent Explanation This is almost always caused by a memory error Action Free up memory GWIA Processing inbound message Source GroupWise Internet Agent Explanation This is an informational message A message is being received by the Internet Agent from the foreign system Action None GWIA Processing outbound command Source GroupWise Internet Agent Explanation This is an informational message ConsoleOne has sent a command to the Internet Agent Commands are STATE REQUEST STATS REBOOT and DIRECTORY SYNCHRONIZATION Action None GWIA Processing outbound message Source GroupWise Internet Agent Explanation This is an informational message A message
300. re running the Group Wise client FOxx Unexpected error Source Explanation Action GroupWise engine QuickFinder An engine error has occurred for which GroupWise does not have a specific error message Exit and then restart the GroupWise client Fxxx Engine Error Codes 177 9 16 F1xx Cannot Connect Error e F1xx Cannot connect to remote server on page 178 F1xx Cannot connect to remote server Source Explanation Possible Cause Action Action Action Action GroupWise engine NetWare remote server connection table GroupWise cannot connect to a remote server where needed information is located The POA can no longer access the remote server where a document storage area or backup restore area is located Make sure the remote server is running Make sure the POA startup file contains the user and password or dn startup switches so the POA can log in to the remote server See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide In ConsoleOne specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object Make sure the user the POA is logging in as has sufficient rights to access the needed location on the remote server See Creating a NetWare Account for Agent Access Optional in Installing GroupWise Agents in the GroupWise 7 Installation Guide 178 GroupWi
301. reation error xxxx on page 220 GWIA Scratch pad file write error filename on page 220 GWIA Unable to find TCPIP Kernel on page 220 GWIA Unable to listen on SMTP port on page 220 GWIA Command task could not be added to message body rc xxxx Source Explanation Action GroupWise Internet Agent A file output error occurred probably because of a full disk or an inaccessible directory If re D109 check access rights and privileges in the wocsin directory or If re D907 check access rights and privileges in the wpcsin directory GWIA Configuration data is missing from the database Source Explanation Action Group Wise Internet Agent The domain database wodomain db is damaged Rebuild the database using ConsoleOne See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWIA ConvertPerfect Error while converting attachment file filename Source Explanation Action Group Wise Internet Agent The user sent the message using the Convert Attachment feature of the Advanced Send Option which invokes ConvertPerfect ConvertPerfect might not know how to convert this type of file the file could not be decrypted or a file I O error occurred This problem might generate a different error message than the one listed above None GWIA Currently unhandled command value xxxx was received by the gateway So
302. rectory For example Corel WordPerfect 7 needs a file named wordpfct wpd to exist in the shellnew directory in order to create a new file when called from Group Wise If this error occurs when creating a new document in the Group Wise client the blank template file for the application might be missing Check the shellnew directory for the existence of a blank file for the application in use from GroupWise If the blank file is missing start the application independently then save an empty file under the required name in the shellnew directory You should then be able to create new documents using that application from Group Wise A directory required for the normal flow of GroupWise messages could be missing 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 A required file or subdirectory could be missing from the directory structure of the user s post office 8xxx Engine Error Codes 23 Action Possible Cause Action See Post Office Directory in Directory Structure Diagrams in Group Wise 7 Troubleshooting 3 Message Flow and Directory Structure Verify the existence ownership and rights of the files and subdirectories in the user s post office See GroupWise User
303. rmine the specific problem the POA is encountering See Using POA Startup Switches in Post Office Agent in the GroupWise 7 Administration Guide If this error occurs from the MTA the MTA might not have access to one or more of the post offices in the domain Verify 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 gt Post Offices Check the properties of each Post Office object to make sure that the post office directory for each post office exists Make sure that the post office path is correctly defined in the Post Office object In ConsoleOne right click the Post Office object to display the post office Identification page Also make sure the MTA has access to the post office 22 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Action Action Possible Cause Action Action Possible Cause Action Possible Cause Action Possible Cause If this error occurs when importing a document into GroupWise there might be a problem with the library Check and if necessary fix the library See Maintaining Library Databases and Documents in Databases in the GroupWise 7 Administration Guide Then synchronize the library See Synchronizing Database Information in Databases in the GroupWise 7 Administration Guide If documents
304. rmine what IP addresses are available on the server where the agent is running then configure the agent to use a valid IP address See the following sections of the GroupWise 7 Administration Guide depending on which agent is encountering the problem e Binding the POA to a Specific IP Address 36 GroupWise 7 Troubleshooting 1 Error Messages e Binding the MTA to a Specific IP Address Binding the Internet Agent to a Specific IP Address 891A TCP IP data is not ready for reading Source Explanation Possible Cause Action Action Group Wise engine TCP IP communication The TCP IP connection is blocked The data has been delayed by SSL encryption None TCP IP services will continue to try to read the data If the problem persists check the line connection and the NIC card on the server 891B No SSL certificate supplied Source Explanation Possible Cause Action GroupWise engine TCP IP communication You have configured an agent for SSL but the agent cannot locate the SSL certificate In ConsoleOne you enabled SSL on the Agent object Network Address page but did not provide the certificate information on the SSL Settings page Finish configuring the agent for SSL See the following sections of the GroupWise 7 Administration Guide depending on which agent is encountering the problem Enhancing Post Office Security with SSL Connections to the POA in Post Office Agent
305. rning file logging off Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent could not create the log file so disk logging is being turned off The WebAccess Agent does not have rights to create files in the log file directory Provide the WebAccess Agent with rights to create files in the log file directory or specify a different location for the log files See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide Check the disk to make sure that there is sufficient space available to create the file WEBACC Logging Error writing to file turning file logging off Source Explanation Possible Cause Action 226 GroupWise 7 Troubleshooting 1 GroupWise WebAccess Agent The WebAccess Agent could not write information to the log file so logging is being turned off The WebAccess Agent does not have rights to write to files in the log file directory or the disk is full Provide the WebAccess Agent with rights to write to files in the log file directory or specify a different location for the log files See Using WebAccess Startup Switches in WebAccess in the GroupWise 7 Administration Guide Error Messages WEBACC Login failed Source Explanation Possible Cause Action GroupWise WebAccess Agent A WebAccess user attempted to log in and failed The user did not enter a valid GroupWise user ID or pass
306. rocess control Action See 8xxx Unexpected error on page 42 8xxx Engine Error Codes 41 2 8 8Fxx Errors e 8F03 Invalid configuration option on page 42 8F03 Invalid configuration option Source GroupWise engine server toolkit Explanation Invalid startup switch specified when starting one of the agents Action Check the startup switches in use for the agent reporting the error For lists of startup switches see Using POA Startup Switches in Post Office Agent and Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide 2 9 8xxx Unexpected Error e 8xxx Unexpected error on page 42 8xxx 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 42 GroupWise 7 Troubleshooting 1 Error Messages 9xxx Engine Error Codes e 90xx Errors on page 43 e 93xx Errors on page 43 e Oxxx Unexpected Error on page 44 3 1 90xx Errors e 9007 Client not set up for SSL on page 43 e 9008 Server does not support SSL on page 43 9007 Client not set up for SSL Source Explanation Possible Cause Action Action 9008 Server does Source Explanation Possible Cause Action GroupWise engine client server The POA is configured to require SSL communicate wi
307. ropriate Your application is calling a method that is not supported on the container type for which it was called For example The getQuickMessages method cannot be used on the Contacts folder the Trash folder or a query folder The createCursor method cannot be used on the Contacts folder Use a method that is valid for the container type For more information see e Methods http developer novell com ndk doc gwsoap soap_enu data brx9pkk html brx9pkk EA16 The specified contentType is not supported with this call Source Explanation Possible Cause Action GroupWise engine SOAP protocol The call that generated this error supports only the text plain content type HTML is not yet supported for this call Your application is trying to create a GroupWise item with HTML content type when only the text plain content type is currently supported Use the text plain content type EA17 The specified date time range is invalid Source Explanation Possible Cause Possible Cause Action GroupWise engine SOAP protocol The specified date time range is not usable Your application fails to specify a start date on a recurring item Your application specifies an end date that is earlier than the start date Specify a valid date type range For more information see startDate definition http developer novell com ndk doc gwsoap soap_enu data bwmwd74 html bwmwd74 endDate definition http
308. ror Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F071 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F072 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F073 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 168 GroupWise 7 Troubleshooting 1 Error Messages F074 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F075 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F076 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F077 Database error Source Group Wise engine QuickFinder Action See F0xx Database error index on page 177 F078 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F079 Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F07A Database error Source GroupWise engine QuickFinder Action See F0xx Database error index on page 177 F07B Database error Source GroupWise engine QuickFinder Action
309. roupWise 7 Troubleshooting 3 Message Flow and Directory Structure GWMTA Insufficient disk space Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA does not have sufficient disk space to write files into its input queues or holding queues The MTA requires at least 1 MB of free disk space to run One or more locations are closed resulting in a backlog of messages in the MTA holding queues in the directory Resolve the problems with the closed facilities so that normal message flow resumes See MTA Status Box Shows a Closed Location in GroupWise 7 Troubleshooting 2 Solutions to Common Problems Other programs running the same server with the MTA have used up all available disk space Free up disk space so the MTA can continue processing messages Check the MTA log file to see which queue the MTA can no longer write to so you know where more disk space is required See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide The MTA cannot write message files across a mapped or UNC link into the MTA input queue in a closed domain domain wpcsin directory ora closed post office post _office wpcsin directory because the directory is damaged If the input queue subdirectories are empty you can rename the original input queue directory and then manually re create it along with it
310. roupWise engine QuickFinder Action See F0xx Memory error on page 177 9 5 F04x Errors e F045 Unexpected error on page 164 F046 File I O error on page 164 F047 File I O error on page 164 F048 File I O error on page 164 F049 File I O error on page 164 FO4A File I O error on page 165 FO4C File I O error on page 165 F04D File I O error on page 165 e FO4E File not found during QuickFinder indexing on page 165 e FO4F File I O error on page 165 F045 Unexpected error Source Group Wise engine QuickFinder Action See FOxx Unexpected error on page 177 F046 File I O error Source GroupWise engine OuickFinder Action See FOxx File I O error on page 176 F047 File I O error Source GroupWise engine OuickFinder Action See FOxx File I O error on page 176 F048 File I O error Source Group Wise engine OuickFinder Action See FOxx File I O error on page 176 F049 File I O error Source GroupWise engine QuickFinder Action See FOxx File I O error on page 176 164 GroupWise 7 Troubleshooting 1 Error Messages FO4A File I O error Source GroupWise engine QuickFinder Action See FOxx File I O error on page 176 FO4C File I O error Source GroupWise engine QuickFinder Action See FOxx File I O error on page 176 FO4D File I O error Source Group Wise engine QuickFinder Action See FOxx File
311. route a message to the domain it is addressed to because available indirect links create a circular reference Links between domains in your GroupWise system are not set up correctly Check and if necessary adjust the indirect links between domains in your Group Wise system See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide GWMTA Domain database error transfer domain not found Source Explanation Possible Cause Group Wise Message Transfer Agent The MTA cannot locate the domain to which a message is addressed nor can it locate an indirect link to that domain Links between domains in your Group Wise system are not set up correctly 200 GroupWise 7 Troubleshooting 1 Error Messages Action Check and if necessary adjust the indirect links between domains in your Group Wise system See Link Configuration between Domains and Post Offices in Domains in the GroupWise 7 Administration Guide GWMTA Domain database open failed Source Explanation Possible Cause Action Group Wise Message Transfer Agent The MTA cannot access the domain database wodomain db The domain database has been damaged Rebuild the domain database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA Domain database read error Source Explanation Possible Cause Action Group Wise Message Transfer Agent
312. rtup switch on the POA to increase the maximum size of the data that the POA accepts 150 GroupWise 7 Troubleshooting 1 Error Messages EA05 Invalid cursor Source Explanation Possible Cause Action Possible Cause Action Group Wise engine SOAP protocol Your application cannot read the current cursor value Cursors break lists of data into chunks Your application cannot determine where the boundary of the data chunk is located The cursor has already been freed using the destroyCursor method Create a new cursor A cursor cannot be used again after it has been freed The current value of the cursor is not valid Create a cursor before attempting to position or read from it For more information see Cursors http developer novell com ndk doc gwsoap soap_enu data bwncsce html bwncsce createCursor method http developer novell com ndk doc gwsoap soap_enu data brx85xo html brx85xo positionCursor method http developer novell com ndk doc gwsoap soap_enu data brx94t1 html brx94t1 readCursor method http developer novell com ndk doc gwsoap soap_enu data brx9f6t html brx9f6t destroyCursor method http developer novell com ndk doc gwsoap soap_enu data brx8dol html brx8dol EA06 Invalid session string Source Explanation Possible Cause Possible Cause Action GroupWise engine SOAP protocol Your application cannot access the current session with the POA The SOAP client user has
313. s from backup One or more of the GroupWise databases might have an invalid owner or no owner Check the ownership of the GroupWise databases If necessary change the ownership to a valid user such as the system administrator If this error occurs when users are trying to log in to GroupWise through the Group Wise Internet Agent from a POP3 mail client the post office link information needed by the GroupWise Internet Agent might be incorrect Check the post office link set up for the GroupWise Internet Agent In ConsoleOne browse to and select the Domain object where the Internet Agent is installed Right click the GWIA object then click Properties Click Post Office Links select the post office then click Edit Link Make sure the IP address and TCP port for the POA are specified correctly in the Client Server Access box See Internet Agent in the GroupWise 7 Administration Guide 8201 Access to file denied Source Explanation Possible Cause Action Possible Cause Group Wise engine file input output Access denied The program tried to access or open a file that did not have or allow sharing The program might also have tried to create a file that already exists If this error occurs from the POA the POA might not have access to a required file Start the POA including the rights switch to determine the specific problem the POA is encountering See Using POA Startup Switches in Post Office
314. s required subdirectories 204 GroupWise 7 Troubleshooting 1 Error Messages GWMTA Insufficient memory Source GroupWise Message Transfer Agent Explanation Not enough memory is available for the MTA to function properly Possible Cause Ifthe 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 in Installing GroupWise Agents in the GroupWise 7 Installation Guide Action Stop some other programs on the server to free up memory for use by the MTA Action Add memory to the server to accommodate the MTA along with other existing programs Action Select a different server to run the MTA on where adequate resources are available See Moving the MTA to a Different Server in Message Transfer Agent in the GroupWise 7 Administration Guide Possible Cause Ifthe MTA starts successfully then encounters a memory error later during otherwise normal processing some other program on the server or another agent thread might have temporarily used a large quantity of memory Action Wait to see if the memory problem resolves itself The MTA will retry its operation and should succeed at a later time when the other program has released some memory Action Ifthe MTA starts successfully but frequently encounters memory errors during later processing treat the situation as if the MTA cannot start
315. same name as the personal group a circular reference is created Edit the groups to remove the circular reference or include the contents of one of the subgroups in a higher level group to reduce the levels in the structure DOOF Remote mail error Source Explanation Possible Cause Action Action Action Group Wise engine Invalid remote mail request Remote mail error This error is displayed whenever a more specific error is not available The most common cause is a request for items that have already been deleted Check and repair the databases of the master mailbox See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide In Remote mode the GroupWise client should automatically repair any problems with the remote databases If the client is unable to repair the problem you can delete the rofdata directory on the remote computer then request all information from the master mailbox again 7 2 DO1x Errors D017 Too many users in address on page 82 D018 Unexpected error on page 83 D019 Password incorrect on page 83 DOIA Password too long on page 83 DOIB Access to Group Wise denied on page 83 D01C Remote mail error on page 83 DO1E Cannot execute rule on page 84 DOIF Archive pat
316. se GroupWise replication is still in progress and the data has become inconsistent Action Wait for the replication to complete then rebuild the database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide 0036 Cannot access object in different GroupWise system Source GroupWise Administrator association Possible Cause You are accessing an object in eDirectory that belongs to a different Group Wise system than the one you are connected to Action Connect to the appropriate GroupWise system See Connecting to a Domain in Domains in the GroupWise 7 Administration Guide 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 Action Enter a valid distinguished name 0039 Invalid UNC path Source GroupWise Administrator UNC path validator Explanation The UNC path entered does not specify a valid network resource Action Enter a correct UNC path 0041 Cannot authenticate Source GroupWise Administrator eDirectory operation Explanation The NetWare login DLL file was not found GroupWise was unable to authenticate Possible Cause Your NetWare client installation was incomp
317. se 7 Administration Guide Action Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide 104 GroupWise 7 Troubleshooting 1 Error Messages Action Action If a user database cannot be repaired you can rename the existing user database then recreate it See Re creating a User Database in Databases in the GroupWise 7 Administration Guide If the database cannot be recreated you must restore it from backup See Restoring GroupWise Databases from Backup in Databases in the GroupWise 7 Administration Guide D117 GroupWise version too old Source Explanation Possible Cause Action Group Wise engine database interface Old program version An attempt was made to open a database with an older version of GroupWise software You are running an older version of the Group Wise client Your post office has been updated to a newer version Reinstall GroupWise with the version of the software that matches the database See in Installing the GroupWise Windows and Cross Platform Clients in the GroupWise 7 Installation Guide D118 Database error Source Explanation Possible Cause Action Action GroupWise engine database interface Field not found Unable to find the field in the database Check and repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Mess
318. se 7 Troubleshooting 1 Error Messages Agent Error Messages The Group Wise agents are responsible for message transfer and delivery throughout your Group Wise system This part of Troubleshooting 1 Error Messages helps you resolve agent error messages that appear in agent log files and other places where agent status information is displayed e Chapter 10 Post Office Agent Error Messages on page 181 e Chapter 11 Message Transfer Agent Error Messages on page 193 Chapter 12 Internet Agent Error Messages on page 215 e Chapter 13 WebAccess Agent Error Messages on page 221 Chapter 14 Monitor Agent and Application Error Messages on page 233 Other sources of assistance include Novell Support http support novell com Novell Support Knowledgebase http support novell com search kb_index jsp GroupWise 7 Support Forums http support novell com forums 2gw html Novell GroupWise Support Community http support novell com products groupwise GroupWise Cool Solutions http www novell com coolsolutions gwmag index html Agent Error Messages 179 180 GroupWise 7 Troubleshooting 1 Error Messages Post Office Agent Error Messages GWPOA Admin database for post_office could not be recovered on page 182 GWPOA Administrator record not found in database on page 182 GWPOA Application connection table full on page 182 GWPOA Authentication failed for the
319. se Administrator that it could not respond to GroupWise Administrator has been updated but the GroupWise agent software has not yet been updated Install the latest version of the GroupWise agent software See the Installing the GroupWise 7 Software in Update in the GroupWise 7 Installation Guide GWMTA Running the agent with conflicting effective users Source Explanation Possible Cause Possible Cause Action GroupWise Message Transfer Agent for Linux You are starting the MTA as a user that is different from the user the MTA is configured to run as The user specified in the uid conf file does not match the user specified in the uid run file The user specified in the uid conf file has been manually edited The uid conf file has been deleted Verify that the uid conf file specifies the desired user then delete the uid run file For more information see Running the Linux Group Wise Agents as a Non root User in Installing GroupWise Agents in the GroupWise 7 Installation Guide GWMTA StartServiceCtrlDispatcher failed when attempting to start Windows agent service Source Explanation Possible Cause Action Group Wise Message Transfer Agent for Windows The Windows MTA cannot start its dispatcher thread The Windows server is not functioning properly Reboot the Windows server GWMTA Target queue temporarily locked Source Explanation Possible Cause Group Wis
320. se error on page 57 C00B Database error on page 57 COOC Field type mismatch on page 57 C00D Database error on page 57 COOE Invalid index number on page 57 COOF Invalid password on page 57 C003 Invalid object name has been passed in Source Internet Agent Installation program or WebAccess Installation program on Linux Explanation The Installation program cannot create an Agent object with the name you specified Possible Cause You did not specify the object name in the correct format Action Use the following format cn username ou organizational_unit o organization Possible Cause An object by the name you specified already exists Action Specify a different object name Cxxx Engine Error Codes 55 C005 Invalid container has been selected for the GW objects Source Explanation Possible Cause Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program cannot create an Agent object in the context you specified The container object you specified was not a GroupWise Domain object an Organizational Unit object or an Organization object Specify an appropriate container for the Agent object C006 Record key or key reference not found Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action GroupWise engine database services A record or key was not found I
321. se repair strategies on page 77 C044 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C045 Unexpected error Source GroupWise engine database services Action See C0xx Unexpected error on page 78 C046 Database error Source GroupWise engine database services Cxxx Engine Error Codes 67 Action See COxx Database error general database repair strategies on page 77 C047 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C048 Unexpected error Source GroupWise engine database services Action See COxx Unexpected error on page 78 C04A Unexpected error Source GroupWise engine database services Action See COxx Unexpected error on page 78 C04B Database error Source Group Wise engine database services Action See C0xx Database error Support assistance recommended on page 77 C04C Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C04D Memory error Source GroupWise engine database services Action See C0xx Memory error on page 78 C04E Database error Source GroupWise engine database services Action See C0xx Database error general database repair strategies on page
322. sgnnn db Action Restore the message database from backup 37 Exclusive access denied to message database Source GroupWise Check utility GWCheck Explanation GWCheck cannot get sufficient access to the specified message database msgnnn db Possible Cause Insufficient rights Action Make sure you have write access to the directory where the message database is located 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 38 Error writing message record as user outbox item Source GroupWise Check utility GWCheck Explanation GWCheck cannot add a message as a received item in a user s mailbox Action Perform a structural analyze fix on the user s message database by supplying the name of the message database in the User Resource field See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Action For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 39 Error writing message record as user inbox item Source GroupWise Check utility GWCheck Explanation GWCheck cannot add a message as a sent item in a user s mailbox Action Perform a structural analyze fix on the user s message database by supplying the name of the
323. sistance recommended on page 77 C008 Database error Source Action Group Wise engine database services See COxx Database error general database repair strategies on page 77 56 GroupWise 7 Troubleshooting 1 Error Messages C009 Database error Source GroupWise engine database services Action C0xx Database error Support assistance recommended on page 77 C00A Database error Source GroupWise engine database services Action C0xx Database error Support assistance recommended on page 77 COOB Database error Source GroupWise engine database services Action See COxx Database error general database repair strategies on page 77 COOC Field type mismatch Source GroupWise engine database services Explanation Invalid field type in record being added Possible Cause If this error occurs when rebuilding a database you might not be connected to the correct GroupWise system Action Connect to the GroupWise system where the database is located See Select Domain in System in the GroupWise 7 Administration Guide Then perform the rebuild again COOD Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 COOE Invalid index number Source GroupWise engine database services Explanation Invalid index number Possible Cause When converting a post office from 5 x to 6 x th
324. specified in the uid conf file does not match the user specified in the uid run file The user specified in the uid conf file has been manually edited The uid conf file has been deleted Verify that the uid conf file specifies the desired user then delete the uid run file For more information see Running the Linux GroupWise Agents as a Non root User in Installing GroupWise Agents in the GroupWise 7 Installation Guide WEBACC Startup file not found Source Explanation Possible Cause Action GroupWise WebAccess Agent The WebAccess Agent could not find the startup file specified by the filename startup switch The startup file is not in the same directory as the WebAccess Agent and filename does not include the complete path to the file Move the startup file to the same directory as the WebAccess Agent or include the full path in the filename for example j startup webstart txt WEBACC TCP socket accept failed Source Explanation Possible Cause Action GroupWise WebAccess Agent The GroupWise WebAccess CGI Extension tried to start a new session with the WebAccess Agent but the WebAccess Agent could not handle another session Insufficient memory Free up memory or add additional memory WEBACC The post office is closed Source GroupWise WebAccess Agent 230 GroupWise 7 Troubleshooting 1 Error Messages Explanation While processing a request for a user the WebA
325. specified in the modem connection doesn t match the login ID of the gateway the modem is dialing 272 GroupWise 7 Troubleshooting 1 Error Messages Action Verify that the gateway login ID in the modem connection definition is correct In ConsoleOne double click the Domain object where the gateway is located then double click the Gateway object On the GroupWise client Profiles page select the profile that is not working then click Edit Verify the login ID displayed in the Remote Profile dialog box Correct it if necessary Cannot log in to the gateway Check the gateway login password Source GroupWise Windows client Remote mode Possible Cause The password to the gateway specified in the modem connection doesn t match the gateway password the modem is dialing The password might be entered incorrectly or there might be a password change Action Verify that the gateway password in the modem connection definition is correct In ConsoleOne double click the Domain object where the gateway is located then double click the Gateway object On the Group Wise client Profiles page select the profile that is not working then click Edit Verify the password displayed in the Remote Profile dialog box and correct it if necessary LDAP failure detected Source GroupWise Windows client Remote mode Explanation A GroupWise client user is using LDAP to authenticate to GroupWise but GroupWise is unable to authenticate Possible Cause
326. specify the domain directory See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide The location specified by the home startup switch is on a server that is currently not available Message Transfer Agent Error Messages 209 Action Possible Cause Action 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 If running the MTA on a Windows server the location might be on a server that is not currently mapped Make sure the server where the MTA is running has a drive mapped to the domain directory on the server where the domain is located if it is using a mapped link See GWMTA Cannot attach to server or volume on page 196 GWMTA Post office database open failed insufficient memory Source Explanation Possible Cause Action Possible Cause Action Group Wise Message Transfer Agent The MTA cannot access one of its post office databases wphost db Insufficient memory See GWMTA Insufficient memory on page 205 The post office database has been damaged Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA Post office database read error Source Explanation Possible Cause Action Group Wise Message Transfer Agent Th
327. ss Book 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 Select the correct user in the pop up list or use the Address Book to find the user D105 Directory Services data missing Source GroupWise engine database interface Explanation Directory Services error Possible Cause Domain or post office not found during user or post office lookup Action Check the ph switch when starting the GroupWise client to make sure it specifies the correct path to the user s post office Also check the u switch to make sure it specifies a valid user in the specified post office See Startup Switches for the GroupWise Client in Client in the GroupWise 7 Administration Guide D106 Database error Source GroupWise engine database interface Explanation General database error Possible Cause The index is not synchronized with the data Action Check and repair the database See Maintaining Domain and Post Office Databases in Databases in the GroupWise 7 Administration Guide D107 Record not found Source GroupWise engine database interface Dxxx Engine Error Codes 101 Explanation Possible Cause Possible Cause Action Action Possible Cause Action Record not found
328. ssistance recommended on page 77 C027 Database error Source GroupWise engine database services Action See C0xx Database error Support assistance recommended on page 77 C028 Database error Source GroupWise engine database services Action See COxx Database error Support assistance recommended on page 77 C029 Database version unsupported Source GroupWise engine database services Explanation Unsupported version of database Possible Cause The database was created with an older version of GroupWise and cannot be opened by the current version C02A Cannot access database dictionary file Source GroupWise engine database services Explanation Dictionary file access error Possible Cause In the GroupWise client this error usually indicates there was a file I O error accessing one of the database dictionary dc files which are used to create databases Action Check for any problems accessing the disk where the dictionary files reside To determine the standard locations for the various database dictionary files see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure Action Make sure the ngwguard dc file exists in the post office directory If it does not copy it from the po subdirectory of your software distribution directory For the specific locations of this file see Post O
329. stallation Options LDAP Information and Clustering in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide for details about the SSL certificate file then provide the correct information The LDAP Server object in ConsoleOne is not properly configured for SSL Make sure that the LDAP Server object is configured with the correct SSL certificate information in ConsoleOne AD11 SSL could not be initialized Source Explanation Possible Cause Action Internet Agent Installation program or WebAccess Installation program on Linux You selected to use an SSL connection with the LDAP server but the Installation program cannot establish an SSL connection The LDAP Server object in ConsoleOne is not properly configured for SSL Make sure that the LDAP Server object is configured with the correct SSL certificate information in ConsoleOne AD20 The attribute specified in the request does not exist in the entry Source Explanation Possible Cause Action Action Internet Agent Installation program or WebAccess Installation program on Linux The Installation program is trying to create an Agent object but eDirectory is not providing the necessary attribute The eDirectory schema has not yet been extended to accommodate GroupWise objects Extend the schema as described in Check eDirectory Schema in System in the GroupWise 7 Administration Guide Run the Installation progr
330. store the BLOB file from backup If the damaged BLOB file cannot be restored you can delete it to eliminate the error GWPOA Possibly dangerous message temporarily suspending dispatcher Source Explanation Possible Cause Action Group Wise Post Office Agent No additional message file processor threads will be started until processing of the current message file has completed The current message file is flagged as having caused the POA to shut down in a previous processing attempt The current message file is damaged If all existing message file processor threads successfully process their message files the POA will resume normal processing No action is necessary Post Office Agent Error Messages 189 Action If processing of a message file causes the POA to shutdown do not put message files from the post of fice wpcsout problem directory back into the POA input queue Restart the POA GWPOA Reached inbound connections limit Source Explanation Action Group Wise Post Office Agent message transfer protocol The POA is configured to communicate with the MTA by way of TCP IP The POA has reached the maximum number of inbound connections None Connections are automatically released and reopened as processing continues GWPOA Running the agent with conflicting effective users Source Explanation Possible Cause Possible Cause Action Group Wise Post Office Agent for Linux Yo
331. stration Guide Possible Cause The disk is full where the QuickFinder index is located so the QuickFinder process cannot write more information to disk Action Free up disk space See Managing Database Disk Space in Databases in the GroupWise 7 Administration Guide Possible Cause You do not have rights to the location where the QuickFinder index is located Action Check your access rights See GroupWise User Rights in Security Administration in the GroupWise 7 Administration Guide Action In ConsoleOne you can set the proper user rights for all users in a post office or for an individual user See Group Wise User Rights in Security Administration in the GroupWise 7 Administration Guide F013 Database error Source GroupWise engine QuickFinder Action See FOxx Database error on page 177 F014 Database error Source GroupWise engine QuickFinder Action See FOxx Database error on page 177 F016 Database error Source GroupWise engine QuickFinder Action See FOxx Database error index on page 177 F018 Number contains non numeric characters Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 F019 Search switch requires n Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 FO1A Document summary field name or number required Source GroupWise engine QuickFinder F
332. synchronization Remove the external system synchronization entry then delete the domain See Using Direct Links in Connecting to GroupWise 5 x 6 x and 7 x Systems in the GroupWise 7 Multi System Administration Guide DB49 Cannot use limited visibility distribution list as administrator Source Explanation Action Action Group Wise engine administration engine The selected distribution list cannot be used for the administrator because it is not visible to all users in your Group Wise system Create a new distribution list to use as the administrator that contains only users that can be visible throughout your GroupWise system For information about changing distribution list properties see Creating and Managing Distribution Lists in Distribution Lists Groups and Organizational Roles in the GroupWise 7 Administration Guide Change the visibility of the selected distribution list to system so that all users can see it 130 GroupWise 7 Troubleshooting 1 Error Messages DB4A External sync message from unknown system Source Explanation Possible Cause Action Possible Cause Action Group Wise engine administration engine An external synchronization message was received from a system that the local Group Wise system cannot identify The local GroupWise system is not set up to synchronize with the system that sent the synchronization message Configure the local Group W
333. syntax is correct you might want to add the group to the Address Book The user has specified a distribution list in another post office that has visibility set to none Change the visibility of the distribution list so that users in other post offices can use it For information about visibility see Creating and Managing Distribution Lists in Distribution Lists Groups and Organizational Roles in the GroupWise 7 Administration Guide 3 D11D GroupWise version newer than database Source Explanation Possible Cause Action Possible Cause Action Possible Cause Group Wise engine database interface New program version 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 The GroupWise demo creates a post office database wphost db on the local workstation which can interfere with the functioning of the full GroupWise client Search the workstation for a local wohost db file If found rename or delete it The GroupWise client and agents were updated but ConsoleOne was not As a result the database dictionary dc files do not get updated Copy the dc files from the domain and po subdirectories of the new distribution media to the domain and post office directories of your GroupWise system The version of GroupWise you are running is newer than the database The software cannot do an
334. system requirements See Deciding Where to Install the GroupWise Monitor Components in Installing GroupWise Monitor in the GroupWise 7 Installation Guide The Monitor Agent has gone down Restart the Monitor Agent See Starting the Monitor Agent in Monitor in the GroupWise 7 Administration Guide GWMON The URL to connect to the GroupWise Monitor Agent is invalid Source Possible Cause Action Group Wise Monitor Application The Monitor Agent IP address and port number is not correct in the gwmonitor cfg file Check the gwmonitor cfg file to make sure it provides the correct IP address and port number for the Monitor Agent Correct the information as needed GWMON Unable to communicate with GroupWise Monitor Agent Source Group Wise Monitor Application 234 GroupWise 7 Troubleshooting 1 Error Messages 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 Possible Cause Your firewall is preventing the Monitor Application from communicating with the Monitor Agent Action Adjust the configuration of your firew
335. t TCP agent The POA is configured for TCP IP communication but is unable to establish TCP IP communication TCP IP is not set up correctly on the server where the POA is running Make sure TCP IP is set up correctly GWPOA Error initializing HTTP Source Explanation Action Group Wise Post Office Agent The HTTP port the POA is trying to use for its Web console is not responding correctly Configure the POA to communicate on a different HTTP port See Using the POA Web Console in Post Office Agent in the GroupWise 7 Administration Guide GWPOA Error listening for connection Source Explanation Possible Cause Action Possible Cause Action Group Wise Post Office Agent TCP agent The POA is configured for TCP IP communication but is unable to connect TCP IP is not set up correctly on the server where the POA is running Make sure TCP IP is set up correctly Insufficient memory See GWPOA Not enough memory to complete operation on page 188 GWPOA Error opening listener port Source Explanation Group Wise Post Office Agent TCP agent The POA is configured for TCP IP communication but the port it is configured to listen on is already in use by another program Post Office Agent Error Messages 185 Action See 8555 Port in use on page 28 GWPOA Error putting item in queue Source Explanation Action Group Wise Post Office Agent TCP agent The TC
336. t Office in Post Office Agent in the GroupWise 7 Administration Guide 34 GroupWise 7 Troubleshooting 1 Error Messages Possible Cause Action Possible Cause Action The GroupWise client is trying to use client server mode to connect with the POA but the POA is not set up for client server processing Configure the POA for client server processing to match the needs of the client See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide If this error appears in the Message Transfer Status box of the POA the MTA to which it is transferring messages is not running Check the status of the MTA for the domain Restart the MTA if necessary 8910 Cannot read on connection Source Explanation Action GroupWise engine TCP IP communication Read failed Retry the operation 8911 Cannot write on connection Source Explanation Possible Cause Action Possible Cause Action GroupWise engine TCP IP communication Cannot write on connection the receiver isn t responding A client or server machine has crashed or the process was forced to close without shutting down The machine might have been exited while connections were active Restart the Group Wise client If this error occurs from the POA the server where the POA runs might not have the most current version of TCP IP Install the latest TCP IP For technical ser
337. t novell com search kb index jsp e GroupWise 7 Support Forums http support novell com forums 2gw html Novell Group Wise Support Community http support novell com products groupwise GroupWise Cool Solutions http www novell com coolsolutions gwmag index html Audience This guide is intended for network administrators who install and administer Group Wise Feedback 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 Documentation Updates For the most recent version of GroupWise 7 Troubleshooting 1 Error Messages visit the Novell GroupWise 7 Documentation Web site http www novell com documentation gw7 Additional Documentation For additional GroupWise documentation see the following guides at the GroupWise 7 documentation Web site http www novell com documentation lg gw7 Installation Guide Administration Guide Multi System Administration Guide Interoperability Guide Troubleshooting 2 Solutions to Common Problems Troubleshooting 3 Message Flow and Directory Structure e GroupWise Client User Guides GroupWise Client Frequently Asked Questions FAQ Documentation Conventions In Novell documentation a greater than symbol gt is used to sepa
338. th the GroupWise client but the client is not capable of SSL communication SSL communication was introduced for the GroupWise client in GroupWise 6 5 You are running an older GroupWise client against a post office that has been updated to GroupWise 6 5 or later Update the client to GroupWise 6 5 or later Reconfigure the POA so that SSL is enabled rather than required See Enhancing Post Office Security with SSL Connections to the POA in Configuring the POA in the GroupWise 7 Administration Guide not support SSL GroupWise engine client server The GroupWise client is trying to use an SSL connection to the POA but the POA is not configured for SSL The POA has been reconfigured without SSL since the client logged in Restart the GroupWise client It does not try to use SSL when it detects that the POA is not configured for SSL 3 2 93xx Errors 9302 Unexpected error on page 44 9304 Unexpected error on page 44 9305 Unexpected error on page 44 9307 Unexpected error on page 44 9308 Unexpected error on page 44 9309 Unexpected error on page 44 9xxx Engine ErrorCodes 43 9302 Unexpected error Source GroupWise engine loadable language resource Action See 9xxx Unexpected error on page 44 9304 Unexpected error Source GroupWise engine loadable language resource Action See 9xxx Unexpected error on page 44 9305 Unexpected error Source GroupWise engine
339. that forward mail to an external user who might be forwarding the mail back into GroupWise Look up rules in GroupWise client Help DO5A User database access denied Source Explanation Possible Cause Action Possible Cause Action Possible Cause Action Action Possible Cause Action Action Group Wise engine The Group Wise client cannot start because it cannot access the user s user database user xxx db The user tried to access a mailbox that does not have a password using the wrong NetWare user ID ina post office with security set to high Set a password on the user s mailbox See Creating or Changing a Mailbox Password in Users in the GroupWise 7 Administration Guide The user s current login ID either from NetWare eDirectory or Windows does not match the network login ID stored in the Group Wise user database Make sure the user is using the correct login ID Password information in the user database might be damaged Check and if necessary repair the database including resetting user options to reset the password See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide The post office database wphost db might be damaged Rebuild the index of the post office databas
340. the Group Wise client Action In ConsoleOne right click the Post Office object then click Properties Verify that the ph switch setting matches the path specified on the post office Identification page On the network make sure the specified location still exists Cannot find the post office in the specified path Source GroupWise Windows client Remote mode Possible Cause The path to your post office as specified in your network connection doesn t exist Action Ifyou know the path will be valid at a later time or if you re currently not logged on to your network click No to accept the path If you think the path is valid click Yes to return to the Network Connection dialog box to edit or browse the path for accuracy To check the path in ConsoleOne right click the Post Office then click Properties Verify the path specified on the post office Identification page On the network make sure the specified location still exists Cannot find your remote Mailbox folder Source GroupWise Windows client Remote mode Possible Cause The folder specified in Hit the Road or with the ps startup switch on the command line doesn t exist Action Click Yes to let GroupWise create the folder for you or click No then modify the command line in Windows to include the existing directory Cannot log in to the gateway Check the gateway login ID Source GroupWise Windows client Remote mode Possible Cause The gateway login ID
341. then restart the POA 8210 Cannot create path Source Explanation Possible Cause Action Action Action Action Possible Cause Action Possible Cause Group Wise engine file input output Path create failed An attempt by the file system to create a unique file failed If the error occurs as the user is exiting the GroupWise client the client might be encountering a problem archiving messages GroupWise might not be able to archive messages if the original sender s message database is damaged Manually archive any items that are old enough to be archived You can use a filter to display only items that are older than a specified number of days Look up archive item and filters creating in GroupWise client Help If errors occur during manual archiving determine the user who sent the problem items If that user is not experiencing any problems with GroupWise you can delete the problem items If the sending user is also having problems check and if necessary repair the message database msgnnn db of the user who sent the problem items See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide In the GroupWise client open the archive then use the Repair Mailbox feature to repair the archive See Enabling Group Wise Check in the Windows Client in Client in the GroupWise 7 Administration Guide Run GWCheck on the archive
342. tion A GroupWise agent cannot establish an SSL connection because the other server failed to connect The other server is down Restart the other server The certificate file is damaged Obtain a usable certificate file See Server Certificates and SSL Encryption in Security Administration in the GroupWise 7 Administration Guide 8923 Insufficient memory for SSL Source Explanation Possible Cause Action Possible Cause Action GroupWise engine TCP IP communication A GroupWise agent failed to establish an SSL connection because insufficient memory is available for creating the connection Another program was temporarily using a very large amount of memory on the server Wait and try the operation again Too many programs are currently running on the server Stop some programs that are running on the server in order to free up some memory 8xxx Engine Error Codes 39 Possible Cause Action The server where the agent is running has insufficient memory for proper functioning Run the agent on a more powerful server 8924 SSL handshake timeout failure Source Explanation Possible Cause Action GroupWise engine TCP IP communication You have configured an agent for SSL but the agent failed to establish the SSL connection The agent will try again on the next SSL connection request and might be successful If the agent repeatedly fails to establish the SSL connection t
343. tion Set up the POA for client server communication See Using Client Server Access to the Post Office in Post Office Agent in the GroupWise 7 Administration Guide GWPOA File I O error Source Explanation Possible Cause Action Possible Cause Action Group Wise Post Office Agent The POA cannot access a required file The POA cannot read its startup file Check the existence integrity and rights of the POA startup file specified in the command to start the POA See Installing and Starting the POA in Post Office Agent in the GroupWise 7 Administration Guide The POA cannot view its log file Check the existence integrity and rights of the POA log file See Using POA Log Files in Post Office Agent in the GroupWise 7 Administration Guide 186 GroupWise 7 Troubleshooting 1 Error Messages 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 Action Check the TCP IP configuration of the server to which the POA must connect GWPOA HTTP port nn is already in use Source GroupWise Post Office Agent Explanation The HTTP port the POA is trying to use for its Web console is already in use by another program Action Configure the POA to communicate on a different HTTP p
344. tion list on page 86 e D027 Missing closing brace in distribution list on page 86 D028 Lost attachment on page 86 D029 Recipient not specified on page 86 DO2A Name for group not specified on page 86 DO2F Database error on page 87 84 GroupWise 7 Troubleshooting 1 Error Messages D020 Rule caused infinite loop Source Explanation Possible Cause Action Group Wise engine Rule hop count exceeded The execution of a rule has caused a message to be sent which caused the execution of arule and so on To prevent the possibility of infinite looping the rule execution has been terminated Edit the rule to correct the looping condition Look up rules in Group Wise client Help D021 Cannot deliver message Source Explanation Possible Cause Action Action Group Wise engine Remote send requested with no agents present A message cannot be delivered to a user in a different post office because the POA and MTA are not available Set up the POA for the post office See Installing and Starting the POA in Post Office Agent in the GroupWise 7 Administration Guide Set up the MTA for the domain See Installing and Starting the MTA in Message Transfer Agent in the GroupWise 7 Administration Guide D023 User ID expired Source Explanation Action Group Wise engine User account is expired You can extend or remove the user
345. trusted application tried to log in to the POA and was not successful because the POA was configured for a specific IP address and the trusted application was not running there The trusted application is running on a different server from where it was designed to run Run the trusted application on the server with the IP address that the POA is expecting The POA is configured with an incorrect IP address for the trusted application In eDirectory change the expected IP address to the IP address of the server where the trusted application is running See Trusted Applications in System in the GroupWise 7 Administration Guide Dxxx Engine Error Codes 97 D076 Missing trusted application name Source Explanation Possible Cause Action Possible Cause Action Group Wise engine A trusted application tried to log in to the POA and was not successful because no application name was provided The trusted application is not providing an application name Add an application name to the trusted application The POA is configured with an incorrect application name for the trusted application In eDirectory change the expected application name to the application name that the trusted application is providing See Trusted Applications in System in the GroupWise 7 Administration Guide D077 The problem file is being rebuilt Source Explanation Possible Cause Action Group Wise engine
346. tural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 68 Unable to synchronize document security Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot synchronize security information for the specified document in the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 69 Unable to correct document without version object Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot correct the specified document because the version information was missing in the library database dmsh db in the post office The library database is damaged Perform a structural analyze fix on the library See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 7 Administration Guide 70 Unable to correct version without document Source Explanation Possible Cause Action Group Wise Check utility GWCheck GWCheck cannot correct the version information because the specified document was missing in the library database dmsh db in the post office The library database is damaged
347. u are starting the POA as a user that is different from the user the POA is configured to run as The user specified in the uid conf file does not match the user specified in the uid run file The user specified in the uid conf file has been manually edited The uid conf file has been deleted Verify that the uid conf file specifies the desired user then delete the uid run file For more information see Running the Linux Group Wise Agents as a Non root User in Installing GroupWise Agents in the GroupWise 7 Installation Guide GWPOA StartServiceCtrIDispatcher failed when attempting to start Windows_agent service Source Explanation Possible Cause Action Group Wise Post Office Agent for Windows The Windows POA cannot start its dispatcher thread The Windows server is not functioning properly Reboot the Windows server GWPOA The Windows_agent service fails to set service status service stopped Source Explanation Possible Cause Action Group Wise Post Office Agent for Windows The Windows POA cannot start as a service The Windows POA cannot communicate with the service control manager SCM Reboot the Windows server GWPOA The Windows_agent service fails to initialize memory system service stopped Source Explanation Possible Cause Group Wise Post Office Agent for Windows The Windows POA cannot start as a service The Windows POA has insufficient memory resources 190
348. uest packet contained an invalid identifier Someone is trying to forge packets to break into the system Check your system security The server was shut down and brought back up while GroupWise clients were attached Exit and restart the GroupWise clients A TCP IP packet was damaged in transit None 8563 Client server request packet contained invalid identifier Source Action GroupWise engine general communication See 8562 Client server request packet contained invalid identifier on page 29 8567 Data not in BCEF format Source Explanation Possible Cause Action GroupWise engine general communication A packet of information received by an agent was not in the expected format The packet was damaged somewhere between the source and the destination of the data Use packet trace software to identify the source of the problem It could be something like a bad network card or a problem with dial up software 8xxx Engine Error Codes 29 8568 HTTP port already in use Source Explanation Possible Cause Action GroupWise engine general communication The HTTP port used by the POA for its Web console is already in use by another program on the server You are trying to run two POAs on the same server and you have not given them unique HTTP port numbers Check the HTTP port for each POA object See Setting Up the POA Web Console in Monitoring the POA in the GroupWise 7 Adm
349. ume on page 196 GWMTA Maximum number of inbound connections reached Source GroupWise Message Transfer Agent Explanation The MTA could not start another thread for an inbound connection Possible Cause The maximum number of inbound connections as specified by the tcpinbound startup switch has been reached The default is 40 inbound connections Action Increase the setting of the tcpinbound switch to allow for more inbound connections There is no maximum number of inbound connections They are limited only by available system resources See Adjusting the Number of MTA TCP IP Connections in Message Transfer Agent in the GroupWise 7 Administration Guide GWMTA No agent record found Source GroupWise Message Transfer Agent Explanation The MTA object in the eDirectory tree is missing Possible Cause When a domain is created an MTA object is automatically created for it It might have been deleted Action Check for the MTA object in the domain Make sure it is configured correctly See Configuring the MTA in ConsoleOne in Message Transfer Agent in the GroupWise 7 Administration Guide Possible Cause The domain database wodomain db is damaged Action Check and if necessary repair the domain database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide GWMTA No domain record found Source Group Wise Message Transfer Agent Explan
350. ument content on page 263 77 Error accessing blob for official version distribution list on page 263 78 Error accessing blob for current version distribution list on page 263 79 Error accessing blob for version distribution list on page 263 248 GroupWise 7 Troubleshooting 1 Error Messages 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 wphost db for Address Book information Action In ConsoleOne rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide Action For additional information look up the associated engine error code in Part I Group Wise Engine Error Codes on page 11 03 Record read error Source GroupWise Check utility GWCheck Explanation GWCheck cannot read records from 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 Action For additional information look up the associated engine error code in Part I GroupWise Engine Error Codes on page 11 04
351. ument record number DRN for status The domain database wpdomain db or post office database wphost db might be damaged Rebuild the post office database See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide If rebuilding the post office database does not resolve the problem rebuild the domain database 7 4 D03x Errors D030 Missing post office number for status on page 87 D039 Missing attachment on page 87 D03F Database error on page 87 D030 Missing post office number for status Source Explanation Possible Cause Action Action Group Wise engine Necessary information cannot be accessed Inconsistent database information Check and if necessary repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide D039 Missing attachment Source Explanation Possible Cause Action Group Wise engine An attachment for a message can no longer be found If this error occurs in the GroupWise client in Remote mode there might be a problem with the structure or content of the Remote mailbox Delete the rofdata directory on the remote computer then request all inf
352. ument storage area Source Explanation Possible Cause Action Group Wise Post Office Agent The POA cannot delete the document storage area The library database dmsh db is damaged so that the POA cannot read the information necessary to delete the storage area Repair the library See Maintaining Library Databases and Documents in Databases in the GroupWise 7 Administration Guide 192 GroupWise 7 Troubleshooting 1 Error Messages Message Transfer Agent Error Messages e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA e GWMTA Access denied on page 195 Admin database for domain cannot be recovered on page 195 Administrator record not found in database on page 195 Authentication failure for the above object on page 195 Cannot attach to server or volume on page 196 Cannot create a new receiver thread on page 196 Cannot create read write files directories on page 196 Cannot find domain database on page 197 Cannot find startup file on page 197 Cannot move files on page 198 Cannot proceed incompatible GWENNS NLM
353. urce Action Group Wise engine database interface See Dxxx Unexpected error on page 138 D10D Cannot open any more mailboxes Source Explanation Possible Cause Action GroupWise engine database interface Maximum databases open The maximum number of databases that can be opened at one time has been exceeded The maximum number is approximately 12 Shut down some databases by removing proxies Look up proxy deleting users from Access List in Group Wise client Help 7 10 D11x Errors e D110 Unexpected error on page 104 e D113 Open database maximum exceeded on page 104 D114 Group not found on page 104 e D115 Database error on page 104 e D116 File not database on page 104 e D117 GroupWise version too old on page 105 e D118 Database error on page 105 D119 Unexpected error on page 105 DIIB Too many items in mailbox on page 105 e D11C Cannot use group name on page 106 e DIID GroupWise version newer than database on page 106 Dxxx Engine Error Codes 103 D110 Unexpected error Source GroupWise engine database interface Action See Dxxx Unexpected error on page 138 D113 Open database maximum exceeded Source GroupWise engine database interface Explanation The current operation has attempted to open more than the maximum number of databases allowed Possible Cause You are proxied to too many
354. urce Explanation Action Group Wise Internet Agent An unrecognized command was received from ConsoleOne Resend the command GWIA Database initialization error xxxx Source Explanation Action Group Wise Internet Agent The Internet Agent database management code could not be initialized You might need to rebuild the domain database wodomain db for the domain where the Internet Agent is installed See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide 216 GroupWise 7 Troubleshooting 1 Error Messages 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 Explanation An encrypted non queue file was moved to the gwhold directory Action Do not put any files in gwhold remove any files not named with a HEX time stamp and restart the Internet Agent GWIA Deferred delivery file I O error memory error Source GroupWise Internet Agent Explanation The Internet Agent server ran out of memory Action Free more memory GWIA Deferred delivery file I O error message undeliverable Source GroupWise Internet Agent Explanation The message could not be written to disk in the gfiles
355. urce and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide The database has been renamed to another valid database name for example renaming msg7 db to msg8 db This circumstance could indicate tampering by a user attempting to access another user s messages Restore the original database See Restoring Group Wise Databases from Backup in Databases in the GroupWise 7 Administration Guide For information about databases in the post office see Post Office Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3 Message Flow and Directory Structure 6 8 C07x Errors e C071 Unexpected error on page 75 e C072 Database error on page 75 C073 Unexpected error on page 75 C076 Unexpected error on page 75 C077 Unexpected error on page 75 74 GroupWise 7 Troubleshooting 1 Error Messages C078 Unexpected error on page 75 C079 Unexpected error on page 75 C07A Unexpected error on page 76 C07B Database error on page 76 C07C Unexpected error on page 76 C07D Unexpected error on page 76 C07E Unexpected error on page 76 C07F Unexpected error on page 76 C071 Unexpected error Source GroupWise engine database services Action See C0xx Unexpected
356. ured on page 187 GWPOA Not enough disk space for QuickFinder indexing on page 188 GWPOA Not enough memory to complete operation on page 188 GWPOA One or more connections to a remote storage area have been lost and could not be reestablished on page 189 GWPOA Physical connection table full on page 189 GWPOA Possibly damaged blob in database on page 189 GWPOA Possibly dangerous message temporarily suspending dispatcher on page 189 GWPOA Reached inbound connections limit on page 190 Post Office Agent Error Messages 181 on page 190 GWPOA GWPOA page 190 GWPOA GWPOA GWPOA GWPOA GWPOA GWPOA GWPOA Running the agent with conflicting effective users on page 190 GWPOA StartServiceCtrlDispatcher failed when attempting to start Windows agent service The Windows_agent service fails to set service status service stopped on page 190 The Windows agent service fails to initialize memory system service stopped on Timed out waiting for end of file confirmation on page 191 Transport header build failed on page 191 Unable to add additional message handler maximum reached on page 191 Unable to change all configuration options on page 191 Unable to load viewer on page 192 Unable to remove document storage area on page 192 GWPOA Admin database for post_office could not be recovered Source Explanation Possible
357. users in direct mapped mode Action Close some mailboxes that are currently proxied then try the operation again Look up proxy deleting users from Access List in GroupWise client Help D114 Group not found Source GroupWise engine database interface Explanation Bad personal group or public distribution list Action Check the spelling of the group name or select the group in the Address Book D115 Database error Source GroupWise engine database interface Explanation Invalid database Possible Cause Attempted to open an invalid database Action Check and repair the database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Action Run GWCheck See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide Possible Cause This could represent a security breach of unauthorized foreign packets being introduced into your GroupWise system Action Check your system security D116 File not database Source GroupWise engine database interface Explanation Attempt to open a DOS file as a GroupWise database Possible Cause The database is damaged Action Check and if necessary repair the user database See Maintaining Domain and Post Office Databases and Maintaining User Resource and Message Databases in Databases in the GroupWi
358. ut the error copy message files from the subdirectories of the original wpcsout structure into the corresponding subdirectories of the newly created wpcsout directory so the POA can process them If this error occurs on a server where the NetWare POA performs a substantial amount of indexing temporary files that are created and deleted but not purged can build up on the server Most of these temporary files are created and deleted in the index subdirectories of libraries and users mailboxes but some are placed at the root of the sys volume on NetWare servers Purge deleted files from index subdirectories and the root of the sys volume on the server where the problem is occurring Group Wise engine file input output End of file was reached unexpectedly The ngwguard db file has been damaged Check the size of the ngwguard rf1 file roll forward log If it is less than 24 KB it is considered empty Make backup copies of the ngwguard db ngwguard rfl and ngwguard fbk files Delete the ngwguard db file then copy ngwguard fbk to ngwguard db Be sure to copy it do not rename it See also Information Stored in the Post Office in Post Office Agent in the GroupWise 7 Administration Guide One or more of the GroupWise databases might have an invalid owner or no owner For the locations of critical GroupWise databases in domains and post 20 GroupWise 7 Troubleshooting 1 Error Messages Action Source Explanatio
359. ver might not be running Make sure that the DNS name server is running Specify the IP address instead of the DNS hostname 40 GroupWise 7 Troubleshooting 1 Error Messages 8927 Host not reachable Source GroupWise engine TCP IP communication Explanation An agent that is configured for TCP IP attempted to contact another agent and no route could be found on the network to contact the specified host Possible Cause A firewall is interfering with the connection Action Contact the administrator of the firewall to obtain the external IP address for use outside the firewall Possible Cause A router is down Action Make sure that all routers are running 2 6 8Bxx Errors e 8B02 Unexpected error on page 41 8B02 Unexpected error Source GroupWise engine named memory Action See 8xxx Unexpected error on page 42 2 7 8Cxx Errors 8C04 Unexpected error on page 41 8C09 Unexpected error on page 41 8COA Unexpected error on page 41 8C88 Unexpected error on page 41 8C04 Unexpected error Source GroupWise engine process control Action See 8xxx Unexpected error on page 42 8C09 Unexpected error Source GroupWise engine process control Action See 8xxx Unexpected error on page 42 8C0A Unexpected error Source GroupWise engine process control Action See 8xxx Unexpected error on page 42 8C88 Unexpected error Source GroupWise engine p
360. vices and file updates see Novell Support http support novell com 8912 Cannot read on connection timed out Source Explanation Possible Cause Action Possible Cause Action GroupWise engine TCP IP communication Cannot read on connection The sender isn t writing the required information to GroupWise A client or server machine has crashed or the process was forced to close without shutting down The machine might have been exited while connections were active Restart the GroupWise client when the machine is back up If this error appears in the Message Transfer Status box of the POA the MTA to which it is transferring messages might be restarting Check the status of the MTA for the domain If the MTA is restarting the message transfer status should change to Open after the restart is completed 8913 Cannot write on connection timed out Source GroupWise engine TCP IP communication 8xxx Engine Error Codes 35 Explanation Possible Cause Action Cannot write on connection because it is no longer available A client or server machine has crashed or the process was forced to close without shutting down The machine might have been exited while connections were active Restart the Group Wise client to reestablish the connection 8916 Cannot use TCP IP services Source Explanation Possible Cause Possible Cause Action GroupWise engine TCP IP communication No
361. ways in Message Transfer Agent in the GroupWise 7 Administration Guide Synchronize the user manually See Synchronizing Individual Users or Resources in Databases in the GroupWise 7 Administration Guide The user is logging into a specific server rather than into the tree causing the network ID information not to match Log in to the tree rather than to a specific server If this error occurs when a user sends a message to a group the group might contain user IDs that have been deleted from the system Recreate the group selecting users from the Address Book to ensure they are valid Group Wise users Dxxx Engine Error Codes 99 Possible Cause Action Action Possible Cause Action Possible Cause Action Possible Cause Action Possible Cause Action If this error occurs when the user tries to delete users from the Subscribe to Notify window the users might no longer exist in the GroupWise system Check the Address Book to see if the users are still valid If they are not repair the user database user xxx db See Maintaining User Resource and Message Databases in Databases in the GroupWise 7 Administration Guide Run GWCheck on the post office database wphost db See Standalone Database Maintenance Programs in Databases in the GroupWise 7 Administration Guide The user was not found in the post office database wphost db during the parsing
362. where sufficient disk space is available GWPOA Error creating Source Explanation Possible Cause Action Group Wise Post Office Agent TCP agent The POA is configured for TCP IP communication The TCP agent might display a large number of error messages that begin with Error creating Insufficient memory See GWPOA Not enough memory to complete operation on page 188 184 GroupWise 7 Troubleshooting 1 Error Messages GWPOA Error creating file turning disk logging off Source Explanation Possible Cause Action Action Action Group Wise agents Logging information to disk has been turned off because the agent cannot create a new log file The agent cannot create a file in the location specified by the Log File Path setting on the Log Settings page for the agent in ConsoleOne or specified on the command line using the log startup switch See Using POA Log Files in Post Office Agent in the GroupWise 7 Administration Guide Make sure the location exists or specify a more appropriate location Make sure the agent has rights to create files in the specified location Start the POA including the rights switch to determine the specific problem the POA is encountering Make sure there is available disk space in the specified location GWPOA Error initializing communications protocol Source Explanation Possible Cause Action Group Wise Post Office Agen
363. word 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 WEBACC Login rejected No valid password specified Source Explanation Possible Cause Action GroupWise WebAccess Agent A GroupWise WebAccess user could not log in because he or she did not enter a valid password The user did not enter a password when logging in Make sure the user knows his or her mailbox password and enters it when logging in WEBACC Login rejected No valid userid specified Source Explanation Possible Cause Action GroupWise WebAccess Agent A GroupWise WebAccess user could not log in because he or she did not enter a valid GroupWise user ID The user did not enter a GroupWise user ID or full name when logging in Make sure the user knows his or her GroupWise user ID and enters it when logging in Users can also enter their full names as they appear in eDirectory and the GroupWise Address Book WEBACC Login rejected Password is incorrect Source Explanation Possible Cause Action GroupWise WebAccess Agent The password specified during login is incorrect The user entered the wrong password Make sure the user knows his or her mailbox password and enters it when logging in Passwords are case sensitive WEBACC No gateway alias was specified in NW Admin Source Explanation Possible Cause Action GroupWise W
364. work resource on page 242 e 001D Cannot add non Group Wise account to library membership on page 242 e 0021 Gateway setup file not found on page 242 e 0022 Cannot assign non GroupWise user as administrator on page 242 e 002D Pending move on page 242 e 002E Pending delete on page 242 e 0031 Cannot delete post office that owns Group Wise objects on page 243 e 0032 Cannot delete domain that owns Group Wise objects on page 243 e 0033 Cannot delete post office that owns Group Wise objects on page 243 e 0035 Cannot read Group Wise information for object on page 243 e 0036 Cannot access object in different Group Wise system on page 244 e 0038 Owning object domain post office not found in NDS on page 244 e 0039 Invalid UNC path on page 244 e 0041 Cannot authenticate on page 244 e 0042 Cannot authenticate to requested tree on page 244 e 0045 Domain database not found on page 244 0049 Cannot move user from 6 x post office to 4 x post office on page 245 e 0053 Parent domain database not found on page 245 e 0054 Invalid drive specification on page 245 0056 Non networked drive on page 245 e 0057 Cannot create another agent of this type in this context on page 245 e 0059 Cannot create another GroupWise object on page 245 e 0065 Cannot open domain database on page 246 GroupWise Administrator Snap In to ConsoleO
365. xxx Engine Error Codes on page 79 e Exxx Engine Error Codes on page 139 e Fxxx Engine Error Codes on page 159 Other sources of assistance include Novell Support http support novell com e Novell Support Knowledgebase http support novell com search kb_index jsp GroupWise 7 Support Forums http support novell com forums 2gw html Novell GroupWise Support Community http support novell com products groupwise GroupWise Cool Solutions http www novell com coolsolutions gwmag index html GroupWise Engine Error Codes 11 12 GroupWise 7 Troubleshooting 1 Error Messages Oxxx 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 on page 14 000x Unexpected error on page 14 0002 Unexpected error Source GroupWise engine encryption Action See 000x Unexpected error on page 14 0003 Encryption password failed verification process Source GroupWise engine encryption Explanation Wrong encryption password Action Enter the correct password 0004 Encryption password too long Source GroupWise engine encryption Explanation Password too long Action Reduce the password length 0005 Unexpect
366. xxx Engine Error Codes 161 Action See FOxx Query syntax error on page 176 F01B Unknown field in search command Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 F01C Ambiguous field supply more characters Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 FO1D Empty quotation marks not allowed Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 FO1E nowildcard and prefix cannot be used together Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 F01F Invalid syntax in search query Source GroupWise engine QuickFinder Action See FOxx Query syntax error on page 176 9 3 F02x Errors F020 Date expected on page 162 e F021 Dates of range in wrong order on page 162 e F022 Missing switch after on page 163 F023 Word missing between operators on page 163 F026 Database error on page 163 e FO2A Search query must specify words to search for on page 163 e FO2D Missing word after operator on page 163 FO2E Invalid date on page 163 FO2F Word too long for search on page 163 F020 Date expected Source Group Wise engine OuickFinder Action See FOxx Query syntax error on page 176 F021 Dates of range in wrong order Source GroupWise engine QuickFinder 162 Gr
367. y for the current GroupWise system Message Transfer Agent Error Messages 195 Possible Cause Action The record did not originate in the current GroupWise system which is a possible security violation Someone is trying to tamper with your Group Wise system Check your system security measures GWMTA Cannot attach to server or volume Source Explanation Possible Cause Action Action Possible Cause Action Group Wise Message Transfer Agent last closure reason A domain or post office is closed because the NetWare MTA cannot access the server or volume where the domain or post office is located The domain or post office is located on a different server from where the MTA is running and the MTA has not been configured with user information to enable it to log in Make sure the MTA startup file includes the user and password or dn switches so the MTA can log into the remote server Make sure the user and password information is correct and current Make sure the information is formatted correctly In some configurations you might need to specify a distinguished name for example user org_unit org for the user switch rather than just a simply user ID In some configurations you might need to include the type for example CN user org_unit org If the MTA still cannot log in to the remote server after appropriate user information has been supplied start the MTA with tracelogin 2 to display

GroupWise 7 Troubleshooting 1: Error Messages

Contents

Download Pdf Manuals

Related Search

Related Contents