Unable to connect to server

Marcie · Post by **Marcie** » Tue Mar 30, 2004 11:03 am

Hi,
I've just installed Vault 2.0, but I'm not able to connect to the server (Windows 2003, IIS 6)

I get the error: Unable to connect to http://localhost/VaultService. No server was found at the specified URL. Web Exception: The request failed with HTTP status 404: Not Found.

I also get a 404 when browsing directly to http://localhost/VaultService/VaultWeb/login.aspx, though I can see that the file is there.

So, I'm wondering if I'm missing some kind of permissions issue or similar. Any suggestions welcome!

Thanks!
Marcie

Post by **jeremy_sg** » Tue Mar 30, 2004 11:36 am

Marcie,

Take a look at this KB article to see if it helps

http://support.sourcegear.com/viewtopic.php?t=510

Marcie · Post by **Marcie** » Tue Mar 30, 2004 11:47 am

Hi Jeremy,
I tried that, but still no luck. Any other suggestions?

Thanks!!
Marcie

Post by **jeremy_sg** » Tue Mar 30, 2004 1:19 pm

Are other sites on that server accessible? Can you see something when you go to http://localhost ?

Marcie · Post by **Marcie** » Tue Mar 30, 2004 1:25 pm

Other ASPX files work fine, and I've gotten past the 404 issue (I had that folder still pointing at ASP.NET 1.0, switching to 1.1 fixed that problem), so now I'm able to connect using the Admin Tool (the main goal here), but now I'm getting an ASP.NET error on the web interface,

Could not load type 'VaultService.VaultWeb._default'.

Source Error:

Line 1: <%@ Page language="c#" Codebehind="default.aspx.cs" AutoEventWireup="false" Inherits="VaultService.VaultWeb._default" %>
Line 2: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >
Line 3:

Source File: D:\Inetpub\wwwroot\VaultService\VaultWeb\Default.aspx Line: 1

Thanks!
Marcie

Post by **jeremy_sg** » Tue Mar 30, 2004 2:05 pm

It looks like IIS isn't handling ASPX files with .Net. I am betting that if you try to add or check in any files, you would get an error. My recommendation would be to uninstall the .Net Framework and the reinstall it. There is probably a way to manually restore the setting, but I don't know it off the top of my head.

Post by **jclausius** » Tue Mar 30, 2004 2:21 pm

marcie - a quick interruption...

this might be a red herring, but it is worth mentioning for windows 2003 server.

from the control panel
-> add / remove programs
-> add / remove windows components
-> find the application server component

are all the relevant application server components installed? if not, please install them. if they are already installed, please ignore this message.

Marcie · Post by **Marcie** » Tue Mar 30, 2004 2:47 pm

I got it sorted out now, thanks Jeff and Jeremy for your suggestions.

Marcie

Post by **jeremy_sg** » Tue Mar 30, 2004 3:11 pm

Marcie,

Would you mind telling what the solution was? I'm working on a troubleshooting guide for this error and would like to know if this is worth being put into it.

Marcie · Post by **Marcie** » Tue Mar 30, 2004 3:23 pm

In my case, the main problem was that I had the .NET Framework version 1.0 installed as well as 1.1, and so using Denis Bauer's Version Switcher tool solved that problem for me (after that, no more IIS 404s).

The second error I mentioned above I caused myself when trying to solve that first error-- I had marked VaultWeb as an application, and undoing that solved the second error

Thanks!
Marcie

SourceGear Support

Unable to connect to server

Unable to connect to server

No dic

Update

Fixed

Solution