Map compile error messages

The compile errors display on the Build Results tab of the Organizer. Maps with compile errors may not be run. Correct all compile errors to run a map.

The following table lists the errors than can result when a map is built:

Return Code
Message
M1001
Compile aborted by user.

Hint: You cancelled the build process before it completed.

M1002
Not enough memory available to compile.

Hint: Close other applications that you have open, and build the map again.

M1003
Couldn't open the map source file.

Hint: The map may be corrupt. Please contact Technical Support.

M1004
Couldn't find the executable map.

Hint: The map source file may be corrupt. Please contact Technical Support.

M1005
Duplicate map names in output file.

Hint: If you get this error, please contact Technical Support.

M1006
Tree used in functional map not used by executable map.

Hint: Edit the card in the functional map or the executable map so both cards reference the same schema.

M1007
No delimiter defined for delimited type.

Hint: In the schema designer, specify the delimiter value for the given type.

M1008
Unable to open the schema for input card.

Hint: The schema may not exist in the directory specified, or the schema may be corrupt. If your schema is corrupt, please contact Technical Support.

M1009
Unable to open the schema for output card.

Hint: The schema may not exist in the directory specified or the schema may be corrupt.

M1010
Unable to find a type in an input schema.

Hint: If you get this error, please contact Technical Support.

M1011
Unable to find a type in an output schema.

Hint: If you get this error, please contact Technical Support.

M1012
Could not retrieve query information.

Hint: Either you have not installed the Database Interface Designer or the .mdq file is incorrect.

M1013
Could not retrieve database information.

Hint: Either you have not installed the Database Interface Designer or the .mdq file is incorrect.

M1014
Input data file for executable map missing or invalid.

Hint: Check the file names used for sources and targets.

M1015
Output data file for executable map missing or invalid.

Hint: Check the file names used for sources and targets.

M1016
Parser found an invalid rule.

Hint: If you get this error, contact Technical Support.

M1017
Output card referenced in rule not found.

Hint: If you get this error, please contact Technical Support.

M1018
Invalid component or partition subtype encountered.

Hint: If you get this error, please contact Technical Support.

M1019
Unable to resolve type references in rule.

Hint: If you get this error, please contact Technical Support.

M1020
Couldn't open the compiled map file.

Hint: The compiled map file may be corrupt. Please contact Technical Support.

M1021
Error writing to the compiled map file. (Disk full?)

Hint: Delete unnecessary files from your hard disk.

M1022
Unable to resolve type references in audit.

Hint: If you get this error, please contact Technical Support.

M1023
Unable to open .MDQ file.

Hint: The .mdq file does not exist or is otherwise inaccessible.

M1024
Database not found.

Hint: The named database is not defined in the specified .mdq file.

M1025
Database Error.

Hint: An unexpected error occurred while processing and .mdq file.

M1026
Input MDQ file not found.

Hint: The .mdq file does not exist or is otherwise inaccessible.

M1027
Input query not found.

Hint: The named query is not defined in the specific .mdq file.

M1028
Output MDQ file not found.

Hint: The .mdq file does not exist or is otherwise inaccessible.

M1029
Output database not found.

Hint: The named database is not defined in the specified .mdq file.

M1030
At least one syntax object literal is too long.

Hint: schema designer analysis is required.