locked
the request failed with http status 404 RRS feed

  • Question

  • when I tried to open the team explorer I got the following error
    the request failed with http status 404
    Sad
    Wednesday, October 19, 2005 9:55 PM

Answers

  • I'd recommend moving to Beta 3.  Beta 2 is about a year old now and beta 3 has thousands and thousands of bug fixes and improvements.  If you still have problems with Beta3 we can help you diagnose them.

    Brian
    Thursday, November 10, 2005 2:47 PM
  • There are a number of things that can cause 404.  However, I need to ask a few questions and get some info from you.

    1. When creating a team project, what is the error from the log.
    2. What are you doing when getting a 404?  Are you browsing http://<apptier> or :8080">http://<apptier>:8080 or http://<apptier>:<sharepointport>?
    3. Since you are running WSS SP2, have you run the NTLM command found at http://blogs.msdn.com/robcaron/archive/2005/10/07/478336.aspx.

    Thursday, November 17, 2005 4:16 AM
  • Folks,

    Your problems are likely to be because you are creating a sharepoint virtual server for the Team Foundation Server site.  Please do not do this.   The only site that should be extended is the default web site.

    Please remove the virtual server from the Team Foundation Server site.  Then can you try connecting to the server again using Team Explorer or run Project Creation?

    I'd be interested to know why folks felt compelled to extend the TFS site?  What problems were you experiencing before that led you down this path?

    Thanks,

    Tuesday, January 3, 2006 5:53 PM

