Jump to content


Photo

VDA failed to connect to one or more Delivery Controllers...

Started by christianmdu , 17 March 2017 - 04:00 PM
4 replies to this topic

Best Answer christianmdu , 22 March 2017 - 10:41 AM

I have just installed VDA 7.13 Desktop OS on to a VM in VMware but am having trouble with it registering with either of our two Delivery Controllers.

 

On the 'Delivery Controller' screen, I have added my two DCs and they have passed the 'Test connection' check but on the 'Summary' screen it says:

 

"Failed to connect to one or more Delivery Controllers. An incorrectly configured Controller can result in failure of the Virtual Delivery Agent to register with it, and applications and desktops being unavailable to users."

 

I have run the Citrix Health Assistant which, surprisngly, has passed all "VDA registration checks"!

 

I can't see any errors on my controllers.

Does anyone have any idea what might be causing this?

I managed to resolve this by:

 

1. Uninstall Citrix Virtual Delivery Agent

2. Download and run VDA Cleanup Utility

3. Re-install Citrix Virtual Delivery Agent

 

I think my problem stemed from the versions of VDA I was running. I had previously had 7.9 installed and pointing to a PoC DDC. I needed to upgrade to 7.13 and point to a production DDC.

christianmdu Members

Christian Summerfield
  • 33 posts

Posted 17 March 2017 - 04:00 PM

I have just installed VDA 7.13 Desktop OS on to a VM in VMware but am having trouble with it registering with either of our two Delivery Controllers.

 

On the 'Delivery Controller' screen, I have added my two DCs and they have passed the 'Test connection' check but on the 'Summary' screen it says:

 

"Failed to connect to one or more Delivery Controllers. An incorrectly configured Controller can result in failure of the Virtual Delivery Agent to register with it, and applications and desktops being unavailable to users."

 

I have run the Citrix Health Assistant which, surprisngly, has passed all "VDA registration checks"!

 

I can't see any errors on my controllers.

Does anyone have any idea what might be causing this?

 

Attached Thumbnails

  • vda_registration_pass.png
  • dc_failedtoconnect.png
  • dc_test.png


christianmdu Members

Christian Summerfield
  • 33 posts

Posted 17 March 2017 - 04:04 PM

I have just come across the log file that is generated from the Health Assistant but everything looks OK?

 

