Users are getting "No document libraries available" when trying to create documents
(Last modified: 13Mar2003)
This document (10062174) is provided subject to the disclaimer at the end of this document.
fact
Novell GroupWise 5.5
Novell GroupWise Enhancement Pack
symptom
Users are getting "No document libraries available" when trying to create documents
Some post offices have the problem some post offices do not (example: users in PO1 and PO2 have the problem but users in PO3 and PO4 do not)
fact
The post offices whose users don't have the problem have a DMSH.DB located under the GWDMS directory.
cause
To explain the cause let me explain the scenario. I have a domain with 5 post offices (PO1 thru PO5). PO5 is the post office that owns the library that the users are trying to add documents to. Even though the other post offices do not contain any libraries they still have to have a GWDMS directory (located under the post office) which needs to have a DMSH.DB. The DMSH.DB is like a table of contents it contains a listing of all the libraries in the GroupWise system as well as the libraries that it's own post office may or may not own. When a library is created the other post offices should be synched up to be aware of the new library. In this case the post offices having the problem did not have a DMSH.DB so from their perspective there were no libraries. Troubleshooting determined that somehow the databases had been deleted but the NGWGUARD.DB still had a reference for the DMSH.DB. Since it had a reference for the DMSH.DB it could not create a new one.
fix
To create the DMSH.DB we had to run a Verify Library against the problem post office to see if it would create the DMSH.DB, it didn't. That meant that the NGWGUARD.DB still has the DMSH.DB referenced in the Store Catalog. We had to drop it and run the Verify Library again for the 3 post offices with the problem. ***CAUTION: RECREATING THE DMSH.DB WILL CAUSE YOU TO LOSE ANY LOOKUP TABLES CREATED IN DOCUMENT PROPERTIES MAINTENACE IN NWADMN32 OR CONSOLEONE.
In order to drop a store from the guardian database, the following steps must be followed using the standalone version of GWCheck.
1. Enter the correct path and post office name of the post office in question.
2. Select User/Resource in the Object Type field.
3. Enter the name of the database in the field for the resource (i.e. DMSH.DB).
4. Under Action, select Structural Rebuild.
5. Only check User
6. The GWCheck log should report an error 26: Store file not found.
How to run a Verify Library from the GWCHECK?
1. Enter the correct path and post office name of the post office in question.
2. Select Post Office in the Object Type field.
3. Change Action to equal Analyze/Fix Library
4. Only check Verify Library | click Run -- this will create a new DMSH.DB
******************************************************************************
In another case users would see the message that there were "No Libraries available" when dragging files to the Documents Folder. All the libraries were deleted but the user was unaware of this. The message was correct in this situation.
fact
The post offices with the problem do not have a DMSH.DB
symptom
Not all users have this problem
fact
GroupWise DMS
document
| Document Title: | Users are getting "No document libraries available" when trying to create documents |
| Document ID: | 10062174 |
| Solution ID: | NOVL46956 |
| Creation Date: | 01May2001 |
| Modified Date: | 13Mar2003 |
| Novell Product Class: | Groupware |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.