The request failed or the service did not respond in a timely fashion?

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 resp         


        

Answer 1

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 2

I found from event logs that My SQL server evaluation has expired. I needed to upgrade or needed to use community edition.

Answer 3

Above mentioned issue happened in my local system. Check in sql server configuration manager.
Step 1:
SQL server Network configuration
step 2:

• Protocols for local server name
• Protocol name VIA Disabled or not..
• if not disabled , disable and check

.. after I made changes the sql server browser started working

Answer 4

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 5

If you are running SQL Server in a local environment and not over a TCP/IP connection. Go to Protocols under SQL Server Configuration Manager, Properties, and disable TCP/IP. Once this is done then the error message will go away when restarting the service.

Answer 6

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