Quantcast
Channel: VMware Communities : Discussion List - VMware View
Viewing all articles
Browse latest Browse all 10683

"Another task is already in progress" on Refresh (VM Not Stuck) - View 5.3.1

$
0
0

I know there have been a couple semi-recent topics like this but their issues did not sound the same as mine so I'm starting a new topic.

 

ESXi 5.5.0-1623387

Horizon View 5.3.1

OS: Windows 7 Pro 64 and 32 bit

 

Each evening via PowerCLI I set some of our pools to refresh.  Almost every night at least one pool has a VM that gets the error "Another task is already in progress" which halts the entire task.  I have the pools set to not auto recover of failure because for our own reasons the MAC addresses cannot change so I can't have it auto deleting desktops to recover.

 

Upon resuming the task generally all VMs complete successfully.  Even the one that had the error.

 

When I look at what was going on during that time, I don't see any other tasks showing up that should have preventing the VM from refreshing.  See screenshots from one such VM...

 

VMtasks.png

 

As you can see it failed at 7:40 and then at 10:22 after I resumed the task it went through fine.  This took not intervention on my part other than resuming the task.  The VM was not stuck in some way.

 

VMevents.png

 

Events for the VM around the time of both the failed and working refresh are seen above.  I include the last days date so you know I wasn't leaving something out.

 

I haven't done a lot of research on this yet, but I did try updating the APEX cards to 2.4.0 since it was most often occurring on a pool that runs on hosts with the APEX cards and because I saw another thread where people were discussing it as a possible culprit.  But it is still occurring and it may only be occurring on the pool mentioned because it is our largest pool of desktops.  Last night it happened on 3 different pools and 2 of those did not have APEX cards.

 

I also changed the Blackout Times for Storage Accelerator regeneration on the pools with the issue so that it would not be occurring at the same time the refreshes were running.  Didn't make a difference.  We are not doing Space Reclamation at this time.

 

Anybody have any ideas?  A path to investigate?

 

Thanks!



Viewing all articles
Browse latest Browse all 10683

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>