2.2 82xx Errors
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 it is unrecognizable as a GroupWise database, for example, having a size of 0 KB or 2 GB.
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 . Click , select the post office, then click . 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 8 Administration Guide.
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.
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.
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.
Possible Cause:
If this error occurs for a user who has previously been able to access GroupWise successfully, the user’s Novell eDirectory object might have become damaged.
Action:
Delete the user object from eDirectory, then re-create it. Do not delete the user’s GroupWise account, because this would delete the user’s mailbox as well.
Possible Cause:
If this error occurs when users exit the GroupWise client, the users might have the 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 users exit the GroupWise client, the user database (userxxx.db) might be damaged.
Possible Cause:
If this error occurs when a user is running in Caching mode or Remote mode, the user’s local databases might be damaged.
Possible Cause:
If this error occurs when a user is trying to access his or her archive, the archive might be read only. This can occur if the user copied the archive to a CD.
Action:
Make sure that the archive directory and all its contents are marked read/write.
Possible Cause:
The GroupWise databases might be owned by an invalid user.
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 server. If the post office still cannot be accessed, resolve those network problems.
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.
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.
Possible Cause:
If this error occurs in the GroupWise client in Remote mode, there might be a problem with the structure or content of the Remote mailbox. For example, copying a GroupWise client installation from one laptop to another might introduce this problem.
Action:
Delete the rofdata directory on the remote computer, then request all information from the master mailbox again.
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.
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 re-creates 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.
Source:
GroupWise engine; file input/output.
Explanation:
End of file was reached unexpectedly.
Action:
Check the ownership of the GroupWise databases. If necessary, change the ownership to a valid user such as the system administrator.
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 generates 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.
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.
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 or rename the current file.
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 that the path to the archive directory exists and that you have sufficient rights to create and modify files. Look up “archive, directory” in GroupWise client Help.
Possible Cause
If this error occurs in the GroupWise client when trying to retrieve items from a restore area, the restore area might not be valid.
Possible Cause:
If this error occurs from the POA, the POA might not have access to a required file.
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 that the list of post offices belonging to the domain is correct. To view the list in ConsoleOne, browse to and right-click the Domain object, then click . Click . Check the properties of each Post Office object to make sure that the post office directory for each post office exists. Make sure that the post office path is correctly defined in the Post Office object. In ConsoleOne, right-click the Post Office object to display the post office Identification page. Also make sure the MTA has access to the post office.
Possible Cause:
If this error occurs when importing a document into GroupWise, there might be a problem with the library.
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 . Click . Select a storage area, then click . 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 . If filenames are not currently displayed, right-click the menu bar, then click 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 8 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.
Possible Cause:
A required file or subdirectory could be missing from the directory structure of the user’s post office.
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.
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.
Source:
GroupWise engine; file input/output.
Explanation:
File lock error.
Possible Cause:
An attempt to lock a file failed.
Action:
Verify that the file is not currently locked by another process that has terminated.
Possible Cause:
You cannot open the specified file because another user might have the file open.
Action:
Ask the other user to close the file.
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.
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.
Possible Cause:
If this error occurs from the POA, the POA might not have access to a required location.
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.
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.
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.
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 . For technical services and file updates, see Novell 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 . Check the setting in the Archive Directory field and check whether or not it is locked.
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.
8219 Cannot connect to remote network resource
Source:
GroupWise engine; file input/output.
Explanation:
The POA cannot access a document storage area located on a remote server.
Possible Cause:
If this error occurs when running the Windows agents, the user’s user name and password on the server where the POA is running are different from the user name and password on the server where the document storage area is located.
Action:
Use the same user name and password on the server where the POA is running and the server where the document storage area is located.
Action:
In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object.
821A Access to a critical file denied
Source:
GroupWise engine; file input/output.
Explanation:
The POA cannot access a required file.
Possible Cause:
The required file is locked by another program, for example, a backup program.
Action:
If necessary, restart the server to reset all file locks.