windows could not start sql server service on local computer Error :1067

Question

my sql server and local db not working even I tried by reinstalling. I checked in services.msc it shows sqlexpress services is stopped. After trying to start again I m getting "windows could not start sql server service on local computer Error:1067" Error
please help.

Answer 1

Hi @Prathamesh Shende ,

Please check the Application log, if the unopenable log file exists, verify the path that is set for the errorlog file by SQL Server configuration manager

Try to copy the path and verify that you can access the target in the path, if not, update the path to a valid folder and then restart the SQL Server service

Specific operation, please check out this doc:
Event ID 17058 and SQL Server doesn't start

---

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.

Answer 2

I m getting this errorlog
the path is correct
I really dont know what is the exact issue here -

2022-11-21 07:53:39.61 Server Authentication mode is WINDOWS-ONLY.
2022-11-21 07:53:39.61 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2022-11-21 07:53:39.61 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2022-11-21 07:53:39.61 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2022-11-21 07:53:39.61 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
-m "SqlSetup"
-Q
-q "SQL_Latin1_General_CP1_CI_AS"
-T 4022
-T 4010
-T 3659
-T 3610
-T 8015
-d "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data\master.mdf"
-l "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf"
2022-11-21 07:53:39.61 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-11-21 07:53:39.61 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-11-21 07:53:39.61 Server Detected 15790 MB of RAM. This is an informational message; no user action is required.
2022-11-21 07:53:39.61 Server Using conventional memory in the memory manager.
2022-11-21 07:53:39.62 Server Page exclusion bitmap is enabled.
2022-11-21 07:53:39.69 Server Buffer Pool: Allocating 2097152 bytes for 1912828 hashPages.
2022-11-21 07:53:39.69 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2022-11-21 07:53:39.72 Server Buffer pool extension is already disabled. No action is necessary.
2022-11-21 07:53:39.75 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2022-11-21 07:53:39.78 Server Query Store settings initialized with enabled = 1,
2022-11-21 07:53:39.78 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-11-21 07:53:39.79 Server This instance of SQL Server last reported using a process ID of 19440 at 21-11-2022 07:53:35 (local) 21-11-2022 02:23:35 (UTC). This is an informational message only; no user action is required.
2022-11-21 07:53:39.79 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2022-11-21 07:53:39.79 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.
2022-11-21 07:53:39.79 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2022-11-21 07:53:39.80 Server In-Memory OLTP initialized on standard machine.
2022-11-21 07:53:39.82 Server [INFO] Created Extended Events session 'hkenginexesession'

2022-11-21 07:53:39.82 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2022-11-21 07:53:39.82 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
2022-11-21 07:53:39.83 Server Database Mirroring Transport is disabled in the endpoint configuration.
2022-11-21 07:53:39.83 Server clwb is selected for pmem flush operation.
2022-11-21 07:53:39.84 Server Software Usage Metrics is disabled.
2022-11-21 07:53:39.84 spid10s Warning ******************
2022-11-21 07:53:39.84 spid10s SQL Server started in single-user mode. This an informational message only. No user action is required.
2022-11-21 07:53:39.84 spid10s Starting up database 'master'.
2022-11-21 07:53:39.86 spid10s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data\master.mdf.
2022-11-21 07:53:39.93 Server CLR version v4.0.30319 loaded.
2022-11-21 07:53:40.05 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\

Answer 3

Hi @Prathamesh Shende ,

There have been 256 misaligned log IOs which required falling back to synchronous IO.

Please try to add -T1800 the trace flag as a startup parameter, and then restart

https://www.mssqltips.com/sqlservertip/5942/sql-server-misaligned-log-ios-which-required-falling-back-to-synchronous-io/
https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/message-misaligned-log-ios-which-required-falling-back-to/ba-p/367796

-------------

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.