Q: I get DF17 and/or F107 errors when loading the POA, how can I make them disappear?

 

A: These errors are seen when Libraries are deleted from the system or when aditional storeage areas are moved to another location, to understand the error let's see what is involved in deleting a Library or moving a storage area.

 

A library has multiple records in the different databases of the GroupWise system. The most importent ones are in the wpdomain.db, wphost.db and the ngwguard.db. The records in the wpdomain.db and the wphost.db are the records for the system so the Library is visible to the users etc. The record(s) in the ngwguard.db are there for the POA so it can find the location of the Library and if configured the additional storeage area(s). This is the database we need to look at when the POA will not load with the above errors.

 

When you delete a Library from the system the records get removed from the wpdomain.db by the ConsoleOne snapins, all other databases will get updated with a administration message that is sent from the domain you are connected to while removing the Library. Now the records are gone from the wpdomain.db the updates go trough the system including the post office the Library is located. In this post office the records get removed from the wphost.db. Next to this the ngwguard.db should be updated, in other words the Library records and storeage area records need to be removed. This in certain cases happens only for a part. The main records get removed however the ones related to the additional storeage area are left in the ngwguard.db. This is also the case when a storeage area is moved from one location to the other, updates are going trough the system but the records in the ngwguard.db are sometimes not updated correctly so the old server/volume information is still in the ngwguard.db.

 

When the POA is loaded it will try to find the storeage as defined in the ngwguard.db, when the directory structure is removed or even the server or volume isn't there anymore the POA is not able to connect to the storeage area. When this is the case the POA will not load and reports DF17 or F107 error.

 

At this point you can only get the POA running again when you use the /NOCONFIG switch, the real fix must be done by Novell NTS, we need to remove the left over records manual.