| N/A |
[0] Unknown. This error code is not mapped. |
The Monitoring service cannot determine the reason for the reported launch or connection failure from information shared by the Brokering service. |
Collect CDF logs on the controller and contact Citrix support. |
| [0] None |
[1] None |
None |
N/A |
| [2] MachineFailure |
[2] SessionPreparation |
Session preparation request from the delivery controller to the VDA failed. Possible causes: Communication issues between the controller and the VDA, issues experienced by the Broker Service while creating a prepare request, or network issues resulting in the VDA not accepting the request. |
Refer to troubleshooting steps listed in Knowledge center article, Troubleshooting Virtual Delivery Agent Registration with delivery controllers in Citrix Virtual Apps and Desktops for common problems that cause communication issues between the controller and the VDA. |
| [2] MachineFailure |
[3] RegistrationTimeout |
The VDA was powered on, but a time-out occurred while it was attempting to register with the delivery controller. |
Verify that the Citrix Broker Service is running on the delivery controller and that the Desktop service is running on the VDA. Start each if stopped. |
| [1] ClientConnectionFailure |
[4] ConnectionTimeout |
The client did not connect to the VDA after the VDA was prepared for session launch. The session was successfully brokered, but a time-out occurred while waiting for the client to connect to the VDA. Possible causes: Firewall settings, network interruptions, or settings that prevent remote connections. |
Check the Director console to see if the client currently has an active connection, which means no user is impacted. If no session exists, review the event logs on the client and on the VDA for any errors. Resolve any issues with network connectivity between the client and the VDA. |
| [4] NoLicensesAvailable |
[5] Licensing |
The licensing request failed. Possible causes: Insufficient number of licenses, or the license server has been down for more than 30 days. |
Verify that the license server is online and reachable. Resolve any network connectivity issues to the license server or reboot the license server if it appears to be malfunctioning. Verify that there are sufficient licenses in the environment and allocate more if necessary. |
| [1] ClientConnectionFailure |
[6] Ticketing |
A failure occurred during ticketing, indicating that the client connection to the VDA does not match the brokered request. A launch request ticket is prepared by the Broker and delivered in the ICA® file. When the user attempts to launch a session, the VDA validates the launch ticket in the ICA file with the Broker. Possible causes: ICA file is corrupt or the user is attempting to make an unauthorized connection. |
Verify that the user has access to the application or desktop based on user groups defined in the delivery groups. Instruct the user to relaunch the application or desktop to determine whether this is a one off issue. If the issue occurs again, review the client device event logs for errors. Verify that the VDA to which the user is attempting to connect is registered. If unregistered, review the event logs on the VDA and resolve any registration issues. |
| [1] ClientConnectionFailure |
[7] Other |
A session has been reported as terminated from the VDA after the client has initially contacted the VDA but before it completed the connection sequence. |
Verify if the session was not terminated by the user before launch. Try relaunching the session, if the problem persists, collect CDF logs and contact Citrix support. |
| [1] ClientConnectionFailure |
[8] GeneralFail |
The session failed to launch. Possible causes: A brokered launch was requested while the broker was still starting up or initializing, or internal error during the brokering phase of a launch. |
Verify that the Citrix Broker Service is running and retry launching the session. |
| [5] Configuration |
[9] MaintenanceMode |
The VDA, or the delivery group to which the VDA belongs, is set in maintenance mode. |
Determine whether maintenance mode is required. Disable maintenance mode on the delivery group or machine in question if it is not needed and instruct the user to attempt to reconnect. |
| [5] Configuration |
[10] ApplicationDisabled |
The application cannot be accessed by end users because it has been disabled by the administrator. |
If the application is intended to be available for production use, enable the application and instruct the user to reconnect. |
| [4] NoLicensesAvailable |
[11] LicenseFeature Refused |
The feature being used is not covered by the existing licenses. |
Contact a Citrix sales representative to confirm the features that are covered by the existing Citrix Virtual Apps and Desktops™ license edition and type. |
| [3] NoCapacityAvailable |
[13] SessionLimitReached |
All VDAs are in use and there is no capacity to host more sessions. Possible causes: All VDAs are in use (for single-session OS VDAs), or all VDAs have reached the configured maximum concurrent sessions allowed (for multi-session OS VDAs). |
Verify if there are any VDAs in maintenance mode. Disable maintenance mode if it is not needed to free up more capacity. Consider increasing the value of Maximum Number of Sessions in the Citrix policy setting to allow more sessions per server VDA. Consider adding more multi-session OS VDAs. Consider adding more single-session OS VDAs. |
| [5] Configuration |
[14] DisallowedProtocol |
The ICA and RDP protocols are not allowed. |
Run the Get-BrokerAccessPolicyRule PowerShell command on the delivery controller and verify that the AllowedProtocols value has all the desired protocols listed. This issue occurs only if there is a misconfiguration. |
| [5] Configuration |
[15] ResourceUnavailable |
The application or desktop to which the user is attempting to connect is not available. This application or desktop might not exist, or there are no VDAs available to run it. Possible causes: The application or desktop has been unpublished, or the VDAs hosting the application or desktop have reached maximum load, or the application or desktop is set in maintenance mode. |
Verify that the application or desktop is still published and the VDAs are not in maintenance mode. Determine whether the multi-session OS VDAs are at full load. If so, provision more multi-session OS VDAs. Verify that there are single-session OS VDAs available for connections. Provision more single-session OS VDAs if necessary. |
| [5] Configuration |
[16] ActiveSessionReconnectDisabled |
The ICA session is active and connected to a different endpoint. However, because the Active Session Reconnection is disabled, the client cannot connect to the active session. |
On the delivery controller, verify that Active Session Reconnection is enabled. Verify that the value of DisableActiveSessionReconnect in the registry, under HKEY_LOCAL_MACHINE\Software\Citrix\Desktop\Server is set to 0. |
| [2] MachineFailure |
[17] NoSessionToReconnect |
The client attempted to reconnect to a specific session but the session was terminated. |
Retry the workspace control reconnection. |
| [2] MachineFailure |
[18] SpinUpFailed |
The VDA cannot be powered on for session launch. This is a hypervisor reported issue. |
If the machine is still powered off, attempt to start the machine from Citrix Studio. If this fails, review the hypervisor connectivity and permissions. If the VDA is a PVS-provisioned machine, verify in the PVS console that the machine is running. If not, verify that the machine is assigned a Personal vDisk, log in to the hypervisor to reset the VM. |
| [2] MachineFailure |
[19] Refused |
The delivery controller sends a request to the VDA to prepare for a connection from an end user, but the VDA actively refuses this request. |
Verify via ping, that the delivery controller and the VDA can successfully communicate. If not, resolve any firewall or network routing issues. |
| [2] MachineFailure |
[20] ConfigurationSet Failure |
The delivery controller did not send required configuration data, such as policy settings and session information, to the VDA during session launch. Possible causes: Communication issues between the controller and the VDA, issues experienced by the Broker Service while creating a configuration set request, or network issues resulting in the VDA not accepting the request. |
- |
| [3] NoCapacityAvailable |
[21] MaxTotalInstancesExceeded |
The maximum number of instances of an application has been reached. No additional instances of the application can be opened on the VDA. This issue is related to the application limits feature. |
Consider increasing the application setting, Limit the number of instances running at the same time to a higher value if licensing permits. |
| [3] NoCapacityAvailable |
[22] MaxPerUserInstancesExceeded |
The user is attempting to open more than one instance of an application but the application is configured to allow only a single instance of the application per user. This issue is related to the application limits feature. |
Only one instance of the application is allowed per user by default. If multiple instances per user are required, consider clearing the Limit to one instance per user setting in the application setting. |
| [1] ClientConnectionFailure |
[23] Communication error |
The delivery controller attempted to send information to the VDA, such as a request to prepare for a connection, but an error occurred during the communication attempt. This can be caused due to network disruptions. |
If already started, restart the Desktop service on the VDA to restart the registration process and verify that the VDA registers successfully. Confirm that the delivery controllers configured for the VDA are accurate via the details in the application event log. |
| [3] NoCapacityAvailable |
[100] NoMachineAvailable Monitoring service converts [12] NoDesktopAvailable to this error code. |
The VDA assigned to launch the session is in an invalid state or is unavailable. Possible causes: Power state of the VDA is unknown or unavailable, the VDA did not reboot since the last user's session, session sharing is disabled while the current session requires it to be enabled, or the VDA was removed from the delivery group or from the site. |
Verify that the VDA is in a delivery group. If not, add it to the appropriate delivery group. Verify that there are sufficient VDAs registered and in ready state to be able to launch the published shared desktop or application requested by the user. Verify that the hypervisor hosting the VDA is not in maintenance mode. |
| [2] MachineFailure |
[101] MachineNotFunctional. Monitoring service converts [12] NoDesktopAvailable to this error code. |
The VDA is not operational. Possible causes: The VDA was removed from the delivery group, the VDA is unregistered, the VDA power state is unavailable, or the VDA is experiencing internal issues. |
Verify that the VDA is in a delivery group. If not, add it to the appropriate delivery group. Verify that the VDA shows as powered on in Citrix Studio. If the power state is unknown for several machines, resolve any issues with connectivity to the hypervisor or host failures. Verify that the hypervisor hosting the VDA is not in maintenance mode. Restart the VDA once these issues have been addressed. |
