HTTP 500 After Install When Trying to View VaultService.asmx

mserfass · Post by **mserfass** » Thu Apr 26, 2007 8:09 pm

I just installed Vault Server and cannot view any page except serverInstall.html. When I try to view VaultService.asmx I get HTTP 500 error.

I have tried uninstalling and reinstalling. I installed under the ASP.NET account. I tried installing under the machine account, but the install fails in that case. I made sure the ASP.NET account has full rights to Inetpub\wwwroot\VaultService and windir\Temp. Note that the install did not create a windir\temp\sgvault folder, nor did IIS. I manually added the sgvault folder. No log file was ever written there. VaultService is running asp.net version 2. I changed it to version 1.1, but got the same error. Security is set to anonymous access. I'm logged on as the machine admin. I'm not connected to a network. I get an http 500 when I try http://localhost/VaultService/VaultService.asmx.

The client and admin tools installed fine, but cannot connect to the service (due to the http 500 error).

I have successfully installed VaultService on two different desktops. I compared settings between the laptop and one of the desktops, and see no differences.

I am running Windows XP SP2, IIS 5.1, .NET 2.0, Vault 3.5.2, on a Dell Inspiron 9400 laptop. Norton internet security 2007 is installed. I already tried shutting Norton off but the error persists. My browser is IE 7.0, vault client 3.5.2, vault admin 3.5.2, VS 2005 SP1, .NET Framework 1.1 and 2.0.

Beth · Post by **Beth** » Fri Apr 27, 2007 8:18 am

What you are getting indicates a problem in your IIS settings.

Did you check out our KB articles on this issue?
http://support.sourcegear.com/viewtopic.php?t=736
http://support.sourcegear.com/viewtopic.php?t=202

If you installed IIS after .NET, then you definitely want to check out the second article.

mserfass · Post by **mserfass** » Fri Apr 27, 2007 9:28 am

I read those links before posting, but they didn't help. I read everything in the forum about this and similar problems before I posted, and have already run through all the possible solutions. Unfortunately, none of them resolved this.

I installed IIS before installing any SDK or Visual Studio. I ran aspnet_regiis -i anyway, but that didn't fix it.

I followed the steps in http://support.sourcegear.com/viewtopic.php?t=736 but only get to step 2. When I try to view VaultService.asmx I do not get the message "<%@ WebService Language="c#" Codebehind="VaultService.asmx.cs" Class="VaultService.VaultService" %>" The message I see is "This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying." I tried http://localhost/VaultService/VaultService.asmx and http://Trevor/VaultService/VaultService.asmx, and both give the same error.

I created a very simple ASP.NET application in VS2005. It runs fine when I F5 in VS 2005, but when I publish it locally it does not run. I get the same HTTP 500 error when I try to view it in IE that I get when trying to view the VaultService page. I tried a few aspnet_regiis parameters, but none of them fixed it.

I turned off friendly error messages in my IE settings, and reloaded the page. The error now reads "The server has encountered an error while loading an application during the processing of your request." In Event Viewer's System log, I have a W3SVC error that says "The server failed to load application '/LM/W3SVC'. The error was 'The specified metadata was not found'.

So the good news is that this is not a Vault problem, it's an IIS problem. The bad news is that this is an IIS problem. I will research a resolution and post it here for anyone else who runs into this.

Thanks for you help.

Beth · Post by **Beth** » Fri Apr 27, 2007 1:41 pm

When running the aspnet_regiis, don't do just the -i switch. That won't take care of it. You need to don an uninstall first. Run it once with the -u switch and then a second time with the -i switch. I'd still stand behind doing this. I'd even say uninstall both the 1.1 and 2.0 .NET frameworks if you have them and then perform a reinstall on both (leave 1.0 alone). If you don't have the 2.0 .NET framework, then don't bother with that and just uninstall and reinstall the 1.1 .NET framework.

mserfass · Post by **mserfass** » Fri Apr 27, 2007 2:34 pm

After much research, reconfiguring, restarting, and rebooting, it turns out that my IIS was completely hosed. I had to completely uninstall then reinstall IIS. Even that only put me back to where I started; IIS not rendering aspx or asmx pages and HTTP 500 errors. I had to manually install MSDTC and various IIS components. IIS finally ran properly after I finished recreating the IIS packages. Once IIS was functioning properly, Vault ran just fine. There was no one thing I can say was the fix, other than reworking IIS. I can say the problem was completely IIS.

This link helped me rework IIS: http://support.microsoft.com/?id=309051

I've never had this much difficulty with IIS. Would you guys at SourceGear consider making a Windows Services version that does not rely on IIS?

Beth · Post by **Beth** » Mon Apr 30, 2007 9:43 am

Thanks for the follow up post on what your IIS needed. On the request to not use IIS, I will put in a request for our developers to review. Thanks for the feedback.