Could not load connect string

[Trolle]

Hi,

After a server move we get the folowing error when i try to log in to the vault admin.

--From Log file:
----11-02-2009 12:56:44 --()-- Could not load connect string. There is probably an error with the encrypted password for the sgvaultuser database user. Contact technical support at http://support.sourcegear.com
----11-02-2009 12:56:44 --()-- Vault Failed to establish a connection to the database.
----11-02-2009 12:56:44 --()-- Could not load connect string. There is probably an error with the encrypted password for the sgvaultuser database user. Contact technical support at http://support.sourcegear.com
----11-02-2009 12:56:44 --()-- Vault Failed to establish a connection to the database.
----11-02-2009 12:56:44 --()-- Could not load connect string. There is probably an error with the encrypted password for the sgvaultuser database user. Contact technical support at http://support.sourcegear.com
----11-02-2009 12:56:44 --()-- Vault Failed to establish a connection to the database.
----11-02-2009 12:56:44 --()-- 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
----11-02-2009 12:56:45 --WEB2(127.0.0.1)--SSL Disabled Could not load connect string. There is probably an error with the encrypted password for the sgvaultuser database user. Contact technical support at http://support.sourcegear.com
----11-02-2009 12:56:45 --WEB2(127.0.0.1)--SSL Disabled Vault Failed to establish a connection to the database.
----11-02-2009 12:56:45 admin--WEB2(127.0.0.1)--SSL Disabled Could not load connect string. There is probably an error with the encrypted password for the sgvaultuser database user. Contact technical support at http://support.sourcegear.com
----11-02-2009 12:56:45 admin--WEB2(127.0.0.1)--SSL Disabled Vault Failed to establish a connection to the database.

Some info about our system:
We run Vault on one server on port 8080 because port 80 is used by another web service. Its on Windows server 2008 using IIS 7. The SQL server is on another machine, on port 1431. Also on Windows server 2008 using Microsoft SQL Server 2008.

I have tried all i could think of, including all i could find here on the forum. I have tried keeping the original tables on the sql server, and installing vault, tried deleting the user and making it again, i have even tried backing up the databases and installing Vault as a new install. Nothing i do works.

Hope for help soon, Thanks.

M. Trolle

[Beth]

The easiest way to deal with this error is to:
1) Uninstall Vault, but choose the option to keep your database,
2) In your SQL Server Management Studio (or SQL Enterprise Manager), remove the sgvaultuser schema from the sgvault and sgmaster databases.
3) Remove the sgvaultuser user from the sgvault and sgmaster databases.
4) Remove the sgvaultuser from the SQL security logins.
5) Install Vault, but choose the option to use the same database again. Vault will remake the user it needs.

If you are on a version of Vault prior to Vault 4.x, then there won't be a sgmaster database that you need to do anything with.
If you are not on SQL 2005, then you probably won't have a sgvaultuser schema.

If you know your way around SQL well, you could try recreating the sgvaultuser using our KB article on Moving the Vault database. You would still need to remove the sgvaultuser before doing that.

[Trolle]

Hi,

That did not work, I still get the exact same error after doing what you asked me.

I have tried using the sa user to log in, and that generetes the same error.

Please note we use Windows Server 2008 and SQL Server 2008 - all Clean installs.

M. Trolle

[Beth]

Is this a 64-bit server? If so, then you might be running up tagainst the issue described by mskrobul in this thread: Login Failed with 4.1 and 64bit 2003 server - FailDBConn.

[Trolle]

Hi,

Yes its all 64bit servers, and I have tried mskrobul's solution, still same error.

I cannot login with Windows Authentication, same as jlehew.

M Trolle

[Beth]

Did you try the last portion that user had to do to get it working?

P.S. One other thing I had to do to get 64 bit working is to run aspnet_regiis -i for BOTH 32bit AND 64bit then go to inetmgr and enable both the 32bit and 64bit "Web Service Extensions".

If it still doesn't work after that, it might be best to send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread so that I can take a closer look.

[gabrielrdz]

Your first suggestion about uninstalling and keeping the current db, deleting login and schema, and reinstalling, worked perfectly Beth!

Thank you very much!!

Gabriel

[Beth]

Thanks for the update. I'm happy to hear you are working again.