Share via


A directory is not found

The information in this article applies to:

  • Visual Studio 2005 Team Foundation Server

  • Visual Studio Team System 2008 Team Foundation Server

  • Windows Server 2003 and Windows Server 2008 

  • SQL Server and SQL Server 2008

  • Application-tier server

  • Health check

The Best Practices Analyzer tool for Team Foundation Server verifies that the local path property of each Web site and virtual directory for Team Foundation Server is set to a directory that exists on the disk. An error appears if a directory is missing. This error typically occurs when a directory is deleted or moved. 

The behavior of each Web site differs if it is not configured with a valid directory. Usually, the Web site does not appear correctly or a standard HTTP code appears. The following codes appear most frequently as a result of this error:

  • 403   The Forbidden error indicates that the request was valid but the server cannot respond to it.

  • 404   The Not Found error indicates that the client can communicate with the server but the server could not locate a required resource to fill the request.

To resolve this issue, you should verify the existence of the corresponding directory for each Web site on the application-tier server. Then you should open Internet Information Services (IIS) Manager and verify or change the path assignment to the correct directory.

The following table lists the default path for each Web site:

Note

Default directory assignments might differ with different versions of Team Foundation Server , SQL Server, and the Windows operating system. For example, you manage ReportServer in IIS for SQL Server 2005 but not for SQL Server 2008. This table applies to Visual Studio 2005 Team Foundation Server and Visual Studio Team System 2008 Team Foundation Server. 

Web site

Default directory (Local path)

Default Web Site

..\Inetpub\wwwroot

   Reports (not applicable for SQL Server 2008 Reporting Services)

..\Program Files\Microsoft SQL Server\MSSQL.n\Reporting Services\ReportManager

Note

The number that is assigned to the MSSQL directory varies depending on the SQL Server instance.

   ReportServer (not applicable for SQL Server 2008 Reporting Services)

..\Program Files\Microsoft SQL Server\MSSQL.n\Reporting Services\ReportServer

Note

The number that is assigned to the MSSQL directory varies depending on the SQL Server instance.

Team Foundation Server

..\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services

..\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services

   Build

..\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Build

..\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Build

   Services

..\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Services

..\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services

   VersionControl

..\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControl

..\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\VersionControl

   Warehouse

..\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Warehouse

..\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Warehouse

   WorkItemTracking

..\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\WorkItemTracking

..\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\WorkItemTracking

SharePoint Central Administration (Windows SharePoint Services 2.0)

..\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\template\admin\1033

SharePoint Central Administration V3 (Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007)

\Inetpub\wwwroot\wss\VirtualDirectories\nnnnn

Required Permissions

To perform this procedure, you must be a member of the Administrators security group on the application-tier server for Team Foundation.

To verify or change the path assignment of a Web site or virtual directory in IIS 6.0

  1. Open the Start menu, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. In the tree pane, expand the local computer, and expand Web Sites.

  3. If necessary, expand the Web site that contains the virtual directory.

  4. Right-click the Web site (for example,Default Web Site) or virtual directory, and click Properties.

  5. On the Home Directory tab, verify that A directory located on this computer is clicked.

  6. In Local path, verify that the path matches the default path as listed in the table earlier in this topic. If the paths do not match, click Browse, and change the local path to the default path.

  7. Click Apply, and then click OK.

To verify or change the path assignment of a Web site or virtual directory in IIS 7.0

  1. Open the Start menu, point to Administrative Tools, right-click Internet Information Services (IIS) Manager, and then click Run as administrator.

  2. In the Connections pane, expand the local computer, and expand Sites.

  3. If necessary, expand the Web site that contains the virtual directory.

  4. Click the Web site or virtual directory.

  5. In the Actions area, click Basic Settings.

    The Edit Site or Edit Application dialog box appears.

  6. In Physical path, verify that the path matches the default path as listed in the table earlier in this topic. If the paths do not match, click the browse button (). In the Browse For Folder dialog box, click the local path that matches the default path, and then click OK.

  7. Click OK.

See Also

Tasks

An incorrect default document is detected

Other Resources

Web Service Configuration Issues