Ошибка 17054 sql

The error I’m running into first occurred when I tried to connect to my SQl server database in Toad for SQl Server. The error message stated The System cannot find the file specified.

I opened SQL Server configuration manager and the SQL Server was stopped. I tried to start it but it failed. Here is the error in the log:

2016-07-07 08:52:09.01 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required

2016-07-07 08:52:10.25 spid20s Service Broker manager has shut down.

2016-07-07 08:52:10.25 spid20s Error: 17054, Severity: 16, State: 1.

Community's user avatar

asked Jul 7, 2016 at 14:23

Chris Bilz's user avatar

1

Check the service account.
It might be invalid, wrong password or lack right to logon as a service.
Try login as localsystem just to eliminate this possibility.
Also check the SPNs.

answered Sep 22, 2016 at 21:28

Ricardo Silva's user avatar

Check if the SQL Browser service is running. If yes then stop it and
disable (if you are using only one default instance.)

I had the same issue and after stopping/disabling the SQL Browser
service; it worked for me.

The SQL Server Browser Service is installed often in Disabled state (It is preferred to be disabled unless required).
It is only required for named instances or instances listening on non-default ports.

Your application installer should only restart the Browser service if needed, and certainly should check for a disabled service and ask an administrator permission to enable the service .

answered Aug 29, 2017 at 12:40


  • January 8, 2018 at 12:13 am

    #330784

    In our environment, SQL server 2012 is automatically restarted, what will be issue??? Nothing related information is found in Event Viewer also.

    Message
    The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
    SQL Server shutdown has been initiated
    Message
    SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.

  • January 8, 2018 at 2:19 am

    This was removed by the editor as SPAM

  • RandomStream

    Hall of Fame

    Points: 3735

    Would you are to share a more complete error log? Was there memory dump in the log? OS and SQL version info, processor type, memory size?

  • Narine M

    SSCrazy

    Points: 2672

    NO memory dump over there. 

    Error Log:

    Message
    This instance of SQL Server has been using a process ID of 1448 since 12/14/2017 3:55:38 AM (local) 12/13/2017 10:25:38 PM (UTC). This is an informational message only; no user action is required.
    Message
    SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
    Service Broker manager has shut down.
    Message
    Error: 17054, Severity: 16, State: 1.
    Message
    The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
    Message
    .NET Framework runtime has been stopped.
    Message
    SQL Server shutdown has been initiated
    Message
    SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.

  • Gail Shaw

    SSC Guru

    Points: 1004494

    Narine M — Wednesday, January 10, 2018 3:28 AM

    SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
    .

    That suggests that Windows is booting and SQL shutting down is for the server shutdown.
    Are you seeing the server reboot, or are you certain it’s just SQL restarting?

    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

  • RandomStream

    Hall of Fame

    Points: 3735

    Could it be automatic Windows Update that is causing system reboot?

  • Gail Shaw

    SSC Guru

    Points: 1004494

    It’s possible.

    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

  • January 10, 2018 at 11:24 pm

    This was removed by the editor as SPAM

Viewing 8 posts — 1 through 7 (of 7 total)

Our new database just inaccessible. I have tried to find in error log
and find this error during that time. So when I went to Configuration
manager. I was seeing Browser service, SQL Agent and SQL Server
services were stopped and when tried to restart it just hung and because
of that I have to do reboot.
Do you have this kind of situation. How did you solve that? I am also attaching a screenshot to get a better idea about this situation. It is a production server and this is recurring issue. It happened a month ago and last week it happened and also it happened today. So my DBA has repaired the SQL instance to make the server operation. I am not seeing any issue with database integrity though but I could not find the resolution yet.  This is a SharePoint databases. Any help would be appreciated.

I followed this forums

https://stackoverflow.com/questions/38247986/sql-server-2014-fails-on-start-attempt-error-17054 Opens a new window

https://serverfault.com/questions/154931/mssql-instance-shuts-down-error-17054 Opens a new window

I  am not still not sure of the cause of this issue.
Image: post content

