SQL connectivity issues
When you are connecting to the SQL Server instance hosting the Network Inventory database from your computer, these errors may occur:
These and other errors are caused by connectivity issues between your client computer and your SQL Server instance hosting the database. For example, the "SQL Server does not exist" error occurs when the client is unable to find the SQL Server. The "Error Locating Server/Instance Specified" error is caused by similar reasons.
Microsoft has published an extremely thorough article on how to troubleshoot SQL Server connectivity issues. See "Troubleshoot Connecting to the SQL Server Database Engine" at https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-2017.
Before you delve into troubleshooting specific connectivity errors, we recommend you to go through a sequence of easy steps that may resolve the majority of connectivity issues to SQL server.
Ensure SQL Server Browser service is running.
Ensure TCP/IP protocols are enabled.
Verify basic connectivity over IP address and check for any abnormalities: ping –a <SQL Server machine>, ping –a <SQL Server IP address>. If you notice any issues, work with your network administrator to fix the same.
Get the SQL Server instance TCP port. The default instance is listening on TCP 1433. If there is more than one instance of SQL Server installed, some instances must use other port numbers.
Ensure your firewall is configured properly: the SQL Server instance TCP port is opened.
Ensure the user has a login in your SQL Server instance and appropriate permissions to connect to the database that the user is trying to connect to.
Test your ability to connect to your SQL Server instance using TCP.
TIP: For example, using your PowerShell, execute this:
Test-NetConnection -ComputerName <SQL Server name or IP> -Port <SQL Server Port>
Test your ability to connect from a client application installed locally on the computer that is using SQL Server (use your SQL Server Management Studio).
TIP: If the user with Windows Authentication is experiencing login failures, try to use a Database Account with SQL Server authentication.