18.1 GroupWise Engine Error Codes

0xxx Engine Error Codes

Range: 000x

8xxx Engine Error Codes

Range: 81xx

Range: 82xx

Range: 85xx

Range: 88xx

Range: 89xx

Range: 8Bxx

Range: 8Cxx

Range: 8Fxx

9xxx Engine Error Codes

Range: 90xx

Range: 93xx

Axxx Engine Error Codes

Range A0xx

Range: A5xx

Range: A6xx

Range: A8xx

Range: AAxx

Range: ACxx

Bxxx Engine Error Codes

Range: B3xx

Cxxx Engine Error Codes

Range: C00x

Range: C01x

Range: C02x

Range: C03x

Range: C04x

Range: C05x

Range: C06x

Range: C07x

C08x

Dxxx Engine Error Codes

Range: D00x

Range: D01x

Range: D02x

Range: D03x

Range: D04x

Range: D05x

Range: D06x

Range: D07x

Range: D10x

Range: D11x

Range: D12x

Range: D20x

Range: D50x

Range: D70x

Range: D71x

Range: D90x

Range: DA0x

Range: DA1x

Range: DB0x

Range: DB1x

Range: DB2x

Range: DB3x

Range: DB4x

Range: DB5x

Range: DExx

Range: DFxx

Exxx Engine Error Codes

Range: D50x

Range: D51x

Range: D52x

Range: E7xx

Range: E80x

Range: E81x

Range: E82x

Range: E84x

Fxxx Engine Error Codes

Range: F00x

Range: F01x

Range: F02x

Range: F03x

Range: F04x

Range: F05x

Range: F06x

Range: F07x

Range: F08x

Range: F09x

Range: F0Ax

Range: F0Bx

Range: F0Cx

Range: F1xx

0001 Invalid encryption block

Source: GroupWise® engine; encryption
Explanation: Invalid encryption block. File cannot be decrypted or user access verified.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

0002 Unexpected error

Source: GroupWise engine; encryption.
Action: See 000x Unexpected error.

0003 Encryption password failed verification process

Source: GroupWise engine; encryption.
Explanation: Wrong encryption password.
Action: Enter the correct password.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

0004 Encryption password too long

Source: GroupWise engine; encryption.
Explanation: Password too long.
Action: Reduce the password length.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

0005 Unexpected error

Source: GroupWise engine; encryption.
Action: See 000x Unexpected error

0006 Unexpected error

Source: GroupWise engine; encryption.
Action: See 000x Unexpected error

0007 Unexpected error

Source: GroupWise engine; encryption.
Action: See 000x Unexpected error

0008 Unexpected error

Source: GroupWise engine; encryption.
Action: See 000x Unexpected error

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.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8101 Memory error

Source: GroupWise® engine; memory management.
Explanation: Memory function failure. Invalid memory handle.
Possible Cause: If this error occurs in the NetWare® POA, there might be insufficient memory on the server for the POA to run. On the server where the POA runs, cache buffers should be around 60%. If cache buffers drop below 30%, there is not enough memory available.
Action: 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.
Possible Cause: If this error occurs in the NetWare POA, some current server parameters might be set too low.
Action: Increase the settings for the following NetWare® server parameters:

  • Minimum Packet Receive Buffers

  • Maximum Directory Cache Buffers

  • Maximum Services Processes

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

Possible Cause: If this error occurs in the NetWare agents after updating your GroupWise system, you might not have updated the agents properly.
Action: After exiting all the agents, unload the agent engine (gwenn4.nlm), then perform the update. See “Updating Your GroupWise 6.x System to Version 6.5” in “Update” in the GroupWise 6.5 Installation Guide.
Possible Cause: If this error occurs when starting the GroupWise client, the user might have exceeded the limit of viewable 65,000 items per folder. Remember that Trash 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 at (@) signs 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 GroupWise Remote, GroupWise might not be installed correctly on the remote computer.
Action: Reinstall GroupWise on the remote computer. See the platform-specific setup instructions for GroupWise Remote in “GroupWise Modes” in “Client” in the GroupWise 6.5 Administration Guide.
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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8200 File I/O error

Source: GroupWise engine; file input/output.
Explanation: Generic file I/O error. Any file I/O error that cannot be mapped to a more specific file I/O error message.
Possible Cause: A GroupWise database has been damaged so as to be unrecognizable as a GroupWise database, for example, having a size of 0 KB or 2 GB.
Action: For the locations of GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Restore the damaged database(s) from backup.
Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner.
Action: Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
Possible Cause: If this error occurs when users are trying to log in to GroupWise through the GroupWise Internet Agent from a POP3 mail client, the post office link information needed by the GroupWise Internet Agent might be incorrect.
Action: Check the post office link set up for the GroupWise Internet Agent. In ConsoleOne, browse to and select the Domain object where the Internet Agent is installed. Right-click the GWIA object, then click Properties. Click Post Office Links, select the post office, then click Edit Link. Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server Access box. See “Internet Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8201 Access to file denied

Source: GroupWise engine; file input/output.
Explanation: 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.
Possible Cause: If this error occurs from the POA, the POA might not have access to a required file.
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” in the GroupWise 6.5 Administration Guide.
Possible Cause: 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.
Action: Connect to the domain where you want the post office located. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs when users exit the GroupWise client, the users might have their archive directory set to a location where they do not have sufficient rights.
Action: 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.
Possible Cause: 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.
Action: See “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Make sure all required files are present in the post office directory, especially the *.dc files, which are required for creating new user and message databases. If *.dc files are missing, copy them from another post office or from the po subdirectory of the software distribution directory.
Possible Cause: If this error occurs for a user who has previously been able to access GroupWise successfully, the user’s Novell® eDirectory™ object might have become damaged.
Action: Delete the user object from eDirectory, then recreate it. Do not delete the user’s GroupWise account, because this would delete the user’s mailbox as well.
Possible Cause: If this error occurs when users exit the GroupWise client, the user database (userxxx.db) might be damaged.
Action: Check and, if necessary, repair the user database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The GroupWise databases might be owned by an invalid user.
Action: For the locations of GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
Possible Cause: Another program might already have the required file open with exclusive access.
Action: Check the open/lock activity on GroupWise databases and other files. You might find that a backup program or virus scanner is holding the file open.
Possible Cause: The GroupWise 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.
Action: When the network connection to the post office is reestablished the GroupWise client will function normally again. Reboot the machine. If the post office still cannot be accessed, resolve those network problems.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8202 Cannot access required file

Source: GroupWise engine; file input/output.
Explanation: Bad file handle.
Possible Cause: GroupWise is no longer able to access a required file.
Action: Exit and then restart the GroupWise program that displayed the error.
Possible Cause: An invalid or old (closed) file handle was passed to a file I/O function.
Action: Perform the action again. If the same error occurs, exit and then restart the GroupWise program that displayed the error.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8203 Cannot copy file or directory

Source: GroupWise engine; file input/output.
Explanation: Copy error.
Possible Cause: If this error occurs when trying to rebuild a post office database, the domain or the post office might not contain the correct files.
Action: For the required contents of domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Make sure the post office you are trying to rebuild and the domain it belongs to contain the correct files (especially *.dc files).
Possible Cause: If this error occurs in GroupWise Remote, there might be a problem with the structure or content of the Remote mailbox. For example, copying a GroupWise Remote installation from one laptop to another might introduce this problem.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Reinstall GroupWise Remote on the remote computer. See the platform-specific setup instructions for GroupWise Remote in “GroupWise Modes” in “Client” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8204 Disk full

Source: GroupWise engine; file input/output.
Explanation: Disk full.
Possible Cause: There is no space left on a disk when writing and/or creating a file.
Action: Create space on disk by deleting unwanted or unnecessary files.
Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner.
Action: For the locations of GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
Possible Cause: 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.
Action: Check the ownership of these databases and make sure that owner does not have disk space restrictions.
Action: If disk space is available and database ownership is correct, the disk itself might need repair.
Possible Cause: If this error occurs from the POA, there might be a problem with its input queue.
Action: Stop the POA. Rename the wpcsout directory in the post office. Restart the POA. This recreates the wpcsout directory structure for the post office. If the POA now runs without the error, copy message files from the subdirectories of the original wpcsout structure into the corresponding subdirectories of the newly created wpcsout directory so the POA can process them.
Possible Cause: 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.
Action: Purge deleted files from index subdirectories and the root of the sys: volume on the server where the problem is occurring.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8205 End of file

Source: GroupWise engine; file input/output.
Explanation: End of file was reached unexpectedly.
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 also “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner. For the locations of critical GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8206 Cannot open file

Source: GroupWise engine; file input/output.
Explanation: File open error.
Possible Cause: GroupWise cannot copy the specified file. During an explicit file copy function, failure to create the destination file will generate this error. If the destination file exists and is read only, this error might occur.
Action: Check destination filename specified and ensure it is unique.
Possible Cause: If this error occurs the first time a user tries to archive messages, the user might not have sufficient rights to the archive location.
Action: 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.
Possible Cause: If this error occurs when updating the GroupWise client software, users might be running the client software.
Action: 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 the software. Check the open/lock activity on the GroupWise program files.
Possible Cause: If this error occurs from the POA, the POA might not have access to a required file.
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” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8207 Cannot locate file

Source: GroupWise engine; file input/output.
Explanation: File seek error.
Possible Cause: A failure occurred when positioning file pointers during an explicit file copy function. Cannot open the specified file or directory.
Possible Cause: If this error occurs when a specific user starts the GroupWise client, that user database (userxxx.db) might be damaged.
Action: Check and, if necessary, repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8208 Cannot modify file

Source: GroupWise engine; file input/output.
Explanation: File modify error.
Possible Cause: Cannot move or rename the file. An error occurred when renaming or moving a file to another location.
Action: Check to see if another file with the same name exists (the filename must be unique). If so, rename that file, or move/rename the current file.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8209 Path not found

Source: GroupWise engine; file input/output.
Explanation: Drive or path not found.
Possible Cause: GroupWise cannot find the specified drive or path.
Action: Use Browse to find the correct path.
Possible Cause: The file you are trying to perform an action on does not exist.
Action: Enter a valid filename.
Possible Cause: If this error occurs shortly after starting the GroupWise client, the path to the archive directory might not be correct.
Action: In the GroupWise client, verify the path to the archive directory exists and that you have sufficient rights to create and modify files. Look up "archive, directory" in GroupWise client Help.
Action: 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 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Possible Cause: If this error occurs from the POA, the POA might not have access to a required file.
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” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs from the MTA, the MTA might not have access to one or more of the post offices in the domain.
Action: Verify the list of post offices belonging to the domain is correct. To view the list in ConsoleOne, browse to and right-click the Domain object, then click Properties. Click GroupWise > Post Offices. Check the properties of each Post office object to make sure that the post office directory for each post office exists. Make sure the post office path is correctly defined in the Post Office object. In ConsoleOne, right-click the Post Office object to display the post office Identification page. Also make sure the MTA has access to the post office.
Possible Cause: If this error occurs when importing a document into GroupWise, there might be a problem with the library.
Action: Check and, if necessary, fix the library. See “Maintaining Library Databases and Documents” in “Databases” in the GroupWise 6.5 Administration Guide. Then synchronize the library. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If documents are being stored at the post office, make sure the docs subdirectory exists for the library.
Action: 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 > 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.
Possible Cause: If this error occurs when trying to access a document in a library, the BLOB file containing the document might no longer exist.
Action: You can determine what BLOB file the document was in from the GroupWise client. Right-click the document reference, then click Properties > Activity Log. If filenames are not currently displayed, right-click the menu bar, then click Filename to display the filename in the activity log. If the document is needed, you can restore the BLOB file from backup. See “Restoring Archived Documents” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.

If the document is not needed, you can delete it from the library to eliminate the error.

Action: Have the original sender of the message resend the attachment.
Possible Cause: Some applications, such as Corel WordPerfect* 7, MS Word 95, and Excel 95, need a blank file stored in the c:/windows/shellnew directory. For example, Corel WordPerfect 7 needs a file named wordpfct.wpd to exist in the shellnew directory in order to create a new file when called from GroupWise. If this error occurs when creating a new document in the GroupWise client, the blank template file for the application might be missing.
Action: 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 GroupWise.
Possible Cause: A directory required for the normal flow of GroupWise messages could be missing.
Action: See “Message Transfer/Storage Directories” in “Directory Structure Diagrams” in GroupWise 6.5 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).
Possible Cause: A required file or subdirectory could be missing from the directory structure of the user’s post office.
Action: See “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Verify the existence, ownership, and rights of the files and subdirectories in the user’s post office. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide.
Possible Cause: 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.
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 location of this file, see “Post Office Directory” and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. New user databases (userxxx.db files) and message databases (msgnn.db files) cannot be created for new users if this file is missing.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

820A Cannot open any more files

Source: GroupWise engine; file input/output.
Explanation: Too many files open.
Action: Record the conditions under which you encountered the error. For r the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

820B Path too long

Source: GroupWise engine; file input/output.
Explanation: Path too long.
Possible Cause: The file system cannot build or modify a path because the specified path contains too many characters.
Action: 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.
Possible Cause: 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 Windows* Explorer or Network Neighborhood to map the drive, you might have browsed under the tree icon, rather than under the server icon.
Action: Make sure you have mapped the drive where you are creating the GroupWise system to the correct volume on the server, not to an object in the eDirectory tree.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

820D File too large

Source: GroupWise engine; file input/output.
Explanation: File size is too large.
Possible Cause: When truncating a file, the passed size of the file is greater than the actual size of the file.
Action: Record the conditions under which you encountered the error. For r the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

820E Cannot lock file

Source: GroupWise engine; file input/output.
Explanation: File lock error.
Possible Cause: An attempt to lock a file failed.
Action: Check to verify the file is not currently locked by another process that has terminated.
Possible Cause: You cannot open the specified file because another user might have the file open.
Action: Ask the other user to close the file.
Action: Retry the action later.
Action: If no valid user or process has the file open, delete the connection to unlock the file.
Possible Cause: You cannot open the specified file because you might not have rights to open the file.
Action: Obtain rights to the file.
Possible Cause: 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.
Action: 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.
Action: Exit, then restart the POA.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

820F Cannot unlock file

Source: GroupWise engine; file input/output.
Explanation: File unlock error.
Possible Cause: An attempt to unlock a file failed.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8210 Cannot create path

