The Five Most Common GroupWise Errors


The following sections include a quick reference to the five most common errors seen in GroupWise, what they typically mean, and the actions to take to solve them.

D107Record Not Found

Description: This error means that one record has a reference to a second record, and the second record is not found. This is typically considered a content-related problem in a message store database (rather than a structural problem). This typically happens when a pointer record in a user's database (USERxxx.DB) points to a record in a message database that no longer exists. Another possibility is that a master record in a message database (MSGxxx.DB) points to another record in the message database that does not exist.

Action: In the case of a message store database, usually a contents check of the database resolves the problem. The trick is determining which database to check. Chapter 20, "Troubleshooting Message Flow," explains where data is kept based on the message type or who sent it. If you have questions as to which database to check, read Chapter 20.

Tip

You can run a contents check on a specific MSGxxx.DB file. To do so, run the standalone GWCHECK and enter the name of the MSGxxx.DB file in the User/Resource field. See Figure 23.1 for an example.

Figure 23.1. Running GWCHECK on an MSGxxx.DB file



8209Path to File Not Found

Description: In this case, GroupWise is trying to access a file and it cannot. This generally means that either the path you specified is incorrect, or the GroupWise software cannot reach the path because of assigned rights. If the software can reach the path, it cannot find the file it expects to find there.

Action: Indicate a correct path, put the file in place that GroupWise is looking for, and make sure that the GroupWise process has rights to the location indicated.

C05DDependent Store Does Not Exist on Disk

Description: Every database in the GroupWise message store is registered in the NGWGUARD.DB file. This error means that a database is registered in the NGWGUARD.DB file, but it is not physically in the location where the NGWGUARD.DB says the file should be. In the case of an NGWGUARD.DB on a post office, all USERxxx.DB files should be in the post office\OFUSER directory. If the post office agent (POA) reports a C05D error on a file by the name of USER123.DB, this means that the NGWGUARD.DB file reports that the file is in the post office\OFUSER directory, but it cannot find the file there. If the POA complains of a C05D error on an MSGxxx.DB file, that means it cannot find the file in the post office\OFMSG directory.

The GroupWise message store can also exist in a GroupWise archive, a GroupWise caching mailbox, or a GroupWise remote mailbox.

Action: Although the cause is easily stated, the action is not so easy to spell out. The solution varies based on the conditions in which you have the problem. This is best illustrated with a few scenarios.

Scenario 1Issue: UserA moved from PO1 to PO2. However, the user's mail did not move to PO2. The administrator moved UserA back to PO1, fixed UserA's mailbox, and then attempted to move UserA to PO2. The POA at PO2 gives the error C05D with reference to UserA's USERxxx.DB file.

Scenario 1Explanation: On PO2, a new USERxxx.DB file was created for UserA the first time UserA moved there. UserA might have even received a couple of messages from USERxxx.DB from the PO2 post office. When UserA was moved back to PO1, PO2 sent the few new message items to PO1, deleted the USERxxx.DB file from the post office, and unregistered it in the NGWGUARD.DB file. Everything is correct, but the POA has an old image of the NGWGUARD.DB cached in memory, and it hasn't reread the NGWGUARD.DB file. As strange as it might seem, the POA is the same one that deleted the reference to the USERxxx.DB file in the NGWGUARD.DB, but it doesn't even acknowledge that.

Scenario 1Action: You need to bring the POA down and then back up so that it rereads the NGWGUARD.DB file. Then you must attempt to move UserA again. See Chapter 13, "Moving Users," for more guidance on trying to move a user when a move fails the first time.

Scenario 2Issue: A user is attempting to archive a message, and receives a C05D error. You look in the Archive directory and there is only a NGWGUARD.DB and a MSG.DB file (there's no USER.DB file).

Scenario 2Explanation: In the Archive directory (the OFXXXARC directory, in which the XXX is the user's three-character FID), there is an NGWGUARD.DB file. This file is complaining that the USER.DB or the MSG.DB file in the OFXXXARC directory is not registered in the NGWGUARD.DB file.

Scenario 2Action: Follow these steps:

1.

Exit the GroupWise client as the user with the problem.

2.

Go to the archiveOFxxxARC directory.

3.

Rename the NGWGUARD.DB to NGWGUARD.BAD.

4.

Rename the MSG.DB to MSG.GOOD (if there is a MSG.DB).

5.

Go into GroupWise as the user.

6.

Have the user send one simple message to and from his or her email address.

7.

Archive that one message.

8.

Exit GroupWise.

9.

Go to the archiveOFxxxARC directory.

10.

Delete the newly created MSG.DB file.

11.

Rename the MSG.GOOD file to MSG.DB.

12.

Run the standalone GWCHECK on the user's archive, as shown in Figure 23.2. Perform the Re-create User Database action.

Figure 23.2. Running GWCHECK on a user's archive


After doing this, all the user's messages that were recovered from the MSG.DB file will have their pointers added to the USER.DB file. The messages will be placed in the Cabinet.

C067Store Number Is Invalid

Description: This error means that a database in the GroupWise message store is physically located in the message store, but is not registered in the NGWGUARD.DB file. This error might be thought of as the reverse of the C05D error. This is generally evidence of the fact that the NGWGUARD.DB file is damaged, and therefore lost its reference to a database, or the file was placed back into the message store area manually, but was not reregistered in the NGWGUARD.DB file.

Action: Once again, the action you take varies based on the scenario. Here's an example of one scenario:

Issue: The user TKRATZER tries to log into his account. He cannot log in; he gets a C067 error when trying to do so. The POA also reports a C067 error in its log when user TKRATZER tries to log in.

Explanation: TKRATZER's user database file (USERTAY.DB) is not registered in the NGWGUARD.DB file. It does exist in the post office\OFUSER directory. The NGWGUARD.DB file probably sustained some damage, and as a result the Registry for USERTAY.DB was lost from the NGWGUARD.DB.

Action: Follow these steps:

1.

Go to the post office\OFUSER directory of the post office where TKRATZER resides.

2.

Rename the file USERTAY.DB to USERTAY.GOOD.

3.

Have the user TKRATZER log in, and then have user TKRATZER log out. Doing so will create a new USERTAY.DB file that is now registered in the NGWGUARD.DB file.

4.

Rename the new USERTAY.DB file to USERTAY.NEW. (You might have to wait for several minutes to be able to do this because the POA has this file cached. Otherwise, you can bring the POA down and back up.)

5.

Rename the USERTAY.GOOD file to USERTAY.DB.

The user TKRATZER should be able to log in now, without getting the C067 error.

C022Database Damage

Description: The database is damagedstructurally. This means that when GroupWise is attempting to read the database, it isn't finding the layout of the database to be standard. GroupWise cannot proceed in accessing the database, because it cannot guarantee consistent results. Let's tie this to an analogy: Imagine you come into your bedroom in the dark and your other half has moved the furniture around. There's no guarantee you aren't going to stub your toe if you proceed.

Action: The database needs to be rebuilt. If the database is a GroupWise domain or post office database, it must be rebuilt from the System Maintenance utility. If it's a message store database, it must be structurally rebuilt from GWCHECK or from Mailbox/Library Maintenance.



NOVELL GroupWise 7 Administrator Solutions Guide
Novell GroupWise 7 Administrator Solutions Guide
ISBN: 0672327880
EAN: 2147483647
Year: 2003
Pages: 320
Authors: Tay Kratzer

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net