How to: Restart a Service and Set it to Start Automatically
For Visual Studio Team System Team Foundation Server to function correctly, all required services must be running so that the application and data tiers can exchange information as designed, and services should be set to start automatically. In single-server deployments, each service must be running on the server that is running Team Foundation Server. In dual-server deployments, each service must be running on the appropriate server. In the following table, the display name of each required service precedes the service name in parentheses:
Services |
Location |
|---|---|
|
Must be running on the application-tier server. |
|
Must be running on the server where the database server for Team Foundation is deployed. |
|
Must be running on the server where SQL Server Reporting Services is deployed. |
|
Must be running on the server where SQL Server Analysis Services is deployed. |
|
Must be running on the server where SharePoint Products and Technologies is deployed. |
.gif "Note")
Note:
If you suspect that a required service is not running, you should first make sure that the most recent service pack for Visual Studio Team System Team Foundation Server has been installed and then verify whether each required service is running. If a required service is not running, you must restart it. If necessary, you should set it to start automatically. For more information, see the procedures later in this topic.
If you cannot restart a service, the password for the service account that manages that service might be incorrect or have expired. For more information, see the event logs. If a password for a service account has expired, you must change it by following these procedures:
For the TFSService account, see How to: Change the Service Account or Password for Team Foundation Server.
For the TFSReports account, see How to: Change the Service Account or Password for SQL Server Reporting Services.
An incorrectly configured service account or password is the most likely cause for a service to stop running, especially if other services that use the same account have not started either. For more information about which service accounts manage which services, see Managing and Resetting Service Accounts and Passwords.
.gif "Important note") Important Note: |
|---|
For optimal security, the TFSService account should not be an administrator on a computer that is running a component of Team Foundation. If you have deployed Team Foundation Server in an Active Directory domain, you should select the Account is sensitive and cannot be delegated check box for each service account. |
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 start a service that is stopped
Log on to the server on which the service is stopped.
Click Start, point to Administrative Tools, and click Services.
The Services Microsoft Management Console (MMC) opens.
Right-click the service that is not running, and click Start.
Close the Services console.
To configure a service for automatic startup
Log on to the server on which the service is installed.
Click Start, point to Administrative Tools, and then click Services.
The Services console opens.
Right-click the service that is not set to start automatically, and then click Properties.
For example, right-click SQL Server Agent (TFSINSTANCE), and then click Properties.
The SQL Server Agent (TFSINSTANCE)Properties window opens
On the General tab, click Automatic in the Startup type list, and then click OK.
Close the Services console.
See Also
Tasks
How to: Change the Service Account or Password for Team Foundation Server
How to: Change the Service Account or Password for SQL Server Reporting Services
Resolving Problems Connecting to the Data-tier Server
Concepts
Managing and Resetting Service Accounts and Passwords