October 26, 2015 at 4:56 pm
I'm running SQL 2012 on a Win 2012 VM and the SQL server shuts down automatically after starting the SQL Server & SQL Server Agent Jobs.
Did anyone came across this issue ?
October 26, 2015 at 5:01 pm
sandeepraichura (10/26/2015)
I'm running SQL 2012 on a Win 2012 VM and the SQL server shuts down automatically after starting the SQL Server & SQL Server Agent Jobs.Did anyone came across this issue ?
Quick question, what do you see in the SQL Error Log and the Windows Event Logs?
😎
October 26, 2015 at 5:04 pm
There's about a thousand possible causes.
Locate the latest error log, go to the end of the file and look for error messages. SQL is very, very good about logging the entire startup process and it will log anything that will cause the startup to fail.
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
October 26, 2015 at 10:20 pm
Yes, I did check that and didn't see anything relevant.
I see the following in SQL log file
Error: 18456, Severity: 14, State: 38.
I see four critical errors in Event Viewer
Event 13 - vmicvss
Event 41 - Kernel-Power
Event 2 - Hyper-V
Event 107
October 26, 2015 at 10:43 pm
Post the error log please, 19456 is, iirc, a SQL login failure and so probably irrelevant.
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
October 26, 2015 at 11:14 pm
2015-10-26 18:40:19.77 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-10-26 18:40:19.82 Server (c) Microsoft Corporation.
2015-10-26 18:40:19.82 Server All rights reserved.
2015-10-26 18:40:19.82 Server Server process ID is 1372.
2015-10-26 18:40:19.82 Server System Manufacturer: 'Microsoft Corporation', System Model: 'Virtual Machine'.
2015-10-26 18:40:19.83 Server Authentication mode is WINDOWS-ONLY.
2015-10-26 18:40:19.83 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2015-10-26 18:40:19.83 Server The service account is 'DGI\DGI-SQL2012$'. This is an informational message; no user action is required.
2015-10-26 18:40:19.86 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2015-10-26 18:40:19.86 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2015-10-26 18:40:22.34 Server SQL Server detected 1 sockets with 1 cores per socket and 1 logical processors per socket, 1 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-10-26 18:40:22.34 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-10-26 18:40:22.34 Server Detected 8191 MB of RAM. This is an informational message; no user action is required.
2015-10-26 18:40:22.36 Server Using conventional memory in the memory manager.
2015-10-26 18:40:26.98 Server This instance of SQL Server last reported using a process ID of 1632 at 10/26/2015 5:39:29 PM (local) 10/26/2015 9:39:29 PM (UTC). This is an informational message only; no user action is required.
2015-10-26 18:40:27.01 Server Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-10-26 18:40:27.02 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.
2015-10-26 18:40:29.06 spid5s Starting up database 'master'.
2015-10-26 18:40:29.55 spid5s 82 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-10-26 18:40:29.94 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-10-26 18:40:31.69 Server CLR version v4.0.30319 loaded.
2015-10-26 18:40:33.59 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-10-26 18:40:33.69 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-10-26 18:40:37.03 spid5s SQL Trace ID 1 was started by login "sa".
2015-10-26 18:40:37.38 spid5s Server name is 'DGI-SQL2012'. This is an informational message only. No user action is required.
2015-10-26 18:40:39.44 spid10s A self-generated certificate was successfully loaded for encryption.
2015-10-26 18:40:40.48 spid10s Server is listening on [ 'any' <ipv6> 1433].
2015-10-26 18:40:40.48 spid10s Server is listening on [ 'any' <ipv4> 1433].
2015-10-26 18:40:40.55 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2015-10-26 18:40:40.55 spid10s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2015-10-26 18:40:40.55 Server Server is listening on [ ::1 <ipv6> 1434].
2015-10-26 18:40:40.55 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2015-10-26 18:40:40.55 Server Dedicated admin connection support was established for listening locally on port 1434.
2015-10-26 18:40:40.64 spid10s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-10-26 18:40:40.64 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2015-10-26 18:40:40.67 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/DGI-SQL2012.DGI.local ] for the SQL Server service.
2015-10-26 18:40:40.67 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/DGI-SQL2012.DGI.local:1433 ] for the SQL Server service.
2015-10-26 18:40:42.03 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.03 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'SharePoint_AdminContent_74a23c8e-e86f-4ee1-8a80-5bc0f70aa9d5'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.03 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.03 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'Search_Service_Application_DB_40b85c54b831469b89c9019d627cacf5'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.03 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.03 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'SharePoint_Config'. [CLIENT: 192.168.0.155]
2015-10-26 18:40:42.04 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.04 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'SharePoint_Config'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.04 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.04 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_mysite_2626'. [CLIENT: 192.168.0.155]
2015-10-26 18:40:42.04 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.04 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'Search_Service_Application_DB_40b85c54b831469b89c9019d627cacf5'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.19 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.19 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_spdataglove'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.19 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.19 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_8090SP'. [CLIENT: 192.168.0.155]
2015-10-26 18:40:42.19 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.19 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'Search_Service_Application_DB_40b85c54b831469b89c9019d627cacf5'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.20 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.20 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'SharePoint_AdminContent_74a23c8e-e86f-4ee1-8a80-5bc0f70aa9d5'. [CLIENT: 192.168.0.155]
2015-10-26 18:40:42.21 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.21 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_dell'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.22 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.22 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_spdataglove'. [CLIENT: 192.168.0.155]
2015-10-26 18:40:42.23 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.23 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_mysite_2626'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:42.23 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.23 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_dell'. [CLIENT: 192.168.0.155]
2015-10-26 18:40:42.24 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:42.24 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'WSS_Content_8090SP'. [CLIENT: 192.168.0.158]
2015-10-26 18:40:44.22 Logon Error: 18456, Severity: 14, State: 38.
2015-10-26 18:40:44.22 Logon Login failed for user 'DGI\SPSQLSvc'. Reason: Failed to open the explicitly specified database 'Search_Service_Application_DB_40b85c54b831469b89c9019d627cacf5'. [CLIENT: 192.168.0.158]
October 27, 2015 at 12:59 am
You sure you posted complete error log?
October 27, 2015 at 11:12 am
That's right, that's all I see in the error log. It is strange that nothing is recorded in the error log file.
The server went into a continuous loop of rebooting until we stopped the SQL Services. The server is probably overloaded when the SQL Services are started and it will show up BSOD "Critical_process_Died" error.
October 27, 2015 at 11:19 am
Quick question, have you tried starting the SQL Server in single-user mode?
😎
October 27, 2015 at 11:27 am
sandeepraichura (10/26/2015)
I'm running SQL 2012 on a Win 2012 VM and the SQL server shuts down automatically after starting the SQL Server & SQL Server Agent Jobs.Did anyone came across this issue ?
What you really mean is that when we start the SQL Server and SQL Agent services, the WINDOWS server re-boots itself, correct?
For starters, look at the properties of the service in Administrative tools, Services. On the Recovery tab, was this service set to "Restart the computer" if a failure to start occurs? If so, then change that to "Take no Action".
Secondly, from the logs, it appears that the service account 'DGI\SPSQLSvc' cannot log into the server. Please if this is a valid account and password by attempting to log in to another PC, or, use run as, with this account.
Third, change the service account to "local system account" and see if your problems go away.
What do the Windows event logs say?
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
October 27, 2015 at 11:28 am
Nothing wrong with SQL Server here, it's starting up fine.
2015-10-26 18:40:40.64 spid10s SQL Server is now ready for client connections. This is an informational message; no user action is required.
You're probably going to have to debug this at the Windows level if you're having blue screens. Those aren't SQL errors.
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
October 27, 2015 at 12:57 pm
thanks for your help, I also thought the same but the server reboots only after the SQL Services are started so I thought SQL side to be checked before we isolate it to be an OS issue.
Really appreciate your responses ! thanks again.
October 27, 2015 at 10:27 pm
There's something seriously wrong, it just looks from the error log that SQL's the victim, not the cause. All the login failures are because SQL can't open the various databases, which suggests either databases missing or files missing (maybe drives missing) or similar.
And a one-core VM?
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
October 27, 2015 at 10:29 pm
Michael L John (10/27/2015)
Secondly, from the logs, it appears that the service account 'DGI\SPSQLSvc' cannot log into the server.
That's the sharepoint service account by all appearances (trying to connect to all the Sharepoint databases).
From the error log:
The service account is 'DGI\DGI-SQL2012$'
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
Viewing 14 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply