Situation:
We are running into issues during the installation process. We have not had issues while going through the installation wizard previously, but in one specific environment we are running into issues.
"Error in making connection to the database. Unable to get information from SQLServer: SQLS13
We have been able to verify that connection from the installation machine to the sql server machine can be accomplished, which rules out any firewall/network issues. We verified this by writing a powershell script that connects to the sql server using the same connection details (server name, instance, port, adeptia username, adeptia password) and querying the au_users table. We are able to run this query and receive query results fine from the same machine.
Cause:
Per the JTDS/JDBC documentation:
The exception you are getting is usually caused by a timeout. When connecting to named instances jTDS needs to connect via UDP to port 1434 to get information about available SQL Server instances. While doing this it times out, throwing the exception you see (which means that jTDS was not able to get information about the running instances).
On SQL Server 2005 the SQL Browser service must be running on the server host as the instance name lookup port UDP 1434 is hosted by this service on SQL Server 2005 rather than the SQL Server itself. The default install does not configure the SQL Browser service to start automatically so you must do it manually.
Solution:
Open the UDP port 1434 is on the SQL Server.
Workaround:
Skip the need for instance name discovery be simply targeting the instance specific port and dropping the instance specification from the connection url. For example, this worked:
jdbc:jtds:sqlserver://SERVERNAME:INSTANCE-SPECIFIC-PORT;
Note: If the SQL Server database is configured on multiple instances so during installation the Instance name should be mentioned in the following manner:
<DATABASENAME>;instance=<InstanceName>
Comments
0 comments
Article is closed for comments.