Upgrade from 3.0.7 to 3.1.8 broke Vault

PaulMargetts · Post by **PaulMargetts** » Mon Mar 13, 2006 9:44 am

Vault has been working fine for us since we installed it about 11 months ago. I decided to upgrade from the original installation (3.0.7) to the latest version ( 3.1.8 ). I ran "VaultServer_3_1_8.msi" on the server, which also has SQL server running on it, but then I found that I couldn't access Vault with Vault Admin on the server or with Vault Admin, Vault Client or Vault Web Client on remote machines. However, I am able to access the pages "http://yourvaultservername/VaultService" and "http://yourvaultservername/VaultService ... rvice.asmx".

I did not do the original installation, so it is quite possible that I did something "wrong". However, I pretty much stuck to the defaults, so I am surprised that an upgrade has gone so badly wrong. The system administrator has had a look at IIS and SQL and can't see any problems with these programs.

I have not attempted to run any of the other upgrade programs, and I have not rebooted the server.

The only messages I got during the installation were saying that "NT AUTHORITY\NETWORK SERVICE needs read/write permissions for some directories, and I clicked "YES" to have the installation make the changes.

Please let me know how I should go about finding out what is wrong.

mskrobul · Post by **mskrobul** » Mon Mar 13, 2006 12:10 pm

Are there any errors logged to the Vault Server log (%windir%\temp\sgvault\sgvault.log) when you try to connect with the Admin Tool or the Client?

PaulMargetts · Post by **PaulMargetts** » Tue Mar 14, 2006 4:57 am

mskrobul wrote:Are there any errors logged to the Vault Server log (%windir%\temp\sgvault\sgvault.log) when you try to connect with the Admin Tool or the Client?

I tried to do an attachment of the log file to the original post, but clearly that didn't work. Yes, I do get error messages when I try to connect. For example, please see below under today's date :

****START Cut and paste of sgvault.log *****