Source: GroupWise engine; file input/output.
Explanation: Path create failed. An attempt by the file system to create a unique file failed.
Possible Cause: 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.
Action: 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.
Action: 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 (msgnn.db) of the user who sent the problem items. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: In the GroupWise client, open the archive, then use the Repair Mailbox feature to repair the archive. See “Enabling GroupWise Check in the Windows Client” in “Client” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck on the archive. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. GWCheck provides additional repair options compared to the Repair Mailbox feature in the GroupWise client.
Possible Cause: If this error occurs from the POA, the POA might not have access to a required location.
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” in the GroupWise 6.5 Administration Guide.
Possible Cause: 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.
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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8211 Cannot rename file

Source: GroupWise engine; file input/output.
Explanation: File rename failed.
Possible Cause: Attempt by the file system to rename a file failed.
Action: Make sure the specified filename is unique.
Possible Cause: A directory required for the normal flow of GroupWise messages might be missing.
Action: See “Message Transfer/Storage Directories” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Verify the existence, ownership, and rights of the directories involved with message flow (domain, post office, and MTA local directory).
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8212 Password incorrect

Source: GroupWise engine; file input/output.
Explanation: Invalid file password.
Possible Cause: The password entered by the user does not match the one stored in the encrypted file.
Action: Reenter the password.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8213 Invalid file operation

Source: GroupWise engine; file input/output.
Explanation: Invalid file operation.
Possible Cause: Requested an illegal file operation on an encrypted file.
Action: Record the conditions under which you encountered the error. For r the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8214 Unsupported encryption level

Source: GroupWise engine; file input/output.
Explanation: Unsupported encryption level in file.
Possible Cause: Attempted to decrypt a file using an encryption level that is no longer supported.
Action: The file you are trying to open was created in a newer version of GroupWise and cannot be opened in an older version. Update to the latest version of GroupWise. To check the date of the GroupWise client you are using, click Help > About GroupWise. For technical services and file updates, see Novell Technical Support.
Action: Make sure the archive directory is not locked to an unusable location. In ConsoleOne, browse to and select the post office the user belongs to, then click Tools > GroupWise Utilities > Client Options > Environment > File Location. Check the setting in the Archive Directory field and whether or not it is locked.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8215 Path root error

Source: GroupWise engine; file input/output.
Explanation: At path root.
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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8216 Cannot encrypt or decrypt file

Source: GroupWise engine; file input/output.
Explanation: Encryption/decryption error.
Possible Cause: Attempt to encrypt or decrypt a file failed.
Action: Record the conditions under which you encountered the error. For r the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8218 Invalid path

Source: GroupWise engine; file input/output.
Explanation: Invalid path specified.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 machine.
Possible Cause: If this error occurs when running the Windows NT*/2000 agents, the user’s user name and password on the machine where the POA is running is different from their user name and password on the machine where the document storage area is located.
Action: Use the same user name and password on the machine where the POA is running and the machine where the document storage area is located.
Action: Use the /user and /password switches to provide the login information for the machine where the document storage area is located. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8502 Cannot initialize protocol

Source: GroupWise engine; general communication.
Explanation: Cannot open protocol.
Action: See 8901 Cannot use TCP/IP services.

8503 Cannot connect to specified IP address

Source: GroupWise engine; general communication.
Explanation: Cannot open connection to specified address.
Action: See 8908 Cannot connect to specified address.

8509 Cannot access TCP/IP services

Source: GroupWise engine; general communication.
Explanation: TCP/IP bind failed.
Possible Cause: TCP/IP is not loaded on the machine or is not loaded correctly. The TCP port is already in use by another process.
Action: Configure TCP/IP on the machine 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 Technical Support.
Action: Reboot the machine.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

850F Connection no longer valid

Source: GroupWise engine; general communication.
Explanation: Connection was broken while in use.
Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active.
Action: Exit and restart GroupWise when the machine is back up.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8555 Port in use

Source: GroupWise engine; general communication.
Explanation: Port in use.
Possible Cause: The POA defaults to TCP/IP communication, but the necessary TCP/IP information is not configured in ConsoleOne. The default TCP port used by the POA (1667) is in use by another program.
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 6.5 Administration Guide.
Action: To disable TCP/IP communication, use the /notcpip switch when starting the POA. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Possible Cause: You are trying to run two POAs on the same machine in client/server mode and you have not given them unique TCP port numbers.
Action: Check the TCP port for each POA object. See “Using Client/Server Access to the Post Office” in “Configuring the POA” in the GroupWise 6.5 Administration Guide. Change the TCP port for one of the POAs.
Possible Cause: You are trying to run two POAs on the same machine in client/server mode and you haven’t created a second POA object in ConsoleOne.
Action: In ConsoleOne, create a second POA object in the post office. Make sure you give it a unique TCP port number, different from what the first POA is using. Use the /name switch when starting each POA. You might want to create a separate startup file for each POA. See “Creating a POA Object in eDirectory” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8562 Client/server request packet contained invalid identifier

Source: GroupWise engine; general communication.
Explanation: Client/server request packet contained an invalid identifier.
Possible Cause: Someone is trying to forge packets to break into the system.
Action: Check your system security.
Possible Cause: The machine was shut down and brought back up while GroupWise clients were attached.
Action: Exit and restart the GroupWise clients.
Possible Cause: A TCP/IP packet was damaged in transit.
Action: None.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8563 Client/server request packet contained invalid identifier

Source: GroupWise engine; general communication.
Action: See 8562 Client/server request packet contained invalid identifier

8568 HTTP port already in use

Source: GroupWise engine; general communication.
Explanation: The HTTP port used by the POA for its Web console is already in use by another program on the machine.
Possible Cause: You are trying to run two POAs on the same machine and you have not given them unique HTTP port numbers.
Action: Check the HTTP port for each POA object. See “Setting Up the POA Web Console” in “Monitoring the POA” in the GroupWise 6.5 Administration Guide. Change the HTTP port for one of the POAs.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8569 SSL login required for this post office

Source: GroupWise engine; general communication.
Explanation: Starting with GroupWise 6.5, the POA can be configured to require SSL connections with clients.
Possible Cause: Users of clients earlier than GroupWise 6.5 are trying to log in to the post office.
Action: Have users update their GroupWise client software. See “Updating Users’ GroupWise Clients” in “Update” in the GroupWise 6.5 Installation Guide.
Action: Configure the POA so that SSL is enabled rather than required, so that the older GroupWise clients can connect to the post office. See “Enhancing Post Office Security with SSL Connections to the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8570 IMAP port already in use

Source: GroupWise engine; general communication.
Explanation: The IMAP port used by the POA to communicate with IMAP e-mail clients is already in use by another program on the machine.
Possible Cause: You are trying to run two POAs on the same machine and you have not given them unique IMAP port numbers.
Action: Check the IMAP port for each POA object. See “Supporting IMAP Clients” in “Configuring the POA” in the GroupWise 6.5 Administration Guide. Change the IMAP port for one of the POAs.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 machine.
Possible Cause: You are trying to run two POAs on the same machine 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 6.5 Administration Guide. Change the CAP port for one of the POAs.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8809 Unexpected error

Source: GroupWise engine; inter- or intra-process communication
Action: See 8xxx Unexpected error.

880B Unexpected error

Source: GroupWise engine; inter- or intra-process communication
Action: See 8xxx Unexpected error.

880C Unexpected error

Source: GroupWise engine; inter- or intra-process communication
Action: See 8xxx Unexpected error.

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 machine.
Possible Cause: Cannot load WINSOCK (Windows only), or the WINSOCK that did load is not supported. DNS is not loaded and you are trying to resolve DNS names.
Action: Correctly configure TCP/IP on the machine.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8902 Cannot load TCP/IP services

Source: GroupWise engine; TCP/IP communication.
Explanation: TCP/IP load failed because a required file was missing.
Possible Cause: Unable to load TCP/IP services because one or more of the required files is missing: winsock.dll, wsoc32.dll, or tcpip.nlm.
Action: Make sure that you have the required files, and that they are in the search path.
Action: Correctly configure TCP/IP on the machine.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8903 Cannot use TCP/IP services

Source: GroupWise engine; TCP/IP communication.
Action: See 8901 Cannot use TCP/IP services.

8906 Cannot use TCP/IP services

Source: GroupWise engine; TCP/IP communication.
Action: See 8901 Cannot use TCP/IP services.

8907 Cannot use TCP/IP services

Source: GroupWise engine; TCP/IP communication.
Action: See 8901 Cannot use TCP/IP services.

8908 Cannot connect to specified address

Source: GroupWise engine; TCP/IP communication.
Explanation: Connection to the specified address failed.
Possible Cause: Unable to load TCP/IP services because one or more of the required files is missing: winsock.dll, wsoc32.dll, or tcpip.nlm.
Action: Make sure that you have the required files, and that they are in the search path.
Action: Correctly configure TCP/IP on the machine. Make sure you are using a current IP stack. If you must use an older IP stack, try specifying the IP address in dotted numeric format (123.456.78.90), rather than as a host name that requires resolution, when setting the /ipa switch.
Action: When using direct mode rather than client/server, the GroupWise client still requires a valid winsock.dll to be available on the search path. Make sure a current, valid winsock.dll file is available on the machine where the problem is occurring.
Possible Cause: The GroupWise client cannot establish a TCP/IP connection with the POA.
Action: Check the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Check the status of the POA machine and the load on the network.
Possible Cause: If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages is not running.
Action: Check the status of the MTA for the domain. Restart the MTA if necessary.
Possible Cause: 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.
Action: Check the post office link set up for the Internet Agent. In ConsoleOne, click the domain where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties. Click Post Office Links, select the post office, then click Edit Link. Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server box.
Action: Use a UNC or mapped link between the Internet Agent and the POA, rather than a TCP/IP link.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8909 Cannot use TCP/IP services

Source: GroupWise engine; TCP/IP communication.
Action: See 8901 Cannot use TCP/IP services.

890A Cannot listen on specified port

Source: GroupWise engine; TCP/IP communication.
Explanation: Listen failed.
Possible Cause: Unable to listen on the specified port. It is possible the specified port is in use by another process. For example, the user might be running two GroupWise agents on the same machine where both were configured for the same port.
Action: Verify the IP address and port provided in ConsoleOne are correct. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

890B Cannot accept incoming connection

Source: GroupWise engine; TCP/IP communication.
Explanation: Acceptance failed.
Possible Cause: Hardware is overloaded.
Action: Upgrade the hardware.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

890F Connection no longer valid

Source: GroupWise engine; TCP/IP communication.
Explanation: Connection was broken while in use.
Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active.
Action: Make sure the POA is running. Check the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Possible Cause: 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.
Action: 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 6.5 Administration Guide.
Possible Cause: If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages is not running.
Action: Check the status of the MTA for the domain. Restart the MTA if necessary.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8910 Cannot read on connection

Source: GroupWise engine; TCP/IP communication.
Explanation: Read failed.
Action: Retry the operation.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8911 Cannot write on connection

Source: GroupWise engine; TCP/IP communication.
Explanation: Cannot write on connection; the receiver isn’t responding.
Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active.
Action: Restart the GroupWise client.
Possible Cause: If this error occurs from the POA, the machine where the POA runs might not have the most current version of TCP/IP.
Action: Install the latest TCP/IP. For technical services and file updates, see Novell Technical Support.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8912 Cannot read on connection; timed out

Source: GroupWise engine; TCP/IP communication.
Explanation: Cannot read on connection. The sender isn’t writing the required information to GroupWise.
Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active.
Action: Restart the GroupWise client when the machine is back up.
Possible Cause: If this error appears in the Message Transfer Status box of the POA, the MTA to which it is transferring messages might be restarting.
Action: 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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8913 Cannot write on connection; timed out

Source: GroupWise engine; TCP/IP communication.
Explanation: Cannot write on connection because it is no longer available.
Possible Cause: A client or server machine has crashed, or the process was forced to close without shutting down. The machine might have been exited while connections were active.
Action: Restart the GroupWise client to reestablish the connection.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8916 Cannot use TCP/IP services

Source: GroupWise engine; TCP/IP communication.
Explanation: No network error.
Possible Cause: TCP/IP services couldn’t be used. It is possible that TCP/IP isn’t loaded correctly on the machine.
Possible Cause: GroupWise has encountered unusually long timeouts while trying to retrieve names from DNS. This probably occurred in Windows where the machine is not connected to the network.
Action: Check the network connections for the machine.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

891A TCP/IP data is not ready for reading

Source: GroupWise engine; TCP/IP communication.
Explanation: The TCP/IP connection is blocked.
Possible Cause: The data has been delayed by SSL encryption.
Action: None. TCP/IP services will continue to try to read the data.
Action: If the problem persists, check the line connection and the NIC card on the server.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

891B No SSL certificate supplied

Source: GroupWise engine; TCP/IP communication.
Explanation: You have configured an agent for SSL, but the agent cannot locate the SSL certificate.
Possible Cause: In ConsoleOne, you enabled SSL on the Agent object Network Address page but did not provide the certificate information on the SSL Settings page.
Action: Finish configuring the agent for SSL. See the following sections of the GroupWise 6.5 Administration Guide, depending on which agent is encountering the problem:
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

891C Bad SSL certificate

Source: GroupWise engine; TCP/IP communication.
Explanation: You have configured an agent for SSL, but the agent cannot read the SSL certificate.
Possible Cause: The SSL certificate is not in the required format.
Action: Obtain an SSL certificate in the proper format. See “Encryption and Certificates” in “Security” in the GroupWise 6.5 Administration Guide.
Possible Cause: The SSL certificate has been damaged.
Action: Replace the bad SSL certificate with a valid SSL certificate.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

891D Bad SSL private key or password

Source: GroupWise engine; TCP/IP communication.
Explanation: You have configured an agent for SSL, but the agent cannot read the private key file or the password.
Possible Cause: The SSL certificate that accompanies the private key file is not in the required format.
Action: Obtain an SSL certificate in the proper format. See “Encryption and Certificates” in “Security” in the GroupWise 6.5 Administration Guide.
Possible Cause: The password you provided on the agent object SSL Settings page in ConsoleOne does not match the password in the private key file.
Action: Correct the password information in ConsoleOne. See the following sections of the GroupWise 6.5 Administration Guide, depending on which agent is encountering the problem:
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

8B02 Unexpected error

Source: GroupWise engine; named memory.
Action: See 8xxx Unexpected error.

8C04 Unexpected error

Source: GroupWise engine; process control.
Action: See 8xxx Unexpected error.

8C09 Unexpected error

Source: GroupWise engine; process control.
Action: See 8xxx Unexpected error.

8C0A Unexpected error

Source: GroupWise engine; process control.
Action: See 8xxx Unexpected error.

8C88 Unexpected error

Source: GroupWise engine; process control.
Action: See 8xxx Unexpected error.

