Message Reference > E Message Codes > EP Messages
  

EP Messages

EP_13001 Invalid conversion.

Explanation:
In an external procedure, the Integration Service cannot convert the datatype of the port to the datatype of the corresponding parameter, or vice versa. For example, the port may have a Date/Time datatype, while the parameter has an Integer datatype. The Integration Service cannot convert a Date/Time datatype to an Integer datatype.
User Response:
Either change the external procedure datatype or the port datatype before running the session again.

EP_13002 Error freeing external module.

Explanation:
The Integration Service encountered an error while closing a DLL or shared object.
User Response:
This error does not adversely affect the session run. If the message recurs, however, contact Informatica Global Customer Support.

EP_13003 Cannot prepare common external procedure information.

Explanation:
The Integration Service cannot initialize the external procedure.
User Response:
This is a general error message. Check the session log for related error messages.

EP_13004 Cannot prepare pipeline external procedure information.

Explanation:
The Integration Service cannot initialize the external procedure.
User Response:
This is a general error message. Check the session log for related error messages.

EP_13005 Cannot initialize Informatica-style external procedure.

Explanation:
The Integration Service cannot initialize the external procedure.
User Response:
This is a general error message. Check the session log for related error messages.

EP_13006 NULL external module name.

Explanation:
The entry for the Module/Programmatic Identifier property for the External Procedure transformation is empty.
User Response:
Enter a valid entry for the Module/Programmatic Identifier property.

EP_13007 Cannot create external module manager.

Explanation:
The Integration Service cannot create the External Module Manager.
User Response:
This is a general message. Check the session log for related error messages.

EP_13008 Cannot load external module.

Explanation:
The Integration Service cannot locate the DLL or considers the DLL invalid.
User Response:
Verify the name, the location of the DLL, and the Module/Programmatic Identifier property before running the session again.

EP_13010 Cannot create external module object.

Explanation:
The class factory function CreateExternalModuleObject failed to create an external module object in the Informatica external module.
User Response:
Examine the CreateExternalModuleObject function and the constructor for the external module object called within it.

EP_13011 NULL external procedure name.

Explanation:
You did not enter the procedure name in the External Procedure transformation.
User Response:
Enter a valid name for the procedure.

EP_13012 Cannot get external procedure signature.

Explanation:
A call to the TINFExternal Module Impl::GetProcSignature function failed.
User Response:
Examine this function in the file infemimp.cpp. Also, make sure that the INFEMProcSignatures and the p*ParamVector data structures in the module_nameEM.CPP file have not been altered.

EP_13013 Number of ports in transform does not match number of formal arguments.

Explanation:
The Integration Service cannot match the number of ports in an External Procedure transformation with the number of formal arguments in the external procedure.
User Response:
Correct either the number of arguments in the external procedure or the number of ports in the External Procedure transformation before running the session again.

EP_13014 Multiple return ports defined for transform.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13015 Multiple return arguments defined for external procedure.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13020 External procedure has return value, but transform does not.

Explanation:
The external procedure has a return value, but the External Procedure transformation does not.
User Response:
Either add a return value to the External Procedure transformation or remove it from the external procedure code.

EP_13021 Transform has return value, but external procedure does not.

Explanation:
The External Procedure transformation has a return value, but the external procedure does not.
User Response:
Either add a return value to the external procedure code or remove it from the External Procedure transformation.

EP_13022 External procedure return value is not last argument.

Explanation:
The external procedure code has a return value, but it is not the last parameter.
User Response:
Make sure the return value of the external procedure code is the last parameter.

EP_13023 Transform return value is not last port.

Explanation:
The External Procedure transformation has a return value, but it is not the last port.
User Response:
Make sure the return value of the External Procedure transformation is the last port.

EP_13024 Port lookup failed.

Explanation:
An External Procedure transformation port name does not match the corresponding external procedure argument.
User Response:
Change the external procedure argument or the External Procedure transformation port name before running the session again.

EP_13025 Not all input params found.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13026 Multiple connections to input port.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13027 Decimal overflow error.

Explanation:
The Integration Service encountered an error converting decimal numbers on input to or output from an external procedure.
User Response:
Evaluate the external procedure to see if the Decimal datatype is necessary. If possible, change the Decimal datatype to Double.

EP_13028 Unknown error while converting datatype.

Explanation:
Internal error.
User Response:
Send the external procedure to Informatica Global Customer Support with a description of the error.

