Home > Groupwise Error > Groupwise Error 8201

Groupwise Error 8201

The POA requires exclusive access to databases when rebuilding them. What happens is the user goes to Open Archive within the GroupWise client and they immediately get an 8201 error. This has worked for everyone reporting the issue here. What kind of regular maintenance jobs do you run on your post office(s)? (the scheduled stuff) RE: 8201 errors!! http://fileupster.com/groupwise-error/groupwise-error-8201-fix.html

RE: 8201 errors!! RE: 8201 errors!! For support information, please visit Support. Explanation: The POA cannot access a required file.

Join UsClose [prev in list] [next in list] [prev in thread] [next in thread] List: ngw Subject: Re: [ngw] 8201 error on opening GroupWise client From: "Rhonda Tisdell"

Home drives are on an OES2 SP2 - Linux server The server is virtualized on VMWare's VSphere (was ESXi to begin with) The symptoms are usually experienced by a new archive Action: Make sure the ngwguard.dc file exists in the post office directory. The Big EveNt - back in 2012 BrainShare 2011 delayed 8201 Error on Archive location in GroupWise 8.x ► 2010 (56) ► December (2) ► November (3) ► October (7) ► Archive a message that is "ok" to potentially lose (only had this happen once, but it's a caveat you'll want to be aware of) Open Archive and verify the message is

Action: Shorten the path name to a length that is valid for the operating system. Possible Cause: The password entered by the user does not match the one stored in the encrypted file. Action: Use the /user and /password switches to provide the login information for the server where the document storage area is located. check my blog Look up “archive, directory” in GroupWise client Help.

If it does not, copy it from the po subdirectory of your software distribution directory. Are there a lot of MSGXX.DBa, DBb, DBc, etc in this OFMSG directory? Make sure the post office you are trying to rebuild and the domain it belongs to contain the correct files (especially *.dc files). Possible Cause: If this error occurs from the POA, there might be a problem with its input queue.

See Connecting to a Domain in Domains in the GroupWise 2012 Administration Guide. http://support.gwava.com/kb/?View=entry&EntryID=2331 What do I do? 0 Question by:eberhardt2329 Facebook Twitter LinkedIn Google LVL 8 Best Solution bywaybadmojo The MSG DB is most likely corrupted or locked. Reboot the server. Please note the error code in the title.

See Post Office Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure. weblink Also make sure the MTA has access to the post office. To view the list in ConsoleOne, browse to and right-click the Domain object, then click Properties. Action: In the GroupWise client, open the archive, then use the Repair Mailbox feature to repair the archive.

Possible Cause: If this error occurs when users exit the GroupWise client, the users might have the archive directory set to a location where they do not have sufficient rights. SeanAIX430 (TechnicalUser) (OP) 26 Sep 04 17:29 Well you were right about the service pack, I figured that one out on thursday night got all happy cause it seemed to fix I generally use c:\grpwise\archive to keep within the 8.3 file format. http://fileupster.com/groupwise-error/groupwise-fehler-8201.html Are you aComputer / IT professional?Join Tek-Tips Forums!

Action: Use Browse to find the correct path. Then I'll have to restore from backup and change userxxx.db from the old name to the new???? Open Archive, verify that they can see at least the message that was just archived.

Check the location to make sure the required library directory structure exists.

The first one is a memory error. SeanAIX430 (TechnicalUser) (OP) 24 Sep 04 11:33 I ran GW check last night after I finally got SP5 installed, and I had thought it took care of the issues because I Then synchronize the library. RE: 8201 errors!!

Action: Check destination file name specified and ensure it is unique. Make sure users have sufficient rights to create and modify files there. See Tools for Analyzing and Correcting GroupWise Client Problems in Client in the GroupWise 2012 Administration Guide. his comment is here Possible Cause: Attempted to decrypt a file using an encryption level that is no longer supported.

Action: Verify the existence, ownership, and rights of the directories involved with message flow (domain, post office, and MTA local directory). I have checked the documentation and can not really see anything that is relevant other than if this error occurs for a user who has preciously been able to access GroupWise Privacy Policy Site Map Support Terms of Use Login with LinkedIN Or Log In Locally Email or Username Password Remember Me Forgot Password?Register ENGINEERING.com Eng-Tips Forums Tek-Tips Forums Search Posts Provide Feedback < Back to Support Search SUSE Support Forums Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Delete the ngwguard.db file, then copy ngwguard.fbk to ngwguard.db. Possible Cause If this error occurs in the GroupWise client when trying to retrieve items from a restore area, the restore area might not be valid. Red Flag This Post Please let us know here why this post is inappropriate. so when I reboot this is released.