Command line problem: Not recognizing files in external directory

Content Authoring
1

(imported topic written by mauricem)

I’ve been experimenting with the following command line and found that it doesn’t work when deployed in a fixlet

wait “{pathname of system folder}\msiexec.exe” /p “__Download\Ac705RdP_efgj.msp”;"__Download\Rdr707.msp";"__Download\Rdr708.msp" REINSTALLMODE=omus REINSTALL=all REBOOT=REALLYSUPPRESS /qb!

It’s seems to be failing because it can’t find the files. Any ideas why? Is there a workaround to get it to the __download directory?

Thanks

2

(imported comment written by brolly3391)

Hello maruicem,

I have not seen that sort of syntax for msiexec.exe before. Can you apply multiple patches by separating them with ; ? I do not see that documented anywhere. http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/msiexec.mspx?mfr=true

If you copy your msp files to the root of c:\ then will this command work from the run dialog?

msiexec.exe /p c:\Ac705RdP_efgj.msp;c:\Rdr707.msp;c:\Rdr708.msp REINSTALLMODE=omus REINSTALL=all REBOOT=REALLYSUPPRESS /qb!

I think you will want separate your command out into 3 lines.

wait 
"{pathname of system folder}\msiexec.exe" /p 
"__Download\Ac705RdP_efgj.msp" REINSTALLMODE=omus REINSTALL=all REBOOT=REALLYSUPPRESS /qb! wait 
"{pathname of system folder}\msiexec.exe" /p 
"__Download\Rdr707.msp" REINSTALLMODE=omus REINSTALL=all REBOOT=REALLYSUPPRESS /qb! wait 
"{pathname of system folder}\msiexec.exe" /p 
"__Download\Rdr708.msp" REINSTALLMODE=omus REINSTALL=all REBOOT=REALLYSUPPRESS /qb!

Also keep in mind that an MSP is keyed to a specific Product ID (PID). If the MSI that you are trying to patch is not present on the system, then msiexec is going to throw an error to that effect.

Is this a per-machine or per-user MSI install? Per-user installs can further complicate things.

Cheers,

Brolly

3

(imported comment written by mauricem)

Thanks Brolly. It is a usage of msiexec that is taken from an Adobe knowledgebase article here: www.adobe.com/support/techdocs/330817.html

Using the code you quoted above (using C:) does work. It does appear that the executable is running as a per-user MSI install.

Thanks

Updated

Looks like the knowledgebase article has changed so you’ll have to take my word for it. :wink: I’ll see if I can find it somewhere else. You can try the command and it does work though.

Updated