When clicking connect from the GTSubset logon screen to a database connection that is using SQL Server Windows integrated authentication, GTSubset crashes.
Check the log file for a message similar to:
# A fatal error has been detected by the Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000598def23, pid=7840, tid=0x00000000000045e8
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V [jvm.dll+0x13ef23]
This error message is the result of the SQL Server database driver jar files being a different version to the sqljdbc_auth.dll that it calls. It needs to be in the Datamaker directory folder, as well as the Fast Data Masker (FDM) directory folder.
from: C:\Program Files (x86)\Grid-Tools\GTDatamaker\SQLSERVER_DLLs\x64
to: C:\Program Files (x86)\Grid-Tools\GTDatamaker
If that does not resolve the problem:
Copy the sqljdbc_auth.dll file into the FDM folder located here: C:\Program Files\Grid-Tools\FastDataMasker.
Copy the sqljdbc.jar and sqljdbc4.jar file into the FDM lib folder located here: C:\Program Files\Grid-Tools\FastDataMasker\lib.
If that does not resolve the problem, then check the generated hs_err_pidxxxx.log file.
Search for the sqljdbc_auth.dll being used.
If this is a different sqljdbc_auth.dll then the one in the GT Datamaker installation, for example E:\software\Java\bin\sqljdbc_auth.dll, then change the path search order.
Alternatively remove this dll or overwrite the dll with the one from GT Datamaker.
If you experience any further issues, please open a support case by going to https://support.broadcom.com
Then login and select Enterprse Software