Unable to start sql server service

Question

Unable to start sql server service

ramadesai108

SSChampion

Points: 10609
More actions
January 18, 2014 at 2:38 pm

#284646

Hello,
I searched on the internet for hours but cannot resolve my issue, so this is my last resort.
I have 2 instances of SQL Server 2012 on my local machine (Windows 7). One instance starts without any problem, but when I start the other instance from the Services, it starts and immediately it stops.
When I try to Connect to server using SSMS, I get the following error:
No Connection could be made because the target machine actively refused it
My event log shows the following error:
An error occurred during recovery, preventing the database 'model' (3:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Thanks for your help.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 1

ramadesai108 (1/18/2014)
Hello,
I searched on the internet for hours but cannot resolve my issue, so this is my last resort.
I have 2 instances of SQL Server 2012 on my local machine (Windows 7). One instance starts without any problem, but when I start the other instance from the Services, it starts and immediately it stops.
When I try to Connect to server using SSMS, I get the following error:
No Connection could be made because the target machine actively refused it
My event log shows the following error:
An error occurred during recovery, preventing the database 'model' (3:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Thanks for your help.

It sounds like your Model database files could be corrupt. Most people never make changes to the Model database so this might work. Rename the files for you Model database. Copy the Model files from another server (can only be done while the server is stopped) to the server that you're having problems with and then try restarting the service.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

phil.doensen Mr or Mrs. 500 Points: 501 More actions · Answer 2

Or rebuild the system databases and re-attach the database files.

http://technet.microsoft.com/en-us/library/dd207003.aspx

Perry Whittle SSC Guru Points: 234013 More actions · Answer 3

ramadesai108 (1/18/2014)
Hello,
I searched on the internet for hours but cannot resolve my issue, so this is my last resort.
I have 2 instances of SQL Server 2012 on my local machine (Windows 7). One instance starts without any problem, but when I start the other instance from the Services, it starts and immediately it stops.
When I try to Connect to server using SSMS, I get the following error:
No Connection could be made because the target machine actively refused it
My event log shows the following error:
An error occurred during recovery, preventing the database 'model' (3:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Thanks for your help.

is there any other information in the event log? Clear the Windows application log, then try restarting the service and check log again for further errors.

Jeff Moden (1/18/2014)
ramadesai108 (1/18/2014)
Hello,
I searched on the internet for hours but cannot resolve my issue, so this is my last resort.
I have 2 instances of SQL Server 2012 on my local machine (Windows 7). One instance starts without any problem, but when I start the other instance from the Services, it starts and immediately it stops.
When I try to Connect to server using SSMS, I get the following error:
No Connection could be made because the target machine actively refused it
My event log shows the following error:
An error occurred during recovery, preventing the database 'model' (3:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Thanks for your help.
Rename the files for you Model database. Copy the Model files from another server to the server that you're having problems with and then try restarting the service.

You must make sure that the collation matches on both systems otherwise the TempDB will have a different collation to master and that will cause issues.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

https://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/

Under the section on model. You'll need a backup of model, a copy of model from another identical server or to rebuild the system DBs.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass