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 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

I installed new instance of sql & temp works for me. But I'll comment the error in near future as soon as I access that pc. — Vikas, Oct 24 '09 at 13:25
I was getting `An attempt was made to access a socket in a way forbidden by its access permissions [0x8007271d]`. It was a slightly unrelated issue but I narrowed it down to something that Docker was doing to interfere with the server startup (though I am unsure what exactly). Fixed it with `net stop hns && net start hns`. — Reece, Jan 28 '22 at 01:20

score 118 · Answer 1 · edited Oct 07 '16 at 17:42

118

Had the same problem, I fixed it.

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

edited Oct 07 '16 at 17:42

Josh Gribbon

75
1
15

answered Sep 19 '12 at 22:25

Raydelto Hernandez

2,200
2
16
11

After using these methods (in this page), I restart my computer, then it works. – moksef Apr 03 '16 at 14:36
3

Omg, that's a stupid mistake. I changed my windows password and then it stopped working (but I didn't notice right away). Your answer helped me figure that out, I just needed to change the password for my `Built-in account`. – Verena Haunschmid Jun 08 '17 at 07:52
This worked. As above, a recent AD password change had caused the service to stop – SE1986 Mar 22 '18 at 11:31
worked. if your website is still giving an error go to IIS select your website under sites then click stop and start from right section. that's what i did for my dnndev.me website. – Nakres Jun 23 '18 at 14:10
3

I'm getting `WMI Provider Error. The file exists. [0x80070050]]` – rayray Aug 29 '18 at 14:13
1

Fixed it for me. I was able to start the service, but I had to run SQL Config Manager "As Admin". Without running as admin, I got an error: "The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details". – SherlockSpreadsheets Jan 25 '19 at 17:59
Worked for an instance in SQL Server 2017, Cheers! – Santiago Rebella Apr 24 '20 at 15:10
Life saver... Thanks! – Yahya Jun 15 '23 at 13:58

score 28 · Accepted Answer · edited Jul 28 '14 at 19:41

28

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

edited Jul 28 '14 at 19:41

Shashank Shekhar

3,958
2
40
52

answered Mar 31 '11 at 07:11

Abhisek

320
4
3

37

I do not see a "VIA" protocol option (SQL server 2014). – emcor Feb 06 '15 at 21:30
2

"VIA" Protocol is also not available in SQL Server 2012, Unclear Answer. – Muhammad Abbas Jan 15 '20 at 12:31

RGR · Answer 3 · 2018-07-31T12:33:06.117

22

This really works - i had verified lot of sites and finally got the answer.

This may occurs when the master.mdf or the mastlog.ldf gets corrupt . In order to solve the issue goto the following path.

C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL , there you will find a folder ” Template Data ” , copy the master.mdf and mastlog.ldf and replace it in

C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA folder .

That's it. Now start the MS SQL service and you are done.

edited Jul 31 '18 at 12:33

answered Jan 16 '14 at 06:36

RGR

1,521
2
22
36

There are master.mdf and mastlog.ldf. these two files. Then, what I need to do ? my friend – moni123 Apr 06 '17 at 11:52
1

best solution. tnx – hamid May 11 '17 at 08:30
5

I don't have a `Template Data` directory :( – rayray Aug 29 '18 at 14:14
I don't have to. – saeid aslami Dec 06 '19 at 11:50

score 4 · Answer 4 · answered Sep 14 '15 at 23:53

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

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

score 4 · Answer 5 · answered Sep 22 '11 at 06:33

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.

score 3 · Answer 6 · answered Nov 14 '16 at 01:25

After chasing this issue for some hours, we found an log in the SQL Server Agent logs stating the following:

This installation of SQL Server Agent is disabled. The edition of SQL server that installed this service does not support SQL server agent.

We were using SQL Server Express. After some Googling it appears SQL Server Express does not support SQL Server Agent.

I didn't find a direct piece of Microsoft communications stating that SQL Express doesn't support SQL Server Agent, however this sentiment seems to be echoed across many forums.

thank you, here is the link: https://learn.microsoft.com/en-us/troubleshoot/sql/admin/schedule-automate-backup-database — Hassan Alhaj, Sep 04 '21 at 15:01

score 3 · Answer 7 · edited Apr 02 '15 at 14:04

It was very tedious when I get same problem. When I got this problem, I uninstall my SQL Server 2008 but after installing the SQL Server 2008 again,I got the same problem. I was so tensed plus, I had not gotten any help from any site.

