Ignition 7.9.21 and Java 1.8.0_201 Database Connection

Hi Guys,

I know this issue might be related to the TLS but I search the forum and I cannot find the java.security file on the Ignition install folder maybe someone can point me to the solutions. I also added the trustServerCertificate =true to the connection but error still exist. Below is the error.


org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (The TCP/IP connection to the host localhost, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".)
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.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.getConnectionInternal(DatasourceImpl.java:261)
at com.inductiveautomation.ignition.gateway.datasource.DatasourceImpl.runTest(DatasourceImpl.java:215)
at com.inductiveautomation.ignition.gateway.datasource.DatasourceManagerImpl$FaultedDatasourceRetryer.lambda$newRetryRunnable$0(DatasourceManagerImpl.java:1006)
at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$TrackedTask.run(BasicExecutionEngine.java:565)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Don't think it's TLS related. This is just a networking problem. Connection refused on the hostname and port you configured.

Interesting because I have an ASP.NET application hosted on the same server and I have no issues accessing the database. I know it is .NET Framework but I would expect the application to failed too.

Your other app might be going through named pipes or something. Open up SQL Server Configuration Manager and verify that TCP/IP connectivity is enabled for your SQL Server instance--it will be required for Ignition to communicate with it.

I want to apologized because I forgot to follow up and post my finding. IT change the TCP/IP port. At the beginning when I check I did not notice because I just look at the port configure to the IP address and did not scrolled to the end when they set the port for all the IP address. I change my connection to use the port number and everything started communicating.