The request failed or the service did not respond

Question

I have the following error while I connect to SQL Server 2008 Management Studio with Windows authentication.

"The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details."

Is anybody tell me why i am getting this error, whereas my SQL Server is running under network service built in a/c????

I googled it but not getting solution..

Thanks

Answer 1

I had a similar issue. The next solution is in *case to can't launch the server Locally * and you will see the same error msg.(Image 1)

Imagen 1

Imagen 2

To solve that and have the server working you must have the next steps.

1. Go to SQL Server Services
2. Right click to open properties
3. Go to LogOn tab (By default you will see something like Image 3)
4. Select the radio button Built-in account (Image 4)
5. Click on Ok
6. Go back to SQL Server Services and launch again the server (Image 5) After that you must be able to see run it.

Image 3

Image 4

Image 5

I hope that works for you or others with similar issues. Follow me for more tips.

Answer 2

If you recently changed the password associated with the service account:

1. Start SQL Server Configuration Manager.
2. Select SQL Server Services in the left pane.
3. Right click the service you are trying to start in the right pane and click Properties.
4. Enter the new Password and Confirm password.

Answer 3

In my case, the issue was that I was running two other SQL Server instances which were (or at least one of them was) causing a conflict.

The solution was simply to stop the other SQL Server instance and its accompanying SQL Server Agent.

While I'm at it, I'll also recommend making sure Named Pipes is enabled in your server's protocol settings

Answer 4

I think this solution is more appropriate, because it does not prevent you from using TCP/IP access.

To open a port in the Windows firewall for TCP access

On the Start menu, click Run, type WF.msc, and then click OK.

In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.

In the Rule Type dialog box, select Port, and then click Next.

In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port number of the instance of the Database Engine, such as 1433 for the default instance. Click Next.

In the Action dialog box, select Allow the connection, and then click Next.

In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.

In the Name dialog box, type a name and description for this rule, and then click Finish.

(Source: https://msdn.microsoft.com/en-us/library/ms175043.aspx)

Answer 5

Had the same problem, I fixed it.

1. Open SQL Server Configuration manager
2. Click on the SQL Server Services (on the left)
3. Double-click on the SQL Server Instance that I wanted to start
4. Select the Built-in account radio button in the Log On tab and choose Local system from the dropdown menu
5. Click apply at the bottom, then right click the instance and select Start

Answer 6

Just disable the VIA protocol in sql server configuration manager