Error with SQLServer

Question

Error with SQLServer

Anonymous

I am using visual studio 2022 and i am trying to update my database with .NET, the build is succeeding however, towards the end I get this error and it doesn't work: 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: SNI_PN11, error: 50 - Local Database Runtime error occurred. Error occurred during LocalDB instance startup: SQL Server process failed to start. what could be the cause of this? Am I missing a configuration file or an extension/tool. I tried to run the SQLServer from services, since it wasn't running before. This gave me an error, I've uninstalled and reinstalled SQL Expr 2022 a few times to no avail.

Erland Sommarskog 133.9K Reputation points MVP Volunteer Moderator

2024-01-25T22:24:48.41+00:00

Do you have a folder "C:\Users\sommar\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances" If so, what folders do you have?

Assuming that there is a folder MSSQLLocalDB, does this folder have file error.log? If so, can you share it?

Anonymous

Hi all, thank you all for your replies, to give more detail, I'm trying to run a MVC application in VS2022. The migration builds, however when I update the database I get this output:

PM> update-database
Build started...
Build succeeded.
Microsoft.Data.SqlClient.SqlException (0x80131904): 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: SNI_PN11, error: 50 - Local Database Runtime error occurred. Error occurred during LocalDB instance startup: SQL Server process failed to start.
)
 ---> System.ComponentModel.Win32Exception (0x89C5010A): Unknown error (0x89c5010a)
   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnectionString connectionOptions, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.OpenDbConnection(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.<>c__DisplayClass18_0.<Exists>b__0(DateTime giveUp)
   at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.<>c__DisplayClass12_0`2.<Execute>b__0(DbContext _, TState s)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state, Func`3 operation, Func`3 verifySucceeded)
   at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy, TState state, Func`2 operation, Func`2 verifySucceeded)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists(Boolean retryOnNotExists)
   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists()
   at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists()
   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
   at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.UpdateDatabase(String targetMigration, String connectionString, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabaseImpl(String targetMigration, String connectionString, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabase.<>c__DisplayClass0_0.<.ctor>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:-1983577846,State:0,Class:20
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: SNI_PN11, error: 50 - Local Database Runtime error occurred. Error occurred during LocalDB instance startup: SQL Server process failed to start.
)

This is my connection string:

{   "Logging": {     "LogLevel": {       "Default": "Information",       "Microsoft.AspNetCore": "Warning"     }   },   "ConnectionStrings": {     "DefaultConnection": "Server=(localdb)\\MSSQLLocalDB;Database=AppDB; Trusted_Connection=True"   },   "AllowedHosts": "*" }

Anonymous

2024-01-26T10:01:20.58+00:00

SQLServer_ERRORLOG_2024-01-26T09.57.15.txt
Anonymous

2024-01-26T10:02:22.4866667+00:00

The only error I see is to do with the Firewall, I don't use an overly oppressive firewall, even then I've completely disabled it all and tried to install it before and it didn't help.Summary_LAPTOP-2AH94KDE_20240126_095558.txt

3 answers

Your answer

Erland Sommarskog 133.9K Reputation points MVP Volunteer Moderator

2024-01-25T22:24:48.41+00:00

Do you have a folder "C:\Users\sommar\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances" If so, what folders do you have?

Assuming that there is a folder MSSQLLocalDB, does this folder have file error.log? If so, can you share it?
Anonymous

2024-01-26T10:01:20.58+00:00

SQLServer_ERRORLOG_2024-01-26T09.57.15.txt
Anonymous

2024-01-26T10:02:22.4866667+00:00

The only error I see is to do with the Firewall, I don't use an overly oppressive firewall, even then I've completely disabled it all and tried to install it before and it didn't help.Summary_LAPTOP-2AH94KDE_20240126_095558.txt

Answer 1

The error log has this message:

2024-01-26 09:57:14.76 spid23s 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\MSSQL16.SQLEXPRESS01\MSSQL\Template Data\master.mdf.

This is a known issue where Windows 11 for some disk drives reports a sector size that SQL Server does not cope with. Microsoft has published an article with workarounds for the problem.

Your setup has not completed, so your Express instance is likely to be half-baked. Then again, once you have applied the instructions in the article, localdb may work. (But I don't know for sure that it will.)

Answer 2

Hi @Thomas Gillanders - STUDENT,

First please make sure that you have installed SQL Server successfully.

You may connect to the server locally for a try or follow the steps to check.

Click Start, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager.

If you do not have these entries on the Start menu, SQL Server is not correctly installed. Run Setup to install the SQL Server Database Engine.

If you have already installed SQL Server, please follow the documentation to troubleshooting.

Regards，

Zoe Hui

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

Answer 3

Michael Taylor 61,221

The error indicates you have a bad connection string to the database. Please show us the connection string your application is using.

SQL Express is really not used anymore. If you install Visual Studio 2017 (maybe even earlier) or higher then it automatically installs a local, non-service, instance of SQL called LocalDB. This is the instance that you generally develop against. In SQL Server Object Explorer you can see your LocalDB instance. If you are also creating a SQL Project for your database then it shows up as well. This LocalDB instance is run only while VS is debugging your code. You can get the connection string to use by right clicking the database in SQL Server Object Explorer and viewing the properties.

If you are running your own SQL Server instance (Developer edition is free) then that will be installed as a service. You need to ensure the service is running. Then ensure your connection string is using that SQL Server instance. You can get that information from SQL Server Management Studio.

Anonymous

2024-01-26T09:59:47.7833333+00:00

I've had issues fully installing SQL Server, It fails right as it completes.
Anonymous

2024-01-26T10:04:23.68+00:00

I dont believe this is the issue, I've posted the connection string in the thread, I've used it on the university pc's and the issue didn't occur, unfortunately this isn't a solution to just use university machines as I would need to work on the project more time than the class time would give me.
Michael Taylor 61,221 Reputation points

2024-01-26T15:09:21.3+00:00

Go to SQL Server Object Explorer. Does the (localdb)\MSSQLLocalDB instance show up? How about the database that you're connecting to? If it doesn't then the connection string you're using doesn't line up with what is actually available. Did you deploy your database to your local SQL instance?
Anonymous

2024-01-26T18:10:57.1233333+00:00

Hi michael, the database shows up! But I cant update it, the connection string/code is not the issue, I used the same code on a different machine and it works, I just need it to work on my laptop also.

Share via

Error with SQLServer

3 answers

Your answer