Jump to content
Welcome to our new Citrix community!
  • 1

Citrix ICA could not configure Thinwire and switch to the remote ICA display. VDA got stuck while idle!?

Joey Verlinden


We're experiencing a strange issue in our Citrix Environment. We’re running MCS managed VDI's on a Windows 10 1607 LTSB os with VDA 7.18.2. This issue also occurs in VDA 7.18.

It seems that some VDA’s gets "stuck" if it is idle for a while. Somehow Citrix sees the specific/stuck VDA as "Ready" and wants to connect a user to it. Somehow this specific VDA is the first in the queue to host a user who tries to connect. Al upcoming users trying to connect fail with the same issue cause the VDA does not respond as it should. When we shutdown the specific/stuck VDA users are being connected to the next VDA in the queue which is then successful again.


Issue occurred with VMTools 10.2.0 / 10.2.5. No additional GRID/GPU cards involved.


We've build a workaround which shutsdown the VDA if Event ID 6 is found at the VDA. Event ID 45 is also logged at that moment in the Delivery Controller event viewer. With a clean image (vanilla image) we still experience the same issue.


VDA Event(s):

Message              : Citrix ICA could not configure Thinwire and switch to th
                       e remote ICA display. Rebooting the workstation or loggi
                       ng in at the console will fix this.
Id                   : 6
Version              : 0
Qualifiers           : 
Level                : 2
Task                 : 0
Opcode               : 0
Keywords             : 4611686018427387904
RecordId             : 1
ProviderName         : Citrix-HostCore-ICA Service
ProviderId           : d90259ce-e290-4352-bf3c-a9d8b40b6048
LogName              : Citrix-HostCore-ICA Service/Admin
ProcessId            : 2668
ThreadId             : 4540
MachineName          : VDAHOSTNAME.domain.local
UserId               : S-1-5-19
TimeCreated          : 3-12-2018 11:20:52
ActivityId           : 
RelatedActivityId    : 
ContainerLog         : citrix-hostcore-ica service/admin
MatchedQueryIds      : {}
Bookmark             : System.Diagnostics.Eventing.Reader.EventBookmark
LevelDisplayName     : Fout
OpcodeDisplayName    : Info
TaskDisplayName      : 
KeywordsDisplayNames : {}
Properties           : {System.Diagnostics.Eventing.Reader.EventProperty}


Message              : The Citrix Desktop Service detected that a user session

                       has ended. Session 234eac42-4423-47f8-9736-0f85f9a6993b

                       for user 'username' has ended; reason code ConnectionFai


Id                   : 1030

Version              :

Qualifiers           : 16384

Level                : 4

Task                 : 0

Opcode               :

Keywords             : 36028797018963968

RecordId             : 4024

ProviderName         : Citrix Desktop Service

ProviderId           :

LogName              : Application

ProcessId            :

ThreadId             :

MachineName          : VDAHOSTNAME.domain.local

UserId               :

TimeCreated          : 3-12-2018 11:20:52

ActivityId           :

RelatedActivityId    :

ContainerLog         : application

MatchedQueryIds      : {}

Bookmark             : System.Diagnostics.Eventing.Reader.EventBookmark

LevelDisplayName     : Informatie

OpcodeDisplayName    :

TaskDisplayName      :

KeywordsDisplayNames : {Klassiek}

Properties           : {System.Diagnostics.Eventing.Reader.EventProperty, Syste

                       m.Diagnostics.Eventing.Reader.EventProperty, System.Diag



Delivery Controller Event:

Log Name:      Citrix-XenDesktop-BrokerMonitor/Operational

Source:        Citrix-XenDesktop-BrokerMonitor

Date:          3-12-2018 11:20:59

Event ID:      45

Task Category: Session Lifecycle events

Level:         Information


User:          NETWORK SERVICE

Computer:      XDDCHostname.domain.local


BrokerSessionStartFailed event

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


    <Provider Name="Citrix-XenDesktop-BrokerMonitor" Guid="{2386F16F-1B93-4F2B-91A8-0DE5ADFA092A}" />







    <TimeCreated SystemTime="2018-12-03T10:20:59.581541000Z" />


    <Correlation />

    <Execution ProcessID="1476" ThreadID="10700" />


    <Computer> XDDCHostname.domain.local </Computer>

    <Security UserID="S-1-5-20" />



    <Data Name="EventTime">2018-12-03T10:20:52.130000000Z</Data>

    <Data Name="SessionKey">{234EAC42-4423-47F8-9736-0F85F9A6993B}</Data>

    <Data Name="MachineSid">S-1-5-21-2155611120-281562227-2711537737-38359</Data>

    <Data Name="ClientIPAddress">12.34.567.89</Data>

    <Data Name="LaunchedViaIPAddress">


    <Data Name="BrokeringUserSid">S-1-5-21-2155611120-281562227-2711537737-3795</Data>

    <Data Name="BrokeringUserName">dom\username</Data>

    <Data Name="BrokeringUpn">username@domain.local</Data>

    <Data Name="BrokeringUserFullName">Firstname Lastname</Data>

    <Data Name="IsApp">false</Data>

    <Data Name="IsNonBrokered">false</Data>

    <Data Name="ClientName">PC1234</Data>

    <Data Name="ConnectedViaIPAddress">


    <Data Name="IsSecureIca">false</Data>

    <Data Name="Protocol">


    <Data Name="IsAnonymous">false</Data>

    <Data Name="DesktopGroupId">{00000000-0000-0000-0000-000000000000}</Data>

    <Data Name="FailureReason">4</Data>

    <Data Name="LaunchRequestTime">2018-12-03T10:20:50.003000000Z</Data>

    <Data Name="VdaSelectedTime">2018-12-03T10:20:50.050000000Z</Data>

    <Data Name="VdaPowerOnTime">2000-01-01T00:00:00.000000000Z</Data>

    <Data Name="VdaPoweredOnTime">2000-01-01T00:00:00.000000000Z</Data>

    <Data Name="VdaRegisteredTime">2000-01-01T00:00:00.000000000Z</Data>

    <Data Name="VdaPrepareRequestTime">2018-12-03T10:20:50.050000000Z</Data>

    <Data Name="VdaReturnedTime">2018-12-03T10:20:50.393000000Z</Data>

    <Data Name="ValidateSessionTime">2000-01-01T00:00:00.000000000Z</Data>





We're still looking into this issue. Any suggestions would be helpfull!


Link to comment

3 answers to this question

Recommended Posts

  • 1
1 hour ago, Brad Munson1709155772 said:


Sorry I don't have anything to help, but we are experiencing the same thing you explained here but we are on 7.15 LTSR.  Were you able to resolve this yet?



No, we didn't. We have build a workaround which reboots the vda (vdi) while the specific event id is logged. That made it better but did not solve the actual issue. The problem still exists in 7.18, 7.18.2 and 1811. Citrix Support did not have a solution.

  • Like 1
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...