SQL Server does not start with 17051 error

by Chris Hall/December 1, 2016

Tested with SQL Server 2008 and 2012.

SQL Server might not start from all variety of reasons including permission issues, master database not available or corrupted, service account issues, etc. In this article I will talk about diagnose of failed service start and how to fix %%17051 error.

Diagnostic SQL Server service failed to start
General information are being logged into Event log whereas additional information are being logged into Error Log located by default in DRIVE_LETTER:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
When SQL Server does not start which you would find out by simply looking into configuration manager

Then first place where you should start looking is the Event Log System category. Find an error generated by Service Control Manager.


Let’s take a look into the Error Log
Mind the row number 13 “SQL Server evaluation period has expired.” Now you have two options. Uninstall your evaluation copy of SQL Server or run Edition Upgrade – you will need to enter your Product Key during upgrade process.

Edition Upgrade
For Edition Upgrade you will need SQL Server setup files. In SQL Server Installation center navigate to Maintenance section and click Edition Upgrade.

Check whether all Setup Support Rules are marked as Passed and click OK.

Again check whether all Rules are marked as Passed or Not applicable and click Next.
In Product Key step change Radio Button to option Enter the product key and type in your key. If you are using a VLK SQL Server version a Product Key will be already entered at this point.

In next steps accept license terms, specify your instance you wish to upgrade, check edition upgrade rules and finally click Upgrade button.

I my case Upgrade and Back button had been gray for a few minutes. When the upgrade process is done you will see similar screen with link to Setup Boostrap Log.

Now you might need to start your SQL Server Services manually.

When you connect to your instance you may check your edition by running script bellow.



Note for SQL Server setup files
Your setup files does not need to be at same Service Pack level as your instance (no need for slipstreaming). Also you can Edition Upgrade from Standard to Enterprise, Developer and/or Business Intelligence and vice versa between all versions.

← Back to News

Want to say hey or find out more?

If you're part of a small/medium or enterprise level we
can help address your IT Management needs.

Get in touch
View our Services
Make your data
work for you.
Contact Us

+61 438 661 875


Copyright © DataCommand Pty Ltd / Privacy Policy
ABN 98 205 256 068 / ACN 131 977 323