All replies

  • Could you provide more information?  Was this Beta 3?  A single or dual server install?  Did you follow the TFS Installation Guide?
    Wednesday, October 26, 2005 6:29 AM
  • Hi

    I get the same error, I am trying to deply a reporting serivces report from Visual Studio 2005 to the server.

    VS is beta 2 ctp.

    Thanks
    AMJ
    Wednesday, November 9, 2005 2:20 PM
  • I'd recommend moving to Beta 3.  Beta 2 is about a year old now and beta 3 has thousands and thousands of bug fixes and improvements.  If you still have problems with Beta3 we can help you diagnose them.

    Brian
    Thursday, November 10, 2005 2:47 PM
  • I began getting this problem after attempting resolve another.....

    My original problem was not being able to create a new team project....
     
    Cant remember exactly how I did this, but went into Sharepoint Sever and extended the Share point to my TFS VS and got this message...

    Virtual Server Successfully Extended

    After doing so I get the HHTP Status 404 error....

    Dual Install
    Beta 3 Refresh
    SPS SP2
    Wednesday, November 16, 2005 5:09 PM
  • There are a number of things that can cause 404.  However, I need to ask a few questions and get some info from you.

    1. When creating a team project, what is the error from the log.
    2. What are you doing when getting a 404?  Are you browsing http://<apptier> or :8080">http://<apptier>:8080 or http://<apptier>:<sharepointport>?
    3. Since you are running WSS SP2, have you run the NTLM command found at http://blogs.msdn.com/robcaron/archive/2005/10/07/478336.aspx.

    Thursday, November 17, 2005 4:16 AM
  • Were you able to get it working?  I assume that the failure actually is the NTLM issue in my first post.

    Friday, November 18, 2005 10:52 PM
  • 我按照http://blogs.msdn.com/robcaron/archive/2005/10/07/478336.aspx.中所说的步骤,执行了一下,可是还是再连接TFS的时候,还是弹出“the request failed with http status 404
    ”的对话框。

    Monday, November 21, 2005 3:25 AM
  • I also receive the same error ,after i execute by "http://blogs.msdn.com/robcaron/archive/2005/10/07/478336.aspx.".
    Monday, November 21, 2005 3:27 AM
  • What do you mean by same error?  Can you specify the setup?

    Single server or multi server?
    Can you hit http://<at>/Reports
    Can you hit http://<at>
    Can you hit http://localhost
    Is sharepoint extended on the default website

    What is the scenario/steps for getting the error.
    Tuesday, November 22, 2005 4:04 AM
  • Good morning:

    I am new to this forum, and stumbled across this problem.  It appears to be the same behavior that I am experiencing with my new installation of TFS.  I have been pulling my hair out...

    I am receiving the same error: "The request failed with HTTP status 404".

    I am receiving this error when I attempt to do anything that needs to connect to TFS through VS...(i.e. New Team Project, Team Explorer).

    I am prompted to provide the server, which I give, and this message appears rather quickly.  I have attempted the fixes provided above to no avail. 

    Please let me know if there is anything else I can look at.  I would be happy to proide more information, I am just unsure what information I should provide.

    Thank you in advance for your assistance!

    Thursday, December 8, 2005 3:41 PM
  • I'm having the same problem over here. Can't create a new TFS project because I get the error

    ---------------------------
    Microsoft Visual Studio
    ---------------------------
    The request failed with HTTP status 404: .
    ---------------------------
    OK  
    ---------------------------

    We attempted to completely uninstall TFS and WSS before installing the December refresh. We started with WSS SP2 (server farm), then created a new datastore for WSS, then installed TFS.. And that's how we got here.

    http://<server> loads WSS, as does http://<server>:8080, though there is nothing (404) at http://<server>(:8080)/sites...

    Monday, December 19, 2005 4:15 PM
  • I have the same error. At first when I was creating new projects I was receiving that connection terminated error. I am using beta 3. I have rextended sharepoint onto default and team foundation server. when I extended team foundation server it started giving me the 404 when I did any team related functions in Visual Studio. I checked sharepoints authentication and it was set to Kerberos for the default, so I changed it to NTLM. I do not know how to check the team foundation servers, but it may be set to Kerberos. Do i need to set it to NTLM as well. What can I do to rid myself of this 404?
    Sunday, January 1, 2006 1:45 AM
  • Folks,

    Your problems are likely to be because you are creating a sharepoint virtual server for the Team Foundation Server site.  Please do not do this.   The only site that should be extended is the default web site.

    Please remove the virtual server from the Team Foundation Server site.  Then can you try connecting to the server again using Team Explorer or run Project Creation?

    I'd be interested to know why folks felt compelled to extend the TFS site?  What problems were you experiencing before that led you down this path?

    Thanks,

    Tuesday, January 3, 2006 5:53 PM
  • I'm also getting this error. Using a clean install (single server) Beta3Refresh in a virtual machine. On the virtual machine I can open and use Team Explorer fine. Creating projects/opening their portal all works smooth. I installed Team explorer on a client WinXP SP2 machine (my actual dev box) and when I open Visual Studio and choose View -- Team Explorer, I get "The request failed with HTTP status 404: /Services/v1.0/ServerStatus.asmx"

    I never even get the chance to try to specify the TF Server. Any ideas n where I can look to get more info on why?
    Wednesday, January 4, 2006 4:11 PM
  • Speaking for myself, I tried it in attempt to solve the problem I'm getting creating team projects. Essentially at the end of the creation process I get the message below:

    Error
    Unable to connect to the Windows SharePoint Services at TFSRV 

    Explanation
    The Project Creation Wizard was not able to connect to the Windows SharePoint Services at TFSRV. The reason for the failed connection cannot be determined at this time. Because the connection failed, the wizard was not able to complete creating the Windows SharePoint Services site. 


    I've been trying all sorts of things to get past this point, but I'm getting nowhere

    Kev
    Monday, January 16, 2006 12:42 PM
  • I just removed the share point services from the team foundation server web site on the server, as suggested a few messages ago, but now whenever I try to create a new team project I get an error that html was received when xml was expected. The html in question is given below. Any suggestions as to what might be wrong now?

    Server Error in '/services' Application.

    Value cannot be null.
    Parameter name: absoluteUrl

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.ArgumentNullException: Value cannot be null.
    Parameter name: absoluteUrl

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [ArgumentNullException: Value cannot be null.Parameter name: absoluteUrl]   Microsoft.TeamFoundation.Server.ProxyUtilities.GetServerUrl(String absoluteUrl) +265   Microsoft.TeamFoundation.Proxy.BisRegistrationService.ExpandRelativeUrls(RegistrationEntry[] entries, String tfsServerUrl) +26   Microsoft.TeamFoundation.Server.Plugin.InitializePlugins() +97   Microsoft.TeamFoundation.Server.Global.EnsureInitialized() +1101   Microsoft.TeamFoundation.Server.Global.Application_BeginRequest(Object sender, EventArgs e) +22   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
    Monday, January 16, 2006 1:04 PM
  • hi Dan,

    1. The reason that I extended the virtual server is because I get a 403 permission denied on http://localhost:8080. Once removed you can access TFS by just going to http://localhost. - Access is denied if you try port 8080!

    2. Once removing the extend virtual server I get the same error as later in the post where you get HTML rather than XML. (http://localhost:8080/Services/v1.0/ServerStatus.asmx)

    Advice on this would be appreciated.

    Setup:

    Single-Server Mode Clean install (formatted the box)

    Cheers Paul

    Tuesday, January 24, 2006 4:12 AM
  • hi all,

    FYI: The web.config had it's name changed to web_<some date>.config but a new one was not written out during the install process...

    Just copied it and renamed it to web.config and we were up and running.

    Hopefully this might help someone else out there.

    Cheers Paul

    Tuesday, January 24, 2006 10:54 PM
  • Hi Dan,

    I am also getting the 404 and can confirm that we extended and mapped our TFS virtual server (VS) onto the default server.  I confess that we did this in hope of getting the server generated mail working for the alerts (the help file pointed to the central admin page).  After doing this the alerts worked but we can no longer access TFS to list projects etc.  We tried removing sharepoint serves from the TFS VS, we then removed and re-extended the Default VS.  As you can tell by now we were stabbing in the dark.

    Can you (or anyone else) advise on a procedure (as specific as possible) for restoring the VS's and TFS? Please...

    Many Thanks,

    Matthew

    Friday, February 24, 2006 9:22 AM
  • I'll give this a shot.  I installed TFS on a single server, after I installed Sharepoint Services. 

    After trying to create a new Team Project in Team Server addin for VS2005, I got a Sharepoint is actively refusing connections.  After looking at the Sharepoint Central Manager, I noticed the service was not extended.

    Hence, I extended it, figuring it required that in order to manage its content.  Then the 404 errors began.  After I removed the extension from WSS, I now get a nasty dialog when trying to connect to TFS.

    Adam

    Monday, June 26, 2006 9:44 PM
  • this occurs often on government web sites when the information would be embarrassing or reveal their incompetence
    Wednesday, July 12, 2006 8:49 PM