SQL Server Stopped Running RRS feed

  • Question

  • Hello

    First post on this forum - not sure this is correct category.

    Having an issue with SQL Server - here are some details:

    Have Win 7 Pro SP1 64-bit SQL Server 2005.
    SQL Server was running fine up until about one week ago.
    Here is the error log:

    2019-05-24 12:46:24.58 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86) 
    Dec 10 2010 10:56:29 
    Copyright (c) 1988-2005 Microsoft Corporation
    Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)

    2019-05-24 12:46:24.58 Server (c) 2005 Microsoft Corporation.
    2019-05-24 12:46:24.58 Server All rights reserved.
    2019-05-24 12:46:24.58 Server Server process ID is 6268.
    2019-05-24 12:46:24.58 Server Authentication mode is MIXED.
    2019-05-24 12:46:24.58 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\EMMSDE\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2019-05-24 12:46:24.58 Server This instance of SQL Server last reported using a process ID of 2712 at 5/24/2019 12:41:51 PM (local) 5/24/2019 7:41:51 PM (UTC). This is an informational message only; no user action is required.
    2019-05-24 12:46:24.58 Server Registry startup parameters:
    2019-05-24 12:46:24.58 Server -d C:\Program Files (x86)\Microsoft SQL Server\EMMSDE\MSSQL.1\MSSQL\DATA\master.mdf
    2019-05-24 12:46:24.58 Server -e C:\Program Files (x86)\Microsoft SQL Server\EMMSDE\MSSQL.1\MSSQL\LOG\ERRORLOG
    2019-05-24 12:46:24.58 Server -l C:\Program Files (x86)\Microsoft SQL Server\EMMSDE\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2019-05-24 12:46:24.59 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2019-05-24 12:46:24.59 Server Detected 8 CPUs. This is an informational message; no user action is required.
    2019-05-24 12:46:24.90 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
    2019-05-24 12:46:24.96 Server Database mirroring has been enabled on this instance of SQL Server.
    2019-05-24 12:46:24.96 spid4s Starting up database 'master'.
    2019-05-24 12:46:25.02 spid4s Error: 9003, Severity: 20, State: 1.
    2019-05-24 12:46:25.02 spid4s The log scan number (879:408:1) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. 
    2019-05-24 12:46:25.02 spid4s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

    Any help is much appreciated as this is a critical service for us.
    Thanks in advance for your help!

    Saturday, May 25, 2019 4:31 PM

All replies

  • For starters, your version of sql server is very much obsolete and completely unsupported. If you care about this system, you should have a plan for migrating. 

    Next, your master database is corrupt. So do you have a backup? If not, you can try to rebuild the system databases (search the web - and this is one reason why you should be using current technology since it can be frustrating to find the exact steps you need for that version). 

    The last option is to find (i.e, buy) recovery software that might (but no guarantee) be able to fix the corruption. And just in case, I suggest you make copies of all the actual database files (mdf, ndf, ldf) used or present in your server instance before doing anything. 

    Sunday, May 26, 2019 2:31 PM
  • Thanks for your help Scott - not sure if I have a backup or not, rebuild looks complicated, may need to find a technician for assistance.  I will check back once I have more info - thanks again. 
    Sunday, May 26, 2019 9:01 PM
  • Hi guyinpasadena,

    SQL server the copy of master file default location is in C:\Program Files\Microsoft SQL Server\ MSSQL.n\MSSQL\Binn\Templates. Please refer to Use “Template” folder data files.

    You can also restore a backup of the master database on another instance of SQL Server as long as it's the same version of SQL Server, then use the restored files to replace the corrupt files on the broken system. Please refer to The Easiest Way To Rebuild The master Database.

    Best regards,
    Cathy Ji

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact

    Monday, May 27, 2019 3:42 AM
  • Hello again,

    Wondering if an update is causing failure of SQL Server.

    Here is a screenshot - please note Security Quality Rollup .NET Framework - could this be the culprit?

    Reason I am suspicious is b/c this is approximate timeframe we noticed SQL not working.

    Thanks in advance for your help!

    Monday, June 10, 2019 9:23 PM