Hello! I would like some help, on my Commserve server, the Commvault Workflow Engine Service does not start at all. I've tried several ways to fix it.
---Sorry for the writing, I'm Brazilian.
Solved
Commvault Workflow Engine Service does not start at all
+2Best answer by Nutan Pawar G
You are unable to start workflow engine due to unsupported version of SQL Server for TLS 1.2.
It is recommended to be on the supported SQL version or install latest CU.
WorkflowEngine.log
==============
12660 1 07/24 16:56:04 ### WorkflowEngine: ********************************************
12660 1 07/24 16:56:04 ### WorkflowEngine: starting workflow engine
12660 1 07/24 16:56:04 ### WorkflowEngine: ********************************************
12660 1 07/24 16:56:05 ### WorkflowConnection: ERROR: failed to connect to database with error [The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:2dd1c404-feb5-42c1-acae-4b996802c879]. check the KB article KB3135244 to make sure you are running a supported version of SQL Server for TLS 1.2
Database Engine
The Commvault software embeds Microsoft SQL Server as its database engine. The following table shows the releases of MS SQL Server that are supported for the different releases of the Commvault software.
The MS SQL Server application that is installed on the CommServe computer must be dedicated to support the software and cannot be shared by other applications.
| Microsoft SQL Server release | Supported editions | Installed by default when you create a new CommServe server | Certified cumulative update/service pack | Microsoft information about scalability, performance, and other supported features
|
|---|---|---|---|---|
| Microsoft SQL Server 2019 |
| Standard edition only with Feature Release 11.24 and more recent releases. | Cumulative Update 16 | |
| Microsoft SQL Server 2017 |
|
| Cumulative Update 22 (RTM-CU22) | |
| Microsoft SQL Server 2016 Note: In virtual environments, for MS SQL Server 2016, set the socket count and the core count to 4. |
| Feature Release 11.16 and more recent releases. | Service Pack 3 |
Later MS SQL Server service packs and updates must be installed manually. You must update the MS SQL Server with any important updates released by Microsoft.
- Vaulter
- 92 replies
- Vaulter
- 141 replies
Also, check if the SQL browser service is running if it is not running then start the same from CS(Services.msc) and check the status.
+2
Here is the requested log:
12660 1 07/24 16:56:04 ### WorkflowEngine: ********************************************
12660 1 07/24 16:56:04 ### WorkflowEngine: starting workflow engine
12660 1 07/24 16:56:04 ### WorkflowEngine: ********************************************
12660 1 07/24 16:56:05 ### WorkflowConnection: ERROR: failed to connect to database with error [The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:2dd1c404-feb5-42c1-acae-4b996802c879]. check the KB article KB3135244 to make sure you are running a supported version of SQL Server for TLS 1.2
12660 1 07/24 16:56:05 ### WorkflowConnection: ERROR: failed to connect to database with error [The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:40a4fed3-80cb-4c6d-a07c-4c6fd4050cc6]. check the KB article KB3135244 to make sure you are running a supported version of SQL Server for TLS 1.2
12660 1 07/24 16:56:05 ### Server: error initializing workflow engine
java.lang.Exception: failed to initializing workflow properties
at commvault.cte.workflow.WorkflowEngine.initialize(WorkflowEngine.java:154)
at commvault.cte.workflow.Server.main(Server.java:115)
Caused by: commvault.cte.db.CTEDBException: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:c09dde12-7b65-4a88-9222-9ed9f0f4ffde
at commvault.cte.workflow.db.WorkflowConnection$WorkflowReservation.getConnection(WorkflowConnection.java:377)
at commvault.cte.workflow.db.WorkflowConnection$WorkflowReservation.createStatement(WorkflowConnection.java:442)
at commvault.cte.workflow.db.WorkflowConnection$WorkflowReservation.executeQuery(WorkflowConnection.java:455)
at commvault.cte.db.CTEDBTableRow.fill(Unknown Source)
at commvault.cte.db.CTEDBTableRow.fill(Unknown Source)
at commvault.cte.workflow.utils.CommServUtils.getClientFromGUID(CommServUtils.java:544)
at commvault.cte.workflow.WorkflowProperties.initialize(WorkflowProperties.java:109)
at commvault.cte.workflow.WorkflowEngine.initialize(WorkflowEngine.java:152)
... 1 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:c09dde12-7b65-4a88-9222-9ed9f0f4ffde
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3422)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1916)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2970)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2628)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2471)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1470)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:915)
at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
at commvault.cte.workflow.db.WorkflowConnection$ConnectionObject.getConnection(WorkflowConnection.java:571)
at commvault.cte.workflow.db.WorkflowConnection$WorkflowReservation.getConnection(WorkflowConnection.java:375)
... 8 more
Caused by: javax.net.ssl.SSLHandshakeException: The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]
at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source)
at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source)
at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)
at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)
at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)
at java.base/sun.security.ssl.ServerHello$ServerHelloConsumer.onServerHello(Unknown Source)
at java.base/sun.security.ssl.ServerHello$ServerHelloConsumer.consume(Unknown Source)
at java.base/sun.security.ssl.SSLHandshake.consume(Unknown Source)
at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source)
at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source)
at java.base/sun.security.ssl.TransportContext.dispatch(Unknown Source)
at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1824)
... 17 more
+12- Vaulter
- 323 replies
Hello
What is the Commserve version you are using?
What is the SQL version running on the commserve? You can check it in Control Panel under Program and Features (Control Panel\Programs\Programs and Features).
Share the screenshot including the version details which is included on the extreme right of the screen.
Best,
Rajiv Singal
- Vaulter
- 92 replies
- Answer
You are unable to start workflow engine due to unsupported version of SQL Server for TLS 1.2.
It is recommended to be on the supported SQL version or install latest CU.
WorkflowEngine.log
==============
12660 1 07/24 16:56:04 ### WorkflowEngine: ********************************************
12660 1 07/24 16:56:04 ### WorkflowEngine: starting workflow engine
12660 1 07/24 16:56:04 ### WorkflowEngine: ********************************************
12660 1 07/24 16:56:05 ### WorkflowConnection: ERROR: failed to connect to database with error [The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId:2dd1c404-feb5-42c1-acae-4b996802c879]. check the KB article KB3135244 to make sure you are running a supported version of SQL Server for TLS 1.2
Database Engine
The Commvault software embeds Microsoft SQL Server as its database engine. The following table shows the releases of MS SQL Server that are supported for the different releases of the Commvault software.
The MS SQL Server application that is installed on the CommServe computer must be dedicated to support the software and cannot be shared by other applications.
| Microsoft SQL Server release | Supported editions | Installed by default when you create a new CommServe server | Certified cumulative update/service pack | Microsoft information about scalability, performance, and other supported features
|
|---|---|---|---|---|
| Microsoft SQL Server 2019 |
| Standard edition only with Feature Release 11.24 and more recent releases. | Cumulative Update 16 | |
| Microsoft SQL Server 2017 |
|
| Cumulative Update 22 (RTM-CU22) | |
| Microsoft SQL Server 2016 Note: In virtual environments, for MS SQL Server 2016, set the socket count and the core count to 4. |
| Feature Release 11.16 and more recent releases. | Service Pack 3 |
Later MS SQL Server service packs and updates must be installed manually. You must update the MS SQL Server with any important updates released by Microsoft.
+2
Dear Collegeas, thank you for your attention. I solved the problem, I was using version 11.28 and updated to 11.32. Hugs
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.