Error Log Messages

All errors originate from the Runtime Engine, but the log to which they are written depends on the interface being used. For instance, if you are using Map Editor, then errors are logged to an error file. If you are using Runtime Engine, then error messages are displayed in the console and written to a log file. See the following topics for more information on error logging.

Interface	Description
Map Editor	Errors that occur in Map Editor are displayed in a dialog box and logged to a TransformMap.log file. For details about the log file, see Viewing the Error and Event Log File. To learn how to customize the various types of messages and/or error detection that occurs while a map (or batch of maps) is running, see Setting Execution Preferences section in Setting Preferences.
Process Editor	Errors that occur in Process Designer are logged to a process log file named by the designer. For details, see Viewing the Error and Event Log File.
Runtime Engine	In Runtime Engine, the last error message logged while loading, changing or running a transformation or process is logged to the command line interface console. All error messages are logged to a log file. The default name for the log file depends upon which interface you are calling.
EZscript	The EZscript scripting language includes functions and statements that return information about errors to the error log files. For instance, you can use the LogMessage Function to write messages to an error log file, and the On Error GoTo Statement to trap run-time errors.