Login denied - on new installation

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
admjhn
Posts: 2
Joined: Mon Jun 18, 2007 4:09 am

Login denied - on new installation

Post by admjhn » Mon Jun 18, 2007 4:19 am

Hi,

Just installed v. 4.0.0.15759 on a Win2003R2 SP1 server with IIS6. The database is located on a different server. After successful installation I cannot login to the admin interface:

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

The server log has been attached. It tells me to contact you guys.....

Please advise
Regards,
Jesper Nielsen
Attachments
sgvault.log.txt
(15.84 KiB) Downloaded 155 times

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Mon Jun 18, 2007 6:41 am

Did you use a custom account (domain account) for the IIS Process model during installation, plus Windows authentication for the SQL Server setup portion?

Or did you use SQL Server authentication?

It might help to see a copy of the installation log. It's vault_install.log and is in your user's temp directory, %temp%.

Send a copy to support at sourcegear.com, ATTN Linda, with a link to this forum post.
Linda Bauer
SourceGear
Technical Support Manager

admjhn
Posts: 2
Joined: Mon Jun 18, 2007 4:09 am

Post by admjhn » Mon Jun 18, 2007 6:54 am

lbauer wrote:Did you use a custom account (domain account) for the IIS Process model during installation, plus Windows authentication for the SQL Server setup portion?
I used the default IIS account (Network Service) - not a custom account.
For SQL server I chose windows authentication (initially I tried with sql auth using SA but this failed during the db creation)
lbauer wrote: It might help to see a copy of the installation log.
Done.

Thx,

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Mon Jun 18, 2007 10:39 am

This user was using the default ASPNET account, Network Service, which didn't have access to SQL server on a different machine. He changed this to a custom domain account and the problem was resolved.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply