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

PvD 7.8 targets randomly stuck at Preparing/Unregister state


Balaji Muthukrishnan

Question

To give a background about this issue PvD VMs will randomly (some times all VMs) goes in to preparing/unregister state in studio console.

 

we have upgraded VDA from 5.6.500.20 (PvD 7.6.1) to VDA 7.8 (PvD 7.8) and then issue started rite from

 

master target disk failing with update inventory error (Error code 0x2), it was an known issue and that got resolved by LC5051 private

 

When rolling out the updates to PvD targets is were we faced the issue.

Even a PvD reset sometimes failed to work.

 

The symptoms about the issue is explained in detail in this post. pl refer.

 

 https://discussions.citrix.com/topic/376224-pvd-inventory-fails-0x2-after-78-vda-upgrade/page-2

 

Posted 11 June 2016 & 12 June 2016

 

we have created a SR and worked with citrix

 

Link to comment

2 answers to this question

Recommended Posts

based on suggestion we took complete memory dump of the VM based on the symptoms mentioned in the above post (preventing graceful logoff/restart/shutdown)

 

based on the dump analysis from support, it was mentioned that BrokerAgent.exe process is waiting for some threads from ADVAPI32.DLL at c:\windows\system32 and its causing the deadlock.

 

Thus preventing the Citrix desktop service from registration inturn causing VM state as Preparing / unregister.

 

Thats why when we kill the brokeragent.exe process and perform a logoff/restart/shutdown, it does a graceful operation. If we Kill brokeragent.exe and start the Citrix desktop service then the registration state will reflect correctly in the studio console

 

Since the file being in question was a OS dependent we were asked to contact MS and they provided 2 KBs since this was a known issue...

 

the 2 KBs were MS KB3020369 & KB3125574

 

This is the order we did the patch update...

 

1. Create a new versioned disk

2. Install MS KB 3020369 (April 2015 servicing stack update for Windows 7 and Windows Server 2008 R2) if it asked for reboot acknowledge and do a reboot (https://support.microsoft.com/en-us/kb/3020369)
3. Backup the following registry key [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI]. Now run the script file in the MS KB article Known issue-1 (https://support.microsoft.com/en-us/kb/3125574)
4. Install MS KB 3125574 (Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1) and reboot the VM (At this point ADVAPI32.DLL file version is 6.1.7601.23403) (https://support.microsoft.com/en-us/kb/3125574)

 

 

Before updating the MS patches ADVAPI32.DLL file version and Date was 

 

ADVAPI32.DLL file version 6.1.7601.22137 (10/18/2012)

 

5. once the patches are updated, we did a inventory update and promoted the versioned vdisk

6. surprisingly issue got resolved, all the PVD targets which were having the issues were able to register successfully with delivery controller.

 

we did one more OS update and make sure all latest MS patches were installed and then did a update inventory process again to make sure the targets are coming back to registered state and it did.

 

Now if i check the ADVAPI32.DLL file version and date it was 6.1.7601.23418 (4/9/2016)

 

So with this it was concluded that ADVAPI32.DLL file version 6.1.7601.22137 (10/18/2012) is having issue and got that resolved by MS patch KB3020369 & KB3125574.

 

ADVAPI32.DLL file version 6.1.7601.23403 and above is fixing the Citrix Desktop service (BrokerAgent.exe) moving to hung or not responding state issue

 

 

 

If you came across similar issue please make a note of the symptoms mentioned n this post and apply the MS KB as suggested.

 

This is one of the unique issue

Link to comment

I had the same issue on Windows 7 SP1 x64 and Citrix VDA 7.15.3000. The solution was to install all Microsoft hotfixes using Windows-Update-Checker (KUC). Microsoft update won't suffice since it's not installing hotfixes or telling you the status of the patches so do yourself a favor and use KUC for Windows 7 and 2008 R2.

We also had to reinstall the VDA and we ran the cleanup utility.

The image is now much faster and the PvD drive mount just fine.

Link to comment

Archived

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

×
×
  • Create New...