Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Groupwise 6.5, Archive Search function fails, causes error 8210

Status
Not open for further replies.

grandall

MIS
Mar 6, 2003
2
US
Good day Ladies and Gentleman:

We are running GW6.5 backend on a Netware v6 server. The Windows XP client versions being V6.5.4, v6.5.1, and v6.0.2. The user we are interested in has v.6.5.4. The users archives are on the network, same server as the domain and PO resides but on a different volume. The archive location is locked down. The archive directory (ofxxxarc)size is 3.11GB with approx 24,500 files. The MSG.DB is approx 67MB and USER.DB approx 16MB.

ISSUE: When the user enters his archive and tries to perform a SEARCH function, he recieves an "ERROR 8210" Windows appears, user clicks OK and then the "Find Results" Window appears "No items were found, would you like to modify your find". NO button is clicked. We tested the search function with archive messages in front of our face with the user and subject fields in clear view so the Search operation should have picked up at least those messages. This user correspondence is legal history on what occurred on our manage projects so he needs to retrieve archive messages from time to time.

Actions: I used GWCHECK V6.5.1, did a "Analyze/Fix" (checked Structure, Index Check, and Fix problems)against the user archive directory using a Novell map drive to the location, i.e. - G:\(user)\ofxxxarc to the database path. After the operation I had the user enter his archive, perform Search function. The ERROR 8210 occurred again. I had the user close Groupwise. I did a Structural Rebuild on his archive. Operation finished, I had him reenter his archive and search. Again the Error 8210 message.

What is the answer to this problem. I have not done a Recreate User Database operation and I wouldn't like to unless its a last resort. I would appreciate anyone assistance with this. Thanks
Gary Randall
IT Specialist
 
A lot of the info I have on that error points to rights issues on the storage location. I would verify that the rights are correct, but another test could be to bring the files locally and see if that makes any difference.

Marvin Huffaker, MCNE
 
Thanks Marv for your response. I checked the user rights to his archive directory on the server. He has RWECMF (Read, Write, Erase, Create, Modify and File Scan) privileges. This morning I copied his archive down to his boot drive, as him, (c:\temp\(username)), unlocked his archive file location (using Consoleone, Groupwise Util and Client options at the User object) and set it to the hard drive location. Had user reenter Groupwise, go to his Archive and do a Search operation again. Error 8210 again. I should have given you the rest of the message previously. Its as follows "Groupwise Error [8210] Groupwise cannot open the post office files. For solutions, your system administrator can look up the error code in the Groupwise Documentation: Troubleshooting Guide". The documentation doesn't say much on the Error 8210, other then manually archiving files recieving that error.
 
Did you run Analyze/Fix, selecting content as well? (on a copy)
 
Also, despite rights is there any chance that some of the files are Read Only?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top