I have finally got the adobe acrobat pro to install on a test PC with k1000.

Created package with the wizard.

Deployed it to the k1000....installed with a script....with following command

All seems well after successful install on test PC.

BUT....

Pc's in production do not install the software

Even though the log file from both  script says "Successful".

When I check installed programs, it does not show up on the

failed machine.

One seems to install and the other one not.

The event log in the machine that failed shows a 1603 error.

Why is one machine having this installation  error and the other one not?


2 Comments   [ + ] Show Comments

Comments

  • What does your managed install look like?
  • I have zipped up the folder with the included transform I created....
    Chose....."override default installation"
    "Full command line" was........
    msiexec /i "AcroPro.msi" TRANSFORMS="AcropPro.mst" /qn
    also chose......
    "Don't Prepend msiexec.exe"
    So I noticed after a while, that the software is listed in the "installed programs" in the PC's inventory in the k1000.
    BUT.. the actual software is not installed on the computer.
    After another force inventory a few minutes later, the software disappears. Then nothing!!
    Weird!!
    • I believe that recent versions of the K1000 assume that the MI succeeded until an inventory says otherwise. When you zipped the folder did you select the contents and compress or select the folder containing the contents?
      • Hi Chuck.
        After much searching I finally found out the problem.
        Just to let you know (and others).... the problem was the
        "visual C++ redistributable package 2013" was not
        installing in the rollout by default.
        So if the machine didn't have that version of the package, ......then the install fails.
        That was why I some machines succeeded with the install while others failed. All the one that failed didn't have that version of the package.
        Thanks for your help.
Please log in to comment

Answers

0
As usual, without a log, no-one will have the first clue as to why it's failed, least of all us.

Add verbose logging to the command line. In the resulting log, find the text 'Return value 3.' The half-dozen or so lines around that text will have details of what failed.
Answered 03/09/2017 by: VBScab
Red Belt

  • The problem was the
    "visual C++ redistributable package 2013" was not
    installing in the rollout by default.
    So if the machine didn't have that version of the package, ......then the install fails.
    That was why I some machines succeeded with the install while others failed. All the one that failed didn't have that version of the package.
    Thanks for your help.
Please log in to comment
0
Presumably, you have now rolled out a standard set of VC RTs across your estate? They should really be part of your build, of course...
Answered 03/13/2017 by: VBScab
Red Belt

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