Содержание
- Sql error 17054 severity 16
- Answered by:
- Question
- Answers
- Error 17054 severity 16 state 1- SQL Server Automatically Restarts
- error 17054 severity 16 state 1 sql server 2014 enterprise edition
- Ms Sql Error 17054 Severity 16 State 1
- Fix Sql Server Error 17054 Severity 16 State 1 (Solved)
- Error: 17058, Severity: 16, State: 1.
- sql server 2008 — MSSQL instance shuts down error 17054 .
- Database Engine Error Severities — SQL Server Microsoft Docs
- Error may be logged after you run a DBCC command — SQL .
- SQL Server 2019 Linux docker bug — Microsoft Q&A
- Error: 17204 « Help: SQL Server
- SQL Server logon failure occurs frequently (Error: 17189 .
- Ms Sql Error 17054 Severity 16 State 1 Fixes & Solutions
- 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.
Источник
-
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 recoverabilityWe 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 recoverabilityWe 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)
- Remove From My Forums
-
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.
forest
Answers
-
Hi Forest. Perterson,
>> changing the (local) db location to <machineName>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.Based on my research, this might be related to SQL Server permissions issue. Please refer to this article
http://msdn.microsoft.com/en-us/library/ms191465.aspx.
Regards, Amber zhang
-
Marked as answer by
Monday, March 19, 2012 7:48 AM
-
Marked as answer by
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.
02.09.08 — 04:45
по ночам запускается скрипт выгрузки БД, и каждый раз выгрузка не проходит, через 20 мин. выдает сообщение, «Соединение завершено администратором» и ссылка на транзакцию.
если перегрузить сервер со скулем, то выгрузка проходит нормально, в чем дело?
1 — 02.09.08 — 04:46
База УПП, сервер с БД и сервер терминалов на разных машинах, меж собой дружат через 100мб. хаб. сетка стабильна.
2 — 02.09.08 — 04:59
плин придется ждать пока проснется западная часть России :))
3 — 02.09.08 — 06:48
В моем случае были проблемы с планками памяти на сервере 1С + рекомендуемые настройки сервера 1С (на ИТС — «Рабочие процессы перезапускать через…»)
4 — 02.09.08 — 06:50
кто-то сидит в базе
5 — 02.09.08 — 07:02
(4) тогда бы было ‘Ошибка разделенного доступа к информационной базе’
а для (0) это пропадает связь с сервером 1С (перегружается, коннект пропадает etc), можно посмотреть в эвент-логах не ругается ли он. Либо установлена блокировка соединений.
6 — 02.09.08 — 09:59
А если делать руками выгрузку, то такая проблема наблюдается? Если да, то совсем недавно эту проблему решил тем, что снял базу с поддержки, правда там настал такой момент, что просто не мог загрузить базу на сервер…
PS тоже УПП
7 — 02.09.08 — 10:04
(0) О! у нас точно такая же проблема! бьемся уже апру недель. причем схожая ситуация на двух разных серваках (у нас и в филиале). платформа 8.1.11.67, УПП последнего релиза. скуль 2005. рвется при выгрузке с ошибкой «»соединение завершено администратором», лечиться перезагрузкой сервака. есть подозрения на корявый дистриб скуля, так как и у нас и в филиале скуль ставился с одного дистрибутива. танцы с бубном непомогли. причину сего гемора найти не можем. поэтому перед выгрузкой ночью сервак ребутится и только потом архивирует
8 — 02.09.08 — 10:06
(6) при ручной выгрузке та же фигня
9 — 02.09.08 — 10:06
а если перезапустить серевер 1с? таже фигня? может регламентные задания какиенибудь мешают
10 — 02.09.08 — 10:07
(7) сначала через раз так вырубалось, потом вообще перестала делаться выгрузка/загрузка.
вылечили сняв с поддержки полностью конфигурацию.
11 — 02.09.08 — 10:11
(0) кстати… Чем не устраивает бэкап средствами скуля? мы им делаем и не знаем проблем с бэкапами…
12 — 02.09.08 — 10:36
(11) устраивает, но это не решение проблемы. тем более такая же ситуация проявляется при обновлении конфигурации
13 — 03.09.08 — 04:37
У нас конфигурация снята с поддержки, у меня ТИИ не проходит и после перезагрузки, если перепроводку за 2 мес. или выгрузку БД скуль осиливает после перезагрузки, то ТИИ уже никак. буду пробовать ставить апдейты на скуль, если не поможет придется наверно откатиться на 2000
14 — 03.09.08 — 05:46
(11) не устраивает, нельзя быстро развернуть копию в файловой версии или загрузить свежую копию БД в свою файловую версию в которой работаю через хранилище с основной конфигурацией.
15 — 03.09.08 — 08:29
ап
16 — 03.09.08 — 09:09
(0) Логи сервера 1С и MS SQL не пробовали смотреть? Что пишет?
17 — 03.09.08 — 09:17
Включай технологический журнал, отлавливай ошибку. А лучше ЦУП
18 — 03.09.08 — 09:24
+(16) Логи сервака ОС тоже неплохо бы посмотреть. Возможно элементарно ресурсов не хватает…
19 — 03.09.08 — 09:29
не может это какое-нибудь регламентное задание попытаться стартовать ?
20 — 03.09.08 — 09:56
(14) так поставь скуль на локальный комп. У меня так и стоит, правда SQL 2000. Изголяюсь на локалке и никому не мешаю.
21 — 03.09.08 — 10:09
(0) у нас была такая-же проблема.
Расследование показало, что причина скорее всего в следующем:
1. Банальная нехватка памяти при сохранении БД
или
2. Ошибки в логической структуре МД.
Лечение:
1. Рестарт сервера. Поскольку размер доступной памяти можно увеличить с помощью рестарта сервера (как правило именно так и бывает, поскольку существует проблема «утечек памяти»)
или/и
2. Удаление конфигурации поставщика из МД с последующим восстановлением (после/до обновления например)
22 — 04.09.08 — 05:19
В логах скуль жалуется только на незапущенную службу сообщений, и вот еще это:
09/01/2008 22:06:39,Server,Unknown,The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Administrator should deregister this SPN manually to avoid client authentication errors.
09/01/2008 22:06:39,spid5s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.
09/01/2008 22:06:38,spid12s,Unknown,Service Broker manager has shut down.
09/01/2008 22:06:31,Server,Unknown,The current event was not reported to the Windows Events log. Operating system error = 1717(Неизвестный интерфейс.). You may need to clear the Windows Events log if it is full.
09/01/2008 22:06:31,Server,Unknown,Error: 17054<c/> Severity: 16<c/> State: 1.
09/01/2008 22:06:31,Server,Unknown,The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required.
09/01/2008 22:06:29,Server,Unknown,SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
либо комп перезагружается или что, по расписанию перезагрузки в это время нет, по логам системы тоже…
почистил системные журналы на скуле, и запустил службу сообщений, в выходные проверю помогло или нет.
23 — 04.09.08 — 05:24
Как включить технологический журнал?
Есть ли журнал у сервера 1С, в консоли не нашел? 
где посмотреть какие регл. задания запущены в 1С? где они запускаются вообще? на сервере 1С?
24 — 04.09.08 — 05:33
выяснил что за регламентные задания, запускаются программно из 1С, — у меня таких нет.
25 — 04.09.08 — 05:36
кстати на сервере терминалов стоит 12гб. памяти, на сервере скуля 2гб, ежедневно подключаются до 50 чел. и вроде система выдерживает, в редких случаях у пользователей выскакивали сообщения «Соединение завершено администратором» 1 или 2 раза.
26 — 04.09.08 — 05:37
(23) Читай на ИТС, там и примеры даны…
И проверь все таки планки памяти….
>09/01/2008 22:06:31,Server,Unknown,The current event was not reported to the Windows Events log. Operating system error = 1717(Неизвестный интерфейс.). You may need to clear the Windows Events log if it is full.
очисть системные логи, в них вообще иногда много полезного можно увидеть 
-
-
January 22 2018, 17:12
Жила-была мумия одного SQL Server 2014(12.0.5557.0). Бежала мимо уборщица, шваброй махнула сервер упал и как давай по-полу валяться.
Проблема
После аппаратного сбоя старует и падает служба MS SQL Server.
Диагностика
В журналах сервера странное: CHECKDB прошел без ошибок для всех баз, но служба стартовать не хочет.
«000-00-00 00:00:00.00 spid8s Recovery is complete. This is an informational message only. No user action is required.
2000-00-00 00:00:00.00 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2000-00-00 00:00:00.00 spid37s Service Broker manager has shut down.
2000-00-00 00:00:00.00 spid8s .NET Framework runtime has been stopped.
2000-00-00 00:00:00.00 spid8s SQL Server shutdown has been initiated
2000-00-00 00:00:00.00 spid8s SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.
2000-00-00 00:00:00.00 spid8s Error: 17054, Severity: 16, State: 1.
2000-00-00 00:00:00.00 spid8s 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»
В жуналах ОС видим Event 17311, источник MSSQLSERVER:
«SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).»
Решение
Микрософт ничего интересного не предлагает: проверьте базу (это на мертвом сервере) или обратитесь в поддержку.
На самом деле всё оказалось просто: вовремя сбоя была повреждена одна из баз и при попытке её смонтировать MSSQL впадал в истерику (вспоминаем CHECKDB). Пострадавшая база была вычисленна с помощью последовательного блокирования доступа к файлам баз данных (прекратить доступ учетки сервера к файлам БД или, банально, их переименовать).
PS Как всегда, поврежденна оказалась мелкая и уже никому не нужная базуля.


