Check that you have UNICOM Intelligence Data Model 3.0 or later installed on your computer. To use SSIS to transfer your data, you need to have both the UNICOM Intelligence Data Model and SQL Server installed on the same computer. If you are an UNICOM Intelligence Interviewer user, and you have a large system with different computers hosting the interview and data tiers, the UNICOM Intelligence Data Model may not be installed on the data tier computers. However, the UNICOM Intelligence Data Model is always installed on the interview tier computers, so you can run the transfers on one of the interview tier computers, provided you install the SQL Server client tools on that computer.

This can happen if you attempt to run the transfer using the .mdd file in the mrInterviewSource folder on a scriptwriter computer, because the .mdd file has not been synchronized with the case data. Instead you should use one of the following:

However, if you are using Metadata Model to Quantum and you run Metadata Model to Quantum on an .mdd file in the Projects folder on any interview tier computer, you will lose your card and column definitions the next time you activate the project. For more information, see Using Metadata Model to Quantum with UNICOM Intelligence Interviewer - Server Admin.

If you get any of these error messages when you are importing or exporting data using SSIS, try saving the import or export as a SSIS package using the SQL Server option. After you have done that, you should be able to run the package in SQL Server Management Studio without encountering the problem.

If you get this error message when you are exporting data, check that you selected Open metadata read/write in the Data Link Properties dialog box when you were specifying the destination.

When you select the destination details, click the Advanced tab in the Data Link Properties dialog box and select Allow dirty data if you want to get a warning when dirty data is accepted or deselect Perform data validation if you want to switch off data validation altogether. However, note that some problems may prevent the export from succeeding, even when data validation is switched off or when dirty mode is selected. For more information, see Data Link Properties: Advanced. If the data was collected using more than one version of the questionnaire definition, you may need to create a merged version for the export. For more information, see the next answer.

You can select multiple versions of the questionnaire definition for the export. If you select the versions for which you want to export the case data, generally you can export the case data collected with the different versions at the same time without encountering validity errors due to the difference between the versions. However, depending on the version changes, some validity errors may still be encountered. For more information, see Working with versions.

Alternatively, you can use the Metadata Model Version Utility to create a merged version especially for the export. For more information, see Version handling in Metadata Model to Quantum.

Quanvert SSIS has a limit on the number of variables that it can read at one time and it is possible that this limit has been exceeded. For more information, see Quanvert DSC: Limits and known problems.

These errors can be caused by selecting different versions for the input and destination data sources. So if your transfer fails with any of these errors, check that you have selected the same versions for both the input and destination data sources. For more information, see Working with versions.

See Why do some variable names give a syntax error in some third-party applications, such as DTS?.