We are running 2209 with MCS provisioned, non persistent VM's. We have 10+ machine catalogs. This morning, in one of those machine catalogs all the VDA's that were registered were going into an unregistered state during session launch which was producing the error "Cannot Start Desktop" to the users. In Director we were seeing a mixture of "Communication Error", "Other" or "Connection Timeout". Some of these users have access to other VDA's in different machine catalogs and they were able to log into those without issue so we proved it was Machine Catalog specific.
This was replicable for internal and external users.
The last time this machine catalog was updated was a week ago. We have had no issues since the update or in the previous weeks during alpha and beta testing. That update included the 2209 VDA (from 2203) & Windows updates. These same updates have been applied to other machine catalogs (going back as far as early January) and we haven't yet seen a repeat of those issues.
We put all the VDA's in MM, shut them down, brought them back up and they all came back registered but as soon as users started sessions on them they went into the unregistered state again.
Checking the DC's (we have 2) we saw warning events ID #1039 on the Citrix Broker Service:
_______________
"The Citrix Broker Service failed to contact virtual machine 'vm-038.domain.com' (IP address xxx.xxx.xxx.xxx).
Check that the virtual machine can be contacted from the controller and that any firewall on the virtual machine allows connections from the controller. See Citrix Knowledge Base article CTX126992.
Error details:
Exception 'The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.' of type 'System.ServiceModel.FaultException'."
______________
I checked the master image and confirmed that both the DC's were listed in HKLM\Software\Citrix\VirtualDesktopAgent\ListofDDCs - they were. I was able to ping both DC's too and RDP to them from the master image.
---WIERD FIX ALERT---
After checking the registry in the master image I shut it down, took a snapshot and then updated the machine catalog. After rebooting the VM's all users could start sessions.
I'm stumped, any ideas or anyone else seen this behavior?
Question
Ross Faverty1709158252
We are running 2209 with MCS provisioned, non persistent VM's. We have 10+ machine catalogs. This morning, in one of those machine catalogs all the VDA's that were registered were going into an unregistered state during session launch which was producing the error "Cannot Start Desktop" to the users. In Director we were seeing a mixture of "Communication Error", "Other" or "Connection Timeout". Some of these users have access to other VDA's in different machine catalogs and they were able to log into those without issue so we proved it was Machine Catalog specific.
This was replicable for internal and external users.
The last time this machine catalog was updated was a week ago. We have had no issues since the update or in the previous weeks during alpha and beta testing. That update included the 2209 VDA (from 2203) & Windows updates. These same updates have been applied to other machine catalogs (going back as far as early January) and we haven't yet seen a repeat of those issues.
We put all the VDA's in MM, shut them down, brought them back up and they all came back registered but as soon as users started sessions on them they went into the unregistered state again.
Checking the DC's (we have 2) we saw warning events ID #1039 on the Citrix Broker Service:
_______________
"The Citrix Broker Service failed to contact virtual machine 'vm-038.domain.com' (IP address xxx.xxx.xxx.xxx).
Check that the virtual machine can be contacted from the controller and that any firewall on the virtual machine allows connections from the controller. See Citrix Knowledge Base article CTX126992.
Error details:
Exception 'The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.' of type 'System.ServiceModel.FaultException'."
______________
I checked the master image and confirmed that both the DC's were listed in HKLM\Software\Citrix\VirtualDesktopAgent\ListofDDCs - they were. I was able to ping both DC's too and RDP to them from the master image.
---WIERD FIX ALERT---
After checking the registry in the master image I shut it down, took a snapshot and then updated the machine catalog. After rebooting the VM's all users could start sessions.
I'm stumped, any ideas or anyone else seen this behavior?
Link to comment
3 answers to this question
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now