This error usually occurs when you attempt to export data to an existing .sav file. How you get around this error depends on what you are trying to achieve. If you want to export the data to a new file, simply rename or delete the existing file or move it to another location before running the transfer again.

However, if you want to export additional records to the existing file, you will only be able to do this if:

If the structure of the data is unchanged and the output metadata file from the previous export is available, the export should succeed if you change the DMS file accordingly and run the file again.

This is because the validation takes place before the input metadata has been created. You can safely ignore these errors.

Check that you have specified a metadata source in the InputDataSource section (see InputDataSource section). If not, either because you are running a case data-only transfer or because you are using a non-UNICOM Intelligence Data Model OLE DB provider, you will need to remove these sections:

OnJobEnd Event section.

These Event sections are available only when you have specified an input metadata source.

This problem can occur when the missing= keyword has been used in the Quantum specification that was used to set up the Quanvert database. This can lead to the illegal Ctrl-A character appearing in the QVLabel custom property on the affected variable(s) in the MDM Document. If you use the Quanvert MDSC to create an .mdd file in the OnBeforeJobStart Event section, you can remove the illegal character using code similar to the following:

The ChrW function is used to return the Ctrl-A character.

Some other common error messages and suggested solutions:

Make sure that the location you specified for the output metadata file exists, is not read-only, and that you have suitable permissions for it. UNICOM Intelligence Professional 2.1 does not create a new folder if the folder you specify does not exist. If necessary you must create the folder yourself or specify a different folder that does exist.

Check whether you have included one or more line-continuation characters in a #define or #include statement. Line-continuation characters cannot be used in these statements.

Check whether your DMS file includes one or more empty Metadata or Event sections, and if necessary remove them.

This error message originates from the UNICOM Intelligence Professional licensing system and occurs when you attempt to run multiple instances of DMS Runner on separate CPUs on a dual-processor computer. This is because of the single-user restriction that is built into the licensing. The solution is to run the jobs one after the other or to use a single-processor computer.

This rather confusing message indicates that no records passed the filter defined in the WHERE clause in the select query in the InputDataSource section. For example, you would get this message if the WHERE clause specifies records whose serial number is greater than 600 and the highest serial number in the input data source is actually 599.

This error occurs when you are exporting data to Quantum and typically means that no card, column, and punch definitions have been set up in the metadata. If you are setting them up in the DMS file, check the log or error message file generated by the Event section in which you set them up for error messages.

This error may occur when you have an update query in the InputDataSource section and you are using RDB DSC 2 to connect to an RDB database or when you are transferring data to an RDB database using RDB DSC 2. You can avoid this problem by using the Favor Memory option. See the third example in Transferring data from a relational MR database (RDB) for more information.

This error may occur when you have called the MDM Document.Open method in an Event section and not called the Document.Close method to release it. You can avoid this problem by calling Document.Close at the end of the Event section. See the OnAfterMetaDataTransformation Event section for more information.

Other errors

When you use the UNICOM Intelligence Data Model to read or write data, the DSCs that you are using will issue a message when they encounter an error. Each DSC has specific requirements and therefore the things that are likely to cause an error will vary according to which DSCs you are using. Error messages that are issued by a DSC are prefixed by a code. However, sometimes the error message generated by the DSC is preceded by a more general message that is generated by UNICOM Intelligence Professional or the UNICOM Intelligence OLE DB Provider. For example, scroll up to the top of this topic, and look at the first error message that is shown. Notice that the second part of the error message is prefixed by “SAV”. This means that it has been generated by SPSS Statistics SAV DSC.

Transferring data using a DMS file provides general information and tips on using the DSCs provided with the UNICOM Intelligence Data Model, and links to relevant topics in Available DSCs.

This error occurs if there is a space after the continuation character (_) in a string definition. For example, it occurs if you accidentally put a blank space after either of the continuation characters in this statement.