Hey guys, I come here alot to check out the latest headlines and basically just to poke around, I signed up today because i am in need of a little help.

I am trying to rollout WSE 3.0 runtime and im getting the typical :
"msiexec exited on x.x.x.x with error code 1603."

Im using this : PSEXEC \\x.x.x.x msiexec /q /i c:\some_app.msi

I can install this locally, however, it needs to get installed on about 800 systems.

Anyone here have success with this package?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Im using this : PSEXEC \\x.x.x.x msiexec /q /i c:\some_app.msi

Just thinking out loud...
Hmmm, not sure about using an IP address... ;) You might have a syntax error. I use this in a batch file (as an example for you):
psexec \\machinename c:\windows\system32\msiexec.exe /unregister

This will use PSExec on the LOCAL machine to run the msiexec on the REMOTE machine (\\machinename) to unregister the WI Service. I also use the full path to the msiexec.

If your path has any white spaces in it you should put it in double quotes.

You could also add an MSI log file (/l*v c:\temp\some_app.msi) then look at the full paths to see what is causing the 1603.

You might have a permissions problem too.
Answered 06/27/2011 by: bearden3
Purple Belt

Please log in to comment
0
Well, I alway use IP Addresses and not hostnames due the the fact that sometimes i can not access the system via dns. So i have done this before via IP Address and it has worked.

Any other Ideas?
Answered 06/29/2011 by: scripteaze
Senior Yellow Belt

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