Не удалось запустить службу sql server код ошибки 17051

Sql server ошибка 17051

пятница, 22 февраля 2013 г.

Ошибка запуска MS SQL 17051

«Не удалось запустить службу SQL Server на SQLSERVER. Подробности содержатся в журнале системных событий. Если эта служба разработана не в Майкрософт, обратитесь к разработчику службы, и сообщите специфический для этой службы код ошибки 17051»

Связана с проблемой с ключем.

Для решения —
Пуск — Все программы — Microsoft SQL Server 2008 R2 — Средства настройки = Центр установки SQL Server (64-разрядная версия)

После запуска — выбираем слева «Обслуживание» и далее «Обновление выпуска» . Вводим имеющийся ключ.

General information are being logged into Event log whereas additional information are being logged into Error Log located by default in DRIVE_LETTER:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLLogERRORLOG

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.

Sometimes error codes are “G oogleable ” “Bingable” through the Error Log (path is mentioned above) messages are more verbose. 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.

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.

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.

Your setup files does not need to be at same Service Pack level as your instance (no need for slipstreaming). Tested by myself 🙂

SQL DBA – Windows could not start the SQL Server… refer to service-specific error code 17051 – SQL Server Evaluation period has expired

Ok, one fine day you opened SSMS (SQL Server Management Studio) and tried to connect to a SQL Instance, but it is not getting connected. You are getting following error message on a popup box:

–> You may also get following error:

—————————
Microsoft SQL Server Management Studio
—————————
Evaluation period has expired. For information on how to upgrade your evaluation software please go to http://www.microsoft.com/sql/howtobuy
—————————
OK
—————————

–> Investigate

Go to RUN and type services.msc to open Services window and see that SQL Server services are not running. On starting the SQL Server service it is giving you following message with error code 17051:

Now as per the error message you open the Event Viewer and see that the Event with ID 17051, which shows SQL Server Evaluation period has expired under Details section:

Now, you recall that the Instance that you had installed was under Evaluation of 180 days, because you didn’t applied any Product Key. So, now how can you make it live again? All you need is a Product key of SQL Server and some clicks:

1. Open the SQL Server Installation Center and click on Maintenance link, and then click on Edition Upgrade:

2. Now on the Upgrade window Click Next and you will reach the Product Key page, apply the Key and click Next:

3. On the Select Instance page, select the SQL Instance that you want to fix and Click next. It will take some time and finally you will see a final window and click Upgrade:

4. Finally you will see the successful window, click on Close button:

–> But, if the above process fails at Engine_SqlEngineHealthCheck step or anywhere in between, then you can use following command line installation option to skip this specific rule to allow the upgrade process to complete successfully:

a) Open Command Prompt (CMD)

b) Go to the folder where SQL Server Setup, setup.exe file is located (like C:Program FilesMicrosoft SQL Server110Setup BootstrapSQLServer2012)

c) Apply following command: setup.exe /q /ACTION=editionupgrade /InstanceName=MSSQLSERVER /P >

The should be the 25 digit Key.

The above command line runs SQL Server setup in silent mode.

5. Now Restart the SQL Server Service for this Instance, and you will see it running fine.

–> Finally, go back to SSMS and now you can connect to the SQL Instance.

Источник

The sql server mssqlserver service terminated with the following service specific error 17051

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have a fairly significant set of issues that I cannot figure out how to resolve that has brought down a bunch of systems. A windows update occurred and the SQL 2019 RC1 server rebooted itself (do not believe that this error is related just coincidental).

This error indicates that the SQL Server evaluation period has expired. Upon reviewing the startup logs this concurs with my belief:

I am confused about why I am running into this issue as I am running a developer version of SQL and not the evaluation version but none the less it currently appears to be a problem.

To attempt to resolve this issue I have done the following:

1. Attempted to do an edition upgrade and set everything back to developer and the process ran and completed successfully but the service will still not start.
2. Attempted to upgrade editions to a licensed version of SQL (which I do also own) and I cannot complete the upgrade because the SQL server is not running.
3. I attempted to follow instructions to turn back the computer time and set common files registry entry to «3» in an attempt to trick it into being active so that I could upgrade. My system automatically reverts the time back to the standard time almost immediately.
   1. Attempted to turn off network connection to disable time sync
   2. Defaulted the time settings for windows
   3. Unjoined the server from the domain thinking GPO might be interfering

This system MUST be restored. Any ideas you have on how to get it back up and running again would be seriously appreciated!

Источник

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 FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLLogERRORLOG

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.

Sometimes error codes are “G oogleable ” “Bingable” through the Error Log (path is mentioned above) messages are more verbose. 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.

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). Tested by myself 🙂

Источник

The sql server mssqlserver service terminated with the following service specific error 17051

Вопрос

I have an sql 2008 r2 express setup, just yesterday I rebooted the server and now the SQL service wouldn’t start giving me the following error:

The SQL Server (SQLEXPRESS) service terminated with service-specific error %%17051.

