We have a few packages that have active setup components that install whenever a new user logs into the PC.

We are sometimes getting errors whereby one package is trying to install while another one is still in progress, resutling in the error that "another installation is already in progress".

Is there any way to prevent this from happening and to control the packages to install only when the previous package is complete?

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


My guess would be that some of your packages are executables which return control too early. For example, quite a few set-up stubs which launch MSIExec against an MSI will exit once that process is started, thus returning control to the AS process. If MSIExec is still running when the next package comes along, you'll see this. Equally, if the stub calls some other EXE to actually do the work (again, not unusual), the same thing happens.

In the first scenario, you can simply change the call so that you run MSIExec against the extracted MSI and in the second you need to find out which process actually does the work, what parameters you need to pass it and so on.
Answered 04/28/2010 by: VBScab
Red Belt

Please log in to comment