This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Microsoft Engineer:
I am a product personnel at Linatech Medical Company. When we use Microsoft products again, we need help analyzing technical issues:
issues：(Hardware: Dell3660PC)
Installation method 1:
Microsoft SQL Server programs and instances, installed in different partitions, SQL services cannot start after the Win system is turned on
Microsoft SQL Server program, C:\
Microsoft SQL Server instance, D:\
Win system startup，SQL service failed to start. Occasionally, successful startup may result in failures when accessing instances; The system is manually restarted (hot start), that is, the service is successfully started, then turned on (cold start) after shutting down again, and the fault reappears
Installation method 2:
Microsoft SQL Server program and instance, install the same partition, and the SQL service starts normally after the Win system is turned on
Microsoft SQL Server program, C:\
Microsoft SQL Server instance, C:\
Win system startup，SQL service started successfully, accessing instance is normal!
Pj Zhao
Linatech Medical Company
Hi @Lina
You can refer to the link provided by Olaf to view the error log. This allows us to find a workaround based on the error log.
Review SQL Server ErrorLog file and Windows EventLog for more details about the failure.
Please refer to SQL Server ErrorLog file and Windows EventLog as below，Thanks！
Thank Olaf and Percy！
Refer to SQL Server ErrorLog file and Windows EventLog as below
2023-05-11 09:29:43.75 Server Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
Jun 28 2012 08:36:30
Copyright (c) Microsoft Corporation
Express Edition with Advanced Services (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2023-05-11 09:29:43.77 Server (c) Microsoft Corporation.
2023-05-11 09:29:43.77 Server All rights reserved.
2023-05-11 09:29:43.77 Server Server process ID is 4984.
2023-05-11 09:29:43.77 Server System Manufacturer: 'Dell Inc.', System Model: 'Precision 3660'.
2023-05-11 09:29:43.77 Server Authentication mode is MIXED.
2023-05-11 09:29:43.77 Server Logging SQL Server messages in file 'd:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2023-05-11 09:29:43.77 Server This instance of SQL Server last reported using a process ID of 3320 at 2023/5/11 9:29:10 (local) 2023/5/11 1:29:10 (UTC). This is an informational message only; no user action is required.
2023-05-11 09:29:43.77 Server Registry startup parameters:
-d d:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\master.mdf
-e d:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l d:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2023-05-11 09:29:43.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-05-11 09:29:43.79 Server Detected 20 CPUs. This is an informational message; no user action is required.
2023-05-11 09:29:44.18 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.
2023-05-11 09:29:44.18 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2023-05-11 09:29:44.28 Server Node configuration: node 0: CPU mask: 0x00000000000fffff:0 Active CPU mask: 0x00000000000fffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2023-05-11 09:29:44.40 spid6s Starting up database 'master'.
2023-05-11 09:29:44.50 spid6s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2023-05-11 09:29:44.60 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2023-05-11 09:29:44.68 spid6s SQL Trace ID 1 was started by login "sa".
2023-05-11 09:29:44.70 spid6s Starting up database 'mssqlsystemresource'.
2023-05-11 09:29:44.71 spid6s The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
2023-05-11 09:29:44.82 spid10s Starting up database 'model'.
2023-05-11 09:29:44.82 spid6s Server name is 'DESKTOP-BIUTE1P\SQLEXPRESS'. This is an informational message only. No user action is required.
2023-05-11 09:29:44.87 spid6s Informational: No full-text supported languages found.
2023-05-11 09:29:44.87 Server A self-generated certificate was successfully loaded for encryption.
2023-05-11 09:29:44.87 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2023-05-11 09:29:44.87 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2023-05-11 09:29:44.87 spid6s Starting up database 'msdb'.
2023-05-11 09:29:44.87 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2023-05-11 09:29:44.87 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2023-05-11 09:29:44.87 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2023-05-11 09:29:45.11 spid10s Clearing tempdb database.
2023-05-11 09:29:45.37 spid10s Starting up database 'tempdb'.
2023-05-11 09:29:45.43 spid13s The Service Broker protocol transport is disabled or not configured.
2023-05-11 09:29:45.43 spid13s The Database Mirroring protocol transport is disabled or not configured.
2023-05-11 09:29:45.48 spid13s Service Broker manager has started.
2023-05-11 09:29:45.48 spid6s Recovery is complete. This is an informational message only. No user action is required.
Please Refer to attached txt file！
lina
LinaTech