Highlighted
Absent Member.
Absent Member.
1668 views

Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution

We setup a new system which is running Extend v10.2 on Windows 2012 R2 and connect to SQL Server 2014 by Acu4GL. However, it returns "[DBNETLIB]: SSL Security error" when opening table in database server. After checking, it may relate to the SQL Server has enabled TLS 1.2. So I would like to know does Acu4GL v10.2 support TLS 1.2? If it is support, is there any configuration variable to make it work?

Regards,

 

Bobby

Tags (2)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Outstanding Contributor.
Outstanding Contributor.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
This entry in the runtime log shows that the user was blank when the connection was attempted:
[1] 28000 18456 - Login failed for user ''.

I see that you have set 'A-MSSQL-NT-AUTHENICATION TRUE' in the cblcconfi_mssql configuration file, however it is misspelled. The entry should be 'A-MSSQL-NT-AUTHENTICATION TRUE'.

View solution in original post

14 Replies
Highlighted
Outstanding Contributor.
Outstanding Contributor.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
Are you using the latest Microsoft SQL Server driver, 'ODBC Driver 13.1 for SQL Server'? If not, you should install the driver and add the following to your Runtime configuration settings:

A_MSSQL_ODBC_DRIVER_NAME ODBC Driver 13.1 for SQL Server

If you still have errors then you may need to raise a Support Incident. Make sure to provide a level 9 Runtime trace for further troubleshooting. Here's a link to instructions for generating trace files:

community.microfocus.com/.../27977.acucobol-gt-trace-files-for-troubleshooting.aspx
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
I have tried ODBC Driver 13.1 for SQL Server and it works on the SSL Security problem. I have one more question. I am now using SQL Server authentication and successful to access the database. But it is fail if I use Windows authentication (A-MSSQL-NT-AUTHENTICATION enabled). Does ODBC Driver work on Windows Authentication too? Hope you can give me advice.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
I wonder if this is a user permissions issue.
Highlighted
Outstanding Contributor.
Outstanding Contributor.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
You should use the SQL Server Profiler to capture a trace of what happens on a failed connection. I suspect GeorgeK is right that the account being used may not have the required access settings.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
DougP. Refresh my memory. Don't the Windows server and the Windows desktop have to be configured to allow Windows Authentication too? I don't recall.
0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
I don't think so. I didn't do anything other than setting the correct permissions for the account in SQL Server Management Studio.
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
ok
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution

I don't think so because we have used the same account in SSMS which can access the database successfully. I have attached the level 9 runtime trace log and cblconfi file for your reference below. It's seem cannot get the user account. You can see cblconfi file, I just followed your advice and added A_MSSQL_ODBC_DRIVER_NAME ODBC Driver 13 for SQL Server. If I use A-MSSQL-LOGIN and A-MSSQL-PASSWORD, I can access the database. However, I got "Login failed" error if I commented A-MSSQL-LOGIN and A-MSSQL-PASSWORD. But this setting is what we are using to access other databases before add A_MSSQL_ODBC_DRIVER_NAME. So I don't think it is a user permission issue.

Since I just added A_MSSQL_ODBC_DRIVER_NAME ODBC Driver 13 for SQL Server. Do I need to define any other configuration for Windows Authentication access by ODBC Driver?

Trace Log:

A2
A6, "LOGINACT-WINDOW-USER"
A5, 13
A2
A2
find_MSSQLConn
Checking value of DEFAULT-CONNECTION
Leaving through call to init_MSSQLConn
init_MSSQLConn
init_connection
0 = SQLAllocHandle(2, 00000000006273B0, 0000000000137550 (00000000006284A0))
Setting no_time_fractions due to driver issue
Trying to open a connection to server szpqwposdb01\posqa01
report_status called from 1387
[1] 28000 18456 - Login failed for user ''.
[2] IM006 0 - Packet size change not supported by server, default used
No more messages
0 = SQLFreeHandle(2, 00000000006284A0)
SQLDriverConnect failed
Leaving, init_connection
A1
A2
Leaving, find_MSSQLConn
*** File system error value = 18456 ***
*** Login failed for user ''. ***
>>>file status = 9D,18456
Try loading '..\CA_obj\message.out'...
..\CA_obj\message.out: The system cannot find the file specified.
Try loading '..\obj\message.out'...
..\obj\message.out loaded
E:\CS2000\CADATA66/gldata/userh.dat: close (thread 2590)
>>Header accesses: 2 updates, 0 locked reads, 1 unlocked reads
>>0 unlocked reads waited for update, 0 unlocked reads retried
closing data segment (#0): E:\CS2000\CADATA66/gldata/userh.dat
E:\CS2000\CADATA66/gldata/logfail.dat: close (thread 2590)
>>Header accesses: 2 updates, 0 locked reads, 1 unlocked reads
>>0 unlocked reads waited for update, 0 unlocked reads retried
closing data segment (#0): E:\CS2000\CADATA66/gldata/logfail.dat
transaction system shutdown
mssql_exit
Cursors: 0, 0
A68: 'nil'

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

cblcoonfi file:

 

# Acu4GL File Interface
!copy ..\etc\cblconfi_mssql

A_MSSQL_ODBC_DRIVER_NAME ODBC Driver 13 for SQL Server
A-MSSQL-DEFAULT-CONNECTION szpqwposdb01\posqa01
A-MSSQL-DATABASE csdata11_66
A-MSSQL-LOCK-DB aculocks
#A-MSSQL-LOGIN csuser
#A-MSSQL-PASSWD csuser
A-MSSQL-NT-AUTHENICATION TRUE

 

0334.trace_5F00_log.txt

0334.trace_5F00_log.txt

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
This entry in the runtime log shows that the user was blank when the connection was attempted:
[1] 28000 18456 - Login failed for user ''.

I see that you have set 'A-MSSQL-NT-AUTHENICATION TRUE' in the cblcconfi_mssql configuration file, however it is misspelled. The entry should be 'A-MSSQL-NT-AUTHENTICATION TRUE'.

View solution in original post

Highlighted
Absent Member.
Absent Member.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
E:\CS2000\CADATA66/gldata/userh.dat one problem is that path is invalid.

should probably be: E:\CS2000\CADATA66\gldata\userh.dat on windows side.
\ for windows
/for linux
never mixed
0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Does Acu4GL v10.2 support TLS 1.2 on SQL Server 2014?

Jump to solution
E:\CS2000\CADATA66\cblconfi.wts' path is ok here
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.