D365 Finance Operations - Error Handling (Magic xpi 4.14)
The Magic xpi Server Flow Manager checks for errors during the execution of a step. If there is an error in D365 Finance Operations connector step, the Error Handler is invoked and handles the error.
The error codes for the D365 Finance Operations connector are listed below. You can also use Magic xpi's General Component Errors with the D365 Finance Operations connector. The codes are returned to the Magic xpi Server in the Invocation program’s Error Code parameter.
|
|
|
|
8888
|
.Net Exception
|
|
9999
|
Java Exception
|
|
1601
|
Step invocation errors
|
|
1602
|
ACM: No available AC found
|
|
1603
|
AC: Step incorrectly configured
|
|
1604
|
Input/Output error
|
|
1605
|
Communication: Data Transfer error
|
|
1606
|
.Net Launcher: Failed to call .Net connector
|
|
1607
|
.Net Launcher: More than one IStep .Net-assembly found
|
|
1608
|
.Net Launcher: No IStep .Net-assembly found
|
|
1609
|
Communication: Message processing error
|
|
1610
|
RemoteStepInvoker: Invocation timeout error
|
|
1611
|
.Net Launcher: Java-.Net interop failure
|
|
1612
|
AC: Unknown connector name
|
|
1613
|
AC: Unsupported runtime technology
|
|
1614
|
AC: Metadata file for the connector not found
|
|
1615
|
AC: Wrong data in metabata.xml file
|
|
1621
|
Trigger Load Timeout
|
|
1622
|
ACM: No available AC found for the trigger
|
Error Handling in Magic xpi