To over come this problem. Simply You Need to go on SQL Server Configuration Manager and then click On Protocols on left panel. If you running Network service just disable 'VIA' Protocol. And after that try to start your SQL service it will run successfully.

score 2 · Answer 8 · answered Aug 29 '18 at 14:44

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

score 2 · Answer 9 · answered Jan 31 '20 at 15:50

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.

Go to SQL Server Services
Right click to open properties
Go to LogOn tab (By default you will see something like Image 3)
Select the radio button Built-in account (Image 4)
Click on Ok
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.

score 1 · Answer 10 · answered May 14 '14 at 12:39

1

Just disable the VIA protocol in sql server configuration manager

answered May 14 '14 at 12:39

tfa

1,643
16
18

score 1 · Answer 11 · answered May 23 '19 at 04:50

1

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

answered May 23 '19 at 04:50

MAFAIZ

681
6
13

it was my case in this issue – dlopezgonzalez Jan 28 '21 at 12:00

score 1 · Answer 12 · answered Jun 25 '19 at 10:13

1

For me a simple windows update fixed it, I wish I tried it before.

answered Jun 25 '19 at 10:13

musicinmusic

247
1
11

score 1 · Answer 13 · answered Nov 07 '20 at 04:33

I have SQL 2017 installed and this issue happens when the free trial / evaluation period ends, the solution to the problem is the following:

1 - Go to the windows start button, find the Microsoft SQL Server 20XX folder

2- Then, SQL Server 20XX Installation Center

3- On the left, select the option "Maintenance"

4- Then click on “Edition upgrade”

5- Then in the combox select "developer" option, and then click on “next” button

6- Click on the option "I accept the license terms" and then next

7- Finally, click on "Next" and click on "Upgrade", and wait approximately 15 minutes.

8- After this, restart the SQL Server service in "Services.msc" and open SQL again, it should work. For more information: watch this video: https://www.youtube.com/watch?v=EVG35ahhjec

score 0 · Answer 14 · answered Aug 11 '15 at 08:13

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)

score 0 · Answer 15 · answered Jun 21 '21 at 11:40

0

If you are still scrolling through the answers, here is one more step you might have missed.

Open SQL server configuration manager with admin access.

Apply the changes first(to local System) and then try to run.

answered Jun 21 '21 at 11:40

Bhawna Jain

709
10
27

Willy David Jr · Answer 16 · 2021-10-10T02:50:52.797

If you are configuring your SQL Server connection using Computer Management under Administrative Tools or SQL Server Configuration Manager in Enterprise or Corporate environment, make sure you open your Computer Management or SQL Server Configuration Manager as an Administrator or you have

Administrative Privileges

All answers above didn't work for me, but when I run it as Administrative mode, I can now start my SQL Server Agent or SQL Server service.

score 0 · Answer 17 · answered Nov 24 '21 at 21:12

For me happened similar issue when I did uninstall Microsoft Visual C++ 2015-2020 Redistributable and installed the Microsoft Visual C++ 2017 version

Fixed this issue when re-installed Microsoft Visual C++ 2015-2020 Redistrubutable versions. then services started automatically.

score 0 · Answer 18 · answered May 23 '22 at 15:47

Try changing login from different account:

Open SQL Server Configuration Manager as Admin.
Right click SQL sever and SQL Server Integration Services.
Go to Properties and choose Log on.
Choose Built in account.
Select local service.
Apply and Ok.
Start service again.

score 0 · Answer 19 · answered Nov 17 '22 at 05:55

This is beacuse your both SQL Servers are using same TCP Port Number i.e. 1433 and only one server could run at this port at a time. You have to change or Remove Port number from below settings;

In SQL Server Configuration Manager Click on SQL Server Network Configration.

Click on required Protocols for SQL...

Double click on TCP/IP then select IP Address tab.

Scroldown to end double click in TCP Port Textbox.

Change Port number from 1433 to other one or remove it.

After save these settings now Start your required server.

Good Luck

score 0 · Answer 20 · answered Mar 09 '23 at 05:18

0

Also check you have Express edition or developer edition cause Express edition don't allow

answered Mar 09 '23 at 05:18

rhl mngl

53
1
9

score -1 · Answer 21 · answered Jan 07 '19 at 06:27

https://social.technet.microsoft.com/wiki/contents/articles/52394.sql-server-troubleshooting-logon-failure-the-user-has-not-been-granted-the-requested-logon-type-at-this-computer.aspx

event viewer shows Logon failure - the user has not been granted the requested logon type at this computer

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

21 Answers21

Linked

Related