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

The published resource is not available currently. Contact your system administrator for further assistance


Mcddony Ventura

Question

Hello,

 

I have a few VDAs on a child domain.  2 DDCs on the root domain hosting StoreFront.  Recently, users trying to launch apps from the child domain VDAs are getting the below msg.  Sometimes it looks like the app is about to load but gets stock on "Please wait for Local Session Manager"  and then disappears.

 

'The published resource is not available currently.  Contact your system administrator for further assistance'

 

Any tips on solving this issue would be greatly appreciated.  

Link to comment

3 answers to this question

Recommended Posts

Hi Diego,  Here are a few:

 

From VDA

 

image.thumb.png.73121b7daaac3df145865b40f2a65ec5.pngEvent ID:      1018

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      vda.dev.domain.com

Description:

The Citrix Desktop Service has detected that the delivery controller ddc2.domain.com

(IP Address x.x.x.x) cannot connect to the Service. One possible reason for this is that the 'Access this computer from the network' security policy does not allow the delivery controller server identity to access this machine.

 

Please check that a local or group policy is not set incorrectly to disallow access from the delivery controller servers.

 

***********************************************************************************************************************

image.thumb.png.4efea1689a79a5af121b3b0177bd1664.pngTask Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      vda.dev.domain.com

Description:

The Citrix Desktop Service cannot connect to the delivery controller 'http:// ddc2.domain.com:80/Citrix/CdsController/IRegistrar' ( IP Address x.x.x.x)

 

Check that the system clock is in sync between this machine and the delivery controller. If this does not resolve the problem, please refer to Citrix Knowledge Base article CTX117248 for further information.

 

Error Details:

Exception 'Fail worker callback using SPN HOST/vda.dev.domain.com and IP address 10.30.30.2' of type 'System.ServiceModel.FaultException`1[Citrix.Cds.Protocol.Controller.Fault]'..

 

Link to comment

