The SQL Server (MSSQLSERVER) service terminated with service-specific error 3414 (0xD56)

My SQL Server 2005 suddenly stop working by failing the services of sql server and sql agent to start. In event viewer, i am getting the following

For SQL Server Service
The SQL Server (MSSQLSERVER) service terminated with service-specific error 3414 (0xD56).

For SQL Agent Service
The SQL Server Agent (MSSQLSERVER) service depends on the SQL Server (MSSQLSERVER) service which failed to start because of the following error:
The service has returned a service-specific error code

Kindly Help me.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
please check the contents of the ERRORLOG file in the sql server installation folder /LOGS ...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
does the account specified to start the service have the permissions to do so?
has the account been locked out?
atifnaeemmalikAuthor Commented:
I have checked the folder /LOGS and model.ldf was curropt. replaced the file and started the service. all fine again.
thanks for help
out of interest, what was the msg in the log for this?
Greg RowlandSoftware Designer, SysDBA, WebMaster OwnerCommented:
Documented here, for the benefit of those that may encounter Error Event 3414 in the future.
In anticipation of potential hard drive failure, of a production mechanical hard drive that has been in continuous service for 5-6 years. It was decided to replace it with a Solid Stated Hard Drive.

On the bench we rebooted the existing drive to confirm that it was healthy before imaging it.

As luck would have it Windows 2003 Enterprise SP2, started up to an un-scheduled three stage Check Disk, which damaged some SQL system databases, preventing SQL 2005 from starting. Of course we have loads of backups; however, restoring backups is rather hard to do when SQL will not run.

Of course rebuilding the server is an option, although painful. In our environment we are also running SQL 2005 Report Services. Now if you have ever migrated or restored a SSRS server you know this is prohibitive and in some case un-reliable, with encryption keys and a litany of goofy MS constructs.

Now then, following “Guy Hengel [angelIII / a3]’s” comments in this EE thread, by interrogating the SSQL “ERRORLOG” file. By doing so, we were able to determine that “Model.mdf” was the damaged file. Knowing that unlike other system databases “Model.mdf” is not closely tied to the specific SQL install and having another healthy backup SQL Server install. We;
1)      Stopped the SQL service on the backup computer.
2)      Copied the “Model.mdf & Model.ldf” files to the damaged SQL computer.
3)      Rebooted the damaged SQL computer, and it WORKED!!!!
Saved my life and a ton of time.

Just thought it was worth writing up!

All the best,

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.