groupwise C022 error

Ahmed Dadoo

unread,

Sep 9, 1998, 3:00:00 AM9/9/98

to

** High Priority **

hi guys

several of my users cannot send any mail from groupwise 5.2 .. they receive incoming mail though..
check the novell knowledgebase - got the latest novell client, patches .. 5.2.3 ... they suggest to restructure the database/ user mailbox/ postoffice ..blah... blah. Done all of that ..
what next ? delete mailbox - recreate account !!

thanks in advance
regards

Ahmed Dadoo
Generation Information Management, Cape
tel: +27-21-914-3111, fax: +27-11-910-0524

George Taylor

unread,

Sep 9, 1998, 3:00:00 AM9/9/98

to

Shoot, copied all that tech stuff but forgot to mention how it
worked out for us. It actually was two fold for me, probably my fault.
Rebuilt the PO and didn't restart the POA, that causes a problem
with the NWGaurd database, went through the roll back process and
it took care of the problems.

George E. Taylor
Network Analyst
Black Hills Health Care Network
gta...@lhsnet.com
605.642.0143

>>> Ahmed Dadoo <Ahmed...@ESKOM.CO.ZA> 09/09 5:41 AM >>>

George Taylor

unread,

Sep 9, 1998, 3:00:00 AM9/9/98

to

Some possibilities, straight from the tech center.

Source
GroupWise* engine; database services.

Explanation

The integrity of an item or structure in the database has been compromised.

Possible Cause(s)

Using the original Microsoft** client for NetWare.

Action(s)

Use the latest Novell** Client 32 for Windows 95 or obtain the necessary patch to the Microsoft client for NetWare. The patch is called NWREDIR.VXD, located under the file name MSRD95.EXE, and is dated August 19, 1996.
Check and, if necessary, repair the database. See Mailbox/Library Maintenance.

Possible Cause(s)

The NGWGUARD.DB file has been damaged.

Action(s)

Check the size of the NGWGUARD.RFL file (roll forward log). If it is less than 24 KB, it is considered empty. Make backup copies of the NGWGUARD.DB, NGWGUARD.RFL, and NGWGUARD.FBK files. Delete the NGWGUARD.DB file, then copy NGWGUARD.FBK to NGWGUARD.DB. Be sure to copy it; do not rename it.

Possible Cause(s)

If this error occurs when administering GroupWise, a domain or post office database may be damaged.

Action(s)

Validate and rebuild the domain or post office database. See System Maintenance.

Action(s)

If this error occurs from the POA after you have already rebuilt databases, restart the POA.

Possible Cause(s)

If this error occurs in the GroupWise client in remote mode, there may be a problem with the structure or content of the remote Mailbox. For example, copying a GroupWise installation from one laptop to another might introduce this problem.

Action(s)

Delete the ROFDATA directory on the remote computer, then request all information from the Master Mailbox again.

Action(s)

Reinstall GroupWise on the remote computer. See Enable Remote Capabilities and GroupWise Remote Mailbox.

Possible Cause(s)

The hard disk where the GroupWise databases are stored is damaged.

Action(s)

Scan the hard disk for damage. Correct any problems with the hard disk. Repair the database. See Mailbox/Library Maintenance. If the database cannot be repaired, you must restore it from backup.

Possible Cause(s)

If the post office resides on a NetWare 3.11 server, users may not have sufficient rights to the post office directory.

Action(s)

Make sure users have full rights (RWCEMF) to the post office directory.

Possible Cause(s)

If users are accessing a post office on a NetWare server through an NT server using the Microsoft Gateway for NetWare, the gateway may not be providing adequate support for the number of users trying to access the post office.

Action(s)

The Gateway Service for NetWare is not intended as a full service router for NetWare services. Use a more robust connection to the post office.

Action(s)

Make sure you have all the latest NetWare patches installed.