Jump to content

Recommended Posts

Posted

Hi,

 

I am trying to Deploy Adobe Reader via SCCM.

 

It is failing to install with this in the error log

 

MSI (s) (9C:C8) [10:40:21:240]: Product: Adobe Reader X (10.1.0) -- Installation failed.

MSI (s) (9C:C8) [10:40:21:240]: Windows Installer installed the product. Product Name: Adobe Reader X (10.1.0). Product Version: 10.1.0. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Installation success or error status: 1635.

This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
C:\Windows\system32\CCM\Cache\FPH0000D.3.System\AdbeRdr1010_en_US.msi

 

This is the command i am running in the package

 

AdbeRdr1010_en_US.msi PATCH="AdbeRdrUpd1012.msp" TRANSFORMS="FPHS-Settings.mst" /passive /log C:\Software-Deployment-Logs\Adobe-Reader-10.1.3.log

 

Any thoughts please?

 

Thanks

Posted (edited)

Just to check you have the command right, it should start with msiexec /i

 

Other than that, is the patch in the folder with the msi?

It appears it can't find/open the patch.

Edited by sparkeh
  • Thanks 1
Posted
Just to check you have the command right, it should start with msiexec /i

 

Other than that, is the patch in the folder with the msi?

 

will try it msiexec in front the patch is in the same folder.

 

Thanks

Posted

1) try installation manually as per above, also test without your TRANSFORMS and PATCH lines

2) are the .msp and .mst files in the source folder along with the MSI?

3) has your SCCM package been set to use source files and pointing to the correct folder on the site server?

4) have you added a distribution point for the package?

5) have you checked package status to make sure all files were sent to the distribution point?

Posted
Bah!

 

Hmm does the install complete if you copy the files to a machines and run the command?

 

It doesnt no. If i run it manually there is nothing in the log file.

@gshaw thanks for the input, looks like the error is with the command itself. i will have a play with it.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...