How to prevent MSI error code 3010

[Martin]

Hi,

we made several msi packages and some of them end with the error code
3010 (ERROR_SUCCESS_REBOOT_REQUIRED). In this case I want the msi
package should end with the error code 0 (ERROR_SUCCESS).
How can I do that within the package because the error 3010 is no
error for us?

Regards
Martin

[Kallely Sajan]

If it is no error, the program that launches the installation should be made
to ignore this return code.
You might also want to try setting the property REBOOT=ReallySuppress

--

Regards,
Sajan.

PS: Please don't send me direct emails, use the newsroom.

Post by Martin
Hi,
we made several msi packages and some of them end with the error code
3010 (ERROR_SUCCESS_REBOOT_REQUIRED). In this case I want the msi
package should end with the error code 0 (ERROR_SUCCESS).
How can I do that within the package because the error 3010 is no
error for us?
Regards
Martin

[Martin]

well the program is msiexec himself I think. I logged all and the last
line in the log is "MainEngineThread is returning 3010". The property
REBOOT suppresses all prompts for reboots, we already set this
property to all our packages, so there is no prompt for reboot. But
the exit code is still there. Thanks anyway.

How can I tell msiexec not to look after a required reboot so the
error 3010 is not set?
Btw. we use XP and msiexec 2.0

Post by Kallely Sajan
If it is no error, the program that launches the installation should be made
to ignore this return code.
You might also want to try setting the property REBOOT=ReallySuppress
--
Regards,
Sajan.

[Martin]

Hi David,

We have a specific reason for zero return code.
We roll out our msi packages packaged into Tivoli packages. And Tivoli
does not know msi errors so everything other than msi exit code zero
generates an error. To search in every package for the reason for
reboot is very work intensive so I'd like to have a solution to put
that into our automated processes.
What work around do you mean?

This is by design.
If your installer is suppressing reboots, then your bootstrapping
application should detect the 3010 return code and ask the user to reboot. A
typical reason for this would be to install several things while only
requiring one reboot.
You may be able to work around the problem by determining what is causing
the reboot, and adding custom actions to handle the situation.
If you have a specific reason for requiring a zero return code, we may be
able to suggest some alternative work-around.
David

[David Barnard]

This resource:
http://www-1.ibm.com/support/docview.wss?rs=0&context=SWI00&context=SWJ00&context=SWK00&q=msi&uid=swg1IY24057&loc=en_GB&cs=utf-8&lang=

seems to imply that the problem has been fixed. Perhaps you should explore
this further?

David

Clearly, this is a problem with Tivoli.

Post by Martin
Hi David,
We have a specific reason for zero return code.
We roll out our msi packages packaged into Tivoli packages. And Tivoli
does not know msi errors so everything other than msi exit code zero
generates an error. To search in every package for the reason for
reboot is very work intensive so I'd like to have a solution to put
that into our automated processes.
What work around do you mean?

This is by design.
If your installer is suppressing reboots, then your bootstrapping
application should detect the 3010 return code and ask the user to reboot. A
typical reason for this would be to install several things while only
requiring one reboot.
You may be able to work around the problem by determining what is causing
the reboot, and adding custom actions to handle the situation.
If you have a specific reason for requiring a zero return code, we may be
able to suggest some alternative work-around.
David