SQL Server Connection Error (Win32Exception: Unknown error (0x89c5010a))

Question

SQL Server Connection Error (Win32Exception: Unknown error (0x89c5010a))

Haleniuk Maksum 10

I am encountering an issue while attempting to establish a connection to SQL Server. The following error message is displayed:

Win32Exception: Unknown error (0x89c5010a)
SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. Error occurred during LocalDB instance startup: SQL Server process failed to start.)

I have verified the instance name and checked the configuration for remote connections, but I am still unable to resolve the issue.

Could you please provide guidance on how to troubleshoot this error? Any assistance you can offer would be greatly appreciated.

Thank you for your help!

Ответ

4 answers

Your answer

Answer 1

Erland Sommarskog 121.4K MVP Volunteer Moderator

There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Users\galen\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb\master.mdf.

There we have it. You are running into a known issue where Windows 11 reports a disc-sector size that SQL Server cannot cope with. Microsoft has published an article with workarounds for the problem.

Answer 2

Olaf Helper 47,436

Error occurred during LocalDB instance startup: SQL Server process failed to start.

Lookup Windows EventLog and SQL Server ErrorLog file for more details about the failure.

Haleniuk Maksum 10 Reputation points

2024-10-04T15:04:20.44+00:00
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2024-10-04T21:59:00.6166667+00:00

So what are your regional settings set to?

Answer 3

ZoeHui-MSFT 41,491

Hi @Haleniuk Maksum,

You can recreate the MSSQLLocalDB instance and registry entries by running these commands from a command prompt:

sqllocaldb delete MSSQLLocalDB

sqllocaldb create MSSQLLocalDB -s

Regards，

Zoe Hui

If the answer is helpful, please click "Accept Answer" and upvote it.

Haleniuk Maksum 10 Reputation points

2024-10-07T08:27:32.3733333+00:00

Hi Zoe,

Thank you for the instructions, but unfortunately, they didn’t resolve the issue. I followed the steps to recreate the MSSQLLocalDB instance, but the problem still persists.

Do you have any other suggestions, or perhaps additional steps that might help fix the issue?

Thanks for your assistance!

Regards, @Haleniuk Maksum
Haleniuk Maksum 10 Reputation points

2024-10-07T08:31:29.21+00:00

After running the command sqllocaldb create MSSQLLocalDB -s, I encountered the following error:

Creation of LocalDB instance "mssqllocaldb" failed because of the following error:

Error occurred during LocalDB instance startup: SQL Server process failed to start.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2024-10-07T21:08:12.3566667+00:00

Check the errorlog for instance to see why it does not start. You find it in C:\Users\YOURUSERNAME\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\MSSQLLocalDB\error.log.

Haleniuk Maksum 10


2024-10-09 09:51:02.93 Server      Microsoft SQL Server 2019 (RTM-CU27-GDR) (KB5040948) - 15.0.4382.1 (X64) 
	Jul  1 2024 20:03:23 
	Copyright (C) 2019 Microsoft Corporation
	Express Edition (64-bit) on Windows 10 Home Single Language 10.0 <X64> (Build 22631: )

2024-10-09 09:51:02.95 Server      UTC adjustment: 3:00
2024-10-09 09:51:02.95 Server      (c) Microsoft Corporation.
2024-10-09 09:51:02.95 Server      All rights reserved.
2024-10-09 09:51:02.95 Server      Server process ID is 27084.
2024-10-09 09:51:02.95 Server      System Manufacturer: 'LENOVO', System Model: '82K0'.
2024-10-09 09:51:02.95 Server      Authentication mode is MIXED.
2024-10-09 09:51:02.95 Server      Logging SQL Server messages in file 'C:\Users\galen\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb\error.log'.
2024-10-09 09:51:02.95 Server      The service account is 'LEGION_GALYA\galen'. This is an informational message; no user action is required.
2024-10-09 09:51:02.95 Server      Command Line Startup Parameters:
	 -c
	 -S "MSSQL15E.LOCALDB"
	 -s "LOCALDB#EF2F87CC"
	 -d "C:\Users\galen\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb\master.mdf"
	 -l "C:\Users\galen\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb\mastlog.ldf"
	 -e "C:\Users\galen\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb\error.log"
