Stop processing this rule and Stop processing more rules can be combined, in which case the value is the sum of the two individual values, that is, 6.
The ARM captures the following transaction information from EFT Server, which appears in the ARM database and reports:
Actions
|
ResultID |
Description |
Result Const |
|
0 |
If the Event Action is successfully executed |
EAR_SUCCESS |
|
1 |
If the Event Action fails |
EAR_FAIL |
|
2 |
If STOP Processing this rule is selected as Action. |
EAR_STOP_RULE |
|
4 |
If STOP processing more rules is selected as Action |
EAR_STOP_ALL |
|
|
Stop processing this rule and Stop processing more rules can be combined, in which case the value is the sum of the two individual values, that is, 6. |
SocketConnection
|
ResultID |
Description |
Result Const |
|
0 |
When socket successfully created |
ER_NONE |
|
8 |
Per Site socket connection limit exceeded |
ER_CONNECT_FAILED_TOO_MANY_CONNECTIONS_PER_SITE |
|
9 |
Max connections per IP address limit exceeded |
ER_CONNECT_FAILED_TOO_MANY_CONNECTIONS_PER_IP |
|
10 |
EFT Server denied the connection because the IP address was in the ban list or it is a remote IP address and EFT Server is in developer mode |
ER_CONNECT_FAILED_RESTRICTED_IP |
|
11 |
EFT Server denied the connection (failed) and added the IP address to the auto-ban list |
ER_CONNECT_FAILED_BANNED_IP |
Authentications
|
ResultID |
Description |
Result Const |
|
0 |
Authentication successful |
LR_OK |
|
1 |
Incorrect password |
LR_PASSWORD_NOT_ACCEPTED |
|
2 |
If user account is disabled |
LR_ACCOUNT_DISABLED |
|
3 |
Max connections per Site limit exceeded |
LR_TOO_MANY_CONNECTIONS_PER_SITE |
|
4 |
Max connections per user limit exceeded |
LR_TOO_MANY_CONNECTIONS_PER_USER |
|
5 |
User per- IP address connection limit exceeded |
LR_TOO_MANY_CONNECTIONS_PER_IP |
|
6 |
If given protocol is not supported |
LR_PROTOCOL_NOT_SUPPORTED |
|
7 |
Connection on restricted IP address |
LR_RESTRICTED_IP |
|
8 |
If service is unavailable |
LR_SERVICE_UNAVAILABLE |
ClientOperations
|
ResultID |
Description |
Result Const |
|
1 |
If copy/move/download operation is successful |
TRUE |
|
0 |
If copy/move/download operation fails |
FALSE |
CustomCommands
|
ResultID |
Description |
Result Const |
|
0 |
Command executed successfully |
CER_OK |
|
1 |
Command executed with socket output |
CER_SYNC |
|
2 |
Access is denied |
CER_ACCESS_DENIED |
|
3 |
Command is not found |
CER_COMMAND_NOT_FOUND |
|
4 |
Could not launch the selected process |
CER_PROCESS_FAILED |
|
5 |
Command is disabled |
CER_COMMAND_DISABLED |
|
6 |
Errors in parameters passed to the custom command |
CER_ERROR_IN_PARAMS |
ProtocolCommands
ProtocolCommands are the same as FTP result codes. Below is a short summary.
|
ResultID |
Description |
|
1xx |
Expected another reply before proceeding with a new command |
|
2xx |
Requested action completed successfully |
|
3xx |
On hold pending receipt of further information |
|
4xx |
Temporary failure |
|
5xx |
Permanent failure |