> Groupwise Error
> Groupwise Error 8209 Archive
Groupwise Error 8209 Archive
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 See Enabling GroupWise Check in the Windows Client in Client in the GroupWise 2012 Administration Guide. read all tids ludsy (IS/IT--Management) 18 Feb 03 18:37 Cant say that have seen before but have you checked:1. Select a storage area, then click Edit. http://redhatisnotlinux.org/groupwise-error/groupwise-error-8209.html
If file names are not currently displayed, right-click the menu bar, then click Filename to display the file name in the activity log. If necessary, change the ownership to a valid user such as the system administrator. 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 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
For the specific location of this file, see Post Office Directory and GroupWise Software Distribution Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure. This re-creates the wpcsout directory structure for the post office. Novell makes all reasonable efforts to verify this information.
Click Post Office Links, select the post office, then click Edit Link. Possible Cause: If this error occurs from the POA when rebuilding a database, a user might still have the database open. Explanation: End of file was reached unexpectedly. For example, copying a GroupWise client installation from one laptop to another might introduce this problem.
You can use a filter to display only items that are older than a specified number of days. Action: Verify that the list of post offices belonging to the domain is correct. Explanation: File modify error. http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/hxb2on3e.html Action: For the required contents of domains and post offices, see Domain Directory and Post Office Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.
Action: 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. RE: Archive 8209 Path not found.... Register now while it's still free! Action: If disk space is available and database ownership is correct, the disk itself might need repair.
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! If necessary, change the ownership to a valid user such as the system administrator. An error occurred when renaming or moving a file to another location. Right-click the document reference, then click Properties > Activity Log.
Join Us! *Tek-Tips's functionality depends on members receiving e-mail. this content Action: Run GWCheck. New user databases and message databases cannot be created for new users if this file is missing. * Novell trademark. ** Third-party trademark. You might find that a backup program or virus scanner is holding the file open.
Action: Start the POA including the --rights switch to determine the specific problem the POA is encountering. See Synchronizing Database Information in Databases in the GroupWise 2012 Administration Guide. See GroupWise User Rights in Security Administration in the GroupWise 2012 Administration Guide. weblink 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.