8F03 Invalid configuration option

Source: GroupWise engine; server toolkit.
Explanation: Invalid startup switch specified when starting one of the agents.
Action: Check the startup switches in use for the agent reporting the error. For lists of startup switches, see “Using POA Startup Switches” in “Post Office Agent” and “Using MTA Startup Switches” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

9007 Client not set up for SSL

Source: GroupWise® engine; client/server.
Explanation: The POA is configured to require SSL communicate with the GroupWise client, but the client is not capable of SSL communication.
Possible Cause: 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 higher.
Action: Update the client to GroupWise 6.5 or higher.
Action: 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

9008 Server does not support SSL

Source: GroupWise engine; client/server.
Explanation: The GroupWise client is trying to use an SSL connection to the POA but the POA is not configured for SSL.
Possible Cause: The POA has been reconfigured without SSL since the client logged in.
Action: Restart the GroupWise client. It will not try to use SSL when it detects that the POA is not configured for SSL.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

9302 Unexpected error

Source: GroupWise engine; loadable language resource.
Action: See 9xxx Unexpected error.

9304 Unexpected error

Source: GroupWise engine; loadable language resource.
Action: See 9xxx Unexpected error.

9305 Unexpected error

Source: GroupWise engine; loadable language resource.
Action: See 9xxx Unexpected error.

9307 Unexpected error

Source: GroupWise engine; loadable language resource.
Action: See 9xxx Unexpected error.

9308 Unexpected error

Source: GroupWise engine; loadable language resource.
Action: See 9xxx Unexpected error.

9309 Unexpected error

Source: GroupWise engine; loadable language resource.
Action: See 9xxx Unexpected error.

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.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

A001 Unexpected error

Source: GroupWise® engine; sized string manipulation.
Action: See Axxx Unexpected error.

A501 Unexpected error

Source: GroupWise engine; data array management.
Action: See Axxx Unexpected error.

A502 Unexpected error

Source: GroupWise engine; data array management.
Action: See Axxx Unexpected error.

A504 Unexpected error

Source: GroupWise engine; data array management.
Action: See Axxx Unexpected error.

A602 Unexpected error

Source: GroupWise engine; data list management.
Action: See Axxx Unexpected error.

A801 Auto-Date formula too long

Source: GroupWise engine; Auto-Date.
Explanation: Formula is too long.
Possible Cause: The user either entered formula text which was too large (4 KB is maximum), or the user selected from the graphical Auto-Date window and the generated formula was too large.
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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

A802 Auto-Date formula has incorrect syntax

Source: GroupWise engine; Auto-Date.
Explanation: Formula is invalid.
Possible Cause: The user entered a formula which 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 GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 out and reenter the send window. This will generate a default formula, which will not give the above error. Look up "auto-dates" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

A804 Auto-Date formula generates too many occurrences

Source: GroupWise engine; Auto-Date.
Explanation: Auto-Date occurrences truncated.
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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

AA01 Unexpected error

Source: GroupWise engine; ASCII strings.
Action: See Axxx Unexpected error.

AA02 Unexpected error

Source: GroupWise engine; ASCII strings.
Action: See Axxx Unexpected error.

AA04 Unexpected error

Source: GroupWise engine; ASCII strings.
Action: See Axxx Unexpected error.

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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

AC03 Zipped file damaged

Source: GroupWise engine; zip/compression.
Explanation: The zipped file failed a checksum test.
Action: None. GroupWise cannot unzip the file.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

Axxx 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.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

B300 File transmission failed

Source: GroupWise® engine; Message Transfer Protocol.
Explanation: The POA was not able to transfer a message file to the MTA.
Possible Cause: The MTA restarted during transmission of the file.
Possible Cause: The network experienced a slow-down, causing the MTA to time out while waiting for the rest of the file.
Action: None. The POA will automatically resend the message until the message is sent successfully.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

B309 Port already in use

Source: GroupWise engine; Message Transfer Protocol.
Explanation: The specified port is already in use.
Possible Cause: 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.
Action: The message transfer port configured for the POA should be the same port number as the MTA is using to listen on. Make sure the MTA is set up correctly for TCP/IP links. Make sure the POA is configured with the message transfer port number matching the port number of the MTA. See “Changing the Link Protocol between the Post Office and the Domain” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

B30A No peer listening for connection

Source: GroupWise engine; Message Transfer Protocol.
Explanation: The POA is attempting to communicate with the MTA by way of TCP/IP but the MTA is not responding.
Possible Cause: The MTA is not running.
Action: Start the MTA.
Possible Cause: The machine where the MTA is running is overloaded so the MTA cannot respond to the POA in a timely manner.
Action: Check the load on the machine where the MTA is running. If necessary, stop some other programs or upgrade the machine so adequate resources are available for the MTA to function properly.
Possible Cause: The MTA is not configured for TCP/IP links.
Action: Reconfigure the MTA for TCP/IP links. See “Changing the Link Protocol between Domains” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C006 Record, key, or key reference not found

Source: GroupWise® engine; database services.
Explanation: A record or key was not found.
Possible Cause: In the GroupWise client, the user dragged away all the column headings.
Action: Restore the column headings. Right-click the bar where the column headings belong select some column headings such as From, Subject, Date, etc., from the drop-down list.
Possible Cause: If this error occurs when creating a post office, you might not be connected to the correct domain.
Action: If you try to create a post office in a secondary domain while connected to a different domain, you might not have sufficient rights to create the post office correctly. It might show up in the GroupWise View but not have an Novell® eDirectory™ object created for it. Connect to the secondary domain. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then graft the post office into the correct domain. See “GW / eDirectory Association” in “System” in the GroupWise 6.5 Administration Guide.
Possible Cause: 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.
Action: In ConsoleOne®, display the GroupWise View. Right-click the Library object, then click Properties. Remove the path to the document storage area that no longer exists. Select Store Documents in Post Office, then click OK. Then delete the library object from the GroupWise View.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C007 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C008 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C009 Database error

Source: GroupWise engine; database services.
Action: C0xx Database error (Support assistance recommended).

C00A Database error

Source: GroupWise engine; database services.
Action: C0xx Database error (Support assistance recommended).

C00B Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C00C 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 6.5 Administration Guide. Then perform the rebuild again.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C00D Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C00E 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, the 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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C00F 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 “Moving GroupWise Accounts” in “Users” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs when rebuilding a database, you might not be connected to the correct GroupWise system.
Action: Connect to the GroupWise system where the database is located. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then perform the rebuild again.
Possible Cause: The password information in the user database (userxxx.db) has been damaged.
Action: Check and, if necessary, repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs in the GroupWise client when accessing archived messages, the archive might be damaged.
Action: In the GroupWise client, open the archive, then use the Repair Mailbox feature to repair the archive. See “Enabling GroupWise Check in the Windows Client” in “Client” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck on the user’s archive. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C010 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C011 Database being modified

Source: GroupWise engine; database services.
Explanation: Read encountered a modified block.
Possible Cause: A read operation encountered a block in the database that was being modified by another user. 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 will generally correct itself. As a general rule, transaction logging should never be disabled on GroupWise 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C012 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C014 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C015 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C016 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C017 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C018 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C019 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C01A Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C01B Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C01C Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C01D Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C01E Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C01F Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C020 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C021 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

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” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The 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 6.5 Administration Guide.
Possible Cause: If this error occurs when administering GroupWise, a domain database (wpdomain.db) or post office database (wphost.db) might be damaged.
Action: Validate and rebuild the domain or post office database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If this error occurs from the POA after you have already rebuilt databases, restart the POA.
Possible Cause: If this error occurs in GroupWise Remote, there might be a problem with the structure or content of the Remote mailbox. For example, copying a GroupWise Remote installation from one laptop to another might introduce this problem.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Reinstall GroupWise Remote on the remote computer. See the platform-specific setup instructions for GroupWise Remote in“Setting Up GroupWise Modes and Accounts” in “Client” in the GroupWise 6.5 Administration Guide.
Possible Cause: The hard disk where the GroupWise databases are stored is damaged.
Action: Scan the hard disk for damage. Correct any problems with the hard disk.
Action: Repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If the database cannot be repaired, you must restore it from backup. See “Restoring GroupWise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: In ConsoleOne®, you can set the proper user rights for all users in a post office or for an individual user. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide.
Possible Cause: If users are accessing a post office on a NetWare server through a Windows machine using the Microsoft Gateway for NetWare, the gateway might not be providing adequate support for the number of users trying to access the post office.
Action: The Gateway Service for NetWare is not intended as a full service router for NetWare services. Use a more robust connection to the post office.
Action: Make sure you have all the latest NetWare patches installed. If using the Novell IPX™/IP gateway, make sure you have the latest version.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C023 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C024 Database dictionary damaged

Source: GroupWise engine; database services.
Explanation: Database dictionary compromised.
Possible Cause: The database dictionary (*.dc file) has been damaged.
Action: Make sure the ngwguard.dc file exists in the post office directory. If it does not, copy it from the po subdirectory of your software distribution directory. For the specific locations of this file, see “Post Office Directory” and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: If this does not solve the problem, check and repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C026 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C027 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C028 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

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.
Action: The database should have been upgraded. Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C02A Cannot access database dictionary file

Source: GroupWise engine; database services.
Explanation: Dictionary file access error.
Possible Cause: In the GroupWise client, this error usually indicates there was a file I/O error accessing one of the database dictionary (*.dc) files which are used to create databases.
Action: Check for any problems accessing the disk where the dictionary files reside. To determine the standard locations for the various database dictionary files, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: Make sure the ngwguard.dc file exists in the post office directory. If it does not, copy it from the po subdirectory of your software distribution directory. For the specific locations of this file, see “Post Office Directory” and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: The network might have gone down, or there might be some other transitory problem with the disk. The problem might go away simply by retrying.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C02B Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C02C Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C02D Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C02E Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C02F Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C032 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C033 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C034 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C035 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C037 Memory error

Source: GroupWise engine; database services.
Action: See C0xx Memory error.

C038 Memory error

Source: GroupWise engine; database services.
Action: See C0xx Memory error.

C03A 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 GroupWise software. For technical services and file updates, see Novell Technical Support.

C03B Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C03C Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C03D Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C03F Database error

Source: GroupWise engine; database services.
Explanation: GroupWise tried to open a file that could not be recognized as a valid GroupWise database.
Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide. It can sometimes be helpful to run GWCheck multiple times, because as some errors are fixed, others are uncovered.
Action: If the damaged database cannot be repaired successfully, restore it from backup.
Action: If a damaged user database cannot be repaired or restored, it can be rebuilt. First, archive all personal appointments, tasks, and notes. Make a backup copy of the user database. Then, re-create the user database. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs each time the user exits the GroupWise client, the archive database might be damaged.
Action: In the GroupWise client, open the archive, then use the Repair Mailbox feature to repair the archive. See “Enabling GroupWise Check in the Windows Client” in “Client” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck on the archive. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C040 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C041 Cannot open older version of database

Source: GroupWise engine; database services.
Explanation: Older database error.
Possible Cause: The newer code cannot access the older version database. The database should have been upgraded but was not.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C042 Database being

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 will go away when the operation is retried. Make sure that others are not doing updates to the database, and retry the action. If the problem persists, validate and rebuild the database as necessary. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If this error occurs on a message or user database, run GWCheck. See “Standalone Database Maintenance Programs” in the GroupWise 6.5 Administration Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C043 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C044 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C045 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C046 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C047 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C048 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C04A Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C04B Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C04C Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C04D Memory error

Source: GroupWise engine; database services.
Action: See C0xx Memory error.

C04E Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C04F Database checksum error

Source: GroupWise engine; database services.
Explanation: Checksum error reading database.
Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.

If the error returns, check for bad network cards on machines from which the GroupWise client updates the databases.

Action: If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The guardian database (ngwguard.db) is damaged.
Action: Stop the POA. Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files. Delete the ngwguard.db file, then create a new, empty file named ngwguard.db.

Start the POA. The POA will recognize the invalid ngwguard.db file and rebuild it from the ngwguard.fbk file, merging in transactions from the ngwguard.rfl file.

See also “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.

Possible Cause: If this error occurs in GroupWise Remote, there might be a problem with the structure or content of the GroupWise Remote mailbox.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Reinstall GroupWise on the remote computer. See the platform-specific setup instructions for GroupWise Remote in “Setting Up GroupWise Modes and Accounts” in “Client” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs in the GroupWise client next to the library name in the Find Results dialog box, the POA has not indexed the documents yet and might not be running.
Action: Start the POA. Check its indexing cycle. See “Regulating Indexing” in “Optimizing the POA” in the GroupWise 6.5 Administration Guide.

After the documents have been indexed, the user will be able to use the Find feature in the GroupWise client to access them.

Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C050 Transaction aborted

Source: GroupWise engine; database services.
Explanation: Attempted operation after critical error; transaction aborted.
Possible Cause: If this error occurs during domain-related activities, such as adding users or synchronizing domains, the domain database has been damaged.
Action: Check and, if necessary, repair the domain database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.

C055 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C057 Database maintenance in progress; please exit

Source: GroupWise engine; database services.
Explanation: Maintenance in progress error.
Possible Cause: Database maintenance in progress (one of the databases is being recovered or rebuilt).
Action: Exit GroupWise and try again later. Depending on the size of the database, the maintenance could take from a few seconds to several minutes.
Possible Cause: 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.
Action: Check the open/lock activity on GroupWise databases and other files. You might find that a backup program is holding the file open.
Possible Cause: If this error occurs constantly from the POA, a damaged message file might be blocking its processing.
Action: Check the priority subdirectories of the \wpcsout\ofs directory. See “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Move message files out to a temporary location until the damaged message file is eliminated. Undamaged message files can then be returned to their original subdirectories for processing.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C059 Database file already exists

Source: GroupWise engine; database services.
Explanation: GroupWise attempted to create a user file, message file, or library file, but it could not because the file already existed.
Possible Cause: The ngwguard.db file has been renamed or deleted. When the POA detects the guardian database is missing, it creates a new one. The original guardian database contained a catalog of dependent databases (user, messages, library, and so on). The new guardian database lacks this catalog, so the POA attempts to create the needed dependent databases, but it cannot because they already exist. The POA does not overwrite existing files. See also “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Restore the original ngwguard.db file from backup. If the original guardian database is not available, seek assistance. For technical services, see Novell Technical Support.
Possible Cause: A user was moved to a different post office and then moved back to the original post office. When the user is moved back to the original post office, the POA attempts to create the user database. If the user database was not deleted when the user was moved out, the POA cannot create the new user database.
Action: Delete the residual user database, then move the user back into the post office. See “Moving GroupWise Accounts” in “Users” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C05D Cannot open database file

