See Post Office Directory in Book 4: Directory Structures for the location of this file. Action(s)Make sure that necessary drives are still correctly mapped. Make sure the post office you are trying to rebuild and the domain it belongs to contain the correct files (especially *.dc files). To view the list in ConsoleOne, browse to and right-click the Domain object, then click Properties. weblink
If it does not, copy it from the po subdirectory of your software distribution directory. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 8 Administration Guide. NetWare Note: You can check user access rights to files and directories using the RIGHTS command. The GWTSA might be better solution. http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/hxnjs40x.html
Action: If no valid user or process has the file open, delete the connection to unlock the file. Action: The file you are trying to open was created in a newer version of GroupWise and cannot be opened in an older version. What happens is the user goes to Open Archive within the GroupWise client and they immediately get an 8201 error. If it is less than 24 KB, it is considered empty.
In the NetWare Administrator browser window, click a post office or user objectToolsGroupWise UtilitiesSet Rights. Possible Cause: If this error occurs when importing a document into GroupWise, there might be a problem with the library. Error occurs when trying to Rebuild any domain in the system from the primary and including the primary domain. Open Archive, verify that they can see at least the message that was just archived.
Action: Repair the user’s Caching or Remote mailbox. Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner. This has worked for everyone reporting the issue here. http://www.novell.com/support/kb/doc.php?id=10016619 Possible Cause(s)If this error occurs when importing a document into GroupWise, there may be a problem with the library.
Caller is not allowed access to a file.". ExplanationEnd of file was reached unexpectedly. Possible Cause(s)If this error occurs when the user sends a message to multiple users or to users in a different post office, the user may not have sufficient rights to write You can check user access rights to the file or directory using the RIGHTS command.
NetWare Note: You can check file ownership using the NDIR command. this page See Restoring Archived Documents in Libraries and Documents in the GroupWise 8 Administration Guide. Good news is I have a work around. The program might also have tried to create a file that already exists.
The user may not have rights to the file or directory. http://glitchtest.org/groupwise-error/groupwise-error-code-8201.html Possible Cause: If this error occurs from the POA, there might be a problem with its input queue. Action(s)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 If the post office still cannot be accessed, resolve those network problems. 8202 Cannot access required file Source: GroupWise engine; file input/output.
Action: If necessary, restart the server to reset all file locks. Make backup copies of the NGWGUARD.DB, NGWGUARD.RFL, and NGWGUARD.FBK files. See Using POA Startup Switches in Post Office Agent in the GroupWise 8 Administration Guide. check over here Explanation: File seek error.
ExplanationFile modify error. 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. ExplanationDisk full.
NetWare Note: You can use the NetWare Monitor NLM to perform these actions. To find out what rights a user should have in a post office, see Chapter 3: GroupWise User Rights in the Security Guide. 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 8 Troubleshooting 3: Message Flow and Possible Cause: GroupWise is no longer able to access a required file.
See Maintaining User/Resource and Message Databases in Databases in the GroupWise 8 Administration Guide. 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(s)If this error occurs when exiting the GroupWise client, the user database (USER
This re-creates the wpcsout directory structure for the post office. However, the information provided in this document is for your information only. Caller is not allowed access to a file (8201).'. Possible Cause: An invalid or old (closed) file handle was passed to a file I/O function.
Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server Access box. NetWare Note: You can check user access rights to the file or directory using the RIGHTS command. In some situations, this may mean downing the file server. Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner.
If necessary, change the ownership to a valid user such as the system administrator. 8206 Cannot open file SourceGroupWise engine; file input/output. You can check file and directory ownership using the NDIR command. Possible Cause: If this error occurs from the POA when rebuilding a database, a user might still have the database open. Conditions: Caller tried accessing/opening a file that did not have or allow sharing.