Developer Documentation Library > Data Model > Accessing the UNICOM Intelligence Data Model > Working with the Case Data Model > Accessing case data from third party applications > Transferring data using SQL Server Integration Services > SSIS troubleshooting
 
SSIS troubleshooting
For information on working with the SQL Server Import and Export Wizard, see:
http://technet.microsoft.com/en-us/library/ms141209(SQL.90).aspx
UNICOM Intelligence DM-2 OLE DB Provider does not appear in the list of data sources
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 might 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.
When attempting to export UNICOM Intelligence Interviewer data, VDATA does not appear on the Select Source Tables and Views page of the SQL Server Import/Export wizard
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:
The .mdd file in the FMRoot\Shared folder on the File Management server (which is typically the primary interview server), because this file is synchronized with the case data during activation.
The .mdd file in the Projects folder on any interview tier computer, because this is a copy of the file in the FMRoot\Shared folder and will also be synchronized with the case data.
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.
Failed to load MDM document. Permission denied, file already open
No such interface supported
The application called an interface that was marshalled for a different thread
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.
File open for read-only
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 when you were specifying the destination.
When I export to Quantum/IBM SPSS Statistics, the export fails with a validation error. However, I want to export the data as it is and clean it in Quantum/IBM SPSS Statistics. How can I stop the validation error?
When you select the destination details, click the Advanced tab in the Data Link Properties dialog 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 might 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 might need to create a merged version for the export. For more information, see the following answer.
I want to export to Quantum and/or IBM SPSS Statistics data collected using more than one version of the questionnaire definition at the same time. However, if there have been changes to the variable and/or category definitions between the versions, I get validation errors.
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 validity errors because of the difference between the versions occurring. However, depending on the version changes, some validity errors might still occur. 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.
I am trying to export a Quanvert database to a relational MR database but it fails with an "Access Exception Violation" error.
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.
Column name '______' was not found.
Invalid pointer. An error occurred creating the new table 'VDATA': Invalid pointer.
A DTSTransformationCopy must specify no columns (signifying a sequential 1-to-1 mapping of all columns) or the same number of source and destination columns.
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.
Why do some variable names give a syntax error in some third-party applications, such as SSIS?
See Why do some variable names give a syntax error in some third-party applications, such as DTS?.
Requirements
UNICOM Intelligence Data Model
Microsoft SQL Server
See also
Working with versions
SPSS Statistics SAV DSC error and warning messages
Troubleshooting when writing to a .sav file
Transferring data using SQL Server Integration Services