Connection Failure Reports on Director

Connection Failure Reports on Director

book

Article ID: CTX286909

calendar_today

Updated On:

Description

Reasons for the Connection failure reports on the Director.


Instructions

Here are the different connection failure types:

Client Connection Failures

Failures due to the inability of the client side to complete the session connection. For example, connection timed out, server was not reachable.

Machine Failures

Connection failures that are the result of the machine being in a failed state or failure to start up or respond.

Unavailable Capacity

Failures due to the configured capacity of a particular delivery group having been completely consumed. For example, too many users logged into a Server Desktop OS delivery group or a user accessing a Pooled Random delivery group while all the machines in the delivery group are already assigned to other users.

Unavailable Licenses

Failures that occur when the delivery controller is unable to acquire a license from the license server to launch the session.

Configuration Errors

Failures caused by configuration errors. For example, an administrator places a Delivery Group or a particular machine in Maintenance mode.



Here are the various reasons for connection failures:
 

Session Preparation

Session prepare request from Broker service to VDA failed.

Registration Timeout

VDA did not register in time after being powered on for session launch.

Connection Timeout

Client did not connect to VDA after VDA was prepared for session launch.

Licensing

License request failed (typically no license available).

Ticketing

Failure during ticketing, indicating that the client connection to VDA does not match the brokered request.

Other

General unresolved errors between client and VDI.

General Fail

General unresolved errors during initial brokering operation.

Maintenance Mode

Machine or delivery group in maintenance mode.

Application Disabled

Application can no longer be used and has been disabled by the admin.

License Feature Refused

Feature being used is not licensed (e.g. license doesn’t allow use of multi-session VDAs).

Session Limit Reached

No more sessions allowed (e.g. launching second session on VDI VDA).

Disallowed Protocol

Resource doesn’t allow protocol requested by session launch.

Resource Unavailable

Resource has been removed/disabled since enumeration.

Active Session Reconnect Disabled

Session is already connected to a different endpoint but session stealing is disabled.

No Session To Reconnect

Specified session could not be found during reconnect.

Spin up Failed

VDA could not be powered-on for session launch.

Refused

VDA actively refused session prepare request.

Configuration Set Failure

Failed to send required configuration data to VDA prior to session launch

No Machine Available

No machine available for launch (e.g. all shared VDI machines in group are in use).

Machine Not Functional

Non-power-managed assigned machine not registered.

Additional resources: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/director/failure_reasons_troubleshooting.html

Additional Information