Groupwise Error No Document Libraries Available
Favorite Rating: GW Users can no longer see any Libraries or access any documentsThis document (3360728) is provided subject to the disclaimer at the end of this document. Environment Novell GroupWise 7Novell GroupWise Document ManagementThis is specific to the following Configuration.Single Domain with 2 post offices.Post Office A has only usersPost Office B has only libraries Situation GroupWise users can no longer see any Libraries.From the GroupWise Client, attempting to access Tools | Options | Libraries reports. GroupWise Error: There are No Document Libraries AvailableAnd the GroupWise POA reportsError: Dependent store file does not exist on the disk [C05D] Resolution Discovered the User's Post Office did not have a po\gwdms directory. This is important because the gwdms directory contains the dmsh.db. The dmsh.db contains the library information. The Library post office directories were fine.Since the User's po\gwdms and the dmsh.db is missing here are the steps to resolve this:1 - Unload the User's poa2 - Run GWCheck.exe with the following options: a) fill in the normal fields such as Database Path and the Post Office Name (to the User's PO) b) for object type choose User/Resource and in the field type in dmsh.db. c) On the Databases tab uncheck User and Message and Document. d) Action: Choose Structural Rebuild. e) RunThis will fix the C05D errors. GWCheck Will Error, because the dmsh.db does not exist on disk. This will remove or drop the dmsh.db reference from the ngwguard.db, allowing us to recreate the dmsh.db.To recreate the dmsh.db. 3 - Stay in GWCheck and change these options. a) Object Type - select Post Office b) Action: Select Analyze/Fix Library. With only Verify Library checked. c) Run4 - Reload the User's POAThis recreates the po\gwdms\dmsh.db and will allow the User's to see the Libraries and access their documents. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use
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 http://www.novell.com/support/kb/doc.php?id=3360728 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 http://support.novell.com/docs/Tids/Solutions/10062174.html 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 User6. 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 Library4. Only check Verify Library | click Run -- this will create a new DMSH.DB**************************************
comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/b4k2crp.html by Novell Support as specific customer issues have been resolved. C050 Transaction aborted Source: GroupWise engine; database services. Explanation: Attempted operation after critical error; transaction aborted. Possible Cause: If this error occurs during domain-related activities, such as adding users or synchronizing domains, the domain database has been damaged. Action: Check and, if necessary, repair the domain database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise groupwise error 2012 Administration Guide. C055 Unexpected error Source: GroupWise engine; database services. Action: See C0xx Unexpected error. C057 Database maintenance in progress; please exit Source: GroupWise engine; database services. Explanation: Maintenance in progress error. Possible Cause: Database maintenance in progress (one of the databases is being recovered or rebuilt). Action: Exit GroupWise and try again later. Depending on the size of the database, the maintenance could take from a few groupwise error no seconds to several minutes. Possible Cause: If the condition continues for an extended period and no GroupWise maintenance is being performed, another program might already have the required file open with exclusive access. Action: Check the open/lock activity on GroupWise databases and other files. You might find that a backup program is holding the file open. Possible Cause: If this error occurs constantly from the POA, a damaged message file might be blocking its processing. Action: Check the priority subdirectories of the /wpcsout/ofs directory. See Post Office Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure. Move message files out to a temporary location until the damaged message file is eliminated. Undamaged message files can then be returned to their original subdirectories for processing. C059 Database file already exists Source: GroupWise engine; database services. Explanation: GroupWise attempted to create a user file, message file, or library file, but it could not create the file because the file already existed. Possible Cause: The ngwguard.db file has been renamed or deleted. When the POA detects the guardian database is missing, it creates a new one. The original guardian database contained a catalog of dependent databases (user, messages, library, and so on)