Error: MsiExec.exe exited on xxx-xxx-xxxx with error code 1603.

Im trying to use :
PSEXEC -s \\%1 -i MsiExec.exe /q /X{90120000-0011-0000-0000-0000000FF1CE} /quiet /qn /norestart

Ususally, i never have issues. Can this not be done like this? I have been reading about uninstalling it from a share point using something like "setup.exe /uninstall"
But i want to avoid doing it that way if possible.

Thanks in advance for your time.
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
/quiet /qn ? why are you using both parameters for the same thing?

1603 is usually "access denied". i presume you already checked the event viewer for more info?
Answered 08/25/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
1603 is usually "access denied"That's one hell of an assumption. 1603 is a generic error code and could be a result of almost anything.

@OP, you can think of the ProductCode you have shown there as generic, too, in that using it to try and uninstall Office 2007 will result in failure, since there will be at least 15 entries for the various parts of Office. Use the set-up executeable.

FFR, in determining the cause of an error with Windows Installer, your first step should always be to run the command line but with the inclusion of the verbose logging argument: MSIEXEC [other arguments] /L*V _path_to_log_file\log_file_name. If the install/uninstall has failed, search the resulting log for the text 'Return value 3.' The dozen or so lines above and below the line containing that text will detail the failing action.
Answered 08/25/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

1603 is usually "access denied"That's one hell of an assumption. 1603 is a generic error code and could be a result of almost anything.



you're right, but in my experience, 1603 is almost always that "access denied" error. i should have mentioned that!
Answered 08/25/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
Ok, i thought for some reason that /qn was for logging, my bad for assuming..lol, that might explain why the uninstall is putting an icon of the uninstall process on the taskbar. I was able to uninstall office with my above script, it was just taking forever.

It does auto reboot after removal though, even though i have the /norestart switch in there. I am going to look into uninstalling from the setup file, just so i know how to go about doing so.

Thanks guy for your time.
Answered 08/25/2011 by: scripteaze
Senior Yellow Belt

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