AnsweredAssumed Answered

Solidworks PDM made a vault but not a database

Question asked by Samuel Cohen on Aug 7, 2019
Latest reply on Aug 9, 2019 by Sam Sam

Like • Show 0 Likes0
Comment • 5

Hi, I'm working on the 2018 Student version of Solidworks PDM. We currently have one vault and today I tried to create a new one. Now, when you look at the Administration view, it shows that there are two vaults:

When I open the top one, it works fine. When I open the bottom one, I get this (after logging in using the default admin password):

When I was creating the vault, I got some error about the archive server (which I'm kicking myself for not screenshotting) and the setup decided to rollback it's actions so far. I distinctly remember seeing in the progress bar it saying "Creating database for <vault>" and then after it failed, "Deleting database for <vault>". I then tried again so that I could better document the issue, but I got an error saying that a vault with the same name already exists where it didn't before.

I can't delete or edit the new vault in any way without getting that issue. I've tried working on it both remotely where the PDM and SQL server is installed as well as locally through the administration tool.

Sam Sam Aug 8, 2019 4:06 PM

Correct Answer

Hi,
if you know the name Vault - give search (if search gives nothing - means there are no problems).

But in general watch Registry branches:
HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\Vaults
HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\DatabaseID

HKEY_CURRENT_USER\Software\Solidworks\Applications\PDMWorks Enterprise\ServerConfig
HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\Databases
HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\Vaults
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolidWorks\Applications\PDMWorks Enterprise\Databases
HKEY_USERS\S-1-5-21-***********-**********-**********-1000\Software\SolidWorks\Applications\PDMWorks Enterprise\DatabaseID
HKEY_USERS\S-1-5-21-**********-**********-**********-1000\Software\SolidWorks\Applications\PDMWorks Enterprise\Vaults

It is desirable to check it locally and on the server. having previously (just in case) made the necessary backup copies, backups and recovery points of a system.

If there are no problems here - look bases at SQL Server.

See the reply in context

No one else had this question

Outcomes

Sam Sam Aug 8, 2019 4:39 AM

Hi,
1. Try to look in Registry.
2. Try to remove base directly in SQL (if it can be done).

Actions

Samuel Cohen @ Sam Sam on Aug 8, 2019 10:26 AM

Which registry entry should I be trying to edit?

Edit: Here's a screenshot of regedit, showing that there is no database information for the second vault. Should I just delete the registry entry for the second vault? I'm wary because I don't want to risk accidentally ruining a PDM server being run in production.

Actions

Sam Sam @ Samuel Cohen on Aug 8, 2019 4:06 PM

Hi,
if you know the name Vault - give search (if search gives nothing - means there are no problems).

But in general watch Registry branches:
HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\Vaults
HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\DatabaseID

It is desirable to check it locally and on the server. having previously (just in case) made the necessary backup copies, backups and recovery points of a system.

If there are no problems here - look bases at SQL Server.

Actions

Samuel Cohen @ Sam Sam on Aug 8, 2019 4:25 PM

Should I just go ahead and delete every single reference to the vault that I can find? Will that have any bad effects on the other vault or in trying to make a new vault with the same name?

Actions

Sam Sam @ Samuel Cohen on Aug 9, 2019 3:56 PM

1. Delete Vault in Registry will not influence other Vault and should not prevent creation of new Vault (99.9%). At least in the specified places.
But some information in Registry can be implicitly.
Therefore it is desirable to keep a reserve of the deleted branches (on an emergency).
2. Too most treats SQL Server.

If there are any doubts or fears - what prevents to create Vault with other name?

By the way, except Registry there can be files of Local Views - they can disturb too. Will not prevent to clean the Temp folder yet.

Actions

5 Replies

Sam Sam Aug 8, 2019 4:39 AM
Mark Correct
Correct Answer
Hi,
1. Try to look in Registry.
2. Try to remove base directly in SQL (if it can be done).
Like • Show 0 Likes0
Actions
- Samuel Cohen @ Sam Sam on Aug 8, 2019 10:26 AM
  Mark Correct
  Correct Answer
  Which registry entry should I be trying to edit?
  
  Edit: Here's a screenshot of regedit, showing that there is no database information for the second vault. Should I just delete the registry entry for the second vault? I'm wary because I don't want to risk accidentally ruining a PDM server being run in production.
  Like • Show 0 Likes0
  Actions
  - Sam Sam @ Samuel Cohen on Aug 8, 2019 4:06 PM
    Unmark Correct
    Correct Answer
    Hi,
    if you know the name Vault - give search (if search gives nothing - means there are no problems).
    But in general watch Registry branches:
    HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\Vaults
    HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\DatabaseID
    HKEY_CURRENT_USER\Software\Solidworks\Applications\PDMWorks Enterprise\ServerConfig
    HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\Databases
    HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\Vaults
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolidWorks\Applications\PDMWorks Enterprise\Databases
    HKEY_USERS\S-1-5-21-***********-**********-**********-1000\Software\SolidWorks\Applications\PDMWorks Enterprise\DatabaseID
    HKEY_USERS\S-1-5-21-**********-**********-**********-1000\Software\SolidWorks\Applications\PDMWorks Enterprise\Vaults
    It is desirable to check it locally and on the server. having previously (just in case) made the necessary backup copies, backups and recovery points of a system.
    If there are no problems here - look bases at SQL Server.
    Like • Show 0 Likes0
    Actions
    - Samuel Cohen @ Sam Sam on Aug 8, 2019 4:25 PM
      Mark Correct
      Correct Answer
      Should I just go ahead and delete every single reference to the vault that I can find? Will that have any bad effects on the other vault or in trying to make a new vault with the same name?
      Like • Show 0 Likes0
      Actions
      - Sam Sam @ Samuel Cohen on Aug 9, 2019 3:56 PM
        Mark Correct
        Correct Answer
        1. Delete Vault in Registry will not influence other Vault and should not prevent creation of new Vault (99.9%). At least in the specified places.
        But some information in Registry can be implicitly.
        Therefore it is desirable to keep a reserve of the deleted branches (on an emergency).
        2. Too most treats SQL Server.
        If there are any doubts or fears - what prevents to create Vault with other name?
        
        By the way, except Registry there can be files of Local Views - they can disturb too. Will not prevent to clean the Temp folder yet.
        Like • Show 0 Likes0
        Actions

Solidworks PDM made a vault but not a database

Outcomes

Related Content

Recommended Content