2019-03-24 19:51:17,087: 12 INFO  – 
2019-03-24 19:51:17,087: 12 INFO  – Start VDA health check...
2019-03-24 19:51:17,087: 12 INFO  – >>>>Step 1: (VDA software installation)  Begin. <<<<
2019-03-24 19:51:17,087: 12 INFO  – VDA image path is C:\Program Files\Citrix\Virtual Desktop Agent\BrokerAgent.exe.
2019-03-24 19:51:17,087: 12 INFO  – VDA version number is 7.9.0.5.
2019-03-24 19:51:17,087: 12 INFO  – Registry path at HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\VirtualDesktopAgent is fine.
2019-03-24 19:51:17,087: 12 INFO  – Registry path at HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\VirtualDesktopAgent\InstallData\Location is fine.
2019-03-24 19:51:17,087: 12 INFO  – [UI Message] VDA software installation verified.
2019-03-24 19:51:17,087: 12 INFO  – <<<< Step 1: VDA software installation End. Test Success. >>>>
2019-03-24 19:51:17,087: 12 INFO  – >>>>Step 2: (VDA machine domain membership)  Begin. <<<<
2019-03-24 19:51:17,087: 12 DEBUG – DNS Lookup():
2019-03-24 19:51:17,087: 12 DEBUG – Host Name  = vda.DEV.domain.com
2019-03-24 19:51:17,087: 12 INFO  – VDA Machine:
2019-03-24 19:51:17,087: 12 DEBUG – NetBIOS Name = vda
2019-03-24 19:51:17,087: 12 INFO  – OS Version = Microsoft Windows NT 6.3.9600.0
2019-03-24 19:51:17,087: 12 INFO  – Platform = X64 Platform
2019-03-24 19:51:17,087: 12 DEBUG – Computer Domain: DEV.domain.com
2019-03-24 19:51:17,087: 12 DEBUG – Role = Member Server
2019-03-24 19:51:17,103: 12 DEBUG – Membership is Verified, SID:S-1-5-21-2114113158-23433308-4125902142-xxxx
2019-03-24 19:51:17,103: 12 DEBUG – Machine domain DEV.domain.com membership and DNS resolution verified.Machine SID retrieved successfully.
2019-03-24 19:51:17,103: 12 INFO  – [UI Message] Machine domain DEV.domain.com membership and DNS resolution verified.Machine SID retrieved successfully.
2019-03-24 19:51:17,103: 12 INFO  – <<<< Step 2: VDA machine domain membership End. Test Success. >>>>
2019-03-24 19:51:17,103: 12 INFO  – >>>>Step 3: (VDA communication port availability)  Begin. <<<<
2019-03-24 19:51:17,134: 12 INFO  – [UI Message] Required port access verified.
2019-03-24 19:51:17,134: 12 INFO  – <<<< Step 3: VDA communication port availability End. Test Success. >>>>
2019-03-24 19:51:17,134: 12 INFO  – >>>>Step 4: (VDA services status)  Begin. <<<<
2019-03-24 19:51:17,134: 12 INFO  – OS VDA related services check.
2019-03-24 19:51:17,134: 12 DEBUG – Service : BrokerAgent ("Citrix Desktop Service")
2019-03-24 19:51:17,134: 12 DEBUG – Status = Win32OwnProcess, Running
2019-03-24 19:51:17,134: 12 INFO  – Prereq =
2019-03-24 19:51:17,134: 12 DEBUG – LanmanWorkstation (Win32ShareProcess), Running
2019-03-24 19:51:17,134: 12 INFO  – Service : BrokerAgent is running
2019-03-24 19:51:17,134: 12 INFO  – VDA machine region time is 3/24/2019 7:51:17 PM
2019-03-24 19:51:17,150: 12 INFO  – [UI Message] All VDA services are running No VDA service errors were found in the event log for the past five minutes.
2019-03-24 19:51:17,150: 12 INFO  – <<<< Step 4: VDA services status End. Test Success. >>>>
2019-03-24 19:51:17,150: 12 INFO  – >>>>Step 5: (Windows firewall configuration)  Begin. <<<<
2019-03-24 19:51:17,165: 12 INFO  – Status : Enabled
2019-03-24 19:51:17,165: 12 INFO  – Check Firewall Rules
2019-03-24 19:51:17,165: 12 DEBUG – Firewall TCP rules check ...
2019-03-24 19:51:17,165: 12 DEBUG – Inbound:80
2019-03-24 19:51:17,165: 12 DEBUG – Outbound:80
2019-03-24 19:51:17,165: 12 DEBUG – Inbound:*
2019-03-24 19:51:17,165: 12 DEBUG – Outbound:*
2019-03-24 19:51:17,165: 12 DEBUG – Firewall inbound block rule check...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall inbound allow rule check...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall outbound block rule check...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall outbound allow rule check...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall UDP rules check ...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall inbound block rule check...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall inbound allow rule check...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall outbound block rule check...
2019-03-24 19:51:17,165: 12 DEBUG – Firewall outbound allow rule check...
2019-03-24 19:51:17,165: 12 INFO  – Service port enabled for Firewall
2019-03-24 19:51:17,165: 12 INFO  – [UI Message] The Windows Firewall Service allows communication between the VDA and the Controller.
2019-03-24 19:51:17,165: 12 INFO  – <<<< Step 5: Windows firewall configuration End. Test Success. >>>>
2019-03-24 19:51:17,165: 12 INFO  – >>>>Step 6: (Communication with Controller)  Begin. <<<<
2019-03-24 19:51:17,165: 12 INFO  – Found 0 hosts in hosts file.
2019-03-24 19:51:17,165: 12 DEBUG – Farm GUID (local) : NOT SET
2019-03-24 19:51:17,165: 12 DEBUG – Farm GUID In Use : NOT SET
2019-03-24 19:51:17,165: 12 INFO  – Find farm Guid doesn't Exist.
2019-03-24 19:51:17,165: 12 INFO  – not find any Controller in [VdaData].
2019-03-24 19:51:17,165: 12 INFO  – Registry based Controller list (ListOfDDCs) :
2019-03-24 19:51:17,165: 12 DEBUG – Controller :ddc.DEV.domain.comm:80
2019-03-24 19:51:17,165: 12 DEBUG – DNS Lookup(Local Machine):
2019-03-24 19:51:17,165: 12 DEBUG – Host Name  = ddc.domain.com
2019-03-24 19:51:17,165: 12 INFO  – Ping Service: /Citrix/CdsController/IRegistrar
2019-03-24 19:51:17,212: 12 DEBUG – Connect = Tcp to x.x.x.x:80
2019-03-24 19:51:17,259: 12 INFO  – Service = Listening
2019-03-24 19:51:17,259: 12 DEBUG – Controller : ddc1.domain.com:80
2019-03-24 19:51:17,259: 12 DEBUG – DNS Lookup(Local Machine):
2019-03-24 19:51:17,259: 12 DEBUG – Host Name  = ddc1.domain.com
2019-03-24 19:51:17,259: 12 INFO  – Ping Service: /Citrix/CdsController/IRegistrar
2019-03-24 19:51:17,290: 12 DEBUG – Connect = Tcp to x.x.x.x:80
2019-03-24 19:51:17,337: 12 INFO  – Service = Listening
2019-03-24 19:51:17,337: 12 DEBUG – Controller : ddc.dev.domain.com:80
2019-03-24 19:51:17,337: 12 DEBUG – DNS Lookup(Local Machine):
2019-03-24 19:51:17,337: 12 DEBUG – Host Name  = ddc.dev.domain.com:80
2019-03-24 19:51:17,337: 12 INFO  – Ping Service: /Citrix/CdsController/IRegistrar
2019-03-24 19:51:17,337: 12 DEBUG – Connect = Tcp to x.x.x.x:80
2019-03-24 19:51:17,337: 12 INFO  – Service = Listening
2019-03-24 19:51:17,337: 12 INFO  – [UI Message] VDA and Controller communication verified.
2019-03-24 19:51:17,337: 12 INFO  – <<<< Step 6: Communication with Controller End. Test Success. >>>>
2019-03-24 19:51:17,337: 12 INFO  – >>>>Step 7: (Time sync with Controller)  Begin. <<<<
2019-03-24 19:51:17,337: 12 DEBUG – Controller:ddc.domain.com
2019-03-24 19:51:17,533: 12 DEBUG – NetRemoteTOD query time failure reason: Access is denied
2019-03-24 19:51:17,783: 12 DEBUG – WMI time query with no credential failure reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
2019-03-24 19:51:17,783: 12 DEBUG – WMI time query with credential failure reason: Value does not fall within the expected range.
2019-03-24 19:51:17,783: 12 DEBUG – Controller:ddc.domain.com
2019-03-24 19:51:17,989: 12 DEBUG – NetRemoteTOD query time failure reason: Access is denied
2019-03-24 19:51:18,224: 12 DEBUG – WMI time query with no credential failure reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
2019-03-24 19:51:18,224: 12 DEBUG – WMI time query with credential failure reason: Value does not fall within the expected range.
2019-03-24 19:51:18,224: 12 DEBUG – Controller:ddc.dev.domain.com
2019-03-24 19:51:18,239: 12 DEBUG – Current VDA time is 03/24/2019 23:51:18
2019-03-24 19:51:18,239: 12 DEBUG – Controller ddc.domain.com time is 03/24/2019 23:51:18
2019-03-24 19:51:18,239: 12 INFO  – [UI Message] Warning:Not all Controllers are reachable to retrieve the time. Check log for details.
2019-03-24 19:51:18,239: 12 INFO  – <<<< Step 7: Time sync with Controller End. Test Warning. >>>>
2019-03-24 19:51:18,239: 12 INFO  – >>>>Step 8: (VDA registration status)  Begin. <<<<
2019-03-24 19:51:18,239: 12 INFO  – VDA Registered status is 2
2019-03-24 19:51:18,239: 12 DEBUG – Registered Controller FQDN is ddc.dev.domain.com
2019-03-24 19:51:18,239: 12 INFO  – Registered time is 03/23/2019 00:52:50
2019-03-24 19:51:18,239: 12 INFO  – [UI Message] VDA is registered.
2019-03-24 19:51:18,239: 12 INFO  – <<<< Step 8: VDA registration status End. Test Success. >>>>
2019-03-24 19:51:18,239: 12 INFO  – >>>>Step 9: (Session launch communication port availability)  Begin. <<<<
2019-03-24 19:51:18,362: 12 INFO  – [UI Message] Required port access verified.
2019-03-24 19:51:18,362: 12 INFO  – <<<< Step 9: Session launch communication port availability End. Test Success. >>>>
2019-03-24 19:51:18,362: 12 INFO  – >>>>Step 10: (Session launch services status)  Begin. <<<<
2019-03-24 19:51:18,362: 12 INFO  – OS VDA session launch related services check.
2019-03-24 19:51:18,362: 12 DEBUG – Service : Citrix Encryption Service ("Citrix Encryption Service")
2019-03-24 19:51:18,362: 12 DEBUG – Status = Win32OwnProcess, Running
2019-03-24 19:51:18,362: 12 INFO  – Service : Citrix Encryption Service is running
2019-03-24 19:51:18,362: 12 DEBUG – Service : cpsvc ("Citrix Print Manager Service")
2019-03-24 19:51:18,362: 12 DEBUG – Status = Win32OwnProcess, Running
2019-03-24 19:51:18,362: 12 INFO  – Prereq =
2019-03-24 19:51:18,362: 12 DEBUG – RpcSs (Win32ShareProcess), Running
2019-03-24 19:51:18,362: 12 DEBUG – Spooler (Win32OwnProcess, InteractiveProcess), Running
2019-03-24 19:51:18,362: 12 INFO  – Service : cpsvc is running
2019-03-24 19:51:18,362: 12 INFO  – VDA ProvisioningType is not MCS.
2019-03-24 19:51:18,362: 12 INFO  – OS VDA session launch related services check.
2019-03-24 19:51:18,362: 12 DEBUG – Service : CtxFlashSvc ("Citrix HDX MediaStream for Flash Service")
2019-03-24 19:51:18,362: 12 DEBUG – Status = Win32OwnProcess, Running
2019-03-24 19:51:18,362: 12 INFO  – Service : CtxFlashSvc is running
2019-03-24 19:51:18,362: 12 DEBUG – Service : CitrixCseEngine ("Citrix Group Policy Engine")
2019-03-24 19:51:18,362: 12 DEBUG – Status = Win32OwnProcess, Running
2019-03-24 19:51:18,362: 12 INFO  – Prereq =
2019-03-24 19:51:18,362: 12 DEBUG – RpcSs (Win32ShareProcess), Running
2019-03-24 19:51:18,362: 12 INFO  – Service : CitrixCseEngine is running
2019-03-24 19:51:18,362: 12 INFO  – VDA machine region time is 3/24/2019 7:51:18 PM
2019-03-24 19:51:18,378: 12 INFO  – [UI Message] All session launch related services are verified on VDA. No service errors were found in the event log for the past five minutes.
2019-03-24 19:51:18,378: 12 INFO  – <<<< Step 10: Session launch services status End. Test Success. >>>>
2019-03-24 19:51:18,378: 12 INFO  – >>>>Step 11: (Session launch windows firewall configuration)  Begin. <<<<
2019-03-24 19:51:18,393: 12 INFO  – Status : Enabled
2019-03-24 19:51:18,393: 12 INFO  – Check Firewall Rules
2019-03-24 19:51:18,393: 12 DEBUG – Firewall TCP rules check ...
2019-03-24 19:51:18,393: 12 DEBUG – Inbound:1494
2019-03-24 19:51:18,393: 12 DEBUG – Inbound:2598
2019-03-24 19:51:18,393: 12 DEBUG – Inbound:*
2019-03-24 19:51:18,393: 12 DEBUG – Outbound:*
2019-03-24 19:51:18,393: 12 DEBUG – Firewall inbound block rule check...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall inbound allow rule check...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall outbound block rule check...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall outbound allow rule check...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall UDP rules check ...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall inbound block rule check...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall inbound allow rule check...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall outbound block rule check...
2019-03-24 19:51:18,393: 12 DEBUG – Firewall outbound allow rule check...
2019-03-24 19:51:18,393: 12 INFO  – Service port enabled for Firewall
2019-03-24 19:51:18,409: 12 INFO  – Status : Enabled
2019-03-24 19:51:18,409: 12 INFO  – Check Firewall Rules
2019-03-24 19:51:18,409: 12 DEBUG – Firewall TCP rules check ...
2019-03-24 19:51:18,409: 12 DEBUG – Inbound:8008
2019-03-24 19:51:18,409: 12 DEBUG – Inbound:*
2019-03-24 19:51:18,409: 12 DEBUG – Outbound:*
2019-03-24 19:51:18,409: 12 DEBUG – Firewall inbound block rule check...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall inbound allow rule check...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall outbound block rule check...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall outbound allow rule check...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall UDP rules check ...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall inbound block rule check...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall inbound allow rule check...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall outbound block rule check...
2019-03-24 19:51:18,424: 12 DEBUG – Firewall outbound allow rule check...
2019-03-24 19:51:18,424: 12 INFO  – Service port enabled for Firewall
2019-03-24 19:51:18,424: 12 INFO  – [UI Message] The Windows Firewall Service allows communication between the VDA and the Controller.
2019-03-24 19:51:18,424: 12 INFO  – <<<< Step 11: Session launch windows firewall configuration End. Test Success. >>>>
2019-03-24 19:51:18,424: 12 INFO  – >>>>Step 12: (Windows Hotfix Installation)  Begin. <<<<
2019-03-24 19:51:18,924: 12 INFO  – [UI Message] Windows KB2998527 is not installed. This can cause Russian time zone information to display incorrectly. To avoid such impact, download and install this hotfix from Microsoft supports.
2019-03-24 19:51:18,924: 12 INFO  – <<<< Step 12: Windows Hotfix Installation End. Test Warning. >>>>
2019-03-24 19:51:18,924: 12 INFO  – >>>>Step 13: (Citrix Hotfix Installation)  Begin. <<<<
2019-03-24 19:51:18,924: 12 INFO  – [UI Message] XenDesktop 7.6.300 or later VDA. There is no need to install a time zone redirection hotfix.
2019-03-24 19:51:18,924: 12 INFO  – <<<< Step 13: Citrix Hotfix Installation End. Test Success. >>>>
2019-03-24 19:51:18,924: 12 INFO  – >>>>Step 14: (Microsoft Group Policy Settings)  Begin. <<<<
2019-03-24 19:51:18,924: 12 INFO  – [UI Message] The "Allow time zone redirection" policy is not set. Go to the Domain Controller and set the policy. For more information, see CTX126099.
2019-03-24 19:51:18,924: 12 INFO  – <<<< Step 14: Microsoft Group Policy Settings End. Test Warning. >>>>
2019-03-24 19:51:18,924: 12 INFO  – >>>>Step 15: (Citrix Group Policy Settings)  Begin. <<<<
2019-03-24 19:51:18,924: 12 INFO  – [UI Message] There is no "Use local time of client" policy setting. Set the policy on the Controller, reconnect to the virtual desktop, and then run the tool again to check the time zone feature configuration. For more information, see CTX126099.
2019-03-24 19:51:18,924: 12 INFO  – <<<< Step 15: Citrix Group Policy Settings End. Test Warning. >>>>
2019-03-24 19:51:18,924: 12 INFO  – All tests passed. The VDA can communicate and register with the Controller.
2019-03-24 19:51:19,132: 1 INFO  – Start uploading log to Citrix Insight Service...
2019-03-24 19:51:19,468: 1 DEBUG – Log data (8663 of 8663 bytes) successfully uploaded.
2019-03-24 19:51:19,468: 1 INFO  – Successfully uploaded log to Citrix Insight Service.
2019-03-24 19:51:19,468: 1 DEBUG – Citrix Insight Service upload id is c1c6d993-daa0-41fd-a634-108af201f684.
 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...