EP_13030 Exception error was thrown from external procedure <external procedure name>.

Explanation:
The Integration Service encountered a serious exception while running the external procedure.
User Response:
Debug the external procedure code before running the session again.

EP_13033 Cannot initialize COM-style external procedure.

Explanation:
The Integration Service encountered an error initializing a COM-style external procedure.
User Response:
This is a general error. Check the session log for related error messages.

EP_13034 Unknown COM error.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13035 Cannot initialize column/parameter mapping.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13036 Cannot find all input parameters.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13037 Cannot allocate memory.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13038 Cannot initialize external procedure.

Explanation:
The Integration Service encountered an error initializing an external procedure.
User Response:
This is a general error. Check the session log for related error messages.

EP_13039 Buffer initialization callback failed.

Explanation:
The Integration Service encountered an error creating buffers.
User Response:
This is a general error. Check the session log for related error messages.

EP_13040 Invalid programmatic identifier.

Explanation:
The Integration Service found an invalid programmatic identifier in the registry.
User Response:
Correct the programmatic identifier key in the registry. The key must appear in a two-dot format, such as abc.def. For more information, see the COM documentation.

EP_13041 Programmatic identifier not found in registry.

Explanation:
The Integration Service cannot match the programmatic identifier module with its corresponding key in the registry.
User Response:
Either change and compile the module or register the COM.dll in the registry. For more information, see the COM documentation.

EP_13042 Cannot map programmatic identifier to CLSID.

Explanation:
In the registry, the programmatic ID does not map to the CLSID.
User Response:
Check the programmatic ID in the registry. For more information, see the COM documentation.

EP_13043 Cannot create string representation of CLSID.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13044 Cannot create instance of component object.

Explanation:
The Integration Service call to the CoCreateInstance file failed.
User Response:
Check the CoCreateInstance documentation for appropriate action.

EP_13045 Cannot get dispatch interface for component object.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13046 IDispatch::Invoke failed.

Explanation:
The Integration Service encountered a major exception in a COM-style external procedure.
User Response:
Debug the external procedure code.

EP_13047 Cannot open registry key HKEY_CLASSES_ROOT\\CLSID\\clsid\\Typelib.

Explanation:
The Integration Service could not find the named key in the registry.
User Response:
In the registry, enter a valid library ID. For more information, see the COM documentation.

EP_13048 Cannot get registry value for HKEY_CLASSES_ROOT\\CLSID\\clsid\\Typelib.

Explanation:
The named key has a registry location, but that location is empty.
User Response:
Enter a valid key at that location. For more information, see the COM documentation.

EP_13049 Cannot create CLSID from programmatic identifier.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13050 Cannot open registry key HKEY_CLASSES_ROOT\\TypeLib\\libid.

Explanation:
The Integration Service could not find the named key in the registry.
User Response:
In the registry, enter a valid library ID. For more information, see the COM documentation.

EP_13051 Cannot open registry key HKEY_CLASSES_ROOT\\TypeLib\\libid.

Explanation:
The Integration Service could not open the named key because it is invalid or not at that location.
User Response:
In the registry, make sure the named key exists at the right location and is a valid key. For more information, see the COM documentation.

EP_13052 Cannot load type library.

Explanation:
The Integration Service cannot load the type library because it is not there or because the file is invalid.
User Response:
In the registry, make sure the type library is valid and in the correct location. For more information, see the COM documentation.

EP_13053 Cannot get type library attributes.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13054 Cannot open registry key HKEY_CLASSES_ROOT\\CLSID\\clsid\\server type.

Explanation:
The Integration Service could not open the named key because it is invalid or not at that location.
User Response:
In the registry, make sure the named key exists at the right location and is a valid key. For more information, see the COM documentation.

EP_13055 Cannot get registry value for HKEY_CLASSES_ROOT\\CLSID\\clsid\\<server type>.

Explanation:
The named key has a registry location, but that location is empty.
User Response:
Enter a valid key at that location. For more information, see the COM documentation.

EP_13056 Cannot get component object type information.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13057 Cannot get component object type attributes.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13058 Cannot get reference type of interface.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13059 Cannot get type information of interface.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13060 Cannot get type attributes of interface.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13061 Cannot get function description.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13062 Cannot get names of function and its arguments.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13063 Cannot get IDs of function parameters.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13064 Cannot get function type information.

Explanation:
The Integration Service encountered an error accessing a COM type library.
User Response:
Contact Informatica Global Customer Support.

