This is a followup to Solution Id: S-022257 . That solution would not work for us because we needed to add another vault and we already had a vault in production live and it good not be takin down. So we are publishing our fix.

We tried to add feedback to there system but it wouldn't let us comment on solution s-022257.

READ KB s-022257 first so you are aware of the issue and can see Solids fix.

This solution would work for my clinet if we could shutdown our other vault but that was not a option. We had to get creative and find a better solution and here is what we came up with and it worked.
We had a production vault and we wanted to create a test vault. When we did we got the error could not import defaults. With the info from this kb we made our own solution. And here it is.
Create new vault use sa password for creation and use defaults for admin and as soon as you click finish and the database is right before the importing starts(1-2 seconds best if ran by 2 machines and 2 people one creating on pdm and one logged into sql management studio to run sql query) we ran a sql script on our sql server to add our default sql user for the other vault db to our newly created vault db. The script creates a new user under that new db and adds db_owner role to that user. In our system it worked great and no down time on the prod vault.


You must change NEWDBNAME to your name and also pdmwe to your pdmwelogin sql user account
Also rember you have seconds to run this after you start it must be done as soon as the database is created. This soultion is really only for people wanting to build a second vault and can't shutdown there other vault during so. Otherwise use this KB to do a single vault.

******************************************************************
USE [NEWDBNAME]
GO
CREATE USER [pdmwe] FOR LOGIN [pdmwe] WITH DEFAULT_SCHEMA=[dbo]
GO
sp_addrolemember 'db_owner','pdmwe'


Feel free to contact me for help and or comments at james@jcdataconsulting.com