BW-JDBC-100034 “Configuration Test Failed. Exception [com.microsoft.sqlserver.jdbc.SQLServerException] occurred. com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
<ns1:JDBCSQLException xmlns:ns1 = “http://schemas.tibco.com/bw/plugins/jdbc/5.0/jdbcExceptions“>
<msg>”JDBC error reported: (SQLState = 08S01) – com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset ClientConnectionId:396457ef-182e-4ddb-8b50-57541ce45b3b”</msg>
<detailStr>com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset ClientConnectionId:396457ef-182e-4ddb-8b50-57541ce45b3b</detailStr>
I saw this issue in a Tibco BusinessWorks application using a SQL JDBC Driver 4.0 to connect to a SQL server 2008 R2 server. However, I believe that this could happen with any application written in Java/.NET using JDBC driver 4.0 connecting to SQL server 2008 R2 server.
Solution :- Check If at least Microsoft® SQL Server® 2008 R2 Service Pack 2 is installed on the SQL server. If not, install it. If SP2 or Higher (e.g. SP3) is already installed and you still see the same issue – problem is something else.
How to check If at least SP2 is installed?
Connect to the server from the SQL Management Studio and execute the below query :-
You should see the SP2 as the part of result
Why :- See below :-
FIX: You cannot connect to SQL Server by using JDBC Driver for SQL Server after you upgrade to JRE 6 update 29 or a later version
What If you can not install SP2
We should always update latest service packs on the SQL server – not only for this issue. However, If you couldn’t and you had to live with current database server install – try using the below attribute in your TRA files.
If you are trying to test connection from the Tibco BusinessWorks Designer, add the above attribute in your <TIBCO_HOME>\designer\5.8\bin\designer.tra file.
If you want to deploy this change, add the above attribute in your <TIBCO_HOME>\domain\<Domain Name>\application\<Application>\<Application>.tra file and restart the service instances of the application.
This same issue does not happen when you connect to Sql server 2005. That’s weird! Sounds like somebody broke something in Sql 2008 R2 and fixed it in SP2.
Version number for SQL server in RTM and service packs.