Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
A Web service could not be called

A Web service could not be called

The information in this article applies to:

  • Visual Studio Team Foundation Server 2010

  • Windows Server 2003 and Windows Server 2008 

  • SQL Server 2008

  • Servers that host the application tier, SQL Server Reporting Services, and SharePoint Products

  • Team Foundation Server Complete Health Check

  • Team Foundation Server Framework Health Check

  • Team Foundation Server Warehouse Health Check

  • SharePoint Products Health Check

The Best Practices Analyzer tool for Team Foundation Server performs several Web service calls as part of its health check for a deployment of Team Foundation Server. The tool calls Web services that SQL Server Reporting Services, SharePoint Products, and Team Foundation Server provide. 

In this topic

If the Web service does not return the requested information, a corresponding error message appears:

  • ReportServer Web service experienced a call failure

  • Reporting Services Web request call failed

  • Team Foundation Server Integration Web service failed to retrieve a custom template

  • Team Foundation Server Team Project Collection Web service experienced a call failure

  • Team Foundation Server version control Web service experienced a call failure

  • Team Foundation Server Warehouse Control Web service experienced a call failure

  • Team Foundation Server Web service experienced a call failure

  • Team Foundation Server WorkItemTracking Web service experienced a call failure

  • Team Foundation Server {0} Web service could not be accessed

  • TeamFoundationIntegrationService Web service failed to retrieve Web application URL

  • Windows SharePoint Central Administration Web service experienced a call failure

For information about how to resolve these issues, see Troubleshoot Web Service Call Failures.

When a call to retrieve registered entries from a Web service fails, one of several errors could cause the problem. To resolve these errors, you can perform the following set of troubleshooting tasks.

Required Permissions

To perform these procedures, you must be a member of the Administrators security group on the data-tier or application-tier server for Team Foundation.

To troubleshoot Web service call failures

  1. Resolve all other errors that the scan reported.

  2. Examine the text of the error message. If it indicates an HTTP status code error, resolve the error.

  3. Verify that all SQL Server services are running.

    1. On the data-tier server, click Start, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager.

    2. Click SQL Server 2008 Services.

    3. Verify that each service appears next to a green arrow, which indicates that the service is running.

    4. If a service is stopped, right-click the service, and then click Start.

      For a list of services that must be running on the data-tier server, see A service is not running.

  4. On the application-tier server, verify that Web sites and virtual directories for Team Foundation are running under .NET Framework version 4.

    NoteNote

    Team Web Access runs under ASP.NET 2.0.

    For information about how to verify or change the ASP.NET version for a Web site or virtual directory, see An incorrect version of the .NET Framework is detected.

  5. Identify any login and SQL Server connection failures by restarting the Team Foundation Server Application Pool and noting any event errors that are logged in Event Viewer:

    1. To stop and restart an application pool, see An application pool is not configured correctly.

    2. Open Start, point to Administrative Tools, and then click Event Viewer.

      Event Viewer opens.

    3. Review the events logged to Application and System for any that are related to login and SQL Server connection failures. Resolve any errors that are logged in Event Viewer.

      For more information about how to correct login failures, see A service account is not configured correctly.

      For more information about how to work with service accounts, see the following topic on the Microsoft Web site: Managing and Resetting Service Accounts and Passwords.

  6. Reset Internet Information Services (IIS), and note event errors logged in Event Viewer:

    1. Open Start, click Run, type iisreset, and then click OK.

    2. Review the events logged in Event Viewer, and resolve any errors under Application or System.

  7. Verify that the Team Foundation Server Application Pool is running.

    For more information, see Verify That Application Pools are Running.

  8. Verify that the identity for the Team Foundation Server Application Pool is correctly set.

    For more information, see Verify that the Service Account for an Application Pool is Valid.

  9. Verify that URLs resolve.

    For more information, see Verify URL Resolution from the Local Server.

If the Web services that correspond to an application pool will not run, you should verify that the application pools are started. The following table shows which Web services correspond to which application pools:

Application pool

Web service

DefaultAppPool

Web sites for Team Foundation 

SharePoint Central Administration v3

SharePoint Services Central Administration Web site

Team Foundation Server Application Pool

Build, Configuration, Version Control, Data Warehouse, Work Item Tracking

Team Foundation Server Web Access Application Pool

Team Web Access services

To verify whether an application pool is running or to restart an application pool that has been stopped, see An application pool is not configured correctly.

