If necessary, change the ownership to a valid user such as the system administrator. 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. Action: See Message Transfer/Storage Directories in Directory Structure Diagrams in GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure. If the post office still cannot be accessed, resolve those network problems. 8202 Cannot access required file Source: GroupWise engine; file input/output. http://imagextension.com/groupwise-error/groupwise-error-8200-archive.php
See Maintaining Library Databases and Documents in Databases in the GroupWise 8 Administration Guide. Action: Use Browse to find the correct path. Make sure that the post office path is correctly defined in the Post Office object. Action: If necessary, restart the server to reset all file locks.
Shared folders will continue to function even after the owner has been disabled. In which case without good backupsyour only option isa) open incident with novellorb) unload poa, delete each msg file ,run standalone gwcheck, structuralrebuild, username=filenameofmsgdb. 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: You cannot open the specified file because another user might have the file open.
Possible Cause: One or more of the GroupWise databases might have an invalid owner or no owner. The POA requires exclusive access to databases when rebuilding them. Explanation: Path create failed. Register now while it's still free!
Is it maybe corruption problem with a shared folder from a GW client? Action: If errors occur during manual archiving, determine the user who sent the problem items. 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. https://www.novell.com/support/kb/doc.php?id=7000796 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
Those are monster dbs. If filenames are not currently displayed, right-click the menu bar, then click Filename to display the filename in the activity log. Action: In the GroupWise client, open the archive, then use the Repair Mailbox feature to repair the archive. See also Information Stored in the Post Office in Post Office Agent in the GroupWise 8 Administration Guide.
Action: Delete the user object from eDirectory, then re-create it. click site Action: Start the POA including the /rights switch to determine the specific problem the POA is encountering. Red Flag This Post Please let us know here why this post is inappropriate. If the document is needed, you can restore the BLOB file from backup.
Do not delete the user’s GroupWise account, because this would delete the user’s mailbox as well. Get More Info If necessary, change the ownership to a valid user such as the system administrator. Action: Exit, then restart the POA. 8210 Cannot create path Source: GroupWise engine; file input/output. See GroupWise User Rights in Security Administration in the GroupWise 8 Administration Guide.
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. In which case without good backupsyour only option isa) open incident with novellorb) unload poa, delete each msg file ,run standalone gwcheck, structuralrebuild, username=filenameofmsgdb. 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. useful reference 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.
Those are monster dbs. Close this window and log in. 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.
See Restoring Archived Documents in Libraries and Documents in the GroupWise 8 Administration Guide. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. Possible Cause: A directory required for the normal flow of GroupWise messages might be missing. Action: Purge deleted files from index subdirectories and the root of the sys: volume on the server where the problem is occurring. 8205 End of file Source: GroupWise engine; file input/output.
The program tried to access or open a file that did not have or allow sharing. See Standalone Database Maintenance Programs in Databases in the GroupWise 8 Administration Guide. See Connecting to a Domain in Domains in the GroupWise 8 Administration Guide. this page If the sending user is also having problems, check and, if necessary, repair the message database (msgnnn.db) of the user who sent the problem items.
Novell are having trouble trying to recover data from the two 2Gb databases and we've had to drop those two from the live system in order to get it back giving Join Us! *Tek-Tips's functionality depends on members receiving e-mail. In looking more > closely > > at her mailbox, it appears that these shared folders have been shared > with > > herself. Thanks, F.A.