Problem

This article discusses how to resolve the warning message “No database is connected to this view”. This warning message appears when trying to access a Vault View that is missing registry information on the computer. Without this registry information, the Vault View cannot function.

A vault view can be either Shared or Private. A shared view is accessible to all Windows profiles on the computer. A private view is only accessible to the Windows profile that creates the view. The connection information for a shared vault view is stored under the following registry keys:

• HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\Databases\[Vault Name]
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolidWorks\Applications\PDMWorks Enterprise\Databases\[Vault Name]

If the view is private, the view information is stored in the following registry key instead:

• HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\Vaults\[Vault Name]

When going into the Registry Editor, do not modify or delete anything except what is listed below. If you do not feel comfortable performing the steps listed below, please contact Technical Support.

Solution 1: Re-add the Vault View

If the view is not supposed to be private or is missing the shared view information in the registry, we can delete the problematic vault view and re-add it. Please take note that any files that are checked out in the view remain identified as checked out, so we must perform an Undo Check Out to release the checked-out state files before continuing. Use the steps below to re-add the vault view:

1. Delete the vault view by right-clicking on the vault view and selecting "Delete File Vault View"
2. Go to Start > All Programs > SOLIDWORKS PDM > View Setup.

3. Select "Next"

4. Select the appropriate Archive Server and click "Next"

Note: If the archive server is not shown in the list, it may need to be manually typed in using the Add button. Please see your PDM administrator if you are not sure which server to add.

5. Select the Vault and click "Next"
6. Specify the location for the Vault View, and whether to install the Vault View for only the current Windows Profile or for all Windows Profiles on the computer.

Note: Unless there are different users sharing the same machine, it is usually recommended to select the "For all Users" option. It is recommended to place the vault on or close to the root directory of a drive to avoid potential issues with file path length.

6. Click "Next" and then click "Finish"
7. Attempt to use the Vault View again

Solution 2: Export the Registry Keys from a Working Computer

Another solution is to export the needed registry keys from the registry of a working client computer. These are the registry keys covered at the top of this article. Then, we can import the registry keys to the problematic client computer and verify the following values after the keys have been restored: 

• DbName REG_SZ [Name of the file vault database]
• DbServer REG_SZ [Name of the SQL server]
• ServerLoc REG_SZ [Name of the archive server]
• ServerPort REG_DWORD [Archive server port, by default decimal value 3030]
• ShellRoot REG_SZ [Full path to the vault view folder (including the vault name)]

After importing the registry keys, attempt to use the Vault View again.

Solution 3: Manually Recreate the Registry Keys

The third solution is to download the needed registry file attached to this article in order to recreate the registry keys on the computer. Before the registry file can be used, the correct values will need to be input.

1. Open the registry file in Notepad

2. Edit the registry file with your vault values. The values can be obtained from the Administration tool for PDM with access to the vault properties or the registry of a working computer.

   

   

   

3. Import the updated registry file
4. Attempt to use the Vault View again

For additional support, existing customers can submit a ticket or new customers can contact Hawk Ridge Systems.