Share via

MS SQL SERVER 2008R2 NOT STARTING. ERROR 3414

Muhammad Alqama 1 Reputation point
2021-04-07T07:52:19.887+00:00

Dear experts.

I have ms sql 2008 r2 running. after power failure the system is not starting up.

windows service start gives error 3414.

sql server error log says

SPID10s ERROR: 9003, SEVERITY: 20, STATE 1.
SPID10S THE LOG SCAN NUMBER (78:96:1) PASSED TO LOG SCAN IN DATABASE 'MODEL' IS NOT VALID.

please can you help in this regard.
urgent help will be appreciated.

regards

SQL Server | Other

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator
    2021-04-07T21:32:41.45+00:00

    Looks like model is damaged. Assuming that you have not added something to model, you could take the files from another instance running SQL 2008 R2 (and not some other version). Rename the current files for model, and copy the files from the other instance.

    Hopefully your instances starts now, but run DBCC CHECKDB on all databases, as there may be more damages after the power failure.

    0 comments
  2. CathyJi-MSFT 22,396 Reputation points Microsoft External Staff
    2021-04-08T09:23:20.713+00:00

    Hi @Krishna Kamal Mandava ,

    > windows service start gives error 3414.

    This error can be caused by a transient condition that existed on the system during a given attempt to start up the server instance or to recover a database.

    For information about the cause of this occurrence of error 3414, examine the Windows Event Log or ERROR LOG for a previous error that indicates the specific failure. This helps the user to resolve the issues by applying the appropriate method.

    If the errors cannot be corrected, please using the replace the model files from another instance that has same version as Erland mention.

    Please refer to the blog SQL Server Error 3414: Windows could not start the SQL Server on Local Computer or MS document MSSQLSERVER_3414 to get more information.

    If the response is helpful, please click "Accept Answer" and upvote it, thank you.

    0 comments
  3. Krishna Kamal Mandava 96 Reputation points
    2021-04-09T15:24:29.847+00:00

    This was happening because we had symmetric Key Column level Encryption on the same table. We had multiple Symmetric keys, certs from previous testing. Once we removed all of those, the above issue disappeared. I am not sure what the old Symmetric keys had to do with the above issue as it was on another column on the same table but cleaning them up it resolved it.

  4. Stacy Clark 31 Reputation points
    2021-05-19T10:10:51.77+00:00
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.