Application install fails in software center, appenforce.log shows exit code 0 ?


  • Hi

    Trying to install HP Quick Launch Buttons through the application catalog.

    The installation starts and it seems to get installed but Software center says it failed.

    Appenforce.log shows exit code 0, so why is it showing as failed in Software Center?:

    • App enforcement environment: 
      Context: Machine
      Command line: setup.exe /clone_wait -s /f2%temp%\hpqlb.log
      Allow user interaction: No
      UI mode: 1
      User token: not null
      Session Id: 1
      Content path: C:\Windows\ccmcache\3u
      Working directory: 
    • Prepared working directory: C:\Windows\ccmcache\3u
    • Prepared command line: "C:\Windows\ccmcache\3u\setup.exe" /clone_wait -s /f2C:\Windows\TEMP\hpqlb.log
    • Executing Command line: "C:\Windows\ccmcache\3u\setup.exe" /clone_wait -s /f2C:\Windows\TEMP\hpqlb.log with user context
    • Working directory C:\Windows\ccmcache\3u

    • Post install behavior is BasedOnExitCode
    • Waiting for process 832 to finish.  Timeout = 120 minutes.
    • Process 832 terminated with exitcode: 0
    • Looking for exit code 0 in exit codes table...
    • Matched exit code 0 to a Success entry in exit codes table.

    • Edited by Baatch Tuesday, July 31, 2012 10:17 AM
    Tuesday, July 31, 2012 10:10 AM


All replies

  • My guess: AppEnforce.log tells you "Application not discovered". The application was installed successfully, but the detection method did not detect it as being installed. I've posted a similar log snippet here:

    Torsten Meringer |

    Tuesday, July 31, 2012 10:44 AM
  • OMG, thank you TORSTEN, you saved me lots of time. I already spent like a couple days troubleshooting this application !


    Alexander Phu

    Tuesday, July 31, 2012 11:44 AM
  • FWIW, I found a scenario with which this can happen, and I can't find it documented anywhere so I thought I'd add something that may prove helpful to somebody randomly googling for solutions.  If you specify a file system detection method, and choose a file with an apostrophe in the file name, the file detection can fail in my experience.  And yes, I know, it's bad form to place any importance on a file with a special character in the name anyway.  You'll know if this is happening to you because the dcmwmiprovider.log file will show, for example:

    Query for lantern's provider is: Select * from FileSystem_FileMetadata where BasePath = "C:\\blah\\" and Name = "file"s_name.txt"

    Notice the apostrophe was replaced with a quotation mark.  Take the apostrophe out of the file name, and change your detection method setting to a file name without an apostrophe as well.  Update policy, rereun application deployment evaluation cycle...and for me, it started working without changing anything else.  Kind of a no-brainer, but thought I'd share.  Not sure if other special characters, or just apostrophes, are effected.

    Wednesday, July 23, 2014 6:38 PM