Novell Error Code 8201
Action: Reinstall the GroupWise client on the remote computer. See Connecting to a Domain in Domains in the GroupWise 8 Administration Guide. Look up “archive, directory” in GroupWise client Help. 8219 Cannot connect to remote network resource Source: GroupWise engine; file input/output. Typically, the Novell Groupwise Error 8201 error message may be brought on by Windows system file damage. weblink
To view the list in ConsoleOne, browse to and right-click the Domain object, then click Properties. Restart the POA. Amongst many other things, this guide will cover: GroupWise Architecture Using GroupWise System Operations Installing and Configuring the GroupWise Internet Agent Moving Resources, Distribution Lists and Libraries Troubleshooting Message Flow Securing If necessary, change the ownership to a valid user such as the system administrator.
Action: Verify that the file is not currently locked by another process that has terminated. Hopefully it will work for everyone else as well. Reboot the server.
Possible Cause: If the error occurs as the user is exiting the GroupWise client, the client might be encountering a problem archiving messages. However, none of the TIDs that I've come across seem to have the particular issue I've been running into noted. 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: If this error occurs when a user is trying to access his or her archive, the archive might be read only.
If necessary, change the ownership to a valid user such as the system administrator. Click Post Office Links, select the post office, then click Edit Link. There are 2 methods in which to resolve Novell Groupwise Error 8201 error code: Advanced Solution (advanced): 1) Start your computer and then log on as an administrator. 2) Click on Make backup copies of the ngwguard.db, ngwguard.rfl, and ngwguard.fbk files.
Possible Cause: An attempt to lock a file failed. Action: Run GWCheck. 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 Delete the ngwguard.db file, then copy ngwguard.fbk to ngwguard.db.
- Click Here to join Tek-Tips and talk with other members!
- There is a good TID for this.#100705413.
- Your GroupWise software does not match the Support Pack you are using".
- See Restoring Archived Documents in Libraries and Documents in the GroupWise 8 Administration Guide.
- Then I'll have to restore from backup and change userxxx.db from the old name to the new????
- 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.
Herarchive folder is pointing to the right directory. Just delete "HKCU\Software\Novell\GroupWise\Login Parameters\Path to Remote Database". Join Us! *Tek-Tips's functionality depends on members receiving e-mail. See Standalone Database Maintenance Programs in Databases in the GroupWise 8 Administration Guide.
I think I'm going to install gw from scratch and then update the user accounts? have a peek at these guys Possible Cause: If this error occurs when a user is running in Caching mode or Remote mode, the user’s local databases might be damaged. Go back to the mailbox. Document ID:7011384Creation Date:15-NOV-12Modified Date:15-NOV-12NovellGroupWise Did this document solve your problem?
Possible Cause: If this error occurs the first time a user tries to archive messages, the user might not have sufficient rights to the archive location. gov ! If this error occurs when creating a new document in the GroupWise client, the blank template file for the application might be missing. check over here Action: The file you are trying to open was created in a newer version of GroupWise and cannot be opened in an older version.
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. See "Connecting to a Domain" in "Domains" in the GroupWise 6.5 Administration Guide. Explanation: Bad file handle.
If filenames are not currently displayed, right-click the menu bar, then click Filename to display the filename in the activity log.
If that isn't there, you might try uninstalling the GW client, then delete the HKCU\Software\Novell\GroupWise key to make sure the custom settings are gone. -- Paul Harvey [email protected] Network Engineer Walla RE: 8201 errors!! Possible Cause: Another program might already have the required file open with exclusive access. Action: In the GroupWise client, check the users’ path to the archive directory.
Possible Cause: If this error occurs when a specific user starts the GroupWise client, that user database (userxxx.db) might be damaged. Possible Cause: If this error occurs from the POA, the POA might not have access to a required file. Possible Cause: The required file is locked by another program, for example, a backup program. this content Action: Retry the action later.
Possible Cause: If this error occurs as the GroupWise client starts, the user might have specified an archive path that does not exist. 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! sstoppel (IS/IT--Management) 23 Sep 04 07:52 Are you running in client/server or direct access mode?If the latter you could have a workstation with caching enabled screwing up your databases. 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.
RE: 8201 errors!! Copyright law may
also apply to the contents of this email.
<<<< GWAVASIG >>>>