Error Code 3: MDB Tools install error. SSL handshake failed: The TDS protocol stream is not valid

Document ID : KB000049777
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

ITCM R12.5 installation fails during the MDB install with the following error:

Figure 1

The MDB.log shows the following errors:

12-25,14:05:01 "D:\Program Files\CA\SC\Mdb\Windows\jre\bin\java.exe" -Dfile.encoding=UTF-8 -Djava.library.path=".\lib" -Xmx256m -classpath "C:\Users\w99s05u0
\AppData\Local\Temp\ITRM\database\mdb_install\lib;C:\Users\w99s05u0\AppData\Local\Temp\ITRM\database\mdb_install\lib\mdbsetup.jar;C:\Users\w99s05u0
\AppData\Local\Temp\ITRM\database\mdb_install\lib\eTFWExplorer.jar;C:\Users\w99s05u0\AppData\Local\Temp\ITRM\database\mdb_install\lib\log4j-1.2.13.jar;C:\Users\w99s05u0
\AppData\Local\Temp\ITRM\database\mdb_install\lib\sqljdbc.jar;C:\Users\w99s05u0\AppData\Local\Temp\ITRM\database\mdb_install\lib\iijdbc.jar;C:\Users\w99s05u0
\AppData\Local\Temp\ITRM\database\mdb_install\lib\ojdbc14.jar" com.ca.mdbtools.Utilities -install -apply -verbose -driver mdb104 -schemadir "C:\Users\w99s05u0
\AppData\Local\Temp\ITRM\database\mdb_install\MDB104_mssql" -dbvendor mssql -dbhost INMUMV049SRV.ww930.my-it-solutions.net -db mdb  -dbport 1433 -statusdir "C:\Users\w99s05u0
\AppData\Local\Temp\ITRM\database\mdb_install" -statusstart 5 ...
12-25,14:05:02 INFO - ==========================================================
12-25,14:05:02 INFO - MDBTools Log - Sunday, December 25, 2011 at 2:05:02 PM IST
12-25,14:05:02 INFO - JVM Version: 1.6.0
12-25,14:05:02 INFO - MDBTools Version 1.5 SP1 (32)
12-25,14:05:02 INFO - ==========================================================
12-25,14:05:02 INFO - MDBTools_0101I - Command: install database schema from driver file.
12-25,14:05:02 INFO - MDBTools_0110I - As user: OS user.
12-25,14:05:02 INFO - MDBTools_0112I - For vendor: mssql.
Dec 25, 2011 2:05:02 PM com.microsoft.sqlserver.jdbc.TDSReader readPacket
WARNING: TDSReader@1878144 ( ConnectionID:1 TransactionID:0x0000000000000000) 
Unexpected message type:18 in TDS header; expected type:4
Dec 25, 2011 2:05:02 PM com.microsoft.sqlserver.jdbc.TDSReader throwInvalidTDS
SEVERE: TDSReader@1878144 ( ConnectionID:1 TransactionID:0x0000000000000000) 
got unexpected value in TDS response at offset:4088
Dec 25, 2011 2:05:02 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TDSChannel ( ConnectionID:1 TransactionID:0x0000000000000000) 
SSL handshake failed: The TDS protocol stream is not valid.
Dec 25, 2011 2:05:02 PM com.microsoft.sqlserver.jdbc.TDSReader readPacket
WARNING: TDSReader@2f0df1 ( ConnectionID:2 TransactionID:0x0000000000000000) 
Unexpected message type:18 in TDS header; expected type:4
Dec 25, 2011 2:05:02 PM com.microsoft.sqlserver.jdbc.TDSReader throwInvalidTDS
SEVERE: TDSReader@2f0df1 ( ConnectionID:2 TransactionID:0x0000000000000000) 
got unexpected value in TDS response at offset:4088
Dec 25, 2011 2:05:02 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TDSChannel ( ConnectionID:2 TransactionID:0x0000000000000000) 
SSL handshake failed: The TDS protocol stream is not valid.
12-25,14:05:02 INFO - Url: jdbc:sqlserver://INMUMV049SRV.ww930.my-it-solutions.net:1433;DatabaseName=mdb;integratedSecurity=true
12-25,14:05:02 INFO - User: OS user
12-25,14:05:02 INFO - ErrorCode: 0
12-25,14:05:02 ERROR - The driver could not establish a secure connection to SQL Server by 
using Secure Sockets Layer (SSL) encryption. Error: The TDS protocol stream is not valid..
12-25,14:05:02 INFO - MDBTools_0104I - Total time: 0H:0M:0S.
12-25,14:05:02 MDBTools install error=3

Solution:

This problem is due to the JDBC driver being used to connect to the database. Here, the problem happens as the JDBC driver 1.x is being used to connect to the database in SSL mode.

This issue is resolved by using the Microsoft JDBC driver 2.x release. Replacing the sqljdbc.jar and sqljdbc_auth.dll files in the location "C:\Users\w99s05u0\AppData\Local\Temp\ITRM\database\mdb_install\lib\" will resolve the issue.

These files can be downloaded from MSDN.