Содержание

  1. Sql error 17054 severity 16
  2. Answered by:
  3. Question
  4. Answers
  5. Error 17054 severity 16 state 1- SQL Server Automatically Restarts
  6. error 17054 severity 16 state 1 sql server 2014 enterprise edition
  7. Ms Sql Error 17054 Severity 16 State 1
  8. Fix Sql Server Error 17054 Severity 16 State 1 (Solved)
  9. Error: 17058, Severity: 16, State: 1.
  10. sql server 2008 — MSSQL instance shuts down error 17054 .
  11. Database Engine Error Severities — SQL Server Microsoft Docs
  12. Error may be logged after you run a DBCC command — SQL .
  13. SQL Server 2019 Linux docker bug — Microsoft Q&A
  14. Error: 17204 « Help: SQL Server
  15. SQL Server logon failure occurs frequently (Error: 17189 .
  16. Ms Sql Error 17054 Severity 16 State 1 Fixes & Solutions
  17. SQL Server 2008 won’t start

Sql error 17054 severity 16

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

Answered by:

Question

Hello — extreme newbie

Context: I was using some software without problems for the past couple weeks, occasionally it crashed but when started again worked fine without lost data. Today, crashed and would not start.

The error: «Cannot open database TCM. Check database settings or contact your system administrator. [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied.;clsSBDAO;OpenDataBase, -2147467259»

What I tried: 0) restart computer 1) opened SQL Studio Express 2005 and checked database — looks fine. 2) create new database and restore with backup files — preparing first run —> «Could not connect to server. check that SQL server / MSDE is running and information is correct.»

I must resolve this problem as soon as possible.

Answers

Hi Forest. Perterson,

>> changing the (local) db location to SQLEXPRESS works

Regarding to your description, seems your SQL Server Express installed as a named instance. So you changed something like «yourComputerNameSQLEXPRESS», which works.

According to the system administration account is created by the installer as you mentioned because SQL Server Authentication is used when you have created a user name and password in SQL Server. So you can login through password/username as you said.

Meanwhile only the local admin group will be able to access the database because, this group is added to the sql server instance by default as Built-inAdministrator. Any other users than this group has to be added to the server as login and Database as user explicitly.

Источник

Error 17054 severity 16 state 1- SQL Server Automatically Restarts

January 8, 2018 at 12:13 am

In our environment, SQL server 2012 is automatically restarted, what will be issue. Nothing related information is found in Event Viewer also.

Message
The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
SQL Server shutdown has been initiated
Message
SQL Trace was stopped due to server shutdown. Trace . This is an informational message only; no user action is required.

January 8, 2018 at 2:19 am

This was removed by the editor as SPAM

January 8, 2018 at 10:41 am

Would you are to share a more complete error log? Was there memory dump in the log? OS and SQL version info, processor type, memory size?

January 10, 2018 at 3:28 am

NO memory dump over there.

Message
This instance of SQL Server has been using a process ID of 1448 since 12/14/2017 3:55:38 AM (local) 12/13/2017 10:25:38 PM (UTC). This is an informational message only; no user action is required.
Message
SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
Service Broker manager has shut down.
Message
Error: 17054, Severity: 16, State: 1.
Message
The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
Message
.NET Framework runtime has been stopped.
Message
SQL Server shutdown has been initiated
Message
SQL Trace was stopped due to server shutdown. Trace . This is an informational message only; no user action is required.

Источник

error 17054 severity 16 state 1 sql server 2014 enterprise edition

Our new database just inaccessible. I have tried to find in error log and find this error during that time. So when I went to Configuration manager. I was seeing Browser service, SQL Agent and SQL Server services were stopped and when tried to restart it just hung and because of that I have to do reboot. Do you have this kind of situation. How did you solve that? I am also attaching a screenshot to get a better idea about this situation. It is a production server and this is recurring issue. It happened a month ago and last week it happened and also it happened today. So my DBA has repaired the SQL instance to make the server operation. I am not seeing any issue with database integrity though but I could not find the resolution yet. This is a SharePoint databases. Any help would be appreciated.

I followed this forums

I am not still not sure of the cause of this issue.

Источник

Ms Sql Error 17054 Severity 16 State 1

We have collected for you the most relevant information on Ms Sql Error 17054 Severity 16 State 1, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered Ms Sql Error 17054 Severity 16 State 1 before you, so use the ready-made solutions.

Fix Sql Server Error 17054 Severity 16 State 1 (Solved)

    http://subfield.org/sql-server-error-17054-severity-16-state-1.html
    Error 17054 Severity 16 State 1 Sql Server 2005 This normally indicates the VIA support click to read more the NUMA configuration for this computer. Look for corresponding entries in the event have anything to do with the stoppage of MSSQLSERVER.