2024-10-09 09:51:02.96 Server      SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2024-10-09 09:51:02.96 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-10-09 09:51:02.96 Server      Detected 16236 MB of RAM. This is an informational message; no user action is required.
2024-10-09 09:51:02.96 Server      Using conventional memory in the memory manager.
2024-10-09 09:51:02.96 Server      Page exclusion bitmap is enabled.
2024-10-09 09:51:03.04 Server      Buffer Pool: Allocating 1048576 bytes for 588581 hashPages.
2024-10-09 09:51:03.05 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2024-10-09 09:51:03.14 Server      Buffer pool extension is already disabled. No action is necessary.
2024-10-09 09:51:03.30 Server      Query Store settings initialized with enabled = 1, 
2024-10-09 09:51:03.31 Server      The maximum number of dedicated administrator connections for this instance is '1'
2024-10-09 09:51:03.32 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.
2024-10-09 09:51:03.33 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.
2024-10-09 09:51:03.34 Server      In-Memory OLTP initialized on lowend machine.
2024-10-09 09:51:03.36 Server      [INFO] Created Extended Events session 'hkenginexesession'
2024-10-09 09:51:03.36 Server      Database Instant File Initialization: disabled. 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.
2024-10-09 09:51:03.37 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2024-10-09 09:51:03.38 Server      clwb is selected for pmem flush operation.
2024-10-09 09:51:03.38 Server      Software Usage Metrics is disabled.
2024-10-09 09:51:03.39 spid9s      Starting up database 'master'.
2024-10-09 09:51:03.42 spid9s      There have been 256 misaligned log IOs which required falling back to synchronous IO.  The current IO is on file C:\Users\galen\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb\master.mdf.
2024-10-09 09:51:03.43 Server      CLR version v4.0.30319 loaded.

Julie Campbell 0 Reputation points

2024-10-19T01:26:53.0066667+00:00

I am having the same issue:

:>"C:\Program Files\Microsoft SQL Server\160\Tools\Binn\SqlLocaldb.exe" stop

LocalDB instance "MSSQLLocalDB" stopped.

C:>"C:\Program Files\Microsoft SQL Server\160\Tools\Binn\SqlLocaldb.exe" delete julie

LocalDB instance "julie" deleted.

C:>"C:\Program Files\Microsoft SQL Server\160\Tools\Binn\SqlLocaldb.exe" create julie -s

Creation of LocalDB instance "julie" failed because of the following error:

Error occurred during LocalDB instance startup: SQL Server process failed to start.
Julie Campbell 0 Reputation points

2024-10-19T01:30:58.75+00:00

I thought the problem might be admin rights (which I have, it's my personal laptop/domain), but I tried to start sqllocaldb and got this:
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2024-10-19T07:56:31.4+00:00

Julie, first whatever you got, it did not make it to the forum.

Second, please review the thread, check out the SQL Server errorlog, and see my Answer in the thread. If that answer does not apply to you, do not post anything in this thread, but ask a new Question.
Julie Campbell 0 Reputation points

2024-10-19T11:56:20.1533333+00:00

Erland,

First, I tried creating a new question. I composed correctly enough to get to the human puzzle check which I passed, then to a 401 page. I did this multiple times, same result. There is/was a problem with asking questions to this forum on the learn.microsoft side.

Second, my error log didn't have anything useful in it, though you mentioned the 4096 byte sector size issue. It was necessary to work around this, but insufficient as there is also an account issue where NT AUTHORITY\NETWORK SERVICE is the answer for the user to set up on a fresh installation.

I have added a complete answer here, as the entire point of anyone asking a question is getting them a complete answer. It was comprised of information found here:

https://stackoverflow.com/questions/19538089/wait-on-the-database-engine-recovery-handle-failed-check-the-sql-server-error-l

Answer 4

Haleniuk,

I was having the exact same problem you were. The error log was very long, very full of success messages, with no useful troubleshooting. After much internet search activity, I gave up on SQLLocalDB and went back to trying a SQLExpress installation. The help link Microsoft provides has nothing at all to do with the problem, it is to a Azure Arc page which is seems related but is not. There are two actions I took to get this working:

There is a known issue with Windows 11 and large hard drive sector sizes. The section Cause on this page fixes this.
https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size
There is a problem with the account validation. Using a fresh installation, try using NT AUTHORITY\NETWORK SERVICE.

Both issues are discussed here: https://stackoverflow.com/questions/19538089/wait-on-the-database-engine-recovery-handle-failed-check-the-sql-server-error-l

Share via

SQL Server Connection Error (Win32Exception: Unknown error (0x89c5010a))

4 answers

Your answer