2017-03-16 13:13:45,907: 1 INFO  –
2017-03-16 13:13:45,935: 1 INFO  – ***************
2017-03-16 13:13:45,935: 1 INFO  –
2017-03-16 13:13:45,936: 1 INFO  – Citrix Health Assistant v1.1.0.10
2017-03-16 13:13:45,936: 1 INFO  –
2017-03-16 13:13:45,937: 1 INFO  – ***************
2017-03-16 13:13:45,937: 1 INFO  –
2017-03-16 13:13:51,367: 5 INFO  –
2017-03-16 13:13:51,368: 5 INFO  – Start VDA Registration Check...
2017-03-16 13:13:51,370: 5 INFO  – >>>>Step 1: (VDA software installation)  Begin. <<<<
2017-03-16 13:13:51,529: 5 INFO  – VDA software installation verified.
2017-03-16 13:13:51,530: 5 INFO  – <<<< Step 1: VDA software installation End. Test Success. >>>>
2017-03-16 13:13:51,531: 5 INFO  – >>>>Step 2: (VDA machine domain membership)  Begin. <<<<
2017-03-16 13:13:51,641: 5 INFO  – Machine domain membership and DNS resolution verified. Retrieved machine SID succesfully.
2017-03-16 13:13:51,641: 5 INFO  – <<<< Step 2: VDA machine domain membership End. Test Success. >>>>
2017-03-16 13:13:51,642: 5 INFO  – >>>>Step 3: (VDA communication port availability)  Begin. <<<<
2017-03-16 13:13:52,083: 5 INFO  – Required port access verified.
2017-03-16 13:13:52,084: 5 INFO  – <<<< Step 3: VDA communication port availability End. Test Success. >>>>
2017-03-16 13:13:52,085: 5 INFO  – >>>>Step 4: (VDA services status)  Begin. <<<<
2017-03-16 13:13:52,692: 5 INFO  – All VDA related services are running
No VDA service errors were found in the event log during the last five minutes.
2017-03-16 13:13:52,692: 5 INFO  – <<<< Step 4: VDA services status End. Test Success. >>>>
2017-03-16 13:13:52,696: 5 INFO  – >>>>Step 5: (Windows firewall configuration)  Begin. <<<<
2017-03-16 13:13:52,952: 5 INFO  – The Windows Firewall Service allows communication between the VDA and the Controller.
2017-03-16 13:13:52,953: 5 INFO  – <<<< Step 5: Windows firewall configuration End. Test Success. >>>>
2017-03-16 13:13:52,954: 5 INFO  – >>>>Step 6: (Communication with DDC)  Begin. <<<<
2017-03-16 13:13:53,000: 5 INFO  – VDA and Controller communication verified.
2017-03-16 13:13:53,000: 5 INFO  – <<<< Step 6: Communication with DDC End. Test Success. >>>>
2017-03-16 13:13:53,001: 5 INFO  – >>>>Step 7: (Time sync with DDC)  Begin. <<<<
2017-03-16 13:13:53,448: 5 INFO  – The time difference between the Controller and VDA is less than five minutes.
2017-03-16 13:13:53,448: 5 INFO  – <<<< Step 7: Time sync with DDC End. Test Success. >>>>
2017-03-16 13:13:53,448: 5 INFO  – All tests passed. The VDA can communicate and register with the Controller.
2017-03-16 13:14:04,534: 7 INFO  –
2017-03-16 13:14:04,535: 7 INFO  – Start VDA Registration Check...
2017-03-16 13:14:04,535: 7 INFO  – >>>>Step 1: (VDA software installation)  Begin. <<<<
2017-03-16 13:14:04,536: 7 INFO  – VDA software installation verified.
2017-03-16 13:14:04,536: 7 INFO  – <<<< Step 1: VDA software installation End. Test Success. >>>>
2017-03-16 13:14:04,537: 7 INFO  – >>>>Step 2: (VDA machine domain membership)  Begin. <<<<
2017-03-16 13:14:04,574: 7 INFO  – Machine domain membership and DNS resolution verified. Retrieved machine SID succesfully.
2017-03-16 13:14:04,574: 7 INFO  – <<<< Step 2: VDA machine domain membership End. Test Success. >>>>
2017-03-16 13:14:04,575: 7 INFO  – >>>>Step 3: (VDA communication port availability)  Begin. <<<<
2017-03-16 13:14:04,712: 7 INFO  – Required port access verified.
2017-03-16 13:14:04,712: 7 INFO  – <<<< Step 3: VDA communication port availability End. Test Success. >>>>
2017-03-16 13:14:04,712: 7 INFO  – >>>>Step 4: (VDA services status)  Begin. <<<<
2017-03-16 13:14:04,861: 7 INFO  – All VDA related services are running
No VDA service errors were found in the event log during the last five minutes.
2017-03-16 13:14:04,861: 7 INFO  – <<<< Step 4: VDA services status End. Test Success. >>>>
2017-03-16 13:14:04,862: 7 INFO  – >>>>Step 5: (Windows firewall configuration)  Begin. <<<<
2017-03-16 13:14:04,898: 7 INFO  – The Windows Firewall Service allows communication between the VDA and the Controller.
2017-03-16 13:14:04,899: 7 INFO  – <<<< Step 5: Windows firewall configuration End. Test Success. >>>>
2017-03-16 13:14:04,899: 7 INFO  – >>>>Step 6: (Communication with DDC)  Begin. <<<<
2017-03-16 13:14:04,904: 7 INFO  – VDA and Controller communication verified.
2017-03-16 13:14:04,904: 7 INFO  – <<<< Step 6: Communication with DDC End. Test Success. >>>>
2017-03-16 13:14:04,904: 7 INFO  – >>>>Step 7: (Time sync with DDC)  Begin. <<<<
2017-03-16 13:14:04,915: 7 INFO  – The time difference between the Controller and VDA is less than five minutes.
2017-03-16 13:14:04,916: 7 INFO  – <<<< Step 7: Time sync with DDC End. Test Success. >>>>
2017-03-16 13:14:04,916: 7 INFO  – All tests passed. The VDA can communicate and register with the Controller.
2017-03-17 15:54:42,019: 1 INFO  –
2017-03-17 15:54:42,046: 1 INFO  – ***************
2017-03-17 15:54:42,046: 1 INFO  –
2017-03-17 15:54:42,047: 1 INFO  – Citrix Health Assistant v1.1.0.10
2017-03-17 15:54:42,048: 1 INFO  –
2017-03-17 15:54:42,048: 1 INFO  – ***************
2017-03-17 15:54:42,048: 1 INFO  –
2017-03-17 15:54:43,671: 5 INFO  –
2017-03-17 15:54:43,672: 5 INFO  – Start VDA Registration Check...
2017-03-17 15:54:43,674: 5 INFO  – >>>>Step 1: (VDA software installation)  Begin. <<<<
2017-03-17 15:54:43,862: 5 INFO  – VDA software installation verified.
2017-03-17 15:54:43,862: 5 INFO  – <<<< Step 1: VDA software installation End. Test Success. >>>>
2017-03-17 15:54:43,864: 5 INFO  – >>>>Step 2: (VDA machine domain membership)  Begin. <<<<
2017-03-17 15:54:43,935: 5 INFO  – Machine domain membership and DNS resolution verified. Retrieved machine SID succesfully.
2017-03-17 15:54:43,936: 5 INFO  – <<<< Step 2: VDA machine domain membership End. Test Success. >>>>
2017-03-17 15:54:43,937: 5 INFO  – >>>>Step 3: (VDA communication port availability)  Begin. <<<<
2017-03-17 15:54:44,079: 5 INFO  – Required port access verified.
2017-03-17 15:54:44,079: 5 INFO  – <<<< Step 3: VDA communication port availability End. Test Success. >>>>
2017-03-17 15:54:44,081: 5 INFO  – >>>>Step 4: (VDA services status)  Begin. <<<<
2017-03-17 15:54:44,407: 5 INFO  – All VDA related services are running
No VDA service errors were found in the event log during the last five minutes.
2017-03-17 15:54:44,407: 5 INFO  – <<<< Step 4: VDA services status End. Test Success. >>>>
2017-03-17 15:54:44,416: 5 INFO  – >>>>Step 5: (Windows firewall configuration)  Begin. <<<<
2017-03-17 15:54:44,506: 5 INFO  – The Windows Firewall Service allows communication between the VDA and the Controller.
2017-03-17 15:54:44,507: 5 INFO  – <<<< Step 5: Windows firewall configuration End. Test Success. >>>>
2017-03-17 15:54:44,509: 5 INFO  – >>>>Step 6: (Communication with DDC)  Begin. <<<<
2017-03-17 15:54:44,550: 5 INFO  – VDA and Controller communication verified.
2017-03-17 15:54:44,550: 5 INFO  – <<<< Step 6: Communication with DDC End. Test Success. >>>>
2017-03-17 15:54:44,551: 5 INFO  – >>>>Step 7: (Time sync with DDC)  Begin. <<<<
2017-03-17 15:54:44,595: 5 INFO  – The time difference between the Controller and VDA is less than five minutes.
2017-03-17 15:54:44,595: 5 INFO  – <<<< Step 7: Time sync with DDC End. Test Success. >>>>
2017-03-17 15:54:44,596: 5 INFO  – All tests passed. The VDA can communicate and register with the Controller.
 



