404 error when visiting Admin page

[cknox]

I am working to move our Vault install from a Windows 2003 32 bit server with SQL Server express to a Windows 2003 R2 64 bit server with the database housed on a seperate full SQL server. I've gone through the install, and once I finished the install, when it opens IE to visit the Admin page, I get a 404 error. I recall being told that our previous install did this, but I'm not sure how it was fixed. My testing on a Windows server 2008 server didn't have this happen to it.

Any help would be greatly appreciated.

[Beth]

Can you try the following URLs in a browser on your Vault server and let me know what your results are?
http://localhost/vaultservice
http://<your server name>/vaultservice

If those two bring up the home page, then try:
http://localhost/vaultservice/vaultservice.asmx
http://<your server name>/vaultservice/vaultservice.asmx

[cknox]

I get the default The page cannot be found for the vaultservice.asmx. I get the correct page for VaultService.

I should mention that this is vault 4.1.4 (we're upgrading to 5.0 shortly as we're rolling out VS2010 and want the shelving feature anyways).

[Beth]

Can I have you go to your IIS Manager, click on Web Service Extensions and look to the right. Is ASPNET v2.0 set to allowed?

[cknox]

ASP.NET v2.0.50727 is Allowed. Everything else is Prohibited...

[Beth]

Let's try re-registering your framework. This may disconnect users, so you will want to only perform it at a convenient time.

Run the following:
C:\Windows\Microsoft.net\framework\v2.0.50727\aspnet_regiis -i

Then see if you can bring up the vaultservice.asmx page.

[cknox]

This might be progress...

I'm now getting a runtime error on the asp.net pages...


Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'Logon failure: unknown user name or bad password.


I have successfully logged into the SQL server with the domain account in question, and am able to query the DB with that user...

[cknox]

Now that I've been thinking about it, our SQL Server uses mixed mode authentication. How would I go about changing the Vault to use that instead of Windows Authentication?

[cknox]

I changed the web.config to turn impersonation off, and now I get the login screen, but when I try to login I get this error:

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

I'm not entirely sure what logs I should be looking at. There's nothing in SQL, and I can't see anything within the Windows Event Viewer.

[Beth]

Since you turned off impersonation, I'm not sure what account your install may be trying to use for connecting to the SQL server. What I'd suggest is one of the following:

1) Uninstall Vault, choose the option to keep the database, then reinstall and let it pick up the database again. After uninstalling, it might be good to check your SQL Server Management Studio and remove the user you were trying to have Vault run under before the install again. That will force Vault to remake the user. I've attached a document showing the two places where that user would need to be removed from, the database users and the SQL Server security. In my example, I was using Network Service, but in your case you'd remove the user you were trying to use in the impersonation. Don't make a user in SQL, because Vault will do that. You could also try using SQL authentication instead of Windows authentication on the reinstall, but you will want to login with a SQL admin account when prompted so that it has the rights to make new SQL users.

2) Return to impersonation, but make sure the user is set to db_owner of the sgvault and sgmaster databases. Or, set up the user again using the scripts in this KB article: http://support.sourcegear.com/viewtopic.php?t=924.

[cknox]

Since you turned off impersonation, I'm not sure what account your install may be trying to use for connecting to the SQL server.

I thought about that this weekend. I've gotten it working. What I did was go into IIS Management, and change the Identity of the App Pool.

[Beth]

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

[FthrJACK]

I had this same exact issue.

What i did to fix it was right click on the Admin folder in IIS Manager, and go to properties. There i noticed under the ASP .NET tab that there was no version number set.

Go to the root folder "VaultService" in IIS Manager, right click > properties. Check the ASP.NET tab there to see if there is a version number set for the website, if not - set it. If there is, check if it isnt set on some of the sites subfolders.

Hope this helps someone else who finds this thread

[Beth]

Thanks for the additional information.