Locked out after Vault 4.0 upgrade

pcuce · Post by **pcuce** » Tue Jun 12, 2007 4:39 pm

I can get past this point if I try different things, such as one of the machine users instead of impersonation, but no matter what I do, the admin login never works on the web page.

Beth · Post by **Beth** » Wed Jun 13, 2007 4:35 pm

When you connect to your SQL database during the installation, are you using SQL authentication or Windows authentication?

pcuce · Post by **pcuce** » Thu Jun 14, 2007 7:51 am

I tried both.

Beth · Post by **Beth** » Thu Jun 14, 2007 2:45 pm

Are you installing Vault or Fortress? It looks like you're installing Fortress.

Can you send an email through to support at sourcegear.com (attn: Beth) with a link to this thread?

pcuce · Post by **pcuce** » Thu Jun 14, 2007 2:51 pm

Sure, I can do that. I only want to install Vault. I never saw a choice between installing Vault or Fortress. I don't even know what Fortress is.

lbauer · Post by **lbauer** » Fri Jun 15, 2007 4:23 pm

pcuce - i resolved that problem on my end by adding the sgvaultuser to the sgmaster database in SQL server - giving that account both public and db_owner rights.

I was able to confirm that if the account used by Vault to communicate with the database is not dbo for sgmaster, then no one can log in. This account might be sgvaultuser if you're using SQL Server Authentication, or if you're using Windows Authentication for Vault, it would be the ASPNET Account (Machinename\ASPNET) or NT Authority\Network Service, or the custom account you chose for the IIS process model (identity impersonation).

In SQL 2005 Server Management Studio, look in Security->Roles->Database Roles->db_owner->Properties and make sure the Vault account is listed under Role members.

If you're not SQL savvy, the best best is to uninstall and re-install or run the installer with the Repair option, so that the installer has another chance to make this right.

pcuce · Post by **pcuce** » Mon Jun 18, 2007 8:18 am

I actually reinstalled and repaired about 10 times but never got it to work. I'll file a support request when I have time to deal with it. For now we're just using the old version.