EP_13065 NULL BSTR.

Explanation:
A COM external procedure did not allocate memory for a B-String in a COM-style procedure.
User Response:
Allocate more memory for the B-String.

EP_13066 Error converting COM datatype to Informatica internal datatype.

Explanation:
The Integration Service encountered an error converting between a COM and Informatica datatype. Either the external procedure attempted an invalid conversion, or a data overflow occurred.
User Response:
Check the session log for messages related to data overflow or invalid datatype conversions. If data overflowed, change the external procedure or mapping to accommodate the data. Otherwise, make sure the external procedure uses valid datatype conversions.

EP_13067 Error converting Informatica internal datatype to COM datatype.

Explanation:
The Integration Service encountered an error converting between a COM and Informatica datatype. Either the external procedure attempted an invalid conversion, or a data overflow occurred.
User Response:
Check the session log for messages related to data overflow or invalid datatype conversions. If data overflowed, change the external procedure or mapping to accommodate the data. Otherwise, make sure the external procedure uses valid datatype conversions.

EP_13068 Unsupported COM type.

Explanation:
The external procedure uses a COM datatype that is not supported.
User Response:
Check the supported COM datatypes and make the appropriate changes to the external procedure.

EP_13069 Cannot initialize COM.

Explanation:
The Integration Service call to CoInitialize failed.
User Response:
Check the CoInitialize documentation for appropriate action.

EP_13070 COM-style external procedures not supported on non-Windows platforms.

Explanation:
You tried to run a COM external procedure on a UNIX server. COM-style external procedures only run on Windows platforms.
User Response:
If possible, move the session to a Windows server before running the session again. Otherwise, create an Informatica style external procedure to replace the COM-style procedure.

EP_13071 The Informatica-style transformation has a port with an invalid datatype.

Explanation:
Internal error.
User Response:
Contact Informatica Global Customer Support.

EP_13072 The Informatica-style external procedure has a parameter with an invalid datatype.

Explanation:
The Integration Service encountered a parameter with an invalid datatype in the Informatica-style external procedure.
User Response:
Change the datatype to a supported type before running the session again.

EP_13073 Informatica external procedure log message.

Explanation:
This message appears when the external procedure creates a log message.
User Response:
If necessary, examine the external procedure for the cause of the message.

EP_13074 Informatica external procedure error message.

Explanation:
A session configured with an external procedure has encountered an error.
User Response:
Examine the external procedure for the cause of the message.

EP_13075 The version of the Informatica external module is not supported by the server.

Explanation:
The Integration Service encountered an external procedure that is not supported.
User Response:
Do not use unsupported external procedure modules.

EP_13083 <External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>.

Explanation:
The Init or InitParams method in the specified external procedure returned a fatal error.
User Response:
Check the code for the Init or InitParams method in the specified external procedure and correct the fatal error. Read the session log for related messages logged by the external procedure.

EP_13084 Data conversion error.

Explanation:
The Integration Service cannot convert a String port from the External Procedure transformation to a Date/Time input port in the external procedure. The string is not in the default date format (MM/DD/YYYY HH24:MI:SS).
User Response:
Use TO_DATE with the appropriate format string to convert a string to a date.
Explanation:
The Integration Service cannot convert data from an external procedure Date/Time output port to a String port in the External Procedure transformation.
User Response:
Change the External Procedure transformation port to Date/Time.

EP_13089 Error converting initialization parameter to correct data type for constructor parameter.

Explanation:
In the initialization properties for the External Procedure transformation, you specified a parameter that the Integration Service cannot convert to the COM datatype for the constructor in the external procedure. Before the Integration Service calls the constructor in the external procedure, it tries to convert the initialization parameters in the External Procedure transformation to the required COM datatypes.
User Response:
Edit the parameters in the Initialization Properties tab of the External Procedure transformation. Enter values that the Integration Service can convert to the required COM datatypes for the constructor.

EP_13103 <External Procedure transformation>: Fatal error returned from external procedure <external procedure>.

Explanation:
The specified external procedure returned a fatal error.
User Response:
Check the code for the specified external procedure and correct the fatal error. Read the session log for related messages logged by the external procedure.

EP_13124 <External Procedure transformation>: Fatal error from initialization of external module <module: external procedure>.

Explanation:
The Init or InitParams method in the specified external procedure returned a fatal error.
User Response:
Check the code for the Init or InitParams method in the specified external procedure and correct the fatal error. Read the session log for related messages logged by the external procedure.

