Fast Data Masker Troubleshooting

This article includes information that can help you troubleshoot Fast Data Masker issues.
tdm49
This article includes information that can help you troubleshoot Fast Data Masker issues.
2
2
Chinese Characters Are Not Rendered Correctly
Problem:
I am trying to mask chinese characters using FDM functions. When I enter Chinese characters in parameter fields, the user interface does not display proper characters, but empty boxes.
Solution:
For the GTMapper’s fields to support Chinese characters, configure the locale details in the config.xml file. FDM can mask Chinese data, but only the following functions have been tested: CONCAT, SQLFUNCTION, FIXED and HASHLOV. Note that this configuration does not enable Chinese localization of the user interface.
Default locale values:
<locale> <language>en</language> <country>US</country> <variant></variant> <font>Arial</font> </locale>
For example, configure the following options to be able to display Hong Kong Chinese characters. For more information on subtags, see the language subtags registry: https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry
<locale> <language>zh</language> <country>HK</country> <variant></variant> <font>MS Song</font> </locale>
Connection Error (Microsoft SQL Server) in Fast Data Masker
Symptom:
 After I launch Fast Data Masker and try to connect to a Microsoft SQL Server database profile, I receive the following error:
Connection Error: This driver is not configured for integrated authentication.authentication.
The steps that caused this error in my case are as follows:
  1. Launch Fast Data Masker by clicking 
    Start, All Programs, FastDataMasker, FastDataMasker
    .
  2. Copy the default connection connectSQLSERVER.txt by selecting it in the 
    Connection Files
     list in the left pane and then clicking the 
    Copy Connection
     button at the bottom of the dialog.
  3. Enter the database connection information as required.
    Note:
     The name that you enter in the
    Connection Name
    field shows up in the 
    Connection Files
     list after it is saved. You cannot see any underscores that you type inside this connection dialog. Instead, all underscores look like spaces. For example, 
    connect_test
     appears as 
    connect test
    . Additionally, if you get an error about the connection name, ensure that the name starts with the word connect.
  4. Click 
    Save
     to save the connection information.
  5. Click 
    Connect
     to connect to this profile.
    The following error is displayed:
    Connection Error: This driver is not configured for integrated authentication.Authentication.
Solution:
 If you get this error, it means that a Microsoft SQL Server authentication DLL file is missing from your Fast Data Masker folder. To address this issue, follow these steps:
  1. Close the Fast Data Masker application.
  2. Navigate to the location where you installed Fast Data Masker. For example, the default location is C:\Program Files\Grid-Tools\FastDataMasker.
  3. Open the SQLSERVER_DLLs folder.
  4. Copy the sqljdbc_auth.dll file.
  5. Paste this sqljdbc_auth.dll file into the C:\Program Files\Grid-Tools\FastDataMasker folder.
  6. Launch the Fast Data Masker application.
  7. Enter your Microsoft SQL Server database credentials.
  8. Click 
    Save
    .
  9. Click 
    Connect
    .
    You can now connect to and use Fast Data Masker without any issue.
"no dbjdbc12 in java.library.path" Error in Fast Data Masker
Symptom:
When I try to connect to Fast Data Masker, I receive the following error message
no dbjdbc12 in java.library.path
I followed these steps when I received the error:
  1. Launch Fast Data Masker.
  2. In the
    Connection Files
    pane, click the
    New
    button.
  3. Select a data source from the
    DBMS
    drop-down list.
  4. Enter all the required connection details.
  5. Click the
    Connect
    button. 
    The following error is displayed:
    no dbjdbc12 in java.library.path
Solution:
 This issue pertains to having the SQLANYWHERE drivers (sajdbc.jar and sajdbc4.jar) in the Fast Data Masker
lib
folder. These drivers require an underlying DLL to work, even if you are not connecting to SQLANYWHERE. Fast Data Masker throws an error irrespective of the database you are connecting to.
Since CA TDM 3.5, certain jar files are no longer shipped with the product. If you are upgrading to CA TDM 3.5 (or later) and are seeing this error message, it is because the Fast Data Masker
lib
 folder now contains these jar files. You must remove these files.
To address this issue, you can follow one of the following methods:
  • Method 1: Remove the two JARs
    1. Close the Fast Data Masker interface.
    2. Remove the two JAR files (sajdbc.jar and sajdbc4.jar) from the Fast Data Masker
      lib
       folder.
      The default location is 
      C:\Program Files\Grid-Tools\FastDataMasker\lib
      .
    3. Launch Fast Data Masker because many of these files are loaded upon launch.
      You must be able to connect to Fast Data Masker.
  • Method 2: Ignore the Error
    1. If you are using any other database connection other than SQLANYWHERE (for example, Oracle), you can click the
      OK
      button on the error message to ignore it.
  • Method 3: Copy the old contents
    If you have recently upgraded and have the older version backed up or installed in another location, you can copy and paste the contents (not the actual folder) of your old Fast Data Masker
    lib
    folder over to your current Fast Data Masker
    lib
    folder. This way you can have all the JAR files that you need.
    1. Close the Fast Data Masker interface.
    2. Copy all the contents from your old
      lib
      folder into the new
      lib
      folder. All new drivers remain the same.
    3. Launch Fast Data Masker because many of these files are loaded upon launch.
      You must be able to connect to Fast Data Masker.
Connect to Microsoft SQL Server Using Windows Authentication in Fast Data Masker
Symptom
The data that I want to mask is available in a Microsoft SQL Server database that allows only Windows (Integrated authentication. How can I connect to this database from Fast Data Masker so that I can mask the required data?
Solution
You might need to mask the data that resides in a Microsoft SQL Server database that has been configured only for Windows authentication, not for the Microsoft SQL Server authentication. In such cases, follow these steps to establish the connection:
  1. Close the Fast Data Masker application.
  2. Navigate to the SQLSERVER_DLLs folder under the FastDataMasker installation folder (by default, C:\Program Files\Grid-Tools\FastDataMasker).
  3. Copy the file named sqljdbc_auth.dll from the x64 subfolder. This is the 64-bit version of the DLL and is the one you need, assuming your system runs on a 64-bit processor.
  4. Place the sqljdbc_auth.dll file into the FastDataMasker folder (by default, C:\Program Files\Grid-Tools\FastDataMasker).
  5. Launch the Fast Data Masker UI.
  6. Enter the Microsoft SQL Server database connection details.
  7. Make sure the username and password fields are left blank.
  8. Save the information.
  9. Click the 
    Connect
     button.
    You can now connect to the Microsoft SQL Server database that allows connections using only Windows authentication.
Note: 
After copying the sqljdbc_auth.dll file, if you get the error message like 
This driver is not configured for windows authentication
, it is most likely that the incorrect version of sqljdbc_auth.dll has been copied. Repeat the process with a different version of the DLL.
Disable Fast Data Masker's connection to TDM Portal
Symptom
I have upgraded FDM to version 4.9, but my installation of TDM Portal is still an earlier version, or the TDM Portal service is not active. I experience a delay at startup of FDM, while it attempts to connect with the TDM Portal service.
Solution
To avoid this delay, and to prevent FDM from attempting to connect with TDM Portal, you can change the value of the Windows Environment Variable
TDM_PORTAL_URL
to
N
or
n
.
TDM_PORTAL_URL
defines the address where the TDM Portal service is active.
If you later upgrade TDM Portal to the same version as FDM, you need to amend this parameter again, to the URL where the TDM Portal service runs.