Novell Error 8201

Possible Cause: A directory required for the normal flow of GroupWise messages could be missing. Possible Cause: The file you are trying to perform an action on does not exist. Action: Use backup software that interacts properly with GroupWise file locking, as described in GroupWise Target Service Agent in Databases in the GroupWise 8 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. weblink

Right-click the document reference, then click Properties > Activity Log. Make sure the post office you are trying to rebuild and the domain it belongs to contain the correct files (especially *.dc files). Check the ownership of the GroupWise databases. See Standalone Database Maintenance Programs in Databases in the GroupWise 8 Administration Guide.

The file name is nre12.exe---- Note when you uninstall keep any shared DLL's3. See the GroupWise documentation for information on how to successfully backup your GroupWise post office directory structure. Possible Cause: If this error occurs from the POA when rebuilding a database, a user might still have the database open. Action: You can determine what BLOB file the document was in from the GroupWise client.

Explanation: The POA cannot access a document storage area located on a remote server. I have run gwcheck several times without error messages. Action: Make sure that the archive directory and all its contents are marked read/write. Consult your product manuals for complete trademark information.

GWCheck provides additional repair options compared to the Repair Mailbox feature in the GroupWise client. Bookmark Email Document Printer Friendly Favorite Rating: Error: "8201- access to file has been denied" (Last modified: 27Sep2004) This document (10016619) is provided subject to the disclaimer at the end of If the document is needed, you can restore the BLOB file from backup. Restart the POA.

The POA requires exclusive access to databases when rebuilding them. One way to disconnect an open file instead of bringing the server down is to, dismount the volume concerned and then remount it. Possible Cause: If the error occurs as the user is exiting the GroupWise client, the client might be encountering a problem archiving messages. Caller is not allowed access to a file [8201]" Resolution The customer was running Carbonite backup software on their Windows server, and every time there was a change to any file

Action: Check and, if necessary, repair the database. have a peek at these guys It's been a while. I generally use c:\grpwise\archive to keep within the 8.3 file format. The most common causes of a Deny Write=1 are usually caused by either backup software, or virus protect software.

Make sure the IP address and TCP port for the POA are specified correctly in the Client/Server Access box. Default archive locations for this environment are to the users home drives. Novell makes no explicit or implied claims to the validity of this information. check over here I think I'm going to install gw from scratch and then update the user accounts?

People are unable to send emails to other internal users. 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. Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files.

RE: 8201 errors!!

Pages Home About Me BrainShare Tips & Tricks Monday, January 10, 2011 8201 Error on Archive location in GroupWise 8.x If you've used GroupWise long at all you've probably seen this Document ID: 10067294 Solution ID: NOVL67933 Creation Date: 05Jan2002 Modified Date: 29Aug2002 NovellGroupWise Client/Admin Did this document solve your problem? Novell makes all reasonable efforts to verify this information. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another.

See Enabling GroupWise Check in the Windows Client in Client in the GroupWise 8 Administration Guide. Then create a new user account for them and import the mail and imort the address book. Open the GroupWise client, verify that the File Location is pointing back to the original location. this content Any ideas?

Rename the wpcsout directory in the post office. Consult some Novell Partners to see if they have better solutions to allow GroupWise messages to be scanned for Viruses.https://www.novell.com/products/groupwise/partners/ Determine what is putting the deny write on the WPHOST.DB. If that user is not experiencing any problems with GroupWise, you can delete the problem items. If none are and the database is still locked, break the connection to unlock the file.

Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. For some users it moves from an 8201 error to an 8209 error after several unsuccessful attempts to get at the archive. An attempt by the file system to create a unique file failed. This has worked for everyone reporting the issue here.

In other words, as long as a GroupWise file displays a Deny Write=1, GroupWise does not have access to write to the file. Join UsClose novell.community.chat Discussion: GroupWise Error (8201) (too old to reply) ww 2003-12-09 20:45:31 UTC PermalinkRaw Message In GroupWise 6.5, when trying to move something to archive I get thefollowing error