If an application pool is not running, you might have a problem with the account that is set as the identity of the application pool. This problem is most often caused by an expired password.

During configuration of Team Foundation Server, the identities of the application pools for Team Foundation are all set to run under the same service account for Team Foundation Server. This service account is the only member of the account group for Team Foundation Server. Also, this account is added as a SQL Server login and given access to all the databases for Team Foundation. These databases include those that SharePoint Products uses. The identity that is set for the application pool is the account that accesses the databases.

In addition, a service account for SharePoint Products, WebAppService, may be assigned to the application pools that are configured for SharePoint Products.

For the service account of an application pool to be valid, the account that is assigned in Team Explorer must match the account that is assigned to the application pool identity. Also, the password for the account cannot be expired.

To verify or resolve a problem with the service account that is assigned to an application pool for Team Foundation Server

  1. To view services that Team Foundation Server uses, perform the following actions:

    1. On the application-tier server for Team Foundation, click Start, point to Administrative Tools, and then click Computer Management.

    2. In the navigation pane, expand Services and Applications, and then open Services.

    3. Click the Log On As column header to sort the services by the account under which they run.

      By default, all the services for Team Foundation Server run under the service account that you specified when you installed Team Foundation Server, referred to as TFSService. These services include the Team Foundation Server Web Services, the Visual Studio Team Foundation Background Job Agent service, and the Visual Studio Team Foundation Build service.

      NoteNote

      The Visual Studio Team Foundation Build service is installed only when a build computer is installed.

  2. Verify that the service account that is assigned to an application pool is valid and that its password has not expired.

    1. From the report generated by the health check, access the tree reports.

    2. Expand the following nodes:

      Team Foundation Server Complete Health Check

      Team Foundation Server

      Team Project Collections

      CollectionName

      Group Membership

      Project Collection Service Accounts

      Domain\ServiceAccount

    3. Expand Password Information for Domain\ServiceAccount.

    4. Verify that Expired is set to False. If it is set to True, reset the password for the service account.

      For more information, see the following topic on the Microsoft Web site: Change the Service Account or Password for Team Foundation Server.

  3. Determine the identity that is assigned to the application pools for Team Foundation Server by using Internet Information Services (IIS) Manager. For information about how to determine the identity, see An application pool is not configured correctly.

  4. If the service account that you determined in step 1 does not match the identity that is assigned to an application pool in step 3, correct the mismatch by resetting the password.

    For more information, see the following topic on the Microsoft Web site: Change the Service Account or Password for Team Foundation Server.

    NoteNote

    Before you reassign the new account, it must have the Log on as a service permission for the application-tier server set to Allow. For more information, see A service account is not configured correctly.

The default Web site on the server that hosts SharePoint Products is the home page for the team portal for Team Foundation.

NoteNote

To access Report Manager, reports, or Web sites for SQL Server Reporting Services on a computer that is running Windows Server 2008 or Windows Vista, you might need to add these sites to the list of trusted sites in Internet Explorer or start Internet Explorer as an administrator.

To verify that the localhost and computer name can be resolved

  1. On the server where SharePoint Products is installed, open Internet Explorer.

  2. Type http://localhost, and then press ENTER.

    The home page for team site should appear.

  3. Type http://ComputerName, and then press ENTER.

    The home page for team site should appear.

To verify that the URL for SharePoint Products is correct

  1. In Team Explorer, connect to the application-tier server.

  2. Expand a project, right-click the Documents node, and then click Properties.

  3. Copy the URL that appears, paste it into Internet Explorer, and verify that the URL resolves as you expect.

The tool logs the information that it gathers under the WebServices nodes in the tree report.

  • You can locate this node for each application-tier server by expanding Team Foundation Server Complete Health Check, expanding Team Foundation Server, expanding Team Foundation Server Application Tiers, expanding Team Foundation Server AT - NamedServer, and then expanding a named server.

  • You can locate this node for each team project collection by expanding Team Foundation Server Complete Health Check, expanding Team Foundation Server, expanding Team Foundation Server Applications Tiers, expanding Team Project Collections, and then expanding a named project collection.

  • You can locate this node for each server that hosts Reporting Services by expanding Team Foundation Server Complete Health Check, expanding Reporting Services, and then expanding the URL for a server.

  • You can locate this node for each server that hosts SharePoint Products by expanding Team Foundation Server Complete Health Check, expanding SharePoint Web Applications, and then expanding the URL for a server.

Community Additions

ADD
Show:
© 2015 Microsoft