Exception Code | Description | Notes |
TransactionException001 | Error during processing. Full transaction roll back. | QDoc processing failed. The entire transaction rolls back. |
TransactionException002 | Invalid routing ID | An invalid routing ID was used in the QDoc. The routing ID determines if the QDoc is processed using the service interface API or UI API. Check the routing for each QDoc in the Configuration Manager under Schemas by QAD Enterprise Applications version. |
TransactionException003 | Unable to load routing document | The correct document is not in routing.xml, or is an invalid XML document. |
TransactionException004 | Error creating RoutingTask object | RoutingTask object cannot be instantiated. Review routing.xml for the QDoc for a particular route. |
TransactionException005 | RoutingTask object is not a routing task | The RoutingTask object in routing.xml is not the correct type. |
TransactionException006 | Null field returned by the processor | QAD Enterprise Applications reports that the current field is null, or the session that started the program failed to initialize, or QAD Enterprise Applications aborted abnormally. To determine the cause, run an QAD Enterprise Applications CHUI session manually using the Connection Pool Manager startup script and follow the processing in the QDoc. |
TransactionException007 | Error during processing. Partial transaction roll back. | QXtend was unable to complete the processing of the QDoc. View the response QDoc for the error that caused the problem. This rolls back the current transaction (main iteration level) in QAD Enterprise Applications. |
TransactionException009 | Requested delete operation did not occur | QXtend was unable to delete a record in QAD Enterprise Applications. |
TransactionException010 | Program did not initialize | The QAD Enterprise Applications session failed to initialize; this failure was probably due to an incorrect setting on the QAD Enterprise Applications side. Check for PROGRESS errors and verify that the compilation is correct. Also check the PROPATH settings on the telnet script. |