Error: 17058, Severity: 16, State: 1.

    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/c43a7d20-187e-4f45-9835-422ed965c8ae/error-17058-severity-16-state-1
    2008-11-23 21:26:32.64 Server Error: 17054, Severity: 16, State: 1. 2008-11-23 21:26:32.64 Server The current event was not reported to the Win dows Events log.

sql server 2008 — MSSQL instance shuts down error 17054 .

    https://serverfault.com/questions/154931/mssql-instance-shuts-down-error-17054
    Sounds like the server is rebooting, perhaps because of auto-updates? The error 17054 is shown because SQL Server tried to write an event to the Windows Event Log, but it …

Database Engine Error Severities — SQL Server Microsoft Docs

    https://docs.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-error-severities
    Severity level Description; 0-9: Informational messages that return status information or report errors that are not severe. The Database Engine does not raise system errors with severities of 0 through 9.

Error may be logged after you run a DBCC command — SQL .

    https://docs.microsoft.com/en-us/troubleshoot/sql/admin/17053-and-926-errors-running-dbcc
    Msg 7928, Level 16, State 1, Line 1 The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.

SQL Server 2019 Linux docker bug — Microsoft Q&A

    https://docs.microsoft.com/answers/questions/122031/sql-server-2019-linux-docker-bug.html
    2020-xx-xx xx:xx:xx.xx spid13s Error: 46906, Severity: 16, State: 1. 2020-xx-xx xx:xx:xx.xx spid13s Unable to retrieve registry value ‘NodeRole’ from Windows registry key ‘SoftwareMicrosoftMicrosoft SQL ServerMSSQLPolybaseConfiguration’: (null). First, Express edition does not support Polybase so why is it trying to configure it.

Error: 17204 « Help: SQL Server

    https://sqlserver-help.com/tag/error-17204/
    Aug 07, 2014 · 2014-08-07 05:53:49.68 Logon Error: 17188, Severity: 16, State: 1. 2014-08-07 05:53:49.68 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.