Source: GroupWise engine; database services.
Explanation: Store file not found.
Possible Cause: Cannot open a file associated with a multi-file database. For example, one of the dependent databases listed in ngwguard.db has been deleted.
Action: Restore the missing database from backup.
Possible Cause: If this error occurs when users send mail, the message database (msgnn.db) to which the users belong might be missing.
Action: If the message database cannot be restored from backup, perform a structural rebuild on the user(s) experiencing the problem. See “Performing a Structural Rebuild of a User Database” in “Databases” in the GroupWise 6.5 Administration Guide. This will create a new, empty message database. Old messages will no longer be available to the affected users.
Possible Cause: If the message occurs for only a single user, that user’s user database (userxxx.db) might be missing.
Action: If the user database cannot be restored from backup, re-create the user database. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: A library database is missing.
Action: Library databases must be restored from backup. They cannot be re-created.
Possible Cause: 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.
Action: Run GWCheck to perform a structural rebuild on the dmsh.db file in the post office, then verify the library. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.

Then delete the library. See “Deleting a Library” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.

Possible Cause: If this message occurs from GroupWise Remote, a database might be missing from the Remote mailbox.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C05E Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C060 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C061 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C062 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C063 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (Support assistance recommended).

C066 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C067 Database error

Source: GroupWise engine; database services.
Explanation: Invalid store number.
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 6.5 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 the GroupWise 6.5 Administration Guide.
Action: Reset the client options for that user. See “Resetting Client Options to Default Settings” in “Users” in the GroupWise 6.5 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 anyway.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C068 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies)

C069 Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (database dictionary file).

C06A Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C06B Database error

Source: GroupWise engine; database services.
Explanation: Machine not defined.
Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid.
Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C06C Database error

Source: GroupWise engine; database services.
Explanation: Driver not found.
Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid.
Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C06D Database error

Source: GroupWise engine; database services.
Explanation: Bad driver path.
Possible Cause: The platform-specific definition needed by the database to identify the location of the database files is either missing or invalid.
Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C06E Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C06F Store number mismatch

Source: GroupWise engine; database services.
Explanation: The store number in a database does not match the store number recorded in the store catalog.
Possible Cause: The database is damaged.
Action: Check and, if necessary, repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The database has been renamed to another valid database name (for example, renaming msg7.db to msg8.db). This circumstance could indicate tampering by a user attempting to access another user’s messages.
Action: Restore the original database. See “Restoring GroupWise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide. For information about databases in the post office, see “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C071 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C072 Database error

Source: GroupWise engine; database services.
Explanation: Guardian transaction active.
Possible Cause: Attempted to synchronize a dependent database dictionary file. However, the parent database dictionary file, which contains the definitions, was locked by another process. See “Information Stored in the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Retry the operation.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C073 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C076 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C077 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C078 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C079 Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C07A Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C07B Database error

Source: GroupWise engine; database services.
Action: See C0xx Database error (general database repair strategies).

C07C Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C07D Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C07E Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C07F Unexpected error

Source: GroupWise engine; database services.
Action: See C0xx Unexpected error.

C080 Index not found

Source: GroupWise engine; database services.
Explanation: A QuickFinder™ index is missing.
Action: Repair the indexes in the post office database (wphost.db). See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.

C081 Attachment missing

Source: GroupWise engine; database services.
Explanation: An attachment file that should be available under offiles in the post office 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 > Options > Environment > 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 6.5 Administration Guide. Under the Analyze/Fix action, select the following:

  • Verify Library

  • Fix Document/Version/Element

  • Verify Document Files

  • Validate All Document Security

Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C0xx 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 C0xx Database error (general database repair strategies).
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C0xx Database error (general database repair strategies)

Source: 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 6.5 Administration Guide.
Action: If this error occurs on a message database (msgnn.db) or user database (userxxx.db), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If the damaged database cannot be repaired successfully, restore it from backup.
Action: If a damaged user database cannot be repaired or restored, it can be rebuilt. First, archive all personal appointments, tasks, and notes. Make a backup copy of the user database. Then, re-create the user database. See “Re-creating a User Database” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C0xx Database error (database dictionary file)

Source: GroupWise engine; database services.
Explanation: Problem with a database dictionary (*.dc) file.
Action: Copy the ngwguard.dc file from the po subdirectory of the software distribution directory to the post office directory. For the specific locations of the file, see “Software Distribution Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C0xx Memory error

Source: GroupWise engine; database services.
Explanation: Generic memory error.
Action: Retry the operation that caused the error. If it occurs again, restart GroupWise. If it occurs again, it might be necessary to run GroupWise in an environment with more available memory.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

C0xx Unexpected error

Source: GroupWise engine; database services.
Explanation: An engine error has occurred for which GroupWise does not have a specific error message.
Action: Exit and then restart the GroupWise client.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D001 Unexpected error

Source: GroupWise® engine.
Action: See Dxxx Unexpected error.

D002 Folder not empty

Source: GroupWise engine.
Explanation: Folder not empty.
Action: Delete all items in the folder before attempting to delete it.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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: Check and, if necessary, repair the user database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D006 Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D009 Cannot use group name in distribution list

Source: GroupWise engine.
Explanation: Group in Workflow.
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 users in the group.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D00A Syntax error in address

Source: GroupWise engine.
Explanation: Syntax error.
Possible Cause: A syntax error was detected in the distribution list. One of the following conditions exists:

  • There is a colon (:), at-sign (@), or a period (.) inside a parenthesized list.

  • There are parentheses with nothing between them () or an opening parenthesis followed by a comma (, in the distribution list. There must be a user ID between the parenthesis and the comma.

  • There is a comma followed by a closed parenthesis ,) in the distribution list. There must be a user ID between the comma and the parenthesis.

  • There is a colon (:) somewhere after a closed parenthesis.

Action: Locate the syntax error in the distribution list. A pointer to the location of the syntax error points out where the error is. Correct the syntax error, then retry the operation.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D00B 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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D00C Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D00D 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 D00A Syntax error in address.
Action: Check the distribution list for incorrect usage of parentheses and resend.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D00E Distribution list contains nested groups

Source: GroupWise engine.
Explanation: Groups are nested too deep.
Possible Cause: The distribution list contains groups that are nested more than five levels deep or it might contain a circular reference. For example, if a personal group contains a recipient with the same name as the personal group, a circular reference is created.
Action: Edit the groups to remove the circular reference, or include the contents of one of the sub-groups in a higher level group to reduce the levels in the structure.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D00F Remote mail error

Source: GroupWise engine.
Explanation: Invalid remote mail request.
Possible Cause: Remote mail error. This error is displayed whenever a more specific error is not available. The most common cause is a request for items that have already been deleted.
Action: Check and repair the databases of the master mailbox. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: GroupWise Remote should automatically repair any problems with the remote databases. If the client is unable to repair the problem, you can delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D017 Too many users in address

Source: GroupWise engine.
Explanation: Reply buffer full.
Possible Cause: 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.
Action: To reply to all the users, create a personal group that contains the users and send the reply to that group. If replying to these groups is common, the personal groups could be made into public distribution lists and selected manually when replying to all users.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D018 Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error

D019 Password incorrect

Source: GroupWise engine.
Explanation: Invalid password.
Action: Type the correct password. Note that passwords are case sensitive.
Possible Cause: The password information in the post office database (wphost.db) has been damaged.
Action: Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If rebuilding the post office database does not resolve the problem, rebuild the domain database (wpdomain.db).
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D01A Password too long

Source: GroupWise engine.
Explanation: Password too long. Passwords can contain a maximum of 64 characters.
Action: Type a password with fewer than 64 characters.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D01B Access to GroupWise denied

Source: GroupWise engine.
Explanation: Access to the user database required for this operation has not been granted.
Possible Cause: 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.
Action: 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.
Possible Cause: You are trying to perform an action in a shared folder, but you do not have rights to perform the requested operation.
Action: Ask the owner of the shared folder to grant you the necessary rights. Look up "shared folders" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D01C Remote mail error

Source: GroupWise engine.
Explanation: Invalid remote mail request.
Possible Cause: Remote mail error. This error is displayed whenever a more specific error is not available. The most common cause is a request for items that have already been deleted.
Action: Check and repair the databases of the master mailbox. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: GroupWise Remote should automatically repair any problems with the remote databases. If the client is unable to repair the problem, you can delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D01E Cannot execute rule

Source: GroupWise engine.
Explanation: Invalid rule action.
Possible Cause: 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.
Action: Edit the rule and select a valid execution type. Look up "rules" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D01F Archive path not specified

Source: GroupWise engine.
Explanation: No archive path.
Possible Cause: No archive path specified in the GroupWise client.
Action: Specify the archive path before attempting to archive items. Look up "archive, directory, setting up" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D020 Rule caused infinite loop

Source: GroupWise engine.
Explanation: Rule hop count exceeded.
Possible Cause: The execution of a rule has caused a message to be sent, which caused the execution of a rule, and so on. To prevent the possibility of infinite looping, the rule execution has been terminated.
Action: Edit the rule to correct the looping condition. Look up "rules" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D021 Cannot deliver message

Source: GroupWise engine.
Explanation: Remote send requested with no agents present.
Possible Cause: Message cannot be delivered to a user in a different post office because the POA and MTA are not available.
Action: Set up the POA for the post office. See “Installing and Starting the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Set up the MTA for the domain. See “Installing and Starting the MTA” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D022 Database creation in progress

Source: GroupWise engine.
Explanation: Operation was passed off to the POA.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D023 User ID expired

Source: GroupWise engine.
Explanation: User account is expired.
Action: You can extend or remove the user’s expiration date. See “Expiring a GroupWise Account” in “Users” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D024 Rule cannot forward, reply, accept, or delegate personal item

Source: GroupWise engine.
Explanation: Action not valid for personal item.
Action: Edit the conditions of the rule so that personal items are not included. Look up "rules" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D025 Users not specified

Source: GroupWise engine.
Explanation: No users specified.
Possible Cause: No users have been specified in the distribution list.
Action: Type the names of users, or select users from the Address Book to include in the distribution list.
Possible Cause: If this message occurs from the POA, it might be attempting to process a damaged message file.
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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D026 Missing opening brace in distribution list

Source: GroupWise engine.
Explanation: No opening brace.
Possible Cause: Mismatched braces in 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.
Action: Check the address for incorrect use of braces, then resend the message.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D027 Missing closing brace in distribution list

Source: GroupWise engine.
Explanation: No closing brace.
Possible Cause: Mismatched braces in 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.
Action: Check the address for incorrect use of braces, then resend the message.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D028 Lost attachment

Source: GroupWise engine.
Explanation: Attachment could not be associated with a message.
Possible Cause: The attachment pointer was damaged.
Action: Resend the message.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D029 Recipient not specified

Source: GroupWise engine.
Explanation: No distribution list for delegate rule.
Possible Cause: No recipient has been specified in a delegate rule. The delegate rule must contain a valid user ID to which to delegate the item. This error might indicate the user who sees the message, or some other user, has an incorrect delegate rule.
Action: Make sure the delegate rule contains a valid distribution list. Look up "rules" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D02A Name for group not specified

Source: GroupWise engine.
Explanation: No group name.
Possible Cause: No name has been specified for the distribution list.
Action: Enter a unique group name.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D02F Database error

Source: GroupWise engine.
Explanation: No document record number (DRN) for status.
Possible Cause: The domain database (wpdomain.db) or post office database (wphost.db) might be damaged.
Action: Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If rebuilding the post office database does not resolve the problem, rebuild the domain database.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D030 Missing post office number for status

Source: GroupWise engine.
Explanation: Necessary information cannot be accessed.
Possible Cause: Inconsistent database information.
Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D039 Missing attachment

Source: GroupWise engine.
Explanation: An attachment for a message can no longer be found.
Possible Cause: If this error occurs in GroupWise Remote, there might be a problem with the structure or content of the Remote mailbox.
Action: Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.

D03F Database error

Source: GroupWise engine.
Explanation: No item type.
Possible Cause: The user database (userxxx.db) and/or message database (msgnn.db) for the user have been damaged.
Action: Check and, if necessary, repair the user and/or message databases. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D040 Cannot delete folder used in rule

Source: GroupWise engine.
Explanation: Folder being used in a rule.
Possible Cause: User cannot delete the folder because it is referenced in a rule.
Action: Change or delete the rule, then delete the folder. Look up "rules" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D041 No recipients in post office

Source: GroupWise engine.
Explanation: Insufficient recipient information.
Possible Cause: 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.
Action: Download the personal group.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D043 Inconsistent distribution list

Source: GroupWise engine.
Explanation: Information in the distribution list does not match information elsewhere in the system.
Possible Cause: Outdated information in a distribution list, a damaged distribution list, or a damaged message file could cause this error from the POA.
Action: Check the priority subdirectories of the \wpcsout\ofs directory in the post office. Check the POA log file to determine the offending message file. See “Using POA Log Files” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Determine the originator of the offending message. Check and, if necessary, repair the user database (userxxx.db) for that user. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The POA has been started with the /norecover startup switch and damage to a user or message database has been detected.
Action: Repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Start the POA without the /norecover startup switch so that the POA can automatically recover any databases where damage is detected.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D044 Auto-rebuild disabled

Source: GroupWise engine.
Explanation: Automatic recovery of damaged databases by the POA has been turned off.
Possible Cause: The POA has been started with the /norecover startup switch and damage has been detected in a database.
Action: Repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Start the POA without the /norecover startup switch so that the POA can automatically recover any databases where damage is detected.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D049 Error reported from Novell NDS

Source: GroupWise engine.
Explanation: The GroupWise Administrator snap-in to ConsoleOne was unable to retrieve information from Novell® eDirectory™.
Possible Cause: You might be running ConsoleOne with insufficient Browse, Read, or Compare rights to the required eDirectory object.
Action: Check the rights to the GroupWise user, post office, and agent objects in eDirectory.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D04A Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D04B Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D04F Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D050 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: No TCP/IP services.
Possible Cause: The GroupWise client cannot connect to the specified post office in client/server mode because an IP address has not been provided. The POA in a remote post office is required for cross-post office proxy and library access.
Action: Set up the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Possible Cause: The GroupWise client cannot connect to the specified post office in client/server mode because the POA in that post office is not running. The POA in a remote post office is required for cross-post office proxy and library access.
Action: Make sure the POA is running in the remote post office. See “Monitoring the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Make sure the POA in the remote post office is configured with the correct IP address and TCP port.
Action: 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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D051 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: TCP/IP not allowed.
Possible Cause: 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.
Action: Set up the IP address for the POA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D054 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: Missing path for direct mode connection.
Possible Cause: The post office rejected the client/server mode connection but is allowing direct mode. The path might be set up, but not for this platform.
Action: Set up the path for the specified post office in the post office Identification page in ConsoleOne.
Action: To start the GroupWise client in direct mode, use the /ph switch to provide the path to the post office.
Action: 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D055 Cannot connect to specified post office

