Microsoft SQL Server Error:26

Ahsen Tosun 0 Reputation points

what's the problem?

Cannot connect to ------------------------------


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: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click:

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
11,001 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Olaf Helper 34,276 Reputation points

    Verify that the instance name is correct

    First step is to do what the error message says.

    0 comments No comments

  2. Erland Sommarskog 88,161 Reputation points

    This is general error which says that you were not able to connect to the SQL Server instance you tried to connect to. Since we don't know you environment or why you think conncetion should succeed, we can't what is wrong.

    Common reasons include:

    • Fat-fingering server and/or instance name.
    • SQL Server is not running.
    • Firewalls blocking the way,
    • It's a named instance and the Browser is not running or blocked by firewall.

    See furhter this troubleshooter.

    0 comments No comments

  3. Rahul Randive 4,461 Reputation points Microsoft Employee

    Hi @Ahsen Tosun

    Please provide details about your environment, whether it's SQL on-premise, Azure SQL VM, or Azure SQL Database.

    Are you connecting from your local machine and experiencing issues? Have you checked your network configuration.

    Was it working before and failing now, or is it a new setup. Is anyone else able to connect?

    Here is Microsoft document for reference for such error-

    And the blog (if its SQL on-premise or Azure SQL VM)

    Thank you.

    0 comments No comments