Upgrade 2.0 --> 2.02 problem

leabre · Post by **leabre** » Sat May 01, 2004 12:55 am

Greetings,

I've been using version 2.0 for a while as a single user. I decided to upgade to 2.02 last night. When I did, I can no longer log in. It doesn't seem to find the database server. It says it failed to establish a connection to the database server yet, all my own softwre that I write has no problems connecting to the server and besides, I was connecting just find up until the minute I decided to upgrade (its the source control system I use in the stead of SourceSafe).

My client is WinXP Pro SP1 (all updates applied), server is Win2k Server SP3 (all updates applied), SQL 2k SP3.

The way I upgraded was simply by just installing 2.02. I didn't uninstall the old one but according to the way I read the instructions, that is ok.

Thanks,
Shawn

Post by **jeremy_sg** » Sat May 01, 2004 6:11 am

Does your vault server log give any hints as to the reason it can't find the db? The server log is in c:\windows\temp\sgvault.

leabre · Post by **leabre** » Sat May 01, 2004 2:47 pm

Here is the output:

Code: Select all

----4/29/2004 11:31:17 PM    sgvaultsystem--()--
	Vault Failed to establish a connection to the database.
----4/29/2004 11:31:17 PM    sgvaultsystem--()--
	Login failed for user 'sgvaultuser'.
----4/29/2004 11:31:17 PM    sgvaultsystem--()--
	The session information was not removed from the database.  Please check sgvault.dbo.tblsessions within SQL Server.  There may be orphaned sessions stored within the database. Error: FailDBConn
----4/29/2004 11:31:22 PM    --CHARITY(192.168.1.20)--SSL Disabled
	Vault Failed to establish a connection to the database.

The log is redundant in the manner above.

Thanks for the help,
Shawn

Post by **jeremy_sg** » Sat May 01, 2004 4:46 pm

Most likely, during the upgrade you entered a password for admin that was dfferent from you previous password, or you selected a different authentication scheme. Make sure that the sgvaultuser exists in your database, and that its password matches the vault admin password.
This SQL code is taken from http://support.sourcegear.com/viewtopic ... gvaultuser

Code: Select all

USE [master]
IF ( NOT EXISTS (SELECT sid FROM syslogins WHERE name = 'sgvaultuser') )
EXEC sp_addlogin N'sgvaultuser', N'VAULTS_ADMIN_PWD', N'sgvault'
GO

-- next access should be granted in the vault database
USE [sgvault]
EXEC sp_grantdbaccess N'sgvaultuser'
EXEC sp_addrolemember N'db_owner', N'sgvaultuser'
GO

These commands should configure your database properly.

leabre · Post by **leabre** » Sat May 01, 2004 8:37 pm

Okay, tried this and I get the same results. Is there a way to extract my history somewhere and then wipe the value database and start over again? I can't afford to lose my file history but if it is easier to back it up and restore it from a new database then I'll be happy.

Thanks,
Shawn

Post by **jeremy_sg** » Sat May 01, 2004 9:11 pm

You shouldn't need to restore anything. You're data is there, and it's fine, we just need to get SQL set up so that Vault can access it. Try logging in to your SQL server through Query Analyzer as the sgvaultuser. I'm assuming that you typed a different admin password during the upgrade install. Can you log in as sgvaultuser with the new password? Can you log in as sgvaultuser with the old password?

If all else fails, you can uninstall the server (choosing to keep the database), then reinstall using Windows Authentication for the SQL connection (choosing to keep the database). Windows Authentication doesn't have the problem of updating the password.

leabre · Post by **leabre** » Sun May 02, 2004 7:51 pm

Okay, I'll try uninstalling/reinstalling. When I originally installed, and upgraded, the admin has no password (I hate having to type them in everytime I do something) and I'm the only person at home who would ever log in, anyway.

Thanks,
Shawn