FAQ:SSIS:Common Issues

← SSIS:Data Quality Components

Invalid Permissions

Insufficient privileges can prevent a project from successfully performing file operations at runtime. This issue is often related to the application's permission level, so it is necessary to ensure that the program has the required permissions to write to any specified directories for successful task completion.

These errors can be accompanied by a 0x80004005 code.

Solution: Right-click on the program's shortcut and select “Run as administrator.”

Data File Errors

Outdated or missing data files can cause various error messages when using the On-Premise processing mode in the Contact Verify component. The underlying binaries expect all data files to be present in the designated directory, and the component will not function properly if there are any discrepancies.

Solution: Please follow the steps on this page in order to resolve any data file errors.

Memory Allocation Errors

The size of the buffers allocated for the data flow will significantly impact the performance of an SSIS project. Larger buffers allow more data to be loaded into memory at once, while smaller buffers help manage memory consumption. Both configurations can enhance speed and functionality, so finding the optimal buffer size for a specific system is crucial.

Messages relating to memory errors may resemble:

• "A buffer failed while allocating…"
• "The Data Flow task failed to create a buffer to call PrimeOutput…"

Solution: There are three properties that can be used to modify the data flow’s buffers and mediate memory allocation issues.

1. DefaultBufferMaxRows - This represents the maximum number of rows a buffer can hold before being processed and moved to the next component in the data flow.
2. DefaultBufferSize - This value sets the maximum number of bytes in a buffer.
3. AutoAdjustBufferSize - When set to True, this will dynamically adjust buffer size at runtime based on the system’s available memory and the amount of data being processed.

Missing Components

If Melissa’s components do not appear in the SSIS Toolbox after a successful installation, there may be a mismatch between the Target Server Version configured in SSIS and the version of SQL Server used in the target environment on the system.

Solution: Please refer to this page in order to modify the Target Server Version within SSIS to match the target SQL Server version.

Public Key Token Errors

A mismatch between an SSIS project's Public Key Token and the target SQL Server version can cause errors related to the Public Key Token, which may prevent the successful execution of the project.

Messages related to Public Key Token errors may resemble:

• "Public Key Token could not be loaded."
• "Could not load file or assembly…"

Solution: Please refer to this page in order to correctly set the Public Key Token to the value specific to the target SQL Server version.