[installation] FailDBConn when logging in after fresh instal

[forumtroll]

After installation of SourceGear Vault 6 Pro, we are attempting to log in to the admin panel to insert license and configure, but when attempting to log in the user admin, the following message is displayed:

Login Failed: The server could not establish a connection to the database. Please check the server's log for detailed information. (FailDBConn)

Our installation of sourcegear vault is installed into d:\SourceGear Vault, and we have created a website that runs from that directory with default settings prior to installation. AppPool was DefaultAppPool at the time of installation. After installation, the website appool is successfully set to the Vault app pool created during the installation.

We have configured the website in the installer to run as NT AUTHORITY\IUSR. Connecting to the database is done with Windows authentication. Tables are created successfully, and insepction of database permissions shows that the NT AUTHORITY\IUSR account has permissions to connect to all installed vault databases.

Can you guys help us out here?

[Beth]

Is the SQL Server on the same machine as the Vault server or is it on a different machine?

What version of SQL Server are you using?

[forumtroll]

The DB server is a physically separate server.

Server version is SQL Server 2008 (not sure if R2).

furthermore, I should have noted that this is Windows Server 2008 x64.

[Beth]

What you have going on is a local machine account trying to connect to a different machine. Those accounts don't have the ability to connect across machines.

Your options during install when the SQL Server is on a separate server are:
1) Use the Machine IIS Process model and then connect to the SQL Server using SQL authentication. You would login to SQL Server using a SQL admin account such as sa during the install. Vault won't use that admin account during its normal running, but during install it will use it to create its own SQL account with just the bare minimum rights it needs to run the databases.

2) Use the Custom IIS Process mode and enter in a Active Directory Domain account for Vault to run under. You can then connect to the SQL Server using either SQL authentication or Windows authentication. When using the Windows authentication, Vault will user your windows rights to add the domain user to the SQL Server and give it the rights it needs to run the Vault databases.

3) In some cases you can use the System IIS Process Model and then connect to the SQL Server using SQL authentication.

Uninstall Vault, but choose the option to keep the databases. Then install again, but go one of the three routes I listed.

[forumtroll]

I will get back to you tomorrow.

[forumtroll]

Running app pool as domain user worked perfectly. You may, however, want to add to the documentation if not already present, that the domain user should also be a member of the local IUSR (IIS7)/ASPNET (IIS 6) group on the web server for this to work.

Thank you very much for the help so far

[Beth]

Thank you for the update. I'm happy to hear you're working.