Export (0) Print
Expand All

Access is not available

Updated: August 2011

The information in this article applies to:

  • Visual Studio Team Foundation Server 2010

  • Servers in the deployment

  • Team Foundation Server Complete Health Check

  • Visual Studio Lab Management Health Check

  • Project Server Configuration Health Check

  • Project Server Synchronization Health Check

The Best Practices Analyzer tool for Team Foundation Server performs many queries that require access to information that is stored on the computers that the tool identified from the catalog for Team Foundation Server. For more information, see Unable to perform health check scan.

NoteNote

If the computer that you specified is not available or a functional area is not accessible, the report will not include information that is derived from rules that require access to the respective computers or areas are not included in the report.

In this topic

During the pre-scan check, the tool determines whether it can access the application-tier server and the database for Team Foundation Server. A message appears if the tool finds one of the following conditions to be true:

  • Cannot ping the specified Team Foundation Server

    To resolve this warning, verify that the network is operational and that you can ping the application-tier server from the computer from which you are running the scan. For more information, see Resolving Access Not Available Warnings later in this topic.

  • Cannot determine the IP address for a machine.

    To resolve this warning, verify that the network is operational, that you can ping the named server from the computer from which you are running the scan, and that a firewall is not blocking a connection. For more information, see Resolving Access Not Available Warnings later in this topic.

  • Cannot access SharePoint Server

    To resolve this warning, verify that the IIS Admin service is running on the named server. For more information, see A service is not running.

    Also, verify that the user who is running the scan has the necessary permissions to access the IIS metabase and to make calls to the Windows Management Instrumentation (WMI) for the named server. For more information, see Prerequisites for Using the Best Practices Analyzer Tool.

  • Cannot access SQL Server

    To resolve this error, verify that the data-source property in the web.config file for Team Foundation Server is valid and that the network is operational. Verify that you can ping the data-tier server from the computer from which you are running the scan. For more information, see A web.config file for the application-tier server is not configured correctly.

  • Cannot access the metabase for Project Server

    To resolve this error, verify that the network is operational. Verify that you can ping the machine that hosts Project Server from the machine from which you are running the scan.

During the pre-scan check, the tool determines whether the user who is running the scan has sufficient permissions to run each health check rule. The tool also determines which products have been installed and configured for integration within the deployment for Team Foundation Server. The tool displays the information that it collects as warning messages in the tree report under the Data Unavailable for Collection node. You can locate this node by expanding Scan Environment

Access Not Available

A warning message may appear if the tool finds one of the following conditions to be true:

  • Cannot access the Registry

    The report does not include results for rules that require access to the Registry for the named server.

  • Cannot access the IIS metabase of an application-tier server

    The report does not include results for rules that require access to the Internet Information Services (IIS) metabase for the named application-tier server. To correct this condition, see Enable Metabase Access on the Client Computer later in this topic.

  • Cannot access the IIS metabase for a SharePoint Web application

    The report does not include results for rules that require access to the IIS metabase for the named servers that host SharePoint Products. To correct this condition, see Enable Metabase Access on the Client Computer later in this topic.

  • Cannot determine the connection string for a team project collection

    The report does not include results for rules that require direct access to the database for the named team project collections.

  • Cannot access Windows Management Instrumentation (WMI)

    The report does not include results for rules that require access to WMI for the named servers.

  • The application tier was not scanned

    The report does not include results for rules that require access to the named application-tier server.

  • Unauthorized to call Team Foundation Server Web services

    The report does not include results for rules that require access to Web services that Team Foundation Server provides.

    To correct this condition, review the authentication configuration for Team Foundation Server. A setting of Basic authentication may cause this warning. You should enable Windows Authentication for Web sites on which Team Foundation Server relies. For more information, see Anonymous authentication is enabled.

To resolve any condition in the previous list, verify the permissions of the user who is running the scan. For more information, see Prerequisites for Using the Best Practices Analyzer Tool and Resolving Access Not Available Warnings later in this topic.

Lab Management Checks

