FAQ:SSIS:Known Issues

← SSIS:Data Quality Components

SSIS: Global Verify License Issue

SSIS will complain about license Issue. Fixed in patched build 2575. Please download from FTP ftp://ftp.melissadata.com/Updates/DQC-web.exe

Resolution

Resolution

Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix. ftp://ftp.melissadata.com/Updates/DQC-web.exe

SSIS: Matchup UK Matchcode Not Saving

When using the Matchup UK Matchcodes, it doesn't save the UK matchcodes.

Resolution

Fixed in patched build 2575. Please re-download from the notification email, it has been updated with the fix. ftp://ftp.melissadata.com/Updates/DQC-web.exe

SSIS: Personator Not Verifying

When using the Personator Verify option, no verify result codes are coming back. ftp://ftp.melissadata.com/Updates/DQC-web.exe

Future Resolution

Fixed in patched build 2575. Please redownload from the notification email, it has been updated with the fix.

Upgrading Global Address with Global Name, Phone, and Email

Current users of the Global Verify Component who are only subscribed to Global Address Check and want to upgrade using either Global Name, Phone or Email, are required to re-install the components and enter their new license string in the installer.

Upgrading your license in the Component GUI using File > Advanced Configuration will currently not work. Alternatively, you can manually change your license string by editing the GlobalVerify.SSIS.Config under:

C:\ProgramData\Melissa DATA\GlobalVerify

and replace your license string for this entry:

<License>ENTER NEW LICENSE HERE</License>

Save the file and open SQL Server Data Tools. You should now be able to use the Global Verify Component with Global Address, Name, Phone and Email.

SSIS: Matchup - Date Keys are Not Being Built Correctly

When using the Component Type: Date in your MatchCode, Date Keys sometimes do not get built in the MatchKey. This is due to a conflict in the expected input format for Dates. Date Inputs should be in the format 'yyyMMdd'. This becomes problematic particularly for some DBMS. SQL Server for example may have a Date Column defined with char[30]. This causes trailing spaces to be included in the Date Input which conflicts with the expected Input Format, causing the Date Key to not be built.

Future Resolution

We will be adding a fix in a later build to trim the trailing white spaces for Date Inputs.