Submit a ticketCall us

WebinarUpcoming Webinar: Easily Automate Backups and Simplify Log Message Management

Backing up your network configuration and logging data are a few steps to helping keep your network safe. In this in-depth webinar, we’ll show you how these tasks can be automated to save your IT team time while maintaining accurate archives of your data.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Cannot connect to the SQL server after migration or new installation

Cannot connect to the SQL server after migration or new installation


After migrating the SQL server to a new machine, or  deploying a new SQL server, you get the following error in the Configuration wizard when trying to configure the database:


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.


  • Orion


The SQL server is not configured to accept incoming connections.


  1. Use the name of the instance as well as the server.
    In the Configuration Wizard, make sure you enter the SQL Server name in the format:
  2. Make sure no firewall is blocking port 1433
    There should be no firewall between the Orion server and the SQL server, blocking communication on port 1433.
  3. Verify that the SQL Server Browser service is running:
    a. On the SQL Server, open services.msc.
    b. Verify that the SQL Server Browser service is NOT disabled, and is running.
    c. If it is stopped, start it.
  4. Verify that the TCP protocol is enabled on port 1433
    a. On the SQL Server, open SQL Server Configuration Manager.
    b. Under each category, make sure that TCP/IP is enabled under Client Protocols.
  5. Verify DNS is resolving the proper IP address/DNS name combination.
  6. If you need to, create a new user in the SQL Database via SQL Management Studio with sysadmin and dbowner rights. Run the Configuration Wizard and try to input this name instead of the default user.



Last modified