Your SQL server 2016 version 13.0.1601.5 is the initial release version in 2016. First step I would suggest is to install the latest patch. You can find the latest version here: https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2016/build-versions
The database has been closed. What should I do?
After discovering the issue, I manually restarted the service and normal operation was restored. The SQL Server version is Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64), and there is a third-party CLR involved. I am aware that one of the tasks I need to do is to update to KB4037357, but apart from that, I have no other solutions. I am not sure if it can solve the problem; perhaps it can at least resolve the issue of not being able to create a dump file?
Here is the last part of the error log recorded before the shutdown. Due to the extensive content of the complete error log and some parts being in Chinese which are difficult to translate, I have only taken the final part before the system went down:
06/19/2024 17:19:15,spid11s,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
06/19/2024 17:19:15,Server,SQL Server shutdown has been initiated
06/19/2024 17:19:15,Server,Problem creating stack dump file due to internal exception
06/19/2024 17:19:15,Server,SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception<c/> 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<c/> restart the server (unless SQLAgent is configured to auto restart).
06/19/2024 17:19:15,Server,Error: 17311,Level: 16,State: 1.
06/19/2024 17:19:15,Server,Problem creating stack dump file due to internal exception
06/19/2024 17:19:15,Server,Problem creating symptom dump file due to internal exception
06/19/2024 17:19:15,Server,Unknown Exception raised by task.
06/19/2024 17:19:15,spid23s,AppDomain 2 (BJJG_JJZ.dbo[runtime].1) unloaded.
06/19/2024 15:43:11,spid87,Service Broker needs to access the master key in the database 'BJJG_GQDTF'. Error code:32. The master key has to exist and the service master key encryption is required.
06/19/2024 15:43:11,spid87,Error: 28054,Level: 11,State: 1.
06/19/2024 15:35:39,spid43s,The query notification dialog on conversation handle '{FAADA536-0E2E-EF11-86FE-9ADB167A10FE}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8470</Code><Description>Remote service has been dropped.</Description></Error>'.
06/19/2024 15:35:29,spid43s,The query notification dialog on conversation handle '{F0ADA536-0E2E-EF11-86FE-9ADB167A10FE}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8470</Code><Description>Remote service has been dropped.</Description></Error>'.
06/19/2024 15:33:29,spid67,Service Broker needs to access the master key in the database 'BJJG_JJZ'. Error code:32. The master key has to exist and the service master key encryption is required.
06/19/2024 15:33:29,spid67,Error: 28054,Level: 11,State: 1.
1 additional answer
Sort by: Most helpful
-
LucyChenMSFT-4874 2,825 Reputation points
2024-06-21T02:07:11.89+00:00 Hi @博雄 胡,
Thank you for reaching out and welcome to Microsoft.
Would you like to try Guoxiong's method? You can try to install the latest Service Pack 3 for your SQL Server and observe whether the issue is resolved.
Your time and cooperation are much valued by us. We are looking forward to hearing from you to assist further.
Best regards,
Lucy Chen
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
https://docs.microsoft.com/en-us/answers/support/email-notifications