Portal

Hello,

I'm facing issues while trying to execute deliveries in the command prompt.

The runtime is installed properly, and I'm able to connect to it from the Designer, initiating the flow without errors.

 However, when I run startdelivery.bat -name DHB_DAX_DHB_REF_TSV_DPT, I encounter an error:

com.microsoft.sqlserver.jdbc.SQLServerException: Le pilote n'a pas pu Útablir de connexion sÚcurisÚe au serveur SQL Server Ó l'aide du chiffrement SSL (Secure Sockets Layer). Erreurá: ½áThe server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]á╗. ClientConnectionId:48c9478d-4ace-44d4-88de-5751c5bd654f

        at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2924)

        at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1881)

        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2484)

        at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2142)

        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1993)

        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1164)

        at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:760)

        at com.indy.engine.main.connections.SecuredJdbcDataSource.connectWithStandardJdbc(SecuredJdbcDataSource.java:130)

        at com.indy.runtime.jdbc.JdbcDataSource.getConnection(JdbcDataSource.java:619)

        at com.indy.runtime.jdbc.JdbcDataSource.getConnection(JdbcDataSource.java:130)

        at com.indy.engine.main.connections.jdbc.JDBCConnectionI.<init>(JDBCConnectionI.java:22)

        at com.indy.engine.main.connections.JDBCPoolManagerI.openNewConnection(JDBCPoolManagerI.java:244)

        at com.indy.engine.main.connections.JDBCPoolManagerI.initPool(JDBCPoolManagerI.java:321)

        at com.indy.engine.main.connections.JDBCConnectionContainerI.<init>(JDBCConnectionContainerI.java:52)

        at com.indy.engine.manager.Action$ActionContextI.createJdbcContainer(Action.java:1694)

        at com.indy.engine.manager.ActionCodeExecutor.setConnection(ActionCodeExecutor.java:845)

        at com.indy.engine.action.common.ActionCodeTypeI.setConnection(ActionCodeTypeI.java:186)

        at com.indy.engine.actionCodes.JdbcActionCodeI.executeDDL_DML(JdbcActionCodeI.java:770)

        at com.indy.engine.actionCodes.JdbcActionCodeI.executeSimpleCode(JdbcActionCodeI.java:1273)

        at com.indy.engine.manager.ActionCodeExecutor.executeCode(ActionCodeExecutor.java:138)

        at com.indy.engine.manager.ActionCodeExecutor.run(ActionCodeExecutor.java:265)

        at java.lang.Thread.run(Thread.java:750)

Hello,

The issue is coming from the Java version used.

The "startdelivery" command is using the Java version defined in your JAVA_HOME environment variable.

By directly modifying the initvariables.bat/.sh script to point to the correct Java version, we observed that the issue is resolved.

Ideally, it would be beneficial if you adjust the environment variables, enabling the use of scripts without manual modifications.