I have several HP server utilities that need to be deployed. The process for deploying them is to run an exe that kicks off several msi files one at a time. This deployment is failing, however if I deploy the msi individually it works. It also works if I run the *.exe /s at command line.
I read online where someone ran into this issue and it was because a process was already running that it wouldn't kick off the next process for deployment. There was no solution around this issue for this person.
Below is what I receive from the AppEnforce.log
+++ Application not discovered. [AppDT Id: ScopeId_22479951-7C39-4ED5-B2B3-4C135CC23671/DeploymentType_3126f87e-e6f7-463c-bfb2-6929a723069f, Revision: 3] AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
App enforcement environment:
Context: Machine
Command line: "cpqsetup.exe" /s
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 2
Content path: C:\Windows\ccmcache\7s
Working directory: AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
Prepared working directory: C:\Windows\ccmcache\7s AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
Prepared command line: "C:\Windows\ccmcache\7s\cpqsetup.exe" /s AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
Executing Command line: "C:\Windows\ccmcache\7s\cpqsetup.exe" /s with user context AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
Working directory C:\Windows\ccmcache\7s AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
Post install behavior is BasedOnExitCode AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
Waiting for process 5372 to finish. Timeout = 120 minutes. AppEnforce 10/1/2015 8:46:20 AM 10836 (0x2A54)
Process 5372 terminated with exitcode: 3 AppEnforce 10/1/2015 8:46:21 AM 10836 (0x2A54)
Looking for exit code 3 in exit codes table... AppEnforce 10/1/2015 8:46:21 AM 10836 (0x2A54)
Unmatched exit code (3) is considered an execution failure. AppEnforce 10/1/2015 8:46:21 AM 10836 (0x2A54)
++++++ App enforcement completed (0 seconds) for App DT "HP iLO interface drivers 3.10 x64 APPLICATION" [ScopeId_22479951-7C39-4ED5-B2B3-4C135CC23671/DeploymentType_3126f87e-e6f7-463c-bfb2-6929a723069f], Revision: 3, User SID:
] ++++++ AppEnforce 10/1/2015 8:46:21 AM 10836 (0x2A54)
Has anyone run into this issue and does anyone have a suggestion to fix the problem?