This seems to be referring to a trial period expiring, now this is SQL Ezpress why wouldn’t be expiring? any advice will be apreciated.

Ответы

It appears to me that you are getting 17051 trial period expired error, when you are trying to run your SQL Express 2008 R2.

By any chance you had previously installed SQL Server evaulation edition, if yes then you must first uninstall the trial edition after that you need to launch SQL Server express setup to install SQL Server Express instance.

When you install retail versions of SQL Server, the Setup program tries to start the SQL Server service of the old installation of SQL Server Evaluation Edition. However, the service cannot start because the installation is expired. Therefore, the installation stops, and you receive the error messages

For more info refer to following support article

Источник

SQL with Manoj

SQL DBA – Windows could not start the SQL Server… refer to service-specific error code 17051 – SQL Server Evaluation period has expired

Ok, one fine day you opened SSMS (SQL Server Management Studio) and tried to connect to a SQL Instance, but it is not getting connected. You are getting following error message on a popup box:

–> You may also get following error:

—————————
Microsoft SQL Server Management Studio
—————————
Evaluation period has expired. For information on how to upgrade your evaluation software please go to http://www.microsoft.com/sql/howtobuy
—————————
OK
—————————

–> Investigate

Go to RUN and type services.msc to open Services window and see that SQL Server services are not running. On starting the SQL Server service it is giving you following message with error code 17051:

Now as per the error message you open the Event Viewer and see that the Event with ID 17051, which shows SQL Server Evaluation period has expired under Details section:

Now, you recall that the Instance that you had installed was under Evaluation of 180 days, because you didn’t applied any Product Key. So, now how can you make it live again? All you need is a Product key of SQL Server and some clicks:

1. Open the SQL Server Installation Center and click on Maintenance link, and then click on Edition Upgrade:

2. Now on the Upgrade window Click Next and you will reach the Product Key page, apply the Key and click Next:

3. On the Select Instance page, select the SQL Instance that you want to fix and Click next. It will take some time and finally you will see a final window and click Upgrade:

4. Finally you will see the successful window, click on Close button:

–> But, if the above process fails at Engine_SqlEngineHealthCheck step or anywhere in between, then you can use following command line installation option to skip this specific rule to allow the upgrade process to complete successfully:

a) Open Command Prompt (CMD)

b) Go to the folder where SQL Server Setup, setup.exe file is located (like C:Program FilesMicrosoft SQL Server110Setup BootstrapSQLServer2012)

c) Apply following command: setup.exe /q /ACTION=editionupgrade /InstanceName=MSSQLSERVER /PID= /SkipRules= Engine_SqlEngineHealthCheck

The should be the 25 digit Key.

The above command line runs SQL Server setup in silent mode.

5. Now Restart the SQL Server Service for this Instance, and you will see it running fine.

–> Finally, go back to SSMS and now you can connect to the SQL Instance.

Источник

In this article, we are going to Troubleshoot SQL Service Error. I recently had a client called me and told me that their application stopped working, and they did not know precisely the issue and asked me to investigate it and resolve the issue. As the client’s data center is far from my place, I decided to take the server remote access using VPN and started the investigation.

When I started accessing the app, the app was spitting out that the database was not accessible from the app server. So, I logged into the Microsoft SQL server and started checking the status of the service. I saw the SQL server instance on services not running, and when I tried to start the service, I get the following error. We are going to troubleshoot SQL Service Error 1051 in this article.

As mentioned in the services warning, I went to the system log on the MS SQL server and analyzed the records. I found that the MS SQL server was running on evaluation and stopped working after the evaluation period. So I confirmed license is the issue.

I pointed this to my client and requested them to arrange for the license and its product key.

Upgrade MS SQL server instance edition to Troubleshoot SQL Service Error

I got the license key and launched the SQL installation center from StartàMicrosoft SQL 2017àSQL installation center. You can launch this from launching setup.exe on MS SQL server installation media as well. Once the Installation center is launched, click Maintenance on the left side navigation and click Edition upgrade.

On the product key page, select ”Enter the product key,” and type the product key and click Next.

Accept the license terms and click Next.

Verify the Edition upgrade rules do not have any error. The SQL server is installed on the domain controller in my environment, so ignore the warning and click on Next.

Select the instance you want to upgrade. You can see the instance name and select that instance. In this case, MSSQLSERVER instance, which pointed out with evaluation. Select the instance and click Next.

Once the ”Ready to upgrade edition” page click upgrade.

The upgrade process will take about 5 mins to complete; wait if it even takes more than that.

Once the upgrade is over, you will get a complete status. All succeeded with a green tick stating that Microsoft SQL edition upgraded.

Now for to services and start the Microsoft SQL instance service, and you see the service running.

Conclusion:

In this article, we gone through troubleshooting the SQL server instance services not starting issue and upgrading the SQL server edition for a particular instance. If you want to learn more about MS SQL click here and for installation guidance click here.

I would like to hear from you if you come across any issues doing this or have any feedback to share. I look forward to sharing our thoughts in the comments section, and I sign off for now

---