Secure Private Access sessions codes in DaaS Monitor
The following tables provide a list of error codes related to application enumeration, application launch, and sessions in Citrix Monitor.
For related information, see the following topics:
Session codes
| Code | Status | Description |
|---|---|---|
| 2101 | Failure | Session failure |
| 2102 | active/inactive/failure | Session is active or terminated or at least one app launch in the session failed |
| 2000 | Active | The session is active |
| 2001 | Inactive | Session is terminiated/inactive |
App enumeration message codes
| Code | Status | Description |
|---|---|---|
| 1101 | failure | An internal error occurred during the enumeration |
| 1102 | failure | Some apps were enumerated but at least one app evaluation failed |
| 1103 | failure | No apps were enumerated and at least one app evaluation failed |
| 1000 | Success | Enumeration was successful. At least one app was enumerated |
| 1001 | Success | No apps were enumerated because they were all denied by policies |
| 1002 | Success | No apps were enumerated because no policies matched |
| 1003 | Success | No apps were enumerated because some were denied and for others, no policies matched |
| 1004 | Success | No apps were enumerated because no policies to evaluate |
| 3101 | Failure | App enumeration - An internal error occurred (currently unused) |
| 3102 | Failure | App was not enumerated because there was an exception during policy evaluation |
| 3103 | Failure | App enumeration status is null - An internal error occurred during policy evaluation |
| 3104 | Allow/deny/failure | Error retrieving policy details for the app |
| 3000 | Allow | App enumeration is allowed |
| 3001 | Deny | App enumeration is denied by policy |
| 3002 | Deny | App was not enumerated because no policies matched |
| 3003 | Unknown | App enumeration status is unknown |
| 3004 | App launch from CEB | App launch attempt from Citrix Enterprise Browser |
App launch message codes
| Code | Status | Description |
|---|---|---|
| 4101 | Failure | Application launch error - An internal error occurred during application launch |
| 4102 | Failure | Application launch error (internal) |
| 4103 | Allow/deny/failure | Error retrieving policy details for the app |
| 4104 | Failure | Application Launch Error - No application configuration found |
| 4000 | Allow | App Launch is allowed |
| 4001 | Deny | Application launch was denied because of a policy |
| 4002 | Deny | Application launch was denied because no policy matched |
| 5001 | Failure | TCP - connection failed |
| 5002 | Failure | TCP - peer missing or server state not up |
| 5003 | Failure | TCP - probe failed |
| 5004 | Failure | TCP - memory allocation in gateway failed |
| 0x10050A | Failure | No application configuration found for the FQDN/IP |
| 0x100501 | Failure | No application configuration found for the FQDN/IP |
| 0x100502 | Failure | No application configuration found for the FQDN/IP |
| 0x100503 | Failure | No application configuration found for the FQDN/IP |
| 0x100504 | Failure | Error in enforcing access policy |
| 0x100505 | Failure | Unexpected internal error |
| 0x100506 | Failure | Error in fetching policy configuration |
| 0x100507 | Failure | Error in fetching configuration to enforce policy |
| 0x100508 | Failure | No matched policy condition |
| 0x100509 | Failure | No access policy configuration found for the application |
| 0x10050B | Failure | Unexpected internal error |
| 0x10050C | Failure | One or more applications were either allowed or denied access for various reasons |
| 0x10050D | Failure | Revoked access |
| 0x1800D4 | Failure | TCP/UDP app launch has failed during policy evaluation |
| 0x1800D5 | Failure | TCP/UDP App launch has failed during policy evaluation |
| 0x1800D6 | Failure | TCP/UDP App launch has failed during policy evaluation |
| 0x1800D7 | Failure | TCP/UDP App launch has failed during policy evaluation |
| 0x1800D8 | Failure | TCP/UDP App launch has failed during policy evaluation |
| 0x1800D9 | Failure | TCP/UDP app launch has failed during parsing policy evaluation response |
| 0x1800DA | Failure | TCP/UDP app launch has failed with invalid result during policy evaluation |
| 0x1800DB | Failure | TCP/UDP app launch has failed with invalid resource location configuration |
| 0x1800DC | Failure | TCP app launch has failed due to the unsupported Enhanced Security policy configured for the app |
| 0x1800DD | Failure | TCP app launch has failed due to unsupported Secure Browser Service redirection configured for TCP app |
| 0x1800DE | Failure | TCP/UDP app launch has failed as there is no application configuration found for the destination |
| 0x1800DF | Failure | TCP/UDP app launch is denied as per policy |
| 0x1800E0 | Failure | TCP/UDP app launch failed as length of App Name is too long |
| 0x1800E1 | Failure | TCP/UDP app launch failed with internal error |
| 0x1800E4 | Failure | TCP app launch has failed during connection establishment to private TCP server |
| 0x1800E5 | Failure | TCP app launch has failed during connection establishment to private TCP server |
| 0x1800E6 | Failure | TCP app launch has failed during connection establishment to private TCP server |
| 0x1800E7 | Failure | TCP app launch has failed during connection establishment to private TCP server |
| 0x1800E8 | Failure | TCP app launch has failed during connection establishment to private TCP server |
| 0x1800E9 | Failure | TCP app launch has failed during connection establishment to private TCP server |
| 0x1800EF | Failure | TCP app launch has failed during connection establishment to private TCP server |
| 0x1800EE | Failure | TCP app launch has failed due to an invalid application ID |
| 0x1800EA | Failure | TCP app launch has failed due to destination FQDN is too long |
| 0x1800EB | Failure | TCP app launch has failed due to internal error |
| 0x1800EC | Failure | TCP app launch has failed due to internal error |
| 0x1800ED | Failure | TCP app launch has failed due to destination IP is invalid |
| 0x13000001 | Failure | App access failed as the session expired |
| 0x13000002 | Failure | App access failed as inadequate license |
| 0x13000003 | Failure | App access failed as access forbidden |
| 0x13000004 | Failure | App access failed as the server is unavailable |
| 0x13000005 | Failure | App access failed as the server is unavailable |
| 0x13000006 | Failure | App access failed as the enhanced control restricted |
| 0x13000007 | Failure | App access failed as the access policy is disabled or the user is not subscribed |
| 0x13000008 | Failure | App access failed as access denied due to the configured access policy |
| 0x13000009 | Failure | App access failed as the routing entry is missing |
| 0x1300000A | Failure | App access failed due to an unknown error |
| 0x1300000B | Failure | The client closed the connection |
| 0x1300000C | Failure | The FQDN resolution over ZTNA failed |
| 0x1300000D | Failure | UDP packet sent back to client failed with socket error |
| 0x10000401 | Failure | Citrix rendezvous server dial Failed |
| 0x10000402 | Failure | Unable to register the Connector Appliance |
| 0x10000403 | Failure | Connection error |
| 0x10000404 | Failure | Connection error |
| 0x10000407 | Failure | Connection error |
| 0x10000405 | Failure | Back end Unreachable |
| 0x10000406 | Failure | DNS Resolution Failed |
| 0x10000408 | Failure | UDP packet transmission failure |
| 0x10000409 | Failure | UDP packet receiving failure |
| 0x1000040A | Failure | Control packet parsing failure |
| 0x1000040B | Failure | Control packet transmission failure |
| 0x1000040C | Failure | UDP network connection initialization failure |
| 0x1000040D | Failure | Error on writing back end |
| 0x1000040E | Failure | Error on reading back end |
| 0x1000040F | Failure | Error on reading Gateway service |
| 0x10000410 | Failure | Error on writing Gateway service |
| 0x10000411 | Failure | Gateway service closed the connection |
| 0x10000412 | Failure | Back end closed the connection |
| 0x10000413 | Failure | Error in determining connection teardown reason |
| 0x10000414 | Failure | Invalid IP/hostname or port |
| 0x10000415 | Failure | Connection refused by the destination |
| 0x10000416 | Failure | No such host found |
| 0x10000417 | Failure | Network is unreachable |
| 0x10000302 | Failure | Failed to read proxy server details |
| 0x10000306 | Failure | Configured proxy servers are not reachable |
Secure Private Access sessions codes in DaaS Monitor
Copied!
Failed!