Source: GroupWise engine.
Explanation: Cannot use direct (mapped) connection.
Possible Cause: The post office rejected the direct mode connection but is allowing client/server mode.
Action: 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D057 Cannot connect to any post office

Source: GroupWise engine.
Explanation: TCP/IP default address failed.
Possible Cause: An attempt to connect to a post office using the GroupWise IP address defaults (NGWNAMESERVER and NGWNAMESERVER2) was unsuccessful.
Possible Cause: No client/server or direct information was specified or available.
Action: Make sure the GroupWise name server is properly set up and running. See “Simplifying Client/Server Access with a GroupWise Name Server” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Possible Cause: The GroupWise name server cannot locate any post offices.
Action: Make sure the network connections to the machines where post offices reside are functioning properly.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D058 Version mismatch on GroupWise client/POA/post office

Source: GroupWise engine.
Explanation: The post office directory, with its associated user databases (userxxx.db) and message databases (msgnn.db) was created by a version of GroupWise that is older than the version of the GroupWise client that is accessing the post office.
Possible Cause: A user is running the latest version of the GroupWise client, but the post office has not yet been updated.
Action: Update the post office. See “Update” in the GroupWise 6.5 Installation Guide.
Possible Cause: The post office has been updated, but the latest version of the POA has not yet been installed and started.
Action: Update the POA. See “Updating Post Offices” in “Update” in the GroupWise 6.5 Installation Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D059 Recursion limit exceeded during delivery

Source: GroupWise engine.
Explanation: The POA received a message that contained more than 36 levels of encapsulation. The POA could not deliver the message.
Possible Cause: This can be caused by rule forwarding loops that include one hop to an external user, or by some Internet ’chain letters.’
Action: Check the rule configuration of the GroupWise recipient. Disable any rules that forward mail to an external user who might be forwarding the mail back into GroupWise. Look up "rules" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D05A User database access denied

Source: GroupWise engine.
Explanation: The GroupWise client cannot start because it cannot access the user’s user database (userxxx.db).
Possible Cause: The user tried to access a mailbox that does not have a password using the wrong NetWare user ID, in a post office with security set to high.
Action: Set a password on the user’s mailbox. See “Creating or Changing a Mailbox Password” in “Users” in the GroupWise 6.5 Administration Guide.
Possible Cause: The user’s current login ID, either from NetWare, eDirectory, or Windows, does not match the network login ID stored in the GroupWise user database.
Action: Make sure the user is using the correct login ID.
Possible Cause: Password information in the user database might be damaged.
Action: 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 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The post office database (wphost.db) might be damaged.
Action: Rebuild the index of the post office database. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: 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 6.5 Administration Guide.
Possible Cause: The IP address of the POA has changed, but GroupWise client users are still trying to start the client using old /ipa and /ipp client startup switch settings.
Action: Update the information in users’ /ipa and /ipp switch settings with the current IP address information.
Action: Remove the /ipa and /ipp switches and let the client and/or the POA resolve the address. See “Simplifying Client/Server Access with a GroupWise Name Server” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D05B User has invalid DS_GUID; login failed

Source: GroupWise engine.
Explanation: The domain database (wpdomain.db) contains invalid information for the user.
Possible Cause: Your GroupWise system still contains some GroupWise 4.x components. Very rarely, an invalid string gets written to the domain database if the domain includes a 4.x post office.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D05C Possible data corruption in the domain database

Source: GroupWise engine.
Explanation: The domain database (wpdomain.db) contains invalid information.
Possible Cause: You have recently converted from GroupWise 4.x to GroupWise 6..x Very rarely, an invalid string gets written to the domain database during conversion.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D05D Post office intruder lockout is enforced

Source: GroupWise engine.
Explanation: The POA has detected a possible intruder. The user has been locked out.
Action: You have several options for handling the situation. See “Enabling Intruder Detection” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D05E Message size exceeds limit

Source: GroupWise engine.
Explanation: A user tried to send a message that exceeded that user's message size limit as set by the administrator.
Possible Cause: The user is not aware that there is a message size limit on his or her mailbox.
Action: Notify the user of the message size limit so that the user can send messages of appropriate size.
Possible Cause: The administrator has set a message size limit that is too restrictive. Increase the message size limit.
Action: Increase the maximum message size for the user. See “Send Options: Disk Space Management” in “Users” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D05F Box size limit exceeded

Source: GroupWise engine.
Explanation: A user's GroupWise mailbox exceeds the size limit set by the administrator
Possible Cause: The user is not aware that there is a size limit on his or her mailbox.
Action: Notify the user of the mailbox size limit so that the user can delete unneeded messages from the mailbox.
Possible Cause: The administrator has set a mailbox size limit that is too restrictive. Increase the message size limit.
Action: Increase the maximum mailbox size for the user. See “Send Options: Disk Space Management” in “Users” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D060 Message size exceeds threshold limit

Source: GroupWise engine.
Explanation: A user's GroupWise mailbox is close to exceeding the size limit set by the administrator
Possible Cause: The user is not aware that there is a size limit on his or her mailbox.
Action: Notify the user of the mailbox size limit so that the user can delete unneeded messages from the mailbox.
Possible Cause: The administrator has set a mailbox size limit that is too restrictive. Increase the message size limit.
Action: Increase the maximum mailbox size for the user. See “Send Options: Disk Space Management” in “Users” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D061 Status denied to external Internet user

Source: GroupWise engine.
Explanation: The local GroupWise system is configured so that users outside the local GroupWise system cannot receive status information about messages.
Action: To permit access to status information by external users, enable Allow External Status Tracking. See “System Preferences” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D062 Busy Search denied for external Internet user

Source: GroupWise engine.
Explanation: The local GroupWise system is configured so that users outside the local GroupWise system cannot perform Busy Searches on local users.
Action: To permit Busy Search access by external users, enable Allow External Busy Search. See “System Preferences” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D065 Attempt to purge item that has not been backed up

Source: GroupWise engine.
Explanation: Client Cleanup options are set so that items cannot be purged from users' mailboxes until they have been backed up. A user has tried to purge an item that has not yet been backed up.
Action: You can allow users to purge items that have not yet been backed up. See “Environment Options: Cleanup” in “Users” in the GroupWise 6.5 Administration Guide. See also “GroupWise Time Stamp Utility” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D066 Attempt to purge an item from a user that has not been backed up

Source: GroupWise engine.
Explanation: Client Cleanup options are set so that items cannot be purged from users' mailboxes until they have been backed up. A process has tried to purge an item that has not yet been backed up.
Action: You can allow purging of items that have not yet been backed up. See “Environment Options: Cleanup” in “Users” in the GroupWise 6.5 Administration Guide. See also “GroupWise Time Stamp Utility” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D069 Attempt to open invalid backup location

Source: GroupWise engine.
Explanation: The user attempted to open a backup location that did not contain a valid backup of a GroupWise post office or mailbox.
Possible Cause: The user is unsure of the backup location.
Action: Make sure users know where their backed-up messages have been restored. See “Restoring Deleted Mailbox Items” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The backup location path includes a directory name that has more than eight characters.
Action: Rename any long directory names to eight characters maximum, then make matching changes to the restore area information in ConsoleOne. See “Setting Up a Restore Area” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The restore area is in a location where the POA does not have the necessary rights to access it.
Action: If the restore area is on a different machine from where the POA is running, provide a username and password for the POA to use to access the remote location. You can provide this information in ConsoleOne in the Remote File Server Settings box on the Post Office Settings page of the Post office object or in the POA startup file using the /user and /password switches.
Action: If the restore area is on the same machine, add a trustee assignment to the restore area directory that provides the POA with object file system rights to the directory.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D06B LDAP failure detected

Source: GroupWise engine.
Explanation: GroupWise was unable to authenticate using LDAP.
Action: Make sure your LDAP server is functioning correctly.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D06C LDAP authentication not supported for this platform

Source: GroupWise engine.
Action: LDAP authentication for your platform might be available in a later version of the GroupWise software. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D06E Lockout of older GroupWise clients being enforced

Source: GroupWise engine.
Explanation: The POA is not allowing GroupWise client users with older versions of the client software to access the post office.
Possible Cause: The administrator does not want older versions of the GroupWise client to access the post office. The client version can be controlled as described in “Checking What GroupWise Clients Are in Use” in “Post Office Agent” in the GroupWise 6.5 Administration Guide
Action: 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 6.5” in the GroupWise 6.5 Installation Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D06F This GroupWise client doesn’t match the user’s license

Source: GroupWise engine.
Explanation: The GroupWise administrator has restricted client users to the WebAccess client and a user is attempting to access his or her mailbox using the Windows client.
Action: Explain to the user that he or she must use the WebAccess client.
Action: Allow the user to use the Windows client. See “Setting Client Options” in “Users” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D071 LDAP authentication failed because the password has expired

Source: GroupWise engine.
Explanation: The GroupWise client was attempting to authenticate using LDAP, but the user's LDAP password has expired.
Action: The user needs to contact the administrator of the LDAP server and get the password reset.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D072 Changing the LDAP password has been disabled

Source: GroupWise engine.
Explanation: A user tried to change his or her LDAP password from the GroupWise client but the administrator has disabled that capability for the user's post office.
Action: Enable LDAP password changes in ConsoleOne. See “Providing LDAP Authentication for GroupWise Users” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Show the user what application he or she needs to use to change the LDAP password.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D073 Attempting to log in trusted without SSL

Source: GroupWise engine.
Explanation: A trusted application to log in to the POA and was not successful because an SSL connection could not be established.
Possible Cause: The POA is not configured to support SSL connections.
Action: Enable SSL for the POA that the trusted application needs to log in to. See “Enhancing Post Office Security with SSL Connections to the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D074 Invalid key for trusted application

Source: GroupWise engine.
Explanation: A trusted application tried to log in to the POA and was not successful because the key was invalid.
Possible Cause: The private key offered by the application did the match the private key the POA was configured to accept.
Action: 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D075 Invalid IP address for trusted application

Source: GroupWise engine.
Explanation: A trusted application tried to log in to the POA and was not successful because the POA was configured for a specific IP address and the trusted application was not running there.
Possible Cause: The trusted application is running on a different server from where it was designed to run.
Action: Run the trusted application on the server with the IP address that the POA is expecting.
Possible Cause: The POA is configured with an incorrect IP address for the trusted application.
Action: 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D076 Missing trusted application name

Source: GroupWise engine.
Explanation: A trusted application tried to log in to the POA and was not successful because no application name was provided.
Possible Cause: The trusted application is not providing an application name.
Action: Add an application name to the trusted application.
Possible Cause: The POA is configured with an incorrect application name for the trusted application.
Action: In eDirectory, change the expected application name to the application name that the trusted application is providing. See “Trusted Applications” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D077 The problem file is being rebuilt

Source: GroupWise engine.
Explanation: The database you want to repair cannot be accessed.
Possible Cause: You are trying to perform database maintenance on a database that is currently being repaired.
Action: None. Your database maintenance request will be deferred until the build in completed.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D07F Unexpected error

Source: GroupWise engine.
Action: See Dxxx Unexpected error.

D101 User not found

Source: GroupWise engine; database interface.
Explanation: User not found.
Possible Cause: The GroupWise user ID is not found in the post office database during login.
Action: If using startup switches, check the /ph switch to make sure the path to the post office is correct.
Action: Start the GroupWise client using the /@u or /la startup option to specify the GroupWise user ID.
Possible Cause: The user is not yet set up as a GroupWise user.
Action: Set the user up as a GroupWise user. See “Creating GroupWise Accounts” in “Users” in the GroupWise 6.5 Administration Guide.
Possible Cause: The user ID provided when the user was set up as a GroupWise user is not correct.
Action: 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.
Possible Cause: User information has not replicated from the domain to the post office the user is trying to access.
Action: 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 and Post Offices” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide.
Action: Synchronize the user manually. See “Synchronizing Individual Users or Resources” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The user is logging into a specific machine, rather than into the tree, causing the network ID information not to match.
Action: Log in to the tree rather than to a specific machine.
Possible Cause: 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.
Action: Recreate the group, selecting users from the Address Book to ensure they are valid GroupWise users.
Possible Cause: 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.
Action: Check the Address Book to see if the users are still valid. If they are not, repair the user database (userxxx.db). See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck on the post office database (wphost.db). See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The user was not found in the post office database (wphost.db) during the parsing of To: line or group.
Action: Find the user in the To: line or Group. Either delete the user, or find the correct user ID in the Address Book.
Possible Cause: If this error occurs for all users in a post office, the post office database might be damaged.
Action: Rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs in systems where new users are added from multiple administrator machines, preferences might be set differently on different administrator machines.
Action: On each machine where users are added in ConsoleOne, click Tools > GroupWise System Operations > System Preferences. Make sure that the When Creating or Modifying Objects, For Network ID Use setting is the same on all machines. If some machines are set to Full Distinguished Name and some are set to Common Name, users will be set up differently depending on which machine they were created from, causing problems when users access GroupWise.
Possible Cause: If this error occurs only when using GroupWise Remote, the user ID might be specified incorrectly under Remote Options.
Action: 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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D102 Ambiguous user ID

Source: GroupWise engine; database interface.
Explanation: User ambiguous.
Possible Cause: There is more than one user with same user ID on the same post office.
Action: Select the correct user ID in the pop-up list or select the user in the Address Book.
Possible Cause: If this error occurs when a user starts the GroupWise client, the user’s information in the post office database might not be correct.
Action: 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 6.5 Administration Guide.
Action: Even if the information in the user record looks correct, make a change somewhere so the record is written out again.
Action: If the problem persists, rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D103 Post office not found during login

Source: GroupWise engine; database interface.
Explanation: Post office not found.
Action: If using 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 Address Book.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D104 Ambiguous post office

Source: GroupWise engine; database interface.
Explanation: Post office 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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D107 Record not found

Source: GroupWise engine; database interface.
Explanation: Record not found.
Possible Cause: Relational integrity problem.
Possible Cause: The user database (userxxx.db) and/or message database (msgnn.db) is damaged.
Action: Check and, if necessary, repair the database. See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: A user tried to read an attachment for which the corresponding file has already been deleted from the offiles directory in the post office.
Action: None, unless you want to restore the contents of the offiles directory from a backup.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D108 Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D109 Bad parameter