SQL Server logon failure occurs frequently (Error: 17189 .

    https://docs.microsoft.com/answers/questions/82659/sql-server-logon-failure-occurs-frequently-error-1.html
    SQL Server logon failure occurs frequently (Error: 17189, Severity: 16, State: 1.) Hi, [Environment] Microsoft Windows Server 2012 R2 Standard. The maximum server memory of SQL Server for the DB server is set to 4096(MB).—systeminfo—Total physical memory: 8,191 MB Available physical memory: 1,168 MB Virtual memory: Maximum size: 13,162 MB

Ms Sql Error 17054 Severity 16 State 1 Fixes & Solutions

We are confident that the above descriptions of Ms Sql Error 17054 Severity 16 State 1 and how to fix it will be useful to you. If you have another solution to Ms Sql Error 17054 Severity 16 State 1 or some notes on the existing ways to solve it, then please drop us an email.

Источник

SQL Server 2008 won’t start

October 18, 2008 at 1:17 pm

I just installed SQL Server 2008 on my XP Pro system. Management Studio failed. I then found that SQL Server never started. I tried starting it from services with no success. I then tried to logon as a local systen account but that didn’t work. The error log says «Error: 17054, Severity: 16, State: 1.» Any ideas?

October 18, 2008 at 1:52 pm

Give this a read

and check the SQL Logs for more detailed logging

typically found under C:Program FilesMicrosoft SQL ServerMSSQLLOGERRORLOG

October 18, 2008 at 2:43 pm

I tried starting it from services with no success

And error message is?

October 18, 2008 at 3:00 pm

There was no definitive error message. Here is the log:

2008-10-18 13:51:52.57 Server Microsoft SQL Server 2008 (RTM) — 10.0.1600.22 (Intel X86)

Jul 9 2008 14:43:34

Copyright (c) 1988-2008 Microsoft Corporation

Enterprise Evaluation Edition on Windows NT 5.1 (Build 2600: Service Pack 3)

2008-10-18 13:51:52.57 Server (c) 2005 Microsoft Corporation.

2008-10-18 13:51:52.57 Server All rights reserved.

2008-10-18 13:51:52.60 Server Server process ID is 460.

2008-10-18 13:51:52.60 Server Authentication mode is WINDOWS-ONLY.

2008-10-18 13:51:52.60 Server Logging SQL Server messages in file ‘C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLLogERRORLOG’.

2008-10-18 13:51:52.60 Server This instance of SQL Server last reported using a process ID of 6084 at 10/18/2008 12:12:48 PM (local) 10/18/2008 7:12:48 PM (UTC). This is an informational message only; no user action is required.

2008-10-18 13:51:52.64 Server Registry startup parameters:

-d C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLDATAmaster.mdf

-e C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLLogERRORLOG

-l C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLDATAmastlog.ldf

2008-10-18 13:51:52.70 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2008-10-18 13:51:52.70 Server Detected 1 CPUs. This is an informational message; no user action is required.

2008-10-18 13:51:53.78 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2008-10-18 13:51:53.93 Server Node configuration: node 0: CPU mask: 0x00000001 Active CPU mask: 0x00000001. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2008-10-18 13:51:54.07 spid7s Starting up database ‘master’.

2008-10-18 13:51:54.87 spid7s Resource governor reconfiguration succeeded.

2008-10-18 13:51:54.87 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

2008-10-18 13:51:54.87 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.

2008-10-18 13:51:54.90 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = ‘MSSQLSERVER’.

2008-10-18 13:51:55.35 spid7s SQL Trace ID 1 was started by login «sa».

2008-10-18 13:51:55.37 spid7s Starting up database ‘mssqlsystemresource’.

2008-10-18 13:51:55.43 spid7s The resource database build version is 10.00.1600. This is an informational message only. No user action is required.

2008-10-18 13:51:56.06 spid10s Starting up database ‘model’.

2008-10-18 13:51:56.07 spid7s Server name is ‘NEW-FROM-BYTES’. This is an informational message only. No user action is required.

2008-10-18 13:51:57.50 spid10s Clearing tempdb database.

2008-10-18 13:51:58.06 spid13s Error: 9954, Severity: 16, State: 1.

2008-10-18 13:51:58.06 spid13s SQL Server failed to communicate with filter daemon launch service (Windows error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

). Full-Text filter daemon process failed to start. Full-text search functionality will not be available.

2008-10-18 13:51:58.39 spid7s Starting up database ‘msdb’.

2008-10-18 13:51:59.26 Server A self-generated certificate was successfully loaded for encryption.

2008-10-18 13:51:59.28 Server Error: 26055, Severity: 16, State: 1.

2008-10-18 13:51:59.28 Server The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.

2008-10-18 13:51:59.32 Server Error: 17182, Severity: 16, State: 1.

2008-10-18 13:51:59.32 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: Unable to initialize the VIA listener. The specified module could not be found.

2008-10-18 13:51:59.34 Server Error: 17182, Severity: 16, State: 1.

2008-10-18 13:51:59.34 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The specified module could not be found.

2008-10-18 13:51:59.34 Server Error: 17826, Severity: 18, State: 3.

2008-10-18 13:51:59.34 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

2008-10-18 13:51:59.34 Server Error: 17120, Severity: 16, State: 1.

2008-10-18 13:51:59.34 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Источник

The error I’m running into first occurred when I tried to connect to my SQl server database in Toad for SQl Server. The error message stated The System cannot find the file specified.

I opened SQL Server configuration manager and the SQL Server was stopped. I tried to start it but it failed. Here is the error in the log:

2016-07-07 08:52:09.01 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required

2016-07-07 08:52:10.25 spid20s Service Broker manager has shut down.

2016-07-07 08:52:10.25 spid20s Error: 17054, Severity: 16, State: 1.

Community's user avatar

asked Jul 7, 2016 at 14:23

Chris Bilz's user avatar

1

Check the service account.
It might be invalid, wrong password or lack right to logon as a service.
Try login as localsystem just to eliminate this possibility.
Also check the SPNs.

answered Sep 22, 2016 at 21:28

Ricardo Silva's user avatar

Check if the SQL Browser service is running. If yes then stop it and
disable (if you are using only one default instance.)

I had the same issue and after stopping/disabling the SQL Browser
service; it worked for me.

The SQL Server Browser Service is installed often in Disabled state (It is preferred to be disabled unless required).
It is only required for named instances or instances listening on non-default ports.

Your application installer should only restart the Browser service if needed, and certainly should check for a disabled service and ask an administrator permission to enable the service .

answered Aug 29, 2017 at 12:40

Some of my mssql instances shut down after a while. After enabled logging I was able to get a error message why the services are down:

2010-06-23 15:49:53.34 Server      Server resumed execution after being idle 33570 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-06-24 01:04:48.84 spid1s      Server resumed execution after being idle 32039 seconds. Reason: timer event.
2010-06-24 03:14:42.14 Server      SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2010-06-24 03:15:56.35 spid7s      Server resumed execution after being idle 6949 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-06-24 03:15:59.01 spid7s      Fehler: 17054, Schweregrad: 16, Status: 1.
2010-06-24 03:15:59.01 spid7s      The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.

I can’t seem to google the meaning of error 17054? What does it mean?

How can I prevent the instance services to shutdown? The problem is, that the services do not start up automatically after such error, altough the startup type of the services are set to automatically.
I could program another service that watches the instance services and simplies starts them in case they are down. But I’d rather fix my problem with the MSSQL Server


  • January 8, 2018 at 12:13 am

    #330784

    In our environment, SQL server 2012 is automatically restarted, what will be issue??? Nothing related information is found in Event Viewer also.

    Message
    The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
    SQL Server shutdown has been initiated
    Message
    SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.

  • January 8, 2018 at 2:19 am

    This was removed by the editor as SPAM

  • RandomStream

    Hall of Fame

    Points: 3735

    Would you are to share a more complete error log? Was there memory dump in the log? OS and SQL version info, processor type, memory size?

  • Narine M

    SSCrazy

    Points: 2672

    NO memory dump over there. 

    Error Log:

    Message
    This instance of SQL Server has been using a process ID of 1448 since 12/14/2017 3:55:38 AM (local) 12/13/2017 10:25:38 PM (UTC). This is an informational message only; no user action is required.
    Message
    SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
    Service Broker manager has shut down.
    Message
    Error: 17054, Severity: 16, State: 1.
    Message
    The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
    Message
    .NET Framework runtime has been stopped.
    Message
    SQL Server shutdown has been initiated
    Message
    SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.

  • Gail Shaw

    SSC Guru

    Points: 1004494

    Narine M — Wednesday, January 10, 2018 3:28 AM

    SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
    .

    That suggests that Windows is booting and SQL shutting down is for the server shutdown.
    Are you seeing the server reboot, or are you certain it’s just SQL restarting?

    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

  • RandomStream

    Hall of Fame

    Points: 3735

    Could it be automatic Windows Update that is causing system reboot?

  • Gail Shaw

    SSC Guru

    Points: 1004494

    It’s possible.

    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

  • January 10, 2018 at 11:24 pm

    This was removed by the editor as SPAM

Viewing 8 posts — 1 through 7 (of 7 total)

Our new database just inaccessible. I have tried to find in error log
and find this error during that time. So when I went to Configuration
manager. I was seeing Browser service, SQL Agent and SQL Server
services were stopped and when tried to restart it just hung and because
of that I have to do reboot.
Do you have this kind of situation. How did you solve that? I am also attaching a screenshot to get a better idea about this situation. It is a production server and this is recurring issue. It happened a month ago and last week it happened and also it happened today. So my DBA has repaired the SQL instance to make the server operation. I am not seeing any issue with database integrity though but I could not find the resolution yet.  This is a SharePoint databases. Any help would be appreciated.

I followed this forums

https://stackoverflow.com/questions/38247986/sql-server-2014-fails-on-start-attempt-error-17054 Opens a new window

https://serverfault.com/questions/154931/mssql-instance-shuts-down-error-17054 Opens a new window

I  am not still not sure of the cause of this issue.
Image: post content

I recently updated my personal sandbox to use SQL Server 2016. While the installation succeeded, one of the first few problems that I ran into were:

  • The SQL Server 2016 instance failed to shutdown
  • Error 17054 was logged every time a shutdown is attempted with the error: “The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
  • Installation of KB3207512 (update for SQL Server 2016 SP1 Reporting Services) and latest CUs kept failing
  • User databases would not be accessible with an error: “The operating system returned error 21(The device is not ready.)

While I was trying to figure out what was wrong, I ran into the same problem with a few other instances.

The Solutions

After a lot of rounds of trial and error, the following changes finally did the trick. The items below collectively make up the solution and all items need to be performed in order to get the SQL server instance up-to speed again.

  • Launch the SQL Server Configuration Manager
  • Under “SQL Server Network Configuration” ensure that the TCP/IP protocol is enabled
  • Under “SQL Server Services”, ensure that the following services are started:
    • SQL Server PolyBase Engine
    • SQL Server PolyBase Data Movement

Once the steps provided above are done, all the problems listed above should cease to exist.

Until we meet next time,

Be courteous. Drive responsibly.

  • Remove From My Forums
  • Общие обсуждения

  • Добрый день!

    недеюсь на вашу помощь:

    произошол сбой в SQL, ниже скрины

    подскажите как это решить?

    пробовал пока только создать новго пользователя и новую БЗ — результат не меняется

    хотел выложить логи SQL, но не нахожу как сюда прикрепить файлы логов

Все ответы

  • И какие параметры контроля парольной политики вы установили для логина aist_admin?

  • пользователь создаётся без доп настроек.

    изначально,  кода система работала — создавался пользователь: «добавить пользователя», вводился пароль, назначалась база. без доп. настроек. работало.

  • подскажите как это решить

    ЭТО — что? Не вижу нормальной, технической постановки вопроса.


    www.sqlCMD.ru — all around MS SQL Server

  • Здравствуйте ch888

    Вам удалось решить данную проблему? 

    Если да, то будьте добры
    написать как, чтобы это помогло и другим пользователям.

    Если нет, то напишите, чем еще можем быть Вам полезными?

  • Решить проблему мне не удалось, решением занялся другой специалист. Но как и что он сделал узнать не получится.

  • Я перевел тему в разряд обсуждений, потому как по всей видимости не будет возможности
    получить категоричный ответ, удалось ли решить проблему.  Если Вам будет необходима дополнительная помощь по этой теме, Вы можете возобновить дискуссию, просто оставив сообщение в данной теме. 
     


    Уважаемые участники форума. У меня к Вам просьба: если какой-нибудь из ответов помог Вам решить Вашу проблему, пожалуйста, не забывайте отмечать его. Таким образом, Вы поможете и другим
    пользователям, у которых возникла схожая проблема! Спасибо!

Our new database is just inaccessible. I have tried to find it in the error log and find this error during that time. So when we went to the Configuration manager. we were seeing Browser service, SQL Agent, and SQL Server services were stopped, and then tried to restart it just hung and because of that, I have to do a reboot. It is a production server and this is a recurring issue. It happened a month ago and last week it happened and also it happened today. So my DBA has repaired the SQL instance to make the server operation. I am not seeing any issue with database integrity though but I could not find the resolution yet.  This is a SharePoint database. Do you have this kind of situation? How did you solve that?

r/SQL - error 17054 severity 16, state 1 SQL Server 2014 enterprise edition

The error I’m running into first occurred when I tried to connect to my SQl server database in Toad for SQl Server. The error message stated The System cannot find the file specified.

I opened SQL Server configuration manager and the SQL Server was stopped. I tried to start it but it failed. Here is the error in the log:

2016-07-07 08:52:09.01 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required

2016-07-07 08:52:10.25 spid20s Service Broker manager has shut down.

2016-07-07 08:52:10.25 spid20s Error: 17054, Severity: 16, State: 1.

2 Answers

Check the service account.
It might be invalid, wrong password or lack right to logon as a service.
Try login as localsystem just to eliminate this possibility.
Also check the SPNs.

Check if the SQL Browser service is running. If yes then stop it and
disable (if you are using only one default instance.)

I had the same issue and after stopping/disabling the SQL Browser
service; it worked for me.

The SQL Server Browser Service is installed often in Disabled state (It is preferred to be disabled unless required).
It is only required for named instances or instances listening on non-default ports.

Your application installer should only restart the Browser service if needed, and certainly should check for a disabled service and ask an administrator permission to enable the service .

Понравилась статья? Поделить с друзьями:
  • Ошибка 17653 т4
  • Ошибка 17646 ауди
  • Ошибка 171 шевроле авео т300
  • Ошибка 1762 тойота ленд крузер 100 причины
  • Ошибка 1705 хонда торнео