Joe Deller Citrix Employees

Joe Deller
  • 129 posts

Posted 17 March 2017 - 04:40 PM

I think there might be a bug in studio that is producing a misleading error message, I've recently see this myself but the VDA registered, I only had 1 DDC, but the test connection was ok, but then got the warning message in the UI

 

If you check the controllers node in studio, does it actually show the correct number of VDAs?  On the VDA in the application eventlog do you see the 1012 information message showing the VDA registered with the correct broker ?



George Spiers Members

George Spiers
  • 204 posts

Posted 18 March 2017 - 12:01 PM

It's a known issue

 

http://docs.citrix.com/en-us/xenapp-and-xendesktop/7-13/whats-new/known-issues.html

 

#HDX-5012

When installing a VDA, the Summary page might contain a message indicating failure to connect to a Controller, even if the connection test was successful. The connection test result on the Delivery Controller page is correct.



christianmdu Members

Christian Summerfield
  • 33 posts

Posted 22 March 2017 - 10:41 AM

I have just installed VDA 7.13 Desktop OS on to a VM in VMware but am having trouble with it registering with either of our two Delivery Controllers.

 

On the 'Delivery Controller' screen, I have added my two DCs and they have passed the 'Test connection' check but on the 'Summary' screen it says:

 

"Failed to connect to one or more Delivery Controllers. An incorrectly configured Controller can result in failure of the Virtual Delivery Agent to register with it, and applications and desktops being unavailable to users."

 

I have run the Citrix Health Assistant which, surprisngly, has passed all "VDA registration checks"!

 

I can't see any errors on my controllers.

Does anyone have any idea what might be causing this?

I managed to resolve this by:

 

1. Uninstall Citrix Virtual Delivery Agent

2. Download and run VDA Cleanup Utility

3. Re-install Citrix Virtual Delivery Agent

 

I think my problem stemed from the versions of VDA I was running. I had previously had 7.9 installed and pointing to a PoC DDC. I needed to upgrade to 7.13 and point to a production DDC.


Best Answer