Source: GroupWise engine; database interface.
Explanation: A GroupWise program passed invalid information to another GroupWise program.
Possible Cause: The user's mailbox contains a damaged message.
Action: Run a structural rebuild on the user database (userxxx.db) and message database (msgnn.db). See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: A delay in Directory replication is preventing the user from logging in to the GroupWise client.
Action: Start the client using the /@u-? switch to bypass eDirectory authentication.
Action: Wait for eDirectory replication to complete.
Possible Cause: The user's Client Options settings have been damaged.
Action: Reset the user's Client Options setting back to the default. See “Resetting Client Options to Default Settings” in “Client” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D10A Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D10B Database needs to be repaired

Source: GroupWise engine; database interface.
Explanation: Database invalid or damaged.
Possible Cause: A record is no longer valid.
Action: Validate the database, then take the appropriate actions to either recover or rebuild the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs when running the GroupWise client under Windows for Workgroups, the user login name might be incorrect.
Possible Cause: Check the user login name on the station where the error occurs. In Windows for Workgroups, click Main > Control Panel > Network > Login Name. The login name must match the user’s GroupWise ID.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D10C Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D10D Cannot open any more mailboxes

Source: GroupWise engine; database interface.
Explanation: Maximum databases open.
Possible Cause: The maximum number of databases that can be opened at one time has been exceeded. The maximum number is approximately 12.
Action: Shut down some databases by removing proxies. Look up "proxy, deleting users from Access List" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D10F Database error

Source: GroupWise engine; database interface.
Explanation: Database already created.
Possible Cause: Attempted to create a database; however, the database already exists.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D110 Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D113 Open database maximum exceeded

Source: GroupWise engine; database interface.
Explanation: The current operation has attempted to open more than the maximum number of databases allowed.
Possible Cause: You are proxied to too many users in direct mapped mode.
Action: Close some mailboxes that are currently proxied, then try the operation again. Look up "proxy, deleting users from Access List" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D115 Database error

Source: GroupWise engine; database interface.
Explanation: Invalid database.
Possible Cause: Attempted to open an invalid database.
Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
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 6.5 Administration Guide.
Action: If the database cannot be recreated, you must restore it from backup. See “Restoring GroupWise Databases from Backup” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D117 GroupWise version too old

Source: GroupWise engine; database interface.
Explanation: Old program version.
Possible Cause: An attempt was made to open a database with an older version of GroupWise software. You are running an older version of the GroupWise client. Your post office has been updated to a newer version.
Action: 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 6.5 Installation Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D118 Database error

Source: GroupWise engine; database interface.
Explanation: Field not found.
Possible Cause: Unable to find the field in the database.
Action: Check and repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D119 Unexpected error

Source: GroupWise engine; database interface.
Action: See Dxxx Unexpected error.

D11B Too many items in mailbox

Source: GroupWise engine; database interface.
Explanation: Too many records.
Possible Cause: There are more than 5,000 items in your mailbox. Only the first 5,000 items will be displayed. When you delete messages, additional objects will be displayed.
Action: Have users clean out their mailboxes. You might want to run a statistics check on the mailboxes. “Gathering Mailbox Statistics” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Users could move items to different folders.
Action: Users could archive items. See "archive, items" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D11C Cannot use group name

Source: GroupWise engine; database interface.
Explanation: Groups cannot be listed as users here.
Possible Cause: 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.
Action: Check your Address Book for correct addressing syntax. If the syntax is correct, you might want to add the group to the Address Book.
Possible Cause: The user has specified a distribution list in another post office that has visibility set to none.
Action: Change the visibility of the distribution list so that users in other post offices can use it. For information about visibility, see “Creating Distribution Lists” in “Distribution Lists, Groups, and Organizational Roles” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D11D GroupWise version newer than database

Source: GroupWise engine; database interface.
Explanation: New program version.
Possible Cause: The GroupWise client has been installed on a machine 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 machine, which can interfere with the functioning of the full GroupWise client.
Action: Search the machine for a local wphost.db file. If found, rename or delete it.
Possible Cause: The GroupWise client and agents were updated, but ConsoleOne was not. As a result, the database dictionary (*.dc) files do not get updated.
Action: 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.
Possible Cause: The version of GroupWise you are running is newer than the database. The software cannot do an auto-upgrade on the older database.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D124 Access to user denied

Source: GroupWise engine; database interface.
Explanation: Access rights failure. A required field was not found.
Possible Cause: Moving a resource causes the resource owner to lose access to the resource.
Action: In ConsoleOne, browse to and select the Resource object, then click Tools > GroupWise Utilities > Mailbox/Library Maintenance. Select Reset Client Options in the Action drop-down list.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D201 Unexpected error

Source: GroupWise engine; mail/calendar import and print services.
Action: See Dxxx Unexpected error.

D202 General printing error

Source: GroupWise engine; mail/calendar import and print services.
Explanation: You have attempted to print an item that is missing information.
Possible Cause: The user machine is missing its temporary directory, or there is insufficient disk space available to create the temporary files needed to print the item.
Action: Check for the existence of the temporary directory on the user machine.
Action: Check for available disk space.
Possible Cause: The link to the item to print has been damaged.
Action: Check and, if necessary, repair the message database (msgnn.db). See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D204 Calendar has password

Source: GroupWise engine; mail/calendar import and print services.
Explanation: You have attempted to import a calendar file that has a password.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D205 Cannot import calendar file

Source: GroupWise engine; mail/calendar import and print services.
Explanation: Import of invalid calendar file version.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D502 Unknown task encountered

Source: GroupWise engine; administration services.
Explanation: Unknown task encountered.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D503 Unknown data type encountered

Source: GroupWise engine; administration services.
Explanation: Version incompatible.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D506 Security violation

Source: GroupWise engine; administration services.
Explanation: No authentication.
Possible Cause: 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.
Action: 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 6.5 Administration Guide.
Possible Cause: If this error occurs after a configuration change (for example, after changing which domain is the primary domain of your GroupWise system), the configuration change might not have replicated throughout the system in time to support a following change (for example, adding a user).
Action: Wait for replication to complete, then synchronize the object that caused the error. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: If you do not want to wait for replication to complete, you can rebuild the secondary domain database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs when synchronizing domains or post offices, the databases might be damaged.
Action: Rebuild the databases, then synchronize the databases.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D507 Administrator record not found in database

Source: GroupWise engine; administration services.
Explanation: No administrator record found in database.
Possible Cause: An agent has attempted to send a message to the defined administrator; however, no administrator record was found in the database.
Action: To receive these messages, define an administrator for the domain. See “Notifying the Domain Administrator” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D508 Transaction failed

Source: GroupWise engine; administration services.
Explanation: The transaction failed.
Possible Cause: The database was locked by another process and could not be updated.
Action: None. The message will be retried automatically.
Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner.
Action: For the locations of GroupWise databases in domains and post offices, see “Domain Directory” and “Post Office Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
Possible Cause: The database has been damaged.
Action: If the ownership on the problem database is correct or you are unable to reset it, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D701 Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D704 Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D705 Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D706 Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D707 Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D708 Directory entry record not found

Source: GroupWise 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.
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 6.5 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 6.5 Administration Guide.
Action: Check the current path to the software distribution directory. See “Software Directory Management” in “System” in the GroupWise 6.5 Administration Guide. Correct the path as needed. Make sure the specified software distribution directory actually exists.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D709 Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D70A Memory error

Source: GroupWise engine; directory services access.
Explanation: Memory error.
Possible Cause: Unable to lock or allocate memory.
Action: The GroupWise client user should exit and restart GroupWise.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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: If the 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D70D Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D70E Duplicate entry in database

Source: GroupWise engine; directory services access.
Explanation: Duplicate entry found in database.
Possible Cause: You provided a non-unique entry in a field that requires a unique entry.
Action: Provide a new, unique value in the field.
Possible Cause: The database is damaged.
Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D70F Unexpected error

Source: GroupWise engine; directory services access.
Action: See Dxxx Unexpected error.

D710 Incompatible platform

Source: GroupWise engine; directory services access.
Explanation: Requested platform path not found.
Possible Cause: In a multiple-platform environment, a path was requested for a given platform but none was found.
Action: This is not an error. It is a notification by the program of the return value.
Possible Cause: If this error occurs when the POA is trying to start, a path to a document storage area might be incorrect.
Action: Check the location and existence of any document storage areas for libraries associated with the post office. To list the available libraries, see “Editing Post Office Properties” in “Post Offices” in the GroupWise 6.5 Administration Guide.

To check the path to a document storage area, see “Managing Document Storage Areas” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide. Correct any incorrect path, then try to start the POA.

Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D711 Gateway engine error

Source: GroupWise engine; directory services access.
Explanation: Platform path exists.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D712 Post office currently disabled

Source: GroupWise engine; directory services access.
Explanation: Post office is disabled.
Possible Cause: The system administrator has disabled the post office.
Action: 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 page in ConsoleOne. See “Disabling a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide.
Possible Cause: If this error occurs when the Disable Logins option is not selected, the flag might be set improperly on the post office database.
Action: 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 6.5 Administration Guide.
Action: Rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D713 Database dictionary not found

Source: GroupWise engine; directory services access.
Explanation: Dictionary not found.
Possible Cause: A database create request was made and the corresponding database dictionary file was not found.
Action: Make sure the ngwguard.dc file exists in the post office directory. If it does not, copy it from the po subdirectory of your software distribution directory. For the specific locations of this file, see “Post Office Directory” and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D714 User database temporarily disabled

Source: GroupWise engine; directory services access.
Explanation: The administrator has temporarily disabled GroupWise login for a specific user.
Possible Cause: The user is being moved from GroupWise 5.x to 6.x.
Action: Wait for the move to be completed.
Action: If the problem persists, rebuild the user database (userxxx.db). See “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

D901 Unexpected error

Source: GroupWise engine; messaging services.
Action: See Dxxx Unexpected error.

D902 Unexpected error

Source: GroupWise engine; messaging services.
Action: See Dxxx Unexpected error.

D904 Unexpected error

Source: GroupWise engine; messaging services.
Action: See Dxxx Unexpected error.

D90A Unexpected error

Source: GroupWise engine; messaging services.
Action: See Dxxx Unexpected error.

D90B Unexpected error

Source: GroupWise engine; messaging services.
Action: See Dxxx Unexpected error.

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 subdirectories of the \wpcsout\ofs directory. Check the POA log file to determine the offending message file. See “Using POA Log Files” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. Delete the offending message file so that subsequent messages can be processed.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DA0C 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 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DA0D 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 6.5 Troubleshooting 3: Message Flow and Directory Structure.
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 6.5 Installation Guide.
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 6.5 Troubleshooting 3: Message Flow and Directory Structure. Adjust the path to the post office in the post office Identification page in ConsoleOne.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DA0E 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DA0F Database error

Source: GroupWise engine; Post Office Agent.
Explanation: Internal process communication (IPC) initialization failure.
Possible Cause: The IPC mechanism failed to initialize properly.
Possible Cause: The POA failed to initialize properly.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DA10 Cannot read post office configuration information

Source: GroupWise engine; Post Office Agent.
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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 such 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).
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DA13 /name switch required

Source: GroupWise engine; Post Office Agent.
Explanation: Ambiguous application name.
Possible Cause: 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.
Possible Cause: 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.
Action: The /name switch should be used in conjunction with one of the DNs specified in the error message.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DA17 /user and /password switches required for this configuration

Source: GroupWise engine; Post Office Agent.
Explanation: The /user and /password switches are required when the POA must log into a remote machine.
Possible Cause: The POA needs to log in to a remote machine where a document storage area is located, but it does not have the necessary user and password information to log in with.
Action: See “Using POA Startup Switches” and “Installing and Starting the POA” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object.
Possible Cause: You have renamed the machine where a document storage area is located. The POA can no longer access the original document storage area location, so the POA cannot start.
Action: First, provide the new location of the document storage area. See “Moving a Document Storage Area” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.

Next, start the POA using the /noconfig, /user, and /password switches so the POA can start and process the administrative message containing the new storage location without having to access the old storage location. Finally, exit, then restart the POA with its typical configuration.

Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB01 Operation cancelled

Source: GroupWise engine; administration engine.
Explanation: Operation cancelled.
Possible Cause: Operation cancelled by user.
Action: None.

DB02 Database access error

Source: GroupWise engine; administration engine.
Explanation: Database access error.
Possible Cause: Cannot complete the requested operation because the database is being updated.
Action: Retry the operation later. If you still cannot access the database, check file activity using your network administration utilities.
Action: Rebuild the database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB03 Operation pending; cannot modify

Source: GroupWise engine; administration engine.
Explanation: Unsafe record modification.
Possible Cause: This record has a pending operation and cannot be modified. A remote operation has been requested for this record.
Action: Wait for the MTA or POA to complete the pending operation, or undo the operation. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB04 Owner not valid user

Source: GroupWise engine; administration engine.
Explanation: Invalid owner.
Possible Cause: The owner you specified is not a valid user in the same post office as the resource.
Action: Select an owner for the resource from among the users in the same post office as the resource. See “Changing a Resource’s Owner” in “Resources” in the GroupWise 6.5 Administration Guide.
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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB05 Invalid path

Source: GroupWise engine; administration engine.
Explanation: Invalid path specified.
Possible Cause: The specified path exists; however, it is not a directory.
Action: Enter a new path, or remove the invalid path.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB08 Non-unique name

Source: GroupWise engine; administration engine.
Explanation: Non-unique name.
Possible Cause: The specified name (object.po.domain) conflicts with an existing user, resource, group, or nickname.
Action: Specify a new, unique name.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB09 User owns resource

Source: GroupWise engine; administration engine.
Explanation: User owns a resource.
Possible Cause: The specified user cannot be deleted or moved because he or she owns a resource.
Action: Remove the resource. See “Deleting a Resource” in “Resources” in the GroupWise 6.5 Administration Guide.
Action: Reassign the resource to another owner. See “Changing a Resource’s Owner” in “Resources” in the GroupWise 6.5 Administration Guide.
Possible Cause: 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.
Action: Wait for replication to occur or manually synchronize the resource(s) and user. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Rebuild the post office database (wphost.db). See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB0A Record not found

Source: GroupWise engine; administration engine.
Explanation: Record not found.
Possible Cause: Cannot find a record that was previously in the database. The record might have been deleted.
Action: Check Pending Operations to see if the command is still awaiting execution. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide.
Action: Retry the command.
Action: Make sure the record was replicated throughout the system. See “Synchronizing Database Information” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB0B Required field empty

Source: GroupWise engine; administration engine.
Explanation: Required field empty.
Possible Cause: A required field has no value.
Action: Supply a value for all required fields.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB0C Cannot close database

