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!

8201 errors!!

Status
Not open for further replies.

SeanAIX430

Technical User
Jun 29, 2001
189
My GW system is really acting up. All users are getting a lot of 8201 errors when opening GW and emails, the POA shows lots of 'The Database facility reported error [8201] on userxxx.db, and ngwguard.db' messages. People are unable to send emails to other internal users. I have run gwcheck several times without error messages. I've done a tom of
analyze/fix attempts on individual and post offices and domains, but nothing seems to work.

I have read that the 8201 errors are about a file being open somewhere either by archive, backup or on the server. But almost no one uses archive, i've unloaded the backup software and rebooted several times all without any affect, any Ideas??

GW55 ep sp3. I'm trying to install sp5 today but keep getting:

"Can NOT apply this Support Pack. Your GroupWise software does not match the Support Pack you are using". when I run setup.
 
ALso where do undeliverable email messages go? There have been a bunch over the last few days.

I'm getting to the point of being ready to just make a backup and start from scratch on the whole gw system, but I need more info on how to do it.
 
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.
 
I had read about that and wandered across that setting last night and it is client/server only. I'm going to rebuild a Software distribution directory on my pc to see if i can get the latest service pack onto my server.
 
1. Have you used the standalone gwcheck to do the analyze/fixes? (not the one in NWAdmin) I *think* you can do this in 5.5? It's been a while. In the software dist dir it's under /admin/util/gwcheck

2. have you tried doing a top-down rebuild? There is a good TID for this. #10070541

3. Are you certain that the network connctions are happy? eg: speed and duplex on the nic(s) and switch? This can cause database issues.

4. What kind of regular maintenance jobs do you run on your post office(s)? (the scheduled stuff)
 
I ran GW check last night after I finally got SP5 installed, and I had thought it took care of the issues because I opened mine and one other mailbox and didn't get one 8201 error, but this morning I came in to see plenty more 8201 errors in the POA log as well as a few F03E errors, and 802E. The first one is a memory error. This is from the end of my gwcheck log:

50 Orphaned Blob files deleted........................ 13
52 Blob files with missing trailers deleted........... 570
Correctable conditions encountered:
CODE DESCRIPTION COUNT
---- -------------------------------------------------- -----
35 Rule records with invalid action parameters........ 3
37 Item records with missing message database recs.... 13
39 Unrecognized or invalid files in mail directories.. 734
65 QuickFinder temp files in index directories........ 458
66 GWCheck log files in log directory................. 4
67 Outdated execution records.(notify/alarm).......... 22
82 Inaccessible attachment files...................... 10


I think I'm going to follow that TID this weekend and hopefully fix this freaking thing. Any other suggestions?
 
The F03E sounds like you may need to re-do your quickfinder indexes. You can do that from gwfix.

The 802E does not show up in my GW Toolkit/Logicsource stuff or on the support site. Is that the correct error #?

the 8201 on the POA could be a bad user database. If you can isolate which file this is happening on, there are some things you can do. 1 - try various fixes to that userdb (utilities), restore it from tape, or in the most extreme case you would archive all of the users's mail, and export their address book as a *.NAB file. Then create a new user account for them and import the mail and imort the address book. The POA can give 8201 sometimes when it can't work properly with a particular db becuase it's broken. (for ex, tid# 2951342)

The top down rebuild is a good idea - just make sure you have a good backup first.

 
The real issue is that I'm getting the 8201 error on just about every user db in the system.
 
I just looked at Novell's support site, GW5.5 EP lists 2 SP5's, one for English, one for multilingual. The installation complaint sounds like you need the other version.
8201 errors usually are authentication error warnings, try doing a top down rebuild of Wpdomain.db and your wphost.db files AFTER you get the right agent .nlm's running.

Mike Gallo
 
Well you were right about the service pack, I figured that one out on thursday night got all happy cause it seemed to fix everything, but when I got in on friday morning the same things were happening. I did a rebuild on the DO and PO databases and the errors are still occurring.

I think I'm going to install gw from scratch and then update the user accounts? Is that the logical next step? I'm not sure how to uninstall and then reinstall GW, but I'm sure it's not too hard to figure out. Then I'll have to restore from backup and change userxxx.db from the old name to the new????
 
End of GWCheck run on my own GW db:

*********************************************************************
Uncorrectable conditions encountered:
- No problems found
Correctable conditions encountered:
CODE DESCRIPTION COUNT
---- -------------------------------------------------- -----
37 Item records with missing message database recs.... 1
67 Outdated execution records.(notify/alarm).......... 1
*********************************************************************



BOX COUNT VIOLATORS- count > 500 (NOTE- only violations are shown!)

So it tells me there are a couple of issues but doesn't fix them for me when I have everything checked?
 
I made a new user account to play around with restoring an email db and the brand new mailbox with no mail had an 8201 error come up when I opened it for the first time!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top