Virtualization

Hi,

That error message most likely results from client not having all necessary [C++] runtimes in the local system. I would check first what version of C++ runtime this application install and then deploy it separately (i.e. natively) to the client.

You probably want to do the same in the Sequencer as well, which is to install the runtime before entering into monitoring as to not include it in App-V package.

/Kalle

Have you checked out http://www.shawnbass.com/Blogs/tabid/58/EntryId/170/App-V-4-5-File-System-race-condition-found-and-fixed.aspx

in the eventviewer it shown...
Generate Activation Context failed for T:\PerTra51.003\Personec\Bin\Wintime30.exe. Reference error message: A component version required by the application conflicts with another component version already active.

How can we find which particular component

So the eventlog error is not specifying the component such as this example.

Activation context generation failed for "C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6 595b64144ccf1df_6.0.6001.18000_none_152e7382f3bd50c6.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_659 5b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc.manifest.

I have seen other people say it might have something to do with the application mixing up 32-bit and 64-bit versions of the component but I would hope the eventlog would at least tell you which component it is beyond the exe involved.