Source: GroupWise engine; administration engine.
Explanation: Error closing database.
Possible Cause: An error was encountered while attempting to close the database.
Action: Check the network connection to the database location.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB0E Insufficient memory to initialize database

Source: GroupWise engine; administration engine.
Explanation: Database initialization failure.
Possible Cause: The database failed to initialize due to insufficient memory. ConsoleOne requires at least 500 KB of available RAM.
Action: Check the amount of available memory and reconfigure your system if necessary.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB0F Domain not found

Source: GroupWise engine; administration engine.
Explanation: Domain not found.
Possible Cause: Cannot find the specified domain.
Action: 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.
Possible Cause: If this error occurs from the POA, the post office database (wphost.db) might be damaged so that valid domain information is not available.
Action: Check and, if necessary, repair the database. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB10 Post office not found

Source: GroupWise engine; administration engine.
Explanation: Post office not found.
Possible Cause: Cannot find the specified post office.
Action: Make sure that the post office exists and that the post office name is correct. In ConsoleOne, browse to and right-click the Post Office object, then click Properties.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB11 Unexpected error

Source: GroupWise engine; administration engine.
Action: See Dxxx Unexpected error.

DB12 Maximum number of objects per post office reached

Source: GroupWise engine; administration engine.
Explanation: No more file ID combinations exist for the post office.
Possible Cause: The maximum user limit has been reached for this post office. The maximum number of FID combinations is approximately 46,000 per post office.
Action: Delete obsolete users. See “Removing GroupWise Accounts” in “Users” in the GroupWise 6.5 Administration Guide.
Action: Remove unneeded resources. See “Deleting a Resource” in “Resources” in the GroupWise 6.5 Administration Guide.
Action: Create additional post offices. See “Creating a New Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB16 WP Office 3.1 host already exists in specified directory

Source: GroupWise engine; administration engine.
Explanation: WordPerfect* Office 3.1 host exists.
Possible Cause: WordPerfect Office 3.1 host already exists in the specified directory.
Action: Select a new directory or remove the WordPerfect Office 3.1 host. GroupWise 6.x is not compatible with WordPerfect Office 3.1.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB17 Domain already exists in specified directory

Source: GroupWise engine; administration engine.
Explanation: Directory exists.
Possible Cause: A domain already exists in the specified directory.
Action: Specify a new domain directory or remove the existing domain. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB19 Local post office not found

Source: GroupWise engine; administration engine.
Explanation: No local post office record found.
Possible Cause: GroupWise was unable to find a local post office. The post office database (wphost.db) might have been damaged.
Action: Validate the post office database and rebuild if necessary. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB1A Insufficient administrative rights to perform operation

Source: GroupWise engine; administration engine.
Explanation: No administrative rights to perform action.
Possible Cause: The current domain has no administrative rights to perform the specified action for the selected record.
Action: Connect to the GroupWise system that owns this record. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB1B Message Transfer Agent not installed

Source: GroupWise engine; administration engine.
Explanation: The MTA is not installed.
Possible Cause: The MTA is not installed, or the MTA record is missing from the database.
Action: Set up the MTA. See “Installing GroupWise Agents” in the GroupWise 6.5 Installation Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB1C Invalid object name

Source: GroupWise engine; administration engine.
Explanation: Invalid object.
Possible Cause: An invalid object name was specified for an administrator, group name, or other object.
Action: Make sure the specified object ID is correct.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB1D Cannot delete post office

Source: GroupWise engine; administration engine.
Explanation: Error deleting post office.
Possible Cause: You do not have sufficient rights to perform the operation.
Action: Make sure you have rights to delete files and directories by checking rights for file and directory removal.
Possible Cause: The post office directory or files in that directory are in use by another user.
Action: Check the open/lock activity on files.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB1F Cannot delete current domain

Source: GroupWise engine; administration engine.
Explanation: Error deleting current domain.
Possible Cause: The attempt to delete the current domain failed.
Action: Connect to the primary domain. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then delete the secondary domain from the primary domain. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: If the current domain is the primary domain, you cannot delete it unless you delete all secondary domains first (meaning that you want to delete your entire GroupWise system) or you designate a different domain as the primary domain. See “Converting a Secondary Domain to a Primary Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB20 Unexpected error

Source: GroupWise engine; administration engine.
Action: See Dxxx Unexpected error.

DB21 Database inconsistency detected

Source: GroupWise engine; administration engine.
Explanation: Database invalid or damaged.
Possible Cause: The database is invalid.
Action: Rebuild the database. See “Maintaining Domain and Post Office Databases” and “Maintaining User/Resource and Message Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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: Select a valid link type and link protocol for the domain link. See “Editing a Domain Link” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 .
  • At-sign @
  • Comma ,
  • Colon :
  • Double quote
  • Parentheses ( )
  • Braces { }
  • ASCII characters 0-13
Possible Cause: 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.
Action: Define Lotus Notes users in a foreign domain. See “Connecting to Non-GroupWise Messaging Systems” in the GroupWise 6.5 Multi-System Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB2A Invalid name

Source: GroupWise engine; administration engine.
Explanation: Invalid name.
Possible Cause: An invalid or restricted name has been specified.
Action: Enter a valid name.

DB2B Non-unique entry

Source: GroupWise engine; administration engine.
Explanation: Non-unique entry.
Possible Cause: A new entry conflicts with an existing entry in an index that must be unique. This can occur with a user’s network ID.
Action: Check the network ID for uniqueness on the post office where the user will reside.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB2C Invalid post office database

Source: GroupWise engine; administration engine.
Explanation: Invalid post office database (wphost.db).
Action: Rebuild the post office database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB2D Platform error

Source: GroupWise engine; administration engine.
Explanation: Wrong platform.
Possible Cause: No valid path could be found for the current platform type.
Action: Enter a path for the current platform.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB30 Gateway directory not found

Source: GroupWise engine; administration engine.
Explanation: Gateway directory does not exist.
Action: Check the specified gateway directory path and make sure the requested gateway is installed. For a list of gateways, see GroupWise 6 Documentation. GroupWise 5.5 gateways can be used with GroupWise 6.

DB31 Required field missing or empty

Source: GroupWise engine; administration engine.
Explanation: A required field is missing or empty.
Action: Provide a value for the required field(s).
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB32 Required field missing

Source: GroupWise engine; administration engine.
Explanation: A required field is missing.
Action: Check the record for a missing required field.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB33 Cannot open all post offices

Source: GroupWise engine; administration engine.
Explanation: Unable to open all post offices.
Possible Cause: There are more post offices defined than the operating system file handles allow.
Action: All directory synchronized commands will be performed through the MTA for the closed post offices.
Possible Cause: The link to the post office has been lost.
Action: Reestablish the link to the post office. See “Strategies for Message Delivery Problems” in GroupWise 6.5 Troubleshooting 2: Solutions to Common Problems.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB34 Time zone definition not found

Source: GroupWise engine; administration engine.
Explanation: No time zone defined.
Possible Cause: Unable to find a time zone definition for the current domain or post office.
Action: Select a time zone in the Identification page for the current domain or post office in ConsoleOne. See “Time Zones” in “System” in the GroupWise 6.5 Administration Guide
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB35 No pending operation for record

Source: GroupWise engine; administration engine.
Explanation: No pending operation for record.
Possible Cause: The pending operation has been completed.
Action: Refresh the list of pending operations. See “Pending Operations” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB37 Cannot delete current domain

Source: GroupWise engine; administration engine.
Explanation: Cannot delete the current domain.
Action: Connect to the primary domain. See “Connecting to a Domain” in “Domains” in the GroupWise 6.5 Administration Guide. Then delete the secondary domain from the primary domain. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: If the current domain is the primary domain, you cannot delete it unless you delete all secondary domains first (meaning that you want to delete your entire GroupWise system) or you designate a different domain as the primary domain. See “Converting a Secondary Domain to a Primary Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB38 Cannot delete domain that has post offices

Source: GroupWise engine; administration engine.
Explanation: Post offices exist for this domain.
Possible Cause: An attempt was made to delete a domain that has post offices assigned to it.
Action: Move the post offices to another domain. See “Moving a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. Then delete the domain after it is empty. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Delete the post offices. See “Deleting a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide. Then delete the domain after it is empty. See “Deleting a Domain” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB39 Domain database not found

Source: GroupWise engine; administration engine.
Explanation: Database is not available. No domain database (wpdomain.db) was found; however, a recover.ddb file was found.
Possible Cause: The database is currently being rebuilt.
Action: Allow the rebuild operation to finish.
Possible Cause: A database rebuild failed.
Action: Rename recover.ddb to wpdomain.db in the domain directory, then rerun the rebuild. See “Maintaining Domain and Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB3A Cannot delete domain that has links

Source: GroupWise engine; administration engine.
Explanation: Domain has indirect links.
Possible Cause: Cannot delete the domain because it is used in indirect routing.
Action: Reconfigure domain links before deleting the domain. See “Editing a Domain Link” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB3B Remote management message sent

Source: GroupWise engine; administration engine.
Explanation: Remote management message sent.
Action: 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: GroupWise engine; administration engine.
Explanation: Exclusive open error.
Possible Cause: An exclusive open for a domain to be merged or released failed because the domain is already in use.
Action: Have all administrators exit the domain database (wpdomain.db) before running the merge or release.
Action: Stop the MTA in the domain to be merged or released.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB3D Database sorting language changed

Source: GroupWise engine; administration engine.
Explanation: Database language has changed.
Action: Rebuild the database. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB3F Cannot delete required field

Source: GroupWise engine; administration engine.
Explanation: Cannot remove a required field.
Action: You must supply valid data for all required fields.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB40 Cannot delete gateway used in link

Source: GroupWise engine; administration engine.
Explanation: Gateway links exist.
Possible Cause: The gateway you are attempting to delete is used in a gateway link.
Action: Reconfigure the links before deleting the gateway. See “Editing a Domain Link” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB41 Database does not match domain or post office

Source: GroupWise engine; administration engine.
Explanation: Incorrect database path
Possible Cause: The database found at the specified path does not match the specified domain/post office name.
Action: Enter the correct path.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB42 Information lost during recovery

Source: GroupWise engine; administration engine.
Explanation: Information lost.
Possible Cause: Some records were lost during the recover operation.
Action: You might want to rebuild the database at this time. See “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB43 Maximum number of open post offices reached

Source: GroupWise engine; administration engine.
Explanation: Maximum number of post offices are opened.
Possible Cause: You have tried to open too many post offices.
Action: Close one or more post offices. See “Disabling a Post Office” in “Post Offices” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB44 Invalid user ID

Source: GroupWise engine; administration engine.
Explanation: Invalid user ID.
Possible Cause: This user ID is not recognized by GroupWise.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB45 GroupWise system not found

Source: GroupWise engine; administration engine.
Explanation: No system found.
Action: Verify the path to the domain database (wpdomain.db).
Action: Make sure you are logged in to the machine where the GroupWise system resides.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB46 Path too long

Source: GroupWise engine; administration engine.
Explanation: Path too long.
Action: You can map a drive to a lower level.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB47 Invalid area

Source: GroupWise engine; administration engine.
Explanation: Invalid BLOB area specified.
Possible Cause: ConsoleOne is unable to copy the GroupWise client view files from the software distribution directory into the post office directory structure.
Action: Make sure the software distribution directory has been created in your GroupWise system. See “Software Directory Management” in “System” in the GroupWise 6.5 Administration Guide and “Software Distribution Directory” in “Directory Structure Diagrams” in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB48 Cannot delete domain that has links

Source: GroupWise engine; administration engine.
Explanation: System link exists.
Possible Cause: You are trying to delete a domain that is specified as the link domain for an external system.
Action: Remove the external system or specify a different external domain as the link for the system. See “Using Direct Links” in “Connecting to GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide.
Possible Cause: You are trying to delete a domain that is set up for external system synchronization.
Action: Remove the external system synchronization entry, then delete the domain. See “Using Direct Links” in “Connecting to GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB49 Cannot use limited visibility distribution list as administrator

Source: GroupWise engine; administration engine.
Explanation: The selected distribution list cannot be used for the administrator because it is not visible to all users in your GroupWise system.
Action: 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 Distribution Lists” in “Distribution Lists, Groups, and Organizational Roles” in the GroupWise 6.5 Administration Guide.
Action: Change the visibility of the selected distribution list to system so that all users can see it.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB4A External sync message from unknown system

Source: GroupWise engine; administration engine.
Explanation: An external synchronization message was received from a system that the local GroupWise system cannot identify.
Possible Cause: The local GroupWise system is not set up to synchronize with the system that sent the synchronization message.
Action: Configure the local GroupWise system for external synchronization with that system. See “Exchanging Information Between Systems” in “Connecting to GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide.
Possible Cause: The external synchronization record in the domain database has been damaged.
Action: Delete the external synchronization record. In ConsoleOne, click Tools > GroupWise System Operations > External System Synchronization. Select an external system, then click Delete > Close. Exit and restart the MTA and POA. Re-create the external synchronization record. See “Exchanging Information Between Systems” in “Connecting to GroupWise 5.x and 6.x Systems” in the GroupWise 6.5 Multi-System Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB4B Cannot delete Internet domain name that is still referenced

Source: GroupWise engine; administration engine.
Explanation: The specified Internet domain name is being referenced in a system, domain, post office, or user.
Possible Cause: You are trying to delete an Internet domain record that is still in use.
Action: Change or delete the Internet domain association. See “Internet-Style Addressing” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB4D Database recovery required to update database structure

Source: GroupWise engine; administration engine.
Explanation: The database needs to be recovered.
Possible Cause: The database dictionaries (*.DC files) are newer than the current database, so a recover is needed to update the database.
Action: The admin thread of the POA or MTA should take care of this recovery automatically. If not, perform the recovery manually. See “Recovering Domain or Post Office Databases” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB4E Cannot delete default gateway

