Symptom
The following error occurs randomly when connecting to an Sql Server database (between 1% - 20% connections).
This may happen in the Designer (reverse, consult data) or in the Runtime (executing processes, connecting to log database) or in Analytics (consulting sessions from log database).
java.sql.SQLException: SQL Exception
at com.indy.engine.main.connections.b.b(SourceFile:247)
at com.indy.engine.main.connections.b.a(SourceFile:368)
at com.indy.engine.main.connections.b.a(SourceFile:444)
at com.indy.engine.main.connections.JDBCConnectionContainerI.openConnection(SourceFile:273)
at com.indy.engine.action.common.ActionCodeTypeI.setConnection(SourceFile:478)
at com.indy.engine.actionCodes.SqlFileExportActionCodeI.executeSimpleCode(SourceFile:805)
at com.indy.engine.action.common.ActionCodeTypeI.executeCode(SourceFile:1646)
at com.indy.engine.action.common.ActionCodeTypeI.run(SourceFile:1805)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SQL Server returned an incomplete response.)
at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at com.indy.engine.main.connections.b.b(SourceFile:228)
[...]
Solution
Please read through this Microsoft knowledge base entry:
One possible solution is to upgrade your Sql Server JDBC driver. Make sure that you remove the old jdbc jar file from the Runtime directory tree. Also make sure that your Stambia application uses the required Java version indicated by Microsoft.