Says 'Failed' But Was Infact Successful?

Comments

5 comments

  • TonsOFun

    Hi Andy, 

    Some programs will indeed show a failed if the program is already installed. 

    Much as if you already had the software installed on the target machine, and running the installation program will throw an error. 

    e.g. "This program is already installed, cannot continue installation". 

    Did you make sure that the target machine did not have it installed prior to deployment? 

    If so, then hmmmm. 

    0
    Comment actions Permalink
  • Andy Buckley

    I was installing it from fresh, so it was not already installed, no.

    0
    Comment actions Permalink
  • Adam Ruth

    Some installers will return various codes for successful conditions.  Sometimes these codes are just warnings, which can be ignored.  For example, 3010 typically means that the installer succeeded but the computer will need to be rebooted.  As TonsOfFun mentioned some codes mean that the program is already installed.

    You can edit the "Success Codes" in the package to have certain codes treated as success instead of fail. You can see the codes that were returned by looking at the individual computers in the deployment, you will see "Installer returned code: ####".  Just add it to the Success Codes once you're sure that you can safely treat it as a success.

    0
    Comment actions Permalink
  • Andy Buckley

    I'll run the installer myself later but i imagine it will be a code to say you need to reboot. Thanks a lot.

    0
    Comment actions Permalink
  • harrisandreson

    Failure is the best way to get success, you know that world leaders have a pretty common feature and that is the ultimate of being a consistent failure. When I started screenwritermag I know how much I had to struggle for gaining the confidence of people and that's how I learned how to earn the confidence online when you are not familiar with your audience.

    0
    Comment actions Permalink

Please sign in to leave a comment.