# SourceGear Vault Server
----3/10/2006 11:13:12 AM sgvaultsystem--()--
System Started
Version 3.0.7.2863
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 204800
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain = pc.cognex.com
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://spooks.pc.cognex.com/VaultService
Identity = natick-nt\sanjay
----3/10/2006 11:13:16 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login
----3/10/2006 11:17:21 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Logout
----3/10/2006 11:18:47 AM pmargett--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login
----3/10/2006 11:20:16 AM pmargett--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login
----3/10/2006 11:47:26 AM pmargett--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Logout
----3/10/2006 12:49:03 PM admin--neversaynever(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/10/2006 12:49:03 PM admin--neversaynever(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/10/2006 12:52:00 PM administrator--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/10/2006 12:52:00 PM administrator--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/10/2006 12:52:47 PM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/10/2006 12:52:47 PM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 3:10:42 AM agarcia--192.168.220.206(192.168.220.206)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 3:10:42 AM agarcia--192.168.220.206(192.168.220.206)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 3:11:26 AM agarcia--192.168.220.206(192.168.220.206)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 3:11:26 AM agarcia--192.168.220.206(192.168.220.206)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 3:12:26 AM agarcia--192.168.220.206(192.168.220.206)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 3:12:26 AM agarcia--192.168.220.206(192.168.220.206)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 4:36:36 AM pmargett--is5400035e.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 4:36:36 AM pmargett--is5400035e.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 8:27:30 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 8:27:30 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:30:28 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:30:28 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:42:58 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:42:58 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:46:30 AM pmargett--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:46:30 AM pmargett--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:46:45 AM pmargett--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:46:45 AM pmargett--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:47:18 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:47:18 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:49:33 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:49:33 AM admin--scaramanga4.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:50:08 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:50:08 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:51:50 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:51:50 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:52:19 AM sa--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:52:19 AM sa--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:52:39 AM natick-nt\sa--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:52:39 AM natick-nt\sa--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:58:55 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:58:55 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/13/2006 9:58:59 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Vault Failed to establish a connection to the database.
----3/13/2006 9:58:59 AM admin--spooks.europe.pc.cognex.com(10.90.160.9)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/14/2006 5:33:54 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Vault Failed to establish a connection to the database.
----3/14/2006 5:33:54 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/14/2006 5:34:31 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Vault Failed to establish a connection to the database.
----3/14/2006 5:34:31 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/14/2006 5:35:27 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Vault Failed to establish a connection to the database.
----3/14/2006 5:35:27 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/14/2006 5:35:35 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Vault Failed to establish a connection to the database.
----3/14/2006 5:35:35 AM pplummer--dr-maybe.europe.pc.cognex.com(10.95.80.3)--SSL Disabled Login failed for user 'sgvaultuser'.
----3/14/2006 5:45:32 AM pmargett--neversaynever(10.95.80.4)--SSL Disabled Vault Failed to establish a connection to the database.
----3/14/2006 5:45:32 AM pmargett--neversaynever(10.95.80.4)--SSL Disabled Login failed for user 'sgvaultuser'.

****END Cut and paste of sgvault.log *****

mskrobul · Post by **mskrobul** » Tue Mar 14, 2006 9:37 am

Vault is trying to connect to the database using SQL authentication with the sgvaultuser name and password and can't for some reason.

Most likely a different SQL authentication type was chosen during the upgrade process.

The simplest way to resolve this would be to un-install Vault (make sure to KEEP your database when prompted), then re-install. Of course we always recommend making a backup of your database before you un-install or upgrade Vault just to be extra safe.

When you re-install, you should be able to choose either Windows Authentication or SQL Authentication in the Connect to Database dialog during the install process (on upgrades, the same connection mode should be chosen as the original install, on fresh installs it doesn't matter). If you choose to connect using SQL authentication, make sure you use a SQL user login who has dbowner permissions to the Master database, like the SA user. Note this login will ONLY be used during the install process - a dbowner login must be used so the installer can run all the necessary sql scripts to upgrade the database.

PaulMargetts · Post by **PaulMargetts** » Wed Mar 15, 2006 8:47 am

I did an un-install and then a re-install as you suggested, chosing the option "custom - web config identity impersonation" (supplying the same login credentials I used for the re-install) and I am now able to connect using the admin tool and the client (provided the user does not have "Active Directory Authentication" enabled). However, users constrained to "Active Directory Authentication" get the message "invalid username or password". How can I find out what is going wrong (remembering that Active Directory Authentication was working before I did the upgrade)? Should I have taken the opportunity of creating a new identity (an option during the fresh install process) rather than using my credetials (if so, why and what are the thing to bear in mind in creating the new identity)?

FYI: the message in the sgvault.log file is:

Active Directory authorization for user pmargett failed.
Logon failure: unknown user name or bad password
----3/15/2006 4:09:15 AM pmargett--is5400035e.europe.pc.cognex.com(10.95.80.4)--SSL Disabled Login failed: FailInvalidPassword

lbauer · Post by **lbauer** » Wed Mar 15, 2006 9:05 am

Did you configure the Active Directory Domain in the Vault Admin Tool->Server options?

PaulMargetts · Post by **PaulMargetts** » Fri Mar 17, 2006 4:53 am

lbauer wrote:Did you configure the Active Directory Domain in the Vault Admin Tool->Server options?

Once I fixed this (and rebooted), everything worked just fine.

During this whole process (my first interaction with SourceGear), I learnt 3 things which I will pass on.

Firstly, Vault does NOT seem to remember the previous settings when upgrading. This means that you HAVE to know how the system was previously set up; you can't rely on the default values working for you even though you are upgrading. It would be nice if Vault had an option to "upgrade using previous settings".

Secondly, the support instructions ask for the "sgvault.log" file, but if you naively try to "Add an Attachment" it doesn't work and gives no indication that it hasn't worked. Suprisingly, ".log" is not one of the permitted attachment extensions! I bet I am not the first person to fall into this trap.

Thirdly, I was pleased to find that the support was "on the money" and pointed out what it was I was missing - thanks.