FIX Module Error Codes
0001.1004 The sessionID [{0}] is invalid. Ignoring this session
Explanation: Warning. The specified sessionID does not exist in the Appia engine. FIX Module ignores this session and continues initializing the other valid sessions.
Action: None.
0001.1006 Failed to connect to Appia engine {0}: {1}
Explanation: An error occurred when connecting to the specified Appia engine.
Action: Ensure that the host and port specified are valid or that the Appia engine is running at the specified host and port, and then reload FIX Module.
0001.1008 FIX Module is not yet configured. See the FIX Module Installation and User's Guide to complete the configuration
Explanation: FIX Module needs the host, port, and session information of the Appia engine.
Action: Use the FIX Module-My webMethods Server user interface to set the host, port, and session of the Appia engine.
0001.1012 FIX Module is not yet initialized. Check connection to Appia engine and try again.
Explanation: A request was sent to FIX Module before FIX Module was initialized.
Action: Ensure FIX Module is configured successfully before sending any requests.
0001.1023 FIX Module connection retry limit was reached
Explanation: The connection with the Appia engine could not be established even after retrying for the specified retry limit.
Action: Ensure connectivity with the Appia engine is restored, and then reload FIX Module.
0001.1025 FIX Module cannot connect to the Appia engine. Will retry up to {0} more time(s)
Explanation: Warning. FIX Module lost connectivity with the Appia engine, either because the Appia engine went down or because network connectivity was lost.
Action: Ensure that the connectivity to the Appia engine is established. FIX Module automatically recognizes when connectivity is restored and reloads itself to reinitiate the connection with the Appia engine.
0001.1026 FIX Module connection retry thread is being killed. Reload the FIX Module
Explanation: When FIX Module loses connectivity with the FIX engine, it contacts the engine at fixed intervals to attempt to reestablish the connection. When the configured retry limit is reached, FIX Module stops attempting to reconnect.
Action: Ensure connectivity to the Appia engine, and then manually reload FIX Module.
0001.1027 FIX Module is not configured. See the FIX Module installation and users guide for details on how to configure the FIX Module.
Explanation: During FIX Module startup, FIX engine configuration details were unavailable.
Action: Configure the FIX engine connection details using the FIX Module-My webMethods user interface.
0001.1033 Unrecoverable error in connection retry thread. Reload FIX Module. Error Message {0}
Explanation: FIX Module could not handle an error that occurred.
Action: Reload FIX Module.
0000.1015 Failed to retrieve session list from FIX engine. Supply a valid host and port and try again
Explanation: When attempting to retrieve the session list from FIX engine, the specified host and port for the FIX engine are invalid.
Action: Specify a valid FIX engine host and port and try again.
0000.1021 Error occured while retrieving session list from Appia engine. Reason: {0}
Explanation: FIX Module could not retrieve the FIX engine session list because the specified FIX engine is not running.
Action: Ensure that the FIX engine at the specified host and port is running before attempting to retrieve the session list.
0000.1022 Error occurred while storing FIX engine connection details in repository. Detailed message: {0}
Explanation: The FIX engine connection details were not stored in the repository because the Trading Networks database where the connection details reside was unavailable.
Action: Ensure that the Trading Networks database where the FIX engine connection details are stored is available.
0000.1023 Error occurred while retrieving FIX engine connection details from repository. Detailed message: {0}
Explanation: FIX Module could not retrieve the FIX engine connection information from the Trading Networks database.
Action: Ensure that the Trading Networks database is available.
0000.1025 Error occurred while storing connection retry thread details. Detailed message: {0}
Explanation: FIX Module connection retry thread information was not stored successfully.
Action: Ensure that the Trading Networks database is available.
0000.1026 Error occurred while retrieving connection retry thread details from repository. Detailed message: {0}
Explanation: FIX Module could not retreive the FIX engine connection retry thread information from the Trading Networks database.
Action: Ensure that the Trading Networks database is available.
0000.1032 Error occured while executing the operator command. Detailed message: {0}
Explanation: An error occured while executing the specified FIX engine operator command.
Action: Ensure the syntax of the operator command being executed is correct and the FIX engine is running.
0000.1044 Error initializing FIX Module. Check if Appia jar file is placed in the WmFIX package.
Explanation: During FIX Module startup, the Module could not find the appia.jar file.
Action: Copy the appia.jar file from the AppiaServer_homeDirectory\lib folder to the Integration Server_directory\packages\WmFIX\code\jars directory. Then restart Integration Server.
0000.1045 FIX Module cannot find the WM_FIX_CONFIGRATION_PARAMS table in the Trading Networks database. Create the table and restart FIX Module.
Explanation: FIX engine connection information is stored in the WM_FIX_CONFIGURATION_PARAMS table in the Trading Networks database. During FIX Module startup, FIX Module could not find the table in the Trading Networks database.
Action: Ensure that the WM_FIX_CONFIGURATION_PARAMS table exists. If it does not exist, create it by executing the .sql script provided in the WmFIX\config folder on the same database instance where Trading Networks is connected. Then reload FIX Module.
0002.1007 Error persisting inbound event "{0}". Cause: {1}
Explanation: An inbound Appia event cannot be persisted in Trading Networks.
Action: Examine the cause stated in the error message and contact Software AG Global Support.
0002.1009 Message Type dictionary for FIX version {0} is not loaded. Either the version is wrong or FIX module is not initialized.
Explanation: FIX Module received a FIX message for a version that is not supported.
Action: If the indicated FIX message version is not one that FIX Module supports, contact Software AG Global Support.
0003.1000 Operator command {0} to session {1} failed. Ensure that the Appia engine has network connectivity and the Appia engine is running, and then try again
Explanation: The operator command failed to execute, probably because connection with the Appia engine was lost.
Action: FIX Module automatically reconnects with the Appia engine after losing its connection. Try running the operator command again.
0003.1003 Could not retrieve the application message version for the session {0}.
Explanation: FIX Module is attempting to send a FIX message of FIXT type and cannot obtain the application message version because there is a mismatch in FIX version numbers.
Action: This error might occur if the session receiving the message is not configured for messages of type FIXT. Ensure that the configuration of the FIX engine session version and the FIX message version are the same.
0003.1004 The value {0} for the ApplVerID is invalid. Specify a valid value and try again. Refer to FIX specification for a list of valid values
Explanation: The FIX message being sent has an invalid value for the ApplVerID field.
Action: Ensure a valid value based on FIX specification is set for the AppllVerID field of the FIX message, and then try to send the FIX message again.
0003.1005 The field {0}, of the header is mandatory.
Explanation: FIX Module is sending a message that is missing values for required header fields.
Action: Specify the values for the mandatory fields, and then resend the message.