Source: GroupWise engine; administration engine.
Explanation: The gateway is used in default routing.
Possible Cause: You are trying to delete a GroupWise Internet Agent object that is used as the default gateway for routing Internet messages.
Action: Select a different Internet Agent as the default gateway for Internet messages. See “Internet-Style Addressing” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB4F Cannot delete POA that performs message transfer

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: Set up a different POA to provide the link to the domain MTA. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide. After another POA has been set up to provide the link with the MTA, the original POA can be deleted.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB50 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 6.5 Administration Guide. Then delete the library.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB51 Required network address information is missing

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of insufficient configuration information.
Possible Cause: An agent has not been properly configured with an IP address or TCP port.
Action: The POA is not properly configured. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: The MTA is not properly configured. See “Changing the Link Protocol between Domains” in “Message Transfer Agent” in the GroupWise 6.5 Administration Guide.
Action: The Internet Agent is not properly configured. In ConsoleOne, browse to and right-click the GWIA object, then click Properties. Click Post Office Links, then correct the link information as needed. See “Internet Agent” in the GroupWise 6.5 Administration Guide.
Action: The WebAccess Agent is not properly configured. See “Managing Access to Post Offices” in “WebAccess” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB52 Required path information is missing

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of insufficient configuration information.
Possible Cause: A domain or post office has not been properly configured with the path to the directory where the domain or post office is located.
Action: Check the UNC path information provided for the domain or post offices. See “Editing Domain Properties” in “Domains” or “Editing Post Office Properties” in “Post Offices” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB53 No message transfer POA has been selected

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of insufficient configuration information.
Possible Cause: 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.
Action: Configure the link between the POA and the MTA. See “Editing a Post Office Link” in “Domains” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB55 No POA is available for client/server

Source: GroupWise engine; administration engine.
Explanation: An action cannot be completed because of incorrect configuration.
Possible Cause: A post office has been configured for client/server access mode, but no POA has been configured for client/server processing.
Action: Configure a POA for client/server mode. See “Using Client/Server Access to the Post Office” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DB56 Specified e-mail address conflicts with the address of an existing gateway alias

Source: GroupWise engine; administration engine.
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 names first. See “Email Address Lookup” in “System” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 > GroupWise System Operations > System Preferences > Admin Lockout Settings and you are trying to run ConsoleOne with a version of the snap-ins that is too old.
Action: Update the GroupWise snap-ins. See “ConsoleOne” in “Installing a Basic GroupWise System” in the GroupWise 6.5 Installation Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DE02 Cannot perform delayed action request

Source: GroupWise engine; data store and deferment.
Explanation: Error in defer routine. Unable to perform delayed action request.
Possible Cause: Insufficient memory.
Action: Wait and retry the operation later.
Possible Cause: Invalid defer data file (ngwdfr.db).
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DE05 Unexpected error

Source: GroupWise engine; data store and deferment.
Action: See Dxxx Unexpected error.

DF10 Required file or directory missing

Source: GroupWise engine; mailbox/library maintenance.
Explanation: Path error.
Possible Cause: If this error occurs from the POA, the path specified by the /home switch might be incorrect.
Action: Check the /home setting in the POA startup file. Make sure the specified path exists. Make sure the path is provided in the format required for the platform on which the POA is running. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.

NetWare Note: On a NetWare server, make sure the grpwise.ncf file contains the correct information.

Possible Cause: The ngwguard.dc file is missing from the post office directory.
Action: Copy the ngwguard.dc file from another post office or from the po subdirectory of the software distribution directory.
Possible Cause: 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.
Action: Check for backup user databases (userxxx.db) files with extensions *.dba through *.dbz. If found, move these backup databases to another directory, then try Mailbox/Library Maintenance or GWCheck again.

If no userxxx.db file exists (that is, only backup files exist), rename the most recent backup (for example, userxxx.dbz) to userxxx.db.

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 6.5 Troubleshooting 3: Message Flow and Directory Structure. Adjust the path to the post office in the post office Identification page in ConsoleOne.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DF15 Records lost during rebuild

Source: GroupWise engine; mailbox/library maintenance.
Explanation: The POA has been unable to rebuild 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 6.5 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 (wphost.db), does not match the guardian database (ngwguard.db). The error message includes the conflicting locations.
Action: Modify the UNC path to the document storage area as needed so that the post office database and the guardian database are both updated with the same current information. 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

DF27 Invalid NGWCHECK.DB database migration level

Source: GroupWise engine; mailbox/library maintenance.
Explanation: The GWCheck database (ngwcheck.db) contains invalid information.
Action: Delete the GWCheck database, then rerun GWCheck or Mailbox/Library Maintenance.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E501 Document version not available

Source: GroupWise® engine; document management.
Explanation: Document version not available.
Possible Cause: The document is currently in use.
Action: Have the user who retrieved the document version close it.
Possible Cause: The document is currently checked out.
Action: Have the user who checked it out check it back in. Look up "documents, checking in" in GroupWise client Help.
Possible Cause: The document is neither in use nor checked out, but is erroneously marked as such. This situation can arise because:

  • A user opened the document with a non-integrated application. A non-integrated application cannot check the document back into the GroupWise library when the user closes the document.

  • A user’s machine went down while the document was open.

Action: Manually reset the document status. Look up "document, status" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E503 Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E507 Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E508 Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E50A Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E50B Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E50C Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E50D Maximum number of libraries per post office reached

Source: GroupWise engine; document management.
Explanation: Maximum libraries reached.
Possible Cause: The maximum number of libraries allowed per post office has been reached. Each post office can have as many as 256 libraries. A user attempted to create the 257th library.
Action: Delete any unnecessary libraries on the post office. Then create the new library. See “Libraries” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.
Action: Create the new library on another post office.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E50E Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E512 Invalid user ID

Source: GroupWise engine; document management.
Explanation: The user ID on a document is not valid.
Possible Cause: User information on the document has been damaged.
Action: Repair the document information in the library. See “Maintaining Library Databases and Documents” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Run GWCheck on the library. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: A user tried to start the GroupWise client as a resource, that is, using the /@u-userID startup switch and specifying a resource rather than a user.
Action: None. You cannot start the GroupWise client as a resource. You must use a valid user ID.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E513 Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E514 Document version must be checked out and in by same user

Source: GroupWise engine; document management.
Explanation: User IDs do not match.
Possible Cause: The user is attempting to check in or close a document version using a different user ID than the one used to check it out. A document version must be checked in or closed by same user who checked it out or opened it.
Action: 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 GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E515 Cannot delete last version of document

Source: GroupWise engine; document management.
Explanation: Cannot delete last version.
Action: Delete the entire document, not just the version. Look up "documents, deleting" in GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E516 Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E517 Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E51B Access to feature denied

Source: GroupWise engine; document management.
Explanation: Access to requested feature denied.
Possible Cause: The user is attempting to use a document management feature that is not available to this user on this library.
Action: 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 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E51C Disk space limit exceeded

Source: GroupWise engine; document management.
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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E520 Unexpected error

Source: GroupWise engine; document management.
Action: See Exxx Unexpected error.

E521 Invalid library ID

Source: GroupWise engine; document management.
Explanation: Invalid library ID.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 GroupWise client Help.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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 machine.
Action: Make changes to the document, then save the document.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

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.
Action: Close the document.
Possible Cause: The document is archived.
Action: Restore the document. See “Restoring Archived Documents” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Novell Support Knowledgebase .

E525 Cannot delete lookup table; it is not empty

Source: GroupWise engine; document management.
Explanation: Lookup table not empty.
Possible Cause: Cannot delete the lookup table because it is not empty.
Action: Delete all entries from the lookup table, then retry the operation. See “Customizing Document Properties” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide for information about lookup tables.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

E526 Cannot delete lookup table; it is in use

Source: GroupWise engine; document management.
Explanation: Lookup table in use by a library.
Possible Cause: The lookup table cannot be deleted because it is being used by a library.
Action: Remove all library references to the lookup table, then retry the operation. See “Customizing Document Properties” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide for information about lookup tables.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

E527 Cannot create library; record already exists

Source: GroupWise engine; document management.
Explanation: Library already exists.
Action: Use a unique library name to create the library. See “Libraries” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

E528 Cannot transfer data to server

Source: GroupWise engine; document management.
Explanation: Transport to a machine failed.
Possible Cause: The system was unable to contact a needed machine.
Action: Make sure the needed machine is up, and that all transport hardware is functioning correctly.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

E529 All document blob areas full

Source: GroupWise engine; document management.
Explanation: All BLOB areas are full.
Possible Cause: All of the areas that hold binary large objects (BLOBs) are full, so the system was unable to create a new BLOB.
Action: Create a new library. See “Libraries” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

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 6.5 Administration Guide.

To see where the document belongs, right-click the document reference in the GroupWise client, then click Properties. Click Version, then check the current location and current filename information.

Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

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: If the error persists when the Personal Address Book already exists, see 8101 Memory error.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

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 machine where the error is occurring.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

E801 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E803 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E804 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E805 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E806 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E807 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E808 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E809 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E80C Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E80D Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E80F Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E810 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E811 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E812 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E813 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E814 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E815 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

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. Also see “Managing Library Access” in “Libraries and Documents” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

E818 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

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.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

E821 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E823 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E824 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E82B Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E82C Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E82E Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E82F Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

E848 Unexpected error

Source: GroupWise engine; object framework.
Action: See Exxx Unexpected error.

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.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F000 Memory error

Source: GroupWise® engine; QuickFinder™.
Action: See F0xx Memory error.

F007 End of command reached unexpectedly

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F008 Missing parenthesis in search command

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F009 Missing operator in search command

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F00A Switch at end of search command ignored

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F00B Unknown switch in search command

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F00C Ambiguous switch; supply more characters

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F010 Search cancelled

Source: GroupWise engine; QuickFinder.
Explanation: Search cancelled.
Action: Search was cancelled at user’s request.

F012 File I/O error

Source: GroupWise engine; QuickFinder.
Explanation: The QuickFinder process used by the Find feature cannot access a required file.
Possible Cause: The QuickFinder index is damaged.
Action: Rebuild the index of the database where the error occurred. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The disk is full where the QuickFinder index is located, so the QuickFinder process cannot write more information to disk.
Action: Free up disk space. See “Managing Database Disk Space” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: You do not have rights to the location where the QuickFinder index is located.
Action: Check your access rights. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide.
Action: In ConsoleOne®, you can set the proper user rights for all users in a post office or for an individual user. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide.
Action: Record the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F013 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error.

F014 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error.

F016 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F018 Number contains non-numeric characters

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F019 Search switch requires '=n'

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F01A Document summary field name or number required

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F01B Unknown field in search command

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F01C Ambiguous field; supply more characters

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F01D Empty quotation marks not allowed

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F01E /nowildcard and /prefix cannot be used together

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F01F Invalid syntax in search query

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F020 Date expected

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F021 Dates of range in wrong order

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F022 Missing switch after '/'

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F023 Word missing between operators

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F026 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F02A Search query must specify words to search for

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F02D Missing word after operator

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F02E Invalid date

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F02F Word too long for search

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F030 Empty parentheses not allowed

Source: GroupWise engine; QuickFinder.
Action: See F0xx Query syntax error.

F037 Memory error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Memory error.

F03E Memory error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Memory error.

F045 Unexpected error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Unexpected error.

F046 File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F047 File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F048 File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F049 File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F04A File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F04C File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F04D File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F04E File not found during QuickFinder indexing

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F04F File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F050 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F051 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F052 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F056 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Memory error.

F060 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F061 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F062 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F063 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F064 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F065 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F066 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F067 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F068 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F069 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F06A Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F06B Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F06C Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F06D Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F06E Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F06F Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F070 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F071 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F072 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F073 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F074 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F075 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F076 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F077 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F078 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F079 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F07A Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F07B Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F07C Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F07D Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F07E Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F07F Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F080 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F082 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F083 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F084 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F085 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F086 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F087 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F088 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F089 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F08A Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F08B Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F08D Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F08E Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F08F Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F090 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F091 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F092 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F093 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F094 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F095 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F096 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F097 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F098 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F099 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F09A Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F09B Memory error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Memory error.

F0A1 Memory error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Memory error.

F0B2 Memory error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Memory error.

F0B5 File I/O error

Source: GroupWise engine; QuickFinder.
Action: See F0xx File I/O error.

F0B9 Unexpected error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Unexpected error.

F0BA Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0BB Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0BC Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0BD Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0BE Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0BF Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0C0 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0C2 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F0C4 Database error

Source: GroupWise engine; QuickFinder.
Action: See F0xx Database error (index).

F101 Cannot connect to remote server

Source: GroupWise engine; NetWare® remote server connection table.
Action: See F1xx Cannot connect to remote server.

F102 Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Action: See F1xx Cannot connect to remote server.

F103 Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Action: See F1xx Cannot connect to remote server.

F104 Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Action: See F1xx Cannot connect to remote server.

F105 Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Action: See F1xx Cannot connect to remote server.

F106 Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Action: See F1xx Cannot connect to remote server.

F107 Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Action: See F1xx Cannot connect to remote server.

F108 Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Action: See F1xx Cannot connect to remote server.

F0xx 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. See "find, using operators and conditions" in GroupWise client Help.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F0xx 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 occurs. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide.
Possible Cause: The disk is full where the QuickFinder index is located, so the QuickFinder process cannot write more information to disk.
Action: Free up disk space.
Possible Cause: You do not have rights to the location where the QuickFinder index is located.
Action: Check your access rights.
Action: In ConsoleOne®, you can set the proper user rights for all users in a post office or for an individual user. See “GroupWise User Rights” in “Security” in the GroupWise 6.5 Administration Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F0xx Database error

Source: GroupWise engine; QuickFinder.
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 6.5 Administration Guide.
Action: If this error occurs on a message database (MSGnn.DB) or user database (USERxxx.DB), run GWCheck. See “Standalone Database Maintenance Programs” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F0xx Database error (index)

Source: GroupWise engine; QuickFinder.
Explanation: Generic database error.
Action: Rebuild the index of the database where the error occurs. See “Rebuilding Database Indexes” in “Databases” in the GroupWise 6.5 Administration Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F0xx Memory error

Source: GroupWise engine; QuickFinder.
Explanation: Generic QuickFinder memory error.
Action: Exit and restart the GroupWise client.
Action: Free up more memory before running the GroupWise client.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F0xx Unexpected error

Source: GroupWise engine; QuickFinder.
Explanation: An engine error has occurred for which GroupWise does not have a specific error message.
Action: Exit and then restart the GroupWise client.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .

F1xx Cannot connect to remote server

Source: GroupWise engine; NetWare remote server connection table.
Explanation: GroupWise cannot connect to a remote server where needed information is located.
Possible Cause: The POA can no longer access the remote server where a document storage area is located.
Action: Make sure the remote server is running.
Action: Make sure the POA startup file contains the /user and /password or /dn startup switches so the POA can log in to the remote server. See “Using POA Startup Switches” in “Post Office Agent” in the GroupWise 6.5 Administration Guide.
Action: In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object.
Action: Make sure the user the POA is logging in as has sufficient rights to access the needed location on the remote server. See “Creating a NetWare Account for Agent Access (Optional)” in “Installing GroupWise Agents” in the GroupWise 6.5 Installation Guide.
Action: Record the specific error code and the conditions under which you encountered the error. For the latest error code solutions, search for TIDs about the error code in the Knowledgebase .