FAQ:SSIS:Known Issues

← SSIS:Data Quality Components

SSIS: MatchUp Expired Database without Updates

Users who do not update to MatchUp build 2683 will experience an expired database (actual expiration date is 2015-12-29).

Updating to build 2628 (or newer future builds) will enable Global Matching for supported Countries but may require changes to your application (see build history), and are not effected by an expiring database date.

Users who do not update and need an mdMatchUp.dat with an extended expiration date, please contact our tech support team at tech@melissadata.com or 1-800-800-6245 x4.

SSIS: Global Verify On Premise Crashes

SSIS will crash when specific combination of visual studio and SSIS causes runtime to use only 32 bit processing. For now, we officially only support 64 bit version processing. You can check if the correct behavior is exhibited, by opening process manager and see if there are both 32bit and 64bit DtsDebugHost is running. If only 32bit is running, we do not officially support 32bit run time. We are working hard to provide a stable 32bit runtime DLL.

Resolution

This is a Microsoft SSIS known issue as they left out DTExec 64-bit in SSDT-BI/2013, we provide both 64bit and 32bit dlls but 32bit DLL is not officially supported by Melissa Data. As of current our object is meant to be run in 64bit runtime. If during processing SSIS uses only the 32bit instead of the 64bit. Please the below help links and try the solutions provided by Microsoft. We will notify when we have 32bit version ready.

• https://support.microsoft.com/en-us/kb/2881285
• https://connect.microsoft.com/VisualStudio/feedback/details/1041486/debugging-ssis-package-opens-32-bit-dtsdebughost-exe-instead-of-64-bit-and-causes-errors

Known Setup Issues

Installed SSIS 2012, Using Visual Studio 2012, Visual Studio 2010 Installed

• Behavior: Uses two 32bit DtsdebugHost and crashes

Known Working

Installed SSIS 2012, Installed Visual Studio 2012, Using Visual Studio 2010

• Behavior: Working

Installed SSIS 2014, Using Visual Studio 2013

• Behavior: Working

SSIS: Global Verify License Issue

SSIS will complain about license Issue.

Resolution

Fixed in patched build 2575. Please download from FTP 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

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.