Click here to Skip to main content
15,891,204 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
See more:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connection.(Provider: SQL Network Interfaces, Error:52 - Unable to locate a Local Database Runtime installation. Verify that SQL Server Express is properly installed and that the Local Database Runtime feature is enabled.)

What I have tried:

I have searched but not resolved.
Posted
Updated 18-Dec-17 5:33am
Comments
Jochen Arndt 7-Mar-17 7:30am    
No need to search. Just do what the error message suggests:

"Verify that the instance name is correct and that SQL Server is configured to allow remote connection.
...
Verify that SQL Server Express is properly installed and that the Local Database Runtime feature is enabled."

Nobody here can help because only you can do the above verifications.
Ajit Kumar Pandit 8-Mar-17 3:54am    
Alright sir. I have got the solution. Thanks.

The error message is pretty explicit:
Verify that the instance name is correct and that SQL Server is configured to allow remote connection.(Provider: SQL Network Interfaces, Error:52 - Unable to locate a Local Database Runtime installation. Verify that SQL Server Express is properly installed and that the Local Database Runtime feature is enabled.)

So start by looking at the connection string you are using, and verify that the server instance it refers to can be accessed from the PC you are running the code on.
Then check the login details in the string, and finally that the SQL server instance is configured for remote connections (many aren't for security reasons).

Sorry, but we can't do any of that for you: we can't access your connection string, or the SQL Server you are trying to use.
 
Share this answer
 
Comments
Ajit Kumar Pandit 8-Mar-17 3:54am    
Thanks
Hello You need to install
SQL2022-SSEI-Expr
. It should solve your issue.
https://go.microsoft.com/fwlink/p/?linkid=2216019&clcid=0x4009&culture=en-in&country=in
 
Share this answer
 
Comments
CHill60 23-Aug-23 6:36am    
Highly unlikely just doing that would solve anything, especially if the wrong connection string has been used. Apart from that SQL 2022 wasn't available to the OP in 2017

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900