A warning message may appear if the tool finds one of the following conditions to be true:

  • A problem occurred while accessing Team Foundation Server

  • A problem occurred while accessing the server for System Center Virtual Machine Manager (SCVMM)

  • A problem occurred while querying the Team Foundation Server

  • Cannot access Team Foundation Server

  • VMM access is not available on the host

  • Windows Management Instrumentation (WMI) access was intermittent on the host

  • Windows Management Instrumentation (WMI) access was intermittent on the library server

  • Windows Management Instrumentation (WMI) access was intermittent on the VMM server

  • WMI access was intermittent on the test controller

  • Virtual Machine Manager (VMM) Administrator Console is not installed on the client computer

    The report does not include results for rules that check the health of Lab Management.

    To correct this condition, you must run the scan from a computer where the Virtual Machine Manager (VMM) Administrator Console is installed. The tool cannot validate the configuration of Lab Management if the VMM Administrator Console is not installed on the client computer from which you run the scan.

To resolve any condition in the previous list, verify the permissions of the user who is running the scan. For more information, see Prerequisites for Using the Best Practices Analyzer Tool and Resolving Access Not Available Warnings later in this topic.

Products Not Installed or Not Configured for Integration

A warning message may appear if the tool finds one of the following conditions to be true:

  • SharePoint Products is not installed

    SharePoint Products is not installed or is not integrated with Team Foundation Server.

  • SQL Server Analysis Services is not installed

    Analysis Services is not installed or not configured for the deployment of Team Foundation Server.

  • Team Foundation Build is not configured

    The report does not include results for rules that require access to Team Foundation Build .

  • SQL Server Reporting Services is not installed

    Reporting Services is not installed or not configured for the deployment of Team Foundation Server.

If the tool cannot access the information that it requires to process specific rules, the results of that process do not appear in the scan reports.

If one of these errors appears, you should investigate the following causes first:

  • A network issue is preventing the tool from contacting the computer.

  • If the tool cannot access the catalog for Team Foundation Server, the tool cannot access the locations of the other components to scan. If this situation occurs, the tool cannot determine which servers to scan. As a result, the scan reports will be almost empty.

  • This error may indicate that either the Web site for Team Foundation Server is not running or that you have not configured the application-tier server for Team Foundation.

    For more information, see the following pages on the Microsoft website:

  • The account with which you logged on to run the tool does not have sufficient permissions to perform the query.

    You must have administrative credentials on the computer that you are scanning. Otherwise, the tool cannot call the Windows Management Instrumentation (WMI) providers, access the registry, or access the metabase for IIS.

    For more information, see Prerequisites for Using the Best Practices Analyzer Tool.

  • You are running the scan from a computer other than the one that the error indicates.

    When you run a scan from a Team Foundation client, some information is unavailable. When you troubleshoot issues that relate to the application-tier server, you must run the scan from that server.

    Also, in a dual-server deployment, you might have to explicitly set some WMI permissions before you can scan computers in a distributed environment.

  • One or more of the following services is not running on the computer that you specified for the scan:

    • Windows Management Instrumentation (required to access WMI)

    • Remote Registry (required to access the registry)

    • IIS Admin Service (required to access the IIS metabase)

To resolve an issue where access to information is unavailable, perform the following steps:

  • Verify that you can connect to the computer over the network. Ping the computer that the error specifies to determine whether the computer is available.

  • Review the Run Time Log report that the scan generates for the following messages:

    • General access denied error.   This error indicates that the account with which you logged on does not have the necessary administrative credentials on the computer that you are scanning. Log on using an account that has the necessary credentials, and run the scan again.

    • The RPC server is unavailable.   Verify that the Remote Registry service is running on the computer that you are scanning. If the service is not running, restart it. For more information, see A service is not running.

  • If you run the scan from a client that is running Windows Vista, enable metabase access. For more information, see Enable Metabase Access on the Client Computer.

  • Run the scan from the computer that the error specifies.

By default, metabase access is disabled for Windows Vista. To access metabase information, you must log on to the client computer, and access Windows Features.

Required Permissions

To perform these procedures, you must be a member of the Administrators security group on the client computer for Team Foundation.

To enable metabase access for a client that is running Windows Vista

  1. Click Start, and then click Control Panel.

  2. Click Programs.

  3. Under Programs and Features, click Turn Windows features on or off.

  4. In the Windows Features dialog box, expand Internet Information Services, and then expand Web Management Tools.

  5. Select the IIS Management Console check box, and click OK.

Date

History

Reason

August 2011

Added information about the warning for access to Project Server.

Information enhancement.

Community Additions

ADD
Show:
© 2014 Microsoft