I sequenced 1 application "Personal travel" and I launched the shortcuts both in the sequencer as well as in desktop and were launched successfully.
When I published in Appv management console and when I launched the shortcut in appv client, I am getting the below error.

"The Application virtualization client could not launch Personal Travel 3.0.2.1300
The application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.
Error code 45242F4-1F702639-000036B1"

How can we troubleshoot the issue??
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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
Answered 01/05/2011 by: ksaunam
Orange Senior Belt

Please log in to comment

Please log in to comment
0
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
Answered 01/05/2011 by: rvrajendra
Orange Belt

Please log in to comment
0
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.
Answered 01/06/2011 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity