Windows could not start the SQL Server MSSQLSERVER on Local Computer error code 3417

Question

For some reasons I moved this folder    Program Files Microsoft SQL Server MSSQL11 MSSQLSERVER MSSQL  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

User · Answer

Go to the services and check if the SQL Server  MSSQLSERVER  service is running stop it and start your SQL Server  SQLEXPRESS  service it should work  see the image

User · Answer

Very simple to solve this problem  Just open RUN window Window R  and type services msc  Services msc window Find the SQL within name column and right click on that  right click on SQL as in screenshot  You will get properties option  click on properties  One new window will be open and there you have to click on Log On tab  And select the Local System Account  then apply and okay  Select Local system Account  After that come again in services msc window  and right click on sql and click start  And finally  SQL Server services started successfully  enjoy and keep learning

User · Answer

I have had the same error recently  I have checked the folder Log of my Server instance    x  Program Files Microsoft SQL Server MSSQL11 MSSQLSERVER MSSQL Log    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 Files Microsoft SQL Server MSSQL11 MSSQLSERVER MSSQL DATA master 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 Files Microsoft SQL Server MSSQL11 MSSQLSERVER MSSQL DATA master mdf   Operating system error 5      5 Access is denied     Error  17204  Severity  16  State  1  FCB  Open failed  Could not open file E  Program Files Microsoft SQL Server MSSQL11 MSSQLSERVER MSSQL DATA mastlog 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 Files Microsoft SQL Server MSSQL11 MSSQLSERVER MSSQL DATA mastlog 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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

I encountered this issue after changing database location  And I solved it by moving system databases back to their default locations  Although I will recommend not to move system databases like master and model to some other location  But if you want then you can refer to this article  https   docs microsoft com en-us sql relational-databases databases move-system-databases view sql-server-2017

User · Answer

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

User · Answer

Re-entering credentials will help to start the services    Start   Services Right click on SQL Sever   Properties Log On Re-enter credentials and apply Start the services now

User · Answer

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 Files Microsoft SQL Server MSSQL11 MSSQLSERVER MSSQL  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  quot C Program Files Microsoft SQLServerMSSQL 1MSSqLData quot  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

User · Answer

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 Files Microsoft SQL Server MSSQL10 SQLEXPRESS 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 SQLEXPRESS MSSQL Data folder   Thats it   Now start the MS SQL service and you are done

User · Answer

Run this command after opening cmd as administrator  net start mssqlserver  T902   This command is called trace flag 902  It is used to bypass script upgrade mode  Every time when you try to start your sql service it also looks for script upgrades  and when the script upgrade fail your service unable to start  So  Whenever we have such upgrade script failure issue and SQL is not getting started  we need to use trace flag 902 to start SQL    I hope this will help you

User · Answer

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 Files Microsoft SQL Server MSSQL13 SQLEXPRESS MSSQL Log  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

User · Answer

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 Files Microsoft SQL Server 110 Setup Bootstrap SQLServer2012 gt 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  backup master 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

User · Answer

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

User · Answer

Database rebuild fixed it for me as well  Also had to restore the old database from backup as it got corrupted during power outage    The copy master mdf procedure did not work for me

User · Answer

What is System Event Log saying   Have you tried to repair  Sql Server Installation Center -  Maintenance -  Repair

User · Answer

Make sure both drive have the same partition -   like  FAT or  NTFS  preferably NTFS   also make sure he NETWORK SERVICE account  has the access

User · Answer

Check if you did compress the driver or folder in where you put the  mdf file   If so  plesae goto the driver or folder  change the compress option by      Properties -  Advanced and unticked the    Compress contents to save disk space    checkbox    After above things  you should be able to start the service again

[sql-server] Windows could not start the SQL Server (MSSQLSERVER) on Local Computer... (error code 3417)

Examples related to sql-server