Troubleshooting blasadmin issues

This topic contains troubleshooting information for the blasadmin issue.

Warnings displayed on the command line

When you run commands by using the blasadmin utility (for example, set AccountConfig), warnings similar to the following are displayed on the command line.

Build: 23.1.00.xx

SQL Server:- Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

bladmin:*>set AccountConfig UserAccountInactiveTime 7
Jan 18, 2023 3:39:14 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TLSv1 was negotiated. Please update server and client to use TLSv1.2 at
minimum.
Jan 18, 2023 3:39:15 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TLSv1 was negotiated. Please update server and client to use TLSv1.2 at
minimum.
Jan 18, 2023 3:39:15 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TLSv1 was negotiated. Please update server and client to use TLSv1.2 at
minimum.
Jan 18, 2023 3:39:15 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TLSv1 was negotiated. Please update server and client to use TLSv1.2 at
minimum.
Jan 18, 2023 3:39:16 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TLSv1 was negotiated. Please update server and client to use TLSv1.2 at
minimum.
Jan 18, 2023 3:39:16 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
WARNING: TLSv1 was negotiated. Please update server and client to use TLSv1.2 at
minimum.

Workaround: Upgrade the JDBC drivers to support TLS 1.2. For SQL Server to support TLS 1.2, certain client components and driver updates are required, as discussed in the following Microsoft article: https://support.microsoft.com/en-us/kb/3135244

After you successfully update the drivers, these warnings won't be displayed.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*