adobe acrobat pro DC Installing on one PC and not on another. Error 1603
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
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
7 years ago
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.
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.
Comments:
-
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. - akmagnum 7 years ago
Posted by:
anonymous_9363
7 years ago
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!! - akmagnum 7 years ago
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. - akmagnum 7 years ago