Environment
Novell GroupWise 2012
Situation
Error: "C05D" on Client
Error: "C067" on POA
Error: "C067" on Client
The Definitive C05D and C067 TID.
Resolution
- Ensure that Verbose logging is enabled on the POA
- Find the line in the log where the C05D is reported - here it is possible to see the specific database the the C05D is being reported against.
- Start the standalone version of GWCheck and fill in the Post Office information.
- In the User/Resource field enter the database name that you noted in Step 2, like USERxxx.DB.
- In Action select Structural Rebuild
- Select Run
If the check is successful you will see an Error 26 in the GWCheck log. This means that the database registry entry has been removed from the guardian database (ngwguard.db). It may be necessary to restart the POA as the problem database (or lack thereof) has been cached.
The only time that this has not worked is in the following scenario:
- A database has been manually renamed for some other problem, however, the file extension was left as .DB. For example USERXYZ.DB was renamed to USERXYZOLD.DB
- A contents check was run on this Post Office which had the undesired effect of adopting the USERXYZOLD.DB in the guardian
The only solutions in this scenario are either a restore of the NGWGUARD.DB from backup or opening an incident with Novell Technical Services to have the problem entry removed from the guardian database.
UPDATE: This error can also be seen after a migration from NetWare to Linux. It is a CASE issue and is the result of the case stored in the NGWGuard.db not matching the case of the database stored on disk. If the instances of this error are few after a migration then the easiest solution is to simply reverse the case of the file, so USERXYZ.DB should be renamed to userxyz.db.
To manually fix a C067 follow these steps:
- Ensure that Verbose logging is enabled on the POA
- Find the line in the log where the C067 is reported - here it is possible to see the specific database the the C067 is being reported against.
- Start the standalone version of GWCheck and fill in the Post Office information.
- In the User/Resource field enter the database name that you noted in Step 2, like USERxxx.DB.
- In Action select Analyze/Fix Databases - make sure Contents and Fix Problems are selected.
- Select Run
This should adopt the database into the guardian and the problem should be solved. Again, a restart of the POA may be necessary to clear any cached entries.
Another way to solve this problem is as follows:
- Ensure that Verbose logging is enabled on the POA
- Find the line in the log where the C067 is reported - here it is possible to see the specific database the the C067 is being reported against.
- Stop the POA
- Browse to the Post Office directory structure and rename the database that the C067 was reported against, ensuring that the extension is not left as .DB.
- Restart the POA and log in as the same user that generated the error. Perform the same action that the user was performing. This will create a new, empty version of the problem database.
At this point there are 2 choices:
- Continue with the empty database - nothing more needs to be done.
- Rename the original database back to .DB so no information is lost. The POA will need to be stopped again for this.
Additional Information
"storelowercase" should never be run while the POA is loaded. NOTE: The server GWCHECK launched through ConsoleOne that is run BY the POA will run a storelowercase. This has been reported to engineering. Do NOT EVER run storelowercase as an option from the ConsoleOne launched Mailbox Maintenance, as the POA will not be able to rename many open databases, resulting in similar results as these.
The C05D is always that the database in question is registered in the Guardian database but is not on disk.
The C067 is always that the database in question is found on disk but is not registered in the guardian database. In both cases the POA is not able to resolve the problems on it's own so manual intervention is needed.
Formerly known as TID# 10074228
