ProMapper Error Codes
This appendix describes errors that can occur during ProMapper-related processing and their solutions. When a system error occurs, ProFrame calls pfmMapperGetError and displays the error message.
|
pfmMapperGetError returns an error message as a string if a function returns a value that is not MAPPER_RETURN_OK. |
MAPPER_TDLCALL_ERROR
Cause |
An error occurred when executing tdlcall for a library that creates ProMapper in API function. |
Action |
Check the error message and if tdlcall settings have an issue. |
MAPPER_MALLOC_ERROR
Cause |
A malloc or realloc related error occurred. |
Action |
Check ProFrame system status. |
MAPPER_OUT_OF_BOUND_ERROR
Cause |
The length of a structure or message was incorrectly entered in Studio. For example, the length is not entered for data of string type or a fixed-length stream message field; or, the length of a decimal value of number or integer type is greater than the field length. |
Action |
Check if a user-entered value matches the value registered in meta. |
MAPPER_NULL_DATA_ERROR
Cause |
The value to convert is null. |
Action |
Check the message or structure item to convert. |
MAPPER_FUNCTION_ARGS_MISMATCH
Cause |
The sum of the number of registered input/output structures and that of MapperMapInfo structures is not exceeded. |
Action |
Compare the number of parameters in a called application and that of structures registered in mapping, and then modify the application. |
MAPPER_FUNCTION_CODE_ERROR
Cause |
An undefined macro was used as API function’s argument. |
Action |
Check the argument of the API function. |