EP_13261 Fatal Error: It is illegal to set pass thru port when the transformation scope is not ROW or when the data access mode is ARRAY for active Custom Transformation.

Explanation:
The Custom transformation procedure code uses the INFA_CTSetPassThruPort() function when the transformation scope is transaction or all input and the data access mode is row-based.
User Response:
Change the transformation scope to row.
Explanation:
The procedure code for an active Custom transformation uses the INFA_CTSetPassThruPort() function and the data access mode is array-based.
User Response:
Edit the procedure code and use the array-based mode data handling functions to set the data for all output ports. Do not use the INFA_CTSetPassThruPort() function.

EP_13262 Fatal Error: It is illegal to set default row strategy to pass thru when the transformation scope is not ROW or when the data access mode is ARRAY for active Custom Transformation.

Explanation:
The Custom transformation procedure code uses the INFA_CTSetRowStrategy() function to define the default row strategy to pass through when the transformation scope is transaction or all input and the data access mode is row-based.
User Response:
Change the transformation scope to row.
Explanation:
The procedure code for an active Custom transformation uses the INFA_CTSetRowStrategy() function to define the default row strategy to pass through and the data access mode is array-based.
User Response:
Edit the procedure code and use the INFA_CTASetRowStrategy() function to define the default row strategy to pass through.

EP_13263 Fatal Error: It is illegal to call INFA_CTASetInputErrorRow when the data access mode is not ARRAY.

Explanation:
The Custom transformation procedure code uses the INFA_CTASetInputErrorRowM() or INFA_CTASetInputErrorRowU() function and the data access mode is row-based.
User Response:
Edit the procedure code and remove the INFA_CTASetInputErrorRowM() or INFA_CTASetInputErrorRowU() function. Instead, you can return INFA_ROWERROR in the input row notification function to notify the Integration Service that a particular input row has an error.

EP_13264 Fatal Error: It is illegal to call INFA_CTGetRowStrategy outside inputRowNotification.

Explanation:
The Custom transformation procedure code uses the INFA_CTGetRowStrategy() function inside a function other than the p_<proc_name>_inputRowNotification() function.
User Response:
Edit the procedure code and only use the INFA_CTGetRowStrategy() function inside the p_<proc_name>_inputRowNotification() function.

EP_13265 Fatal Error: It is illegal to call INFA_CTGetRowStrategy when the data access mode is ARRAY.

Explanation:
The Custom transformation procedure code uses the INFA_CTGetRowStrategy() function when the data access mode is array-based.
User Response:
Edit the procedure code and use the INFA_CTAGetRowStrategy() function to get the default row strategy.

EP_13266 Fatal Error: It is illegal to call INFA_CTOutputNotification outside inputRowNotification when the transformation scope is ROW.

Explanation:
The Custom transformation procedure code uses the INFA_CTOutputNotification() function inside a function other than the p_<proc_name>_inputRowNotification() function when the transformation scope is row.
User Response:
Change the transformation scope to transaction or all input.

EP_13267 Fatal Error: Invalid block size is set for OutputNotification.

Explanation:
The Custom transformation procedure code uses the INFA_CTASetNumRowsInBlock() function to set the number of rows in a block. However, the number of rows is invalid.
User Response:
Edit the procedure code and verify the value for the nRows argument in the INFA_CTASetNumRowsInBlock() function is greater than 0 and less than or equal to the value returned by the INFA_CTAGetOutputRowMax() function.

EP_13268 Fatal Error: It is illegal to call INFA_CTASetOutputNumRowsMax at run-time.

Explanation:
The Custom transformation procedure code contains the INFA_CTASetOutputNumRowMax() function in a notification function.
User Response:
Edit the procedure code and only use the INFA_CTASetOutputNumRowMax() function in an initialization function.

EP_13269 Fatal Error: Invalid block size is being passed to INFA_CTASetOutputNumRowsMax.

Explanation:
The Custom transformation procedure code uses the INFA_CTASetOutputNumRowMax() function, but the nRowsMax argument is an invalid number.
User Response:
Edit the procedure code and verify nRowsMax is a positive number.

EP_13270 Fatal Error: Downstream Transformations have encountered a fatal error. Please refer to session log.

Explanation:
A transformation downstream from a Custom transformation encountered a fatal error.
User Response:
Read the session log for other error messages.