We have an application (Accumap) that was recently updated. The original App-V package was sequenced on a Win7 32-bit sequencer. The application is configured as a network install with the client components being virtualized. This allows us to update the
app regularly (there are monthly updated from the vendor) without having to re-sequence.
After the latest update (which changed some of the licensing components), the app hangs at the Licensing window. The application still works locally. However, if it's resequenced with a 4.6 sequencer (not SP1) it works during sequencing. It still hangs if
the client is 4.6 SP1 (launching the newly sequenced 4.6 version). Everything works again if I revert the client back to 4.6.
So basically with 4.6 SP1 sequencer and client, app hangs at licensing. Procmon traces don't reveal much other than it getting stuck reading a dll. The process goes to 100% and sits there. With 4.6 sequencer and client it works fine.
I tried the latest hotfix for 4.6 SP1 with the 4.6-sequenced package but it still hung. Does anybody have any ideas why 4.6 SP1 would cause this app to hang in this way when 4.6 works perfectly?
Thanks,
Darren.
