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 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 Check the location to make sure the required library directory structure exists. Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner. http://kreativexpert.com/novell-error/novell-error-code-8201.html
Right-click the document reference, then click Properties > Activity Log. Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner. An attempt by the file system to create a unique file failed. Possible Cause: Attempt by the file system to rename a file failed.
fix Make sure backup software is not running during production hours. I'm going to rebuild a Software distribution directory on my pc to see if i can get the latest service pack onto my server. The backup program was locking the groupwise databases when trying to back them up. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum!
Consult your product manuals for complete trademark information. When clicking the message for a second time it opens without any problems. In the software dist dir it's under /admin/util/gwcheck2. Action: Reenter the password. 8214 Unsupported encryption level Source: GroupWise engine; file input/output.
See the GroupWise documentation for information on how to successfully backup your GroupWise post office directory structure. BigShyBear (MIS) 24 Sep 04 20:00 I just looked at Novell's support site, GW5.5 EP lists 2 SP5's, one for English, one for multilingual.The installation complaint sounds like you need the The errors occur the FIRST time that the user clicks on something (new mail message, another folder etc.) cause This was a registry issue. Explanation: File lock error.
Is that the correct error #?the 8201 on the POA could be a bad user database. This has worked for everyone reporting the issue here. Possible Cause: The GroupWise databases might be owned by an invalid user. If the destination file exists and is read only, this error might occur.
Explanation: Disk full. have a peek at these guys For the specific location of this file, see Post Office Directory and Software Distribution Directory in Directory Structure Diagrams in GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure. Action: See Message Transfer/Storage Directories in Directory Structure Diagrams in GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure. For technical services and file updates, see Novell Support.
Possible Cause: If this error occurs from the POA, the POA might not have access to a required file. Novell makes no explicit or implied claims to the validity of this information. If the document is not needed, you can delete it from the library to eliminate the error. check over here note The NetWare client and Server feature for File Caching has also been known to cause file locks and can be turned off at the client or server to insure the