Salesforce

FTP - Error Handling (Magic xpi 4.14)

« Go Back

Information

 
Created BySalesforce Service User
Approval Process StatusPublished
Objective
Description

FTP – 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 an FTP component step, the Error Handler is invoked and handles the error.

The first error in the step causes the termination of the step execution. If the step has multiple methods, and an error occurs in one of these methods, all subsequent methods are not executed.

While executing any method on the FTP server if there's a connection error (Socket Exception), then the Reconnection Policy (the Number of login retries and Delay between login retries parameters in the FTP Resource) is applied. If the reconnection is successful, then the process is continued. If the reconnection fails, then the process is terminated and an error message is shown in the Monitor.

The error codes for the FTP component are listed below. You can also use Magic xpi's General Component Errors with the FTP component. The codes are returned to the Magic xpi Server in the Invocation program’s Error Code parameter.

Error Code

Description

502

Java Exception

503

File Not Found

504

IO Error

505

Operation Failed

506

Parse Exception

507

Illegal arguments

508

FTP Exception

509

FTPS (SSL) connection has failed

510

Failed to load Server Certificate

511

Failed to load Client Certificate

512

Incorrect Client certificate password

513

FTP connection has failed

8888

.Net Exception

The following error codes are applicable for Local Agent.

1601

Step invocation error

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

Remote Stepinvoker: 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 metadata.xml file

1621

Trigger Load Timeout

1622

ACM: No available AC found for the trigger

Related Topics

Reference
Attachment 
Attachment