This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Installing Vault for the night
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
I got the bright idea of installing the copy of Source Gear Vault that I had lying around. First I discovered that I did not have SQL Server 2000 installed on this Windows Server 2003 box. No problem, I have MSDN disks. Except that after struggling with multiple install attempts for over an hour, I realized that the damn MSDN DVD disk was corrupt! On to another disk I had and that was now installed. I then begun to install Vault which uses SQL Server. I had some problems but finally got installed. Thats when it got even worse. I could not log into the admin tool no matter if I used the machine name, local, or localhost. The weird thing is I could browse to the ASP.NET page that Vault uses for a main page but when I tried to browseto the ASMX page for Web Service I would get 404s even though the page was there! After struggling for hours with permissions and all sorts of things I finally realized I had a non 1.1 version of ASP.NET/Framework configured. Lets leave it as I have some post 1.1 version. Thats when I realized I had run into the infamous ASP.NET IIS Mapping issue. Running Aspnet_regiis.exe -i was not enough. Well, because that's not the actual problem, its this one. Heck with it. Using Denis Bauer's most excellent ASP.NET Version Switcher did the trick. This tool is so darn indispensible - put it your bin directory now! So 4 hours later, Vault installed. It had better be worth it-)
Previous Topic
