Не удалось запустить службу сервер на локальный компьютер ошибка

Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.

В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей.

For some reasons I moved this folder : (Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQL) to another drive, then returned it to the same location, but sql server has stopped working, showing this error when trying to start it again:

Windows could not start the SQL Server (MSSQLSERVER) on Local
Computer. For more information, review the System Event Log. If this
is a non-Microsoft service, contact the service vendor, and refer to
service-specific error code 3417.

I tried many solutions discussed in different forums, but none of them work for me.

The folder is not compressed or encrypted.

My sql server version is 2012:
Microsoft SQL Server Management Studio      11.0.3128.0
Microsoft Analysis Services Client Tools    11.0.3128.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML             3.0 4.0 6.0 
Microsoft Internet Explorer         9.0.8112.16421
Microsoft .NET Framework            4.0.30319.18047
Operating System                6.1.7601

Thanks for your kind help in advance.

In my particular case, I fixed this error by looking in the Event Viewer to get a clue as to the source of the issue:

I then followed the steps outlined at Rebuilding Master Database in SQL Server.

Note: Take some good backups first. After erasing the master database, you will have to attach to all of your existing databases again by browsing to the .mdf files.

In my particular case, the command to rebuild the master database was:

C:Program FilesMicrosoft SQL Server110Setup BootstrapSQLServer2012>setup /ACTION=rebuilddatabase /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=mike /sapwd=[insert password]

Note that this will reset SQL server to its defaults, so you will have to hope that you can restore the master database from E:backupmaster.bak. I couldn’t find this file, so attached the existing databases (by browsing to the existing .mdf files), and everything was back to normal.

After fixing everything, I created a maintenance plan to back up everything, including the master database, on a weekly basis.

In my particular case, this whole issue was caused by a Seagate hard drive getting bad sectors a couple of months after its 2-year warranty period expired. Most of the Seagate drives I have ever owned have ended up expiring either before or shortly after warranty — so I’m avoiding Seagate like the plague now!!

answered Sep 20, 2014 at 21:32

This usually occurs when the master.mdf or the mastlog.ldf gets corrupt . In order to solve the issue goto the following path C:Program FilesMicrosoft SQL ServerMSSQL10.SQLEXPRESSMSSQL , there you will find a folder ” Template Data ” , copy the master.mdf and mastlog.ldf and replace it in C:Program FilesMicrosoft SQL ServerMSSQL10.SQLEXPRESSMSSQLData folder . Thats it . Now start the MS SQL service and you are done

I have had the same error recently. I have checked the folder Log of my Server instance.

x:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLLog

and I have found this errors in logs

Starting up database 'master'.
Error: 17204, Severity: 16, State: 1.
FCB::Open failed: Could not open file
x:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAmaster.mdf for file number 1.  OS error: 5(Access is denied.).
Error: 5120, Severity: 16, State: 101.
Unable to open the physical file "E:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAmaster.mdf". Operating system error 5:    "5(Access is denied.)".
Error: 17204, Severity: 16, State: 1. FCB::Open failed: Could not open file E:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAmastlog.ldf for file number 2.  OS  error: 5(Access is denied.).
Error: 5120, Severity: 16, State: 101.  Unable to open the physical file "E:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAmastlog.ldf". Operating system error 5: "5(Access is denied.)".
SQL Server shutdown has been initiated

So for me it was an easy fix. I just added proper access rights to this files to the sql server service account.
I hope it will help

answered Mar 4, 2017 at 15:52

In My case I had to Upgrade the SQL Server since evaluation licence had been expired.

answered Apr 18, 2018 at 11:25

I was getting this error today. And above answers didn’t help me. I was getting this error when I try to start the SQL Server(SQLEXPRESS) service in Services(services.msc).

When I checked the error log at the location C:Program FilesMicrosoft SQL ServerMSSQL13.SQLEXPRESSMSSQLLog, there was an entry related TCP/IP port.

