Error with Task Sequence install of MSI, MST & MSP

I’ve run into a head-scratcher here.  Several packages – which work when executed manually - are throwing 1635 errors when run from a Task Sequence from SCCM 2012.  Each of these packages are similar in that I’m running the MSI, MST & at least one MSP on one command line, for example:

msiexec /i "AcroRead.msi" TRANSFORMS="AcroRead.mst" /update "%~dp0AdbeRdrUpd1015.msp;%~dp0AdbeRdrSecUpd1016.msp" /qb- /L*V "%SystemRoot%\logs\AcroReader 10.1.6 install.log"

Log file shows this:

MSI (s) (18:28) [18:43:47:653]: Unable to create a temp copy of patch 'AdbeRdrUpd1015.msp'.

SCCM throws all of the files into C:\_SMSTaskSequence\Packages\PS100110\ - I can see the two patch files next to the MSI & MST files.

In the log file I have this:

MSI (s) (18:28) [18:43:47:627]: Original package ==> C:\_SMSTaskSequence\Packages\PS100110\AcroRead.msi

MSI (s) (18:28) [18:43:47:627]: Package we're running from ==> C:\WINDOWS\Installer\a2c191.msi

Looking in the C:\WINDOWS\Installer folder are a few MSI & MSP files already, so it would seem that there shouldn’t be any problems with that path.  Interestingly, the patch files are flagged Read Only.

Anyone have an idea what’s going on?  Like a pit bull, I’m not letting go of this one. . .

0 Comments   [ + ] Show comments

Answers (4)

Posted by: jaybee96 9 years ago
Red Belt

To get around this problem there are 3 general solutions..

1. Separate the install and patch process (i.e handle them in separate steps)
2. Specify the absolute path the to MSP (which can be difficult if you have multiple installer locations)
3. Create and admin point from the original software and then patch the admin point with the patch.msp. This way you don't have to patch anything when you install as the admin point has the updated files already.

Posted by: jagadeish 9 years ago
Red Belt

Try with this

msiexec /i "AcroRead.msi" TRANSFORMS="AcroRead.mst" PATCH="%~dp0AdbeRdrUpd1015.msp;%~dp0AdbeRdrSecUpd1016.msp" /qb- /L*V "%SystemRoot%\logs\AcroReader 10.1.6 install.log"

Posted by: vjaneczko 9 years ago
9th Degree Black Belt

I'm guessing I'll have to split the package apart; one for the MSI and another for the patches. That really sucks, too. I'm not a big fan of things working only under certain conditions.

@jaybee96; using the %~dp0 does specify the absolute path, while negating the need to have scripts use PUSHD & POPD or other ways to specify the location of the command execution.

@jagadeish; using the "PATCH=" property will only work with a single patch file. When specifying two or more, only the "/update" switch will work.

Posted by: rileyz 9 years ago
Red Belt

I cant remember, but I do recall the something werid with the TaskSequence Engine..what was it.

Test out the install cmd line in an advert (not using a Task Sequnce) and see if that works. I do recall there are some quirks with using a Task Sequence, like some things just dont work.

I cant remember if you can Install and Patch in one go either (im guessing it does work since you would of tested (: In the past we just installed, then patched.

Not really a solution, but I hope it helps.


Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