Case 3: Are the credentials correct?  

Try connecting the SQL Server instance via SQL Server Management Studio using the same credentials.

Note: Connect using the TCP port instead of the instance name, as EventLog Analyzer uses TCP/IP.

Case 4: Is TCP/IP enabled?  

EventLog Analyzer connects to SQL Server using TCP/IP, so ensure that TCP/IP is enabled for the instance.

Troubleshooting:

1. In the SQL Server Configuration Manager console, click SQL Server Network Configuration.

2. Double-click Protocols for (the required instance). In the center pane, under the Protocol Name column, ensure TCP/IP is Enabled. If Disabled:

1. Double-click TCP/IP, toggle the Enabled status from No to Yes and click OK.

2. Restart the SQL Server instance.

Case 5: Is the SQL Server instance using a static port?  

The SQL Server instance should not use a dynamic port.

Troubleshooting:

1. In the SQL Server Configuration Manager console, click SQL Server Network Configuration.

2. Double-click Protocols for (the required instance). In the center pane, under the Protocol Name column, double-click TCP/IP.

3. In the TCP/IP Properties pop-up, click the IP Addresses menu, and go to the IPAll section at the bottom.

4. Ensure that the TCP Dynamic Ports field is empty.

Case 6: Are the required ports allowed?  

The following ports should be allowed through the firewall for remote connection:

1. UDP 1434 (used by the SQL Server Browser Service, which holds the instance details)

2. The TCP port used by the SQL Server instance

Note: To find the TCP port used by an SQL Server instance:

1. In the SQL Server Configuration Manager console, click SQL Server Network Configuration.

2. Double-click Protocols for (the required instance). In the center-pane, under the Protocol Name column, double-click TCP/IP.

3. In the TCP/IP Properties pop-up, click the IP Addresses menu, and go to the IPAll section at the bottom. The TCP Port value is the port used by this SQL Server instance.

Note:

In addition to checking the Windows Defender Firewall, ensure that no other third-party firewall is blocking the required ports.

Case 7: If SQL authentication is used, ensure SQL Server and Windows Authentication mode is enabled.  

Open EventLog Analyzer and go to Settings > Database Audit > SQL Servers > Add Instance(s) > Add SQL Server Instance > SQL Server Instance Configuration > Instance Authentication. If SQL Authentication has been selected, ensure that the SQL Server and Windows Authentication mode is enabled for that instance in SQL Server.

Steps:

1. Connect to the SQL Server instance via SQL Server Management Studio.

2. Right-click on the instance name in the left pane > Properties > Security.

3. Under the Server authentication section, ensure that SQL Server and Windows Authentication mode is enabled.

Case 8: Is remote connection enabled?  

If EventLog Analyzer and SQL Server are running in different machines, then:

1. Connect to the SQL Server instance via SQL Server Management Studio.

2. Right-click on the instance name in the left pane > Properties > Connections.

3. Under the Remote server connections section, ensure that Allow remote connections to this server is enabled.

  Case 9: If SQL Server is running remotely, is the SQL Server Management Studio or sqlcmd utility able to establish connection?  

If SQL Server Management Studio is installed in the machine where EventLog Analyzer is installed, remote connectivity can be checked using SQL Server Management Studio itself. If not, please install the sqlcmd utility in the machine in which EventLog Analyzer is installed to check remote connectivity.

Troubleshooting steps using the sqlcmd utility:

1. Execute the following command using the Command Prompt using administrator privileges.

a. Fomat for Windows authentication:
sqlcmd -S serverName,port
Example:
sqlcmd -S vaisali-4071,1436
Example of a successful connection:

b. Fomat for SQL Server authentication:
sqlcmd -S serverName,port -U userName
Example:
sqlcmd -S vaisali-4071,1436
Example of a successful connection:

Example of a failed connection: