Cannot connect to database

Jonathan Miller · Post by **Jonathan Miller** » Sun Aug 28, 2005 11:22 pm

Hello,

I just installed the 3.1.1 server and cannot connect to it lccally from the client. I'm running on Windows 2003 x64 with VS2005 beta2 and SQL Server 2005x64 april ctp. The install went perfectly without error, the database looks good. Any ideas here? I choose "network service" for authentication. Note, I only have 2.0 beta2 framework installed.

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

lbauer · Post by **lbauer** » Mon Aug 29, 2005 7:51 am

Is this an upgrade or a new installation? Did you make any changes to the Vault web.config file after installation?

We'd like to see your installation log from your user's temp directory and the Vault server log file Email them to linda at sourcegear.com.

Guest · Post by **Guest** » Mon Aug 29, 2005 12:02 pm

This is a new install. After receiving the error, I tried messing with my connection string and had no luck. Then I did repair install to fix the connection string (since I forgot to back it up before I changed it). The email is on the way.

lbauer · Post by **lbauer** » Wed Aug 31, 2005 2:33 pm

Vault couldn't decrypt the sgvaultuser password because the Cryptokey info in the registry was in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear\VaultServer
rather than the expected location:
HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Server

The 64-bit Windows OS uses the Wow6432Node key to present a separate view of HKEY_LOCAL_MACHINE\SOFTWARE for 32-bit applications that run on a 64-bit version of Windows. When a 32-bit application queries a value under the HKEY_LOCAL_MACHINE\SOFTWARE\<company>\<product> subkey, the application reads from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\<company>\<product> subkey. A "registry reflector" copies certain values between the 32-bit and 64-bit registry views (e.g., mainly for COM registration) and resolves any conflicts using a last-writer-wins approach.

Since we haven't tested Vault in this type of scenario, Vault won't be fully supported on 64-bit Windows until a later release.

superic · Post by **superic** » Sun Oct 29, 2006 5:19 pm

I am having the same issue with Windows 64bit, SQL Express 2005 and Source Gear 3.1.9. Has anyone found a solution yet?

Eric

Beth · Post by **Beth** » Mon Oct 30, 2006 1:57 pm

The state of 64-bit testing has not changed. I can add your vote to that feature.

superic · Post by **superic** » Mon Oct 30, 2006 5:16 pm

Add my vote. Thanks!