FailDBConn

Tim Richards · Post by **Tim Richards** » Tue Sep 06, 2005 10:56 am

Duplicate post, this time with attachment.

Vault seems to be a terrific product, but I am having trouble this time around simply connecting to the database.

I cannot connect to the server using MSDE2000a on a trial run of Vault. I used to be able to, on a previous Windows install. I am using MachineName/MachineName$ both times. To try and fix, I have done the following things but seem to be back at square one.

---- 1 ----

I am running XP SP2, VS .NET which includes MDAC 2.7. I verified that Windows Firewall allows HTTP requests to be received by this machine. In IE, http:\\codedell\vaultservice brings up the Vault home page. VaultService.asmx shows what operations are supported, so it doesn't just bring up the one-liner instruction to Vault. (This success is actually a new development that I didn't realize worked, but I don't know how it helps. I still get FailDBConn.)

----- 2 ----

I then tried running Vault Client. Error: FailDBConn 1101. Followed the instructions and submitted the query to enable impersonation, even though I think I am not using impersonation. I am using Windows authentication, and the sa account on MSDE, which responded: ``User or role 'CODEDELL\CODEDELL$' already exists in the current database. 'CODEDELL\CODEDELL$' added to role 'db_owner'.''

So then I stopped IIS, deleted ``C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys\edb...'' and restarted IIS. It didn't seem to have an effect.

---- 3 ----

Following that, I went to C:\Inetpub\wwwroot\VaultService\Web.config and changed the following two lines to include the machine name in place of (local). I am not aware that the first line is anything more than a comment. If it is a script command then the user ID and password are obviously incorrect, and that is where I am having the problem. But these values shouldn't be stored there anyway.


<add key="ConnectString" value="Application Name='SourceGear Vault Server'; Connection Reset='true'; Server=CodeDell; Database=sgvault; Integrated Security='true'" />

---- 4 ----

Finally, I went to C:\Program Files\SourceGear\Vault Client and changed the lines

<proxy usesystemdefault="true"/>


to


<proxy usesystemdefault="false" proxyaddress="http://proxyhost:proxyport" bypassonlocal="false"/>

and brought down Vault Client and brought it up again. FailDBConn persists. Mainly following the instruction on http://support.sourcegear.com/viewtopic.php?p=2450.

--- 5 ---

The user CodeDell/CodeDell$ is a member of Administrators.

Any suggestions? Attached is the log c:\windows\temp\sgvault\sgvault.log.

The extension .log is not allowed on your user forum for attachments. I am suffixing .txt.

lbauer · Post by **lbauer** » Tue Sep 06, 2005 11:25 am

The user CodeDell/CodeDell$ is a member of Administrators.

Even though you may have selected SYSTEM for the IIS process model, Vault is trying to use the ASPNET account, and this is what's failing:

Login failed for user 'CODEDELL\ASPNET'.

Is there a reason not to use this account? I'd suggest uninstalling Vault and re-installing, using CODEDELL\ASPNET for the IIS Process Model.

Tim Richards · Post by **Tim Richards** » Wed Sep 07, 2005 12:13 pm

Thanks for your feedback. I did a search through the forum for ``Server Application Unavailable'' but couldn't find it so I have to ask this question.

I now have Vault set up on the ASPNET account (which didn't used to work but now it seems to get farther than it did) but it doesn't see the server application. Navigating to http://codedell/VaultService/VaultService.asmx yields the following message:

Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

These notes I keep for myself shouldn't be too difficult to parse:

2:08p - I got a response and she suggested I use ASPNET so I delete CodeDell$.

2:28p - I found on the web the suggeston to run C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\aspnet_regiis.exe. Then I restarted IIS. Then I tried to log in to Vault again without first shutting it down. The error is different. Unable to connect. No server was found at the specified URL. Perhaps I could just switch it back to local.

3:#4p - I uninstalled and reinstalled Vault and I get the same error.

3:58p - Again I changed C:\Program Files\SourceGear\Vault Client\VaultGUIClient.exe.config (forgot to add that to the support request) and set it the way I told them. The log file doesn't list anything past 2:18p. So it isn't connecting to the Vault server at all. IIS is up and running.

4:14p - I had installed QueryExpress as well as MSDE Query, both from www.msde.biz, this morning. Even though I can't see SQL Server in the task bar, I can browse the sgvault database using MSDE Query. I shall restart.

9:10a - http://codedell/VaultService comes up, yet http://codedell/VaultService/VaultService.asmx does not.

9:19a - modified C:\Inetpub\wwwroot\VaultService\Web.config. The bottom couple lines. Changed (local) to CodeDell.

9:22a - I restarted the web server, still no effect.

9:49a - I uninstalled vault. THe uninstall removed c:\Inetpub\wwwroot\VaultService.

10:32a - C:\Documents and Settings\CODEDELL\ASPNET is back. I had deleted it. OK. So that's where the problem is. THere's a file in there I have to set up.

10:48a - I removed Vault and the database and I opened Query Express and found the database gone. Reinstalling Vault.

10:52a - Same problem. Unable to connect, html error.

lbauer · Post by **lbauer** » Wed Sep 07, 2005 1:00 pm

Would you email me your phone number so I can call you? Use the email link below or send it to linda at sourcegear.com

Tim Richards · Post by **Tim Richards** » Thu Sep 15, 2005 5:24 am

I did what I thought you suggested in your email: Uninstalled and reinstalled .NET 2.0. Still No go. So I removed .NET 2.0, 1.1 and its SP-1; Vault; and even IIS itself, and restarted. I removed Port 80 that I had added to the firewall, figuring that any firewall changes IIS would do itself. Kept HTTP service enabled for the NIC. Then I reinstalled the entirety of IIS, followed by .NET 1.1 with restarts in between, then Vault. I can log on to the web page and see the .asmx page. Still get FailDBConn. I went to machine.config and changed the IIS password from ``AutoGenerate'' to a known password and forced the changed to the ASPNET user account in Users and Groups. Restarted IIS. Still get FailDBConn.

At this point .NET 2.0 is not installed. SQL Server is up and running.

lbauer · Post by **lbauer** » Thu Sep 15, 2005 9:52 am

Reinstalling .NET probably fixed the .NET/IIS issues you had earlier. The FailDBConn error indicates a problem connecting to the database. Modifying the machine.config file probably won't help with a database connection problem.

From our phone conversation last week, you said your Vault Server is on Windows XP SP 2, which has IIS 5.

In IIS 5.0, look in %windir%\Microsoft.NET\Framework\v.YYY\Config\machine.config, for the "processModel" element. It should say:

<processModel
<snip>
userName="machine"
password="AutoGenerate"
<snip>

You said you modified your machine.config file. Unless you have a reason for some sort of special configuration, you shouldn't have to do this for Vault. Change the settings back to what is shown above.

Then reinstall Vault, using machine\ASPNET for the IIS process model and Windows authentication for the SQL Server setup.

If you still get errors, email me the vault_install.log file from your user's temp directory and the Vault server log file. Send them to Linda at SourceGear.com.

SourceGear Support

FailDBConn

FailDBConn

Server Application Unavailable

More of the same