2018-06-19 20:41:52.20 spid12s TDSSNIClient initialization failed
with error 0x271d, status code 0xa. Reason: Unable to initialize the
TCP/IP listener. An attempt was made to access a socket in a way
forbidden by its access permissions.

Recently I was running a MSSQLEXPRESS image in my docker container, which was using the same TCP/IP port, that caused this issue.

So, what I did is, I just reset my TCP/IP by doing the below command.

netsh int ip reset resetlog.txt

Once the resetting is done, I had to restart the machine and when I try to start the SQLEXPRESS service again, it started successfully. Hope it helps.

answered Jun 19, 2018 at 15:55

answered Jun 24, 2013 at 10:47

answered Mar 13, 2015 at 5:48

i had the same problem before

the error code 3417 : the SQL SERVER cannot start the master database,
without master db SQL SERVER can’t start
MSSQLSERVER_3417

The master database records all the system-level information for a SQL Server system. This includes instance-wide metadata such as logon accounts, endpoints, linked servers, and system configuration settings. In SQL Server, system objects are no longer stored in the master database; instead, they are stored in the Resource database. Also, master is the database that records the existence of all other databases and the location of those database files and records the initialization information for SQL Server. Therefore, SQL Server cannot start if the master database is unavailable
MSDN Master DB
so you need to reconfigure all settings after restoring master db

solutions

• replace master mdf and ldf files with the same files from another instance of sql Server as long as its the same version reference
• Rebuild System Databases refrence
• reinstall sql server

answered Oct 5, 2015 at 17:53

I copied a master.mdf und mastlog.ldf from another Computer (luckily, we have a lot of Clients with the same configuration, otherwise template data would be perhaps necessary). I backed up the damaged master.mdf and mastlog.mdf. After that I replaced the bad ones with the ones from another Computer. And it worked. I needed to start the MSSQLSERVER Service of course. But, after that I had Problem that the user was already existing but orphaned (error code 15023), I executed the query

USE Database_name
EXEC sp_change_users_login ‘Auto_Fix’, ‘username’

after that, everything was working smoothly. Hope this helps you and many thanks for this thread, saved me

answered Oct 12, 2017 at 17:07

Just rename the current ErrorLog to any other name like Errorlog _Old and change any old Log file to Error log file

try to start the SQL server services.. That’s it. it will work..

Sql server error log file got corrupted. that is why it gives the problem even when you have all permissions.. when you delete it. new file will be generated.

answered Oct 30, 2017 at 6:32

Re-entering credentials will help to start the services:

1. Start > Services
2. Right click on SQL Sever > Properties
3. Log On
4. Re-enter credentials and apply
5. Start the services now

answered Jun 18, 2020 at 11:48

The reason behind getting this Error Code : 3417 may be as follows:

• One cause may be due to the Network account for the Data folder in
  Program files.
• The other reason may be because of some Windows
  settings changed somehow.

Example: If for some reasons you have moved this folder (Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQL) to another location then returned it to the same location. So, though it was returned to the same location the server may stop working and show error code 3417 when trying to start it again.

How To Fix SQL Error 3417

• Go to «C:Program Files Microsoft SQLServerMSSQL.1MSSqLData»
• Security/Permission settings
• Network Service Account
• Add a Network Service account
• Then again check all

As stated here, you can try this third party tool as well.

answered Oct 30, 2020 at 9:53

A few times now, I’ve experienced various instances MS SQL Server to fail with this error after a Windows update. Most of the quick fixes above did not work for me.

What did:

• copy all production databases over to some safe place
• remove everything SQL Server via add/remove programs
• get the latest SQL Server Express or Dev & install it
• move the databases over to their home and reattach them.

For me, this was the fastest solution. Trying to find the cause of the error and fixing it is an afternoon of googling misty error messages. But YMMV.

answered Jan 29, 2021 at 19:32

answered Jan 17, 2022 at 14:44