I am using msi wrappers to execute Windows Updates. They work fine as long
as the custom action to execute the update is run Synchronous, Ignore exit
code. Without the "Ignore exit code" the update is executed successfully but
the msi execution fails. The failure happens rights at the end of the custom
action, just at the point that the update would be prompting the user to
restart.
Any ideas why Windows Installer cannot handle the restart return code from
the update? Up to about 6 months ago the patches used to just force a
restart and Windows Installer finished normally,
Thanks,
Anthony

I'm not sure about why MSI isn't handling the restart return code, but can
you configure your program to "SMS Reboots Computer" ??


----
This posting is provided "AS IS" with no warranties, and confers no rights.

SMS Technical FAQ at:
http://www.microsoft.com/technet/pro...q/default.mspx
----
Dave Randall
SMS Software Distribution Team


"Anthony Yates" <anthony.yates@airno~spamdesk.com> wrote in message
news:ein%(E-Mail Removed)...
>I am using msi wrappers to execute Windows Updates. They work fine as long
> as the custom action to execute the update is run Synchronous, Ignore exit
> code. Without the "Ignore exit code" the update is executed successfully
> but
> the msi execution fails. The failure happens rights at the end of the
> custom
> action, just at the point that the update would be prompting the user to
> restart.
> Any ideas why Windows Installer cannot handle the restart return code from
> the update? Up to about 6 months ago the patches used to just force a
> restart and Windows Installer finished normally,
> Thanks,
> Anthony
>
>

I can force a reboot using the REBOOT property in the msi, but the
update.exe itself is returning an error. At the moment I just get round it
by ignoring the return code. I am suprised that the update.exe reboot
request is interpreted by Windows installer as an error,
Anthony




"David Randall [MS]" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> I'm not sure about why MSI isn't handling the restart return code, but can
> you configure your program to "SMS Reboots Computer" ??
>
>
> ----
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> SMS Technical FAQ at:
>
http://www.microsoft.com/technet/pro...aq/default.msp
x
> ----
> Dave Randall
> SMS Software Distribution Team
>
>
> "Anthony Yates" <anthony.yates@airno~spamdesk.com> wrote in message
> news:ein%(E-Mail Removed)...
> >I am using msi wrappers to execute Windows Updates. They work fine as
long
> > as the custom action to execute the update is run Synchronous, Ignore
exit
> > code. Without the "Ignore exit code" the update is executed successfully
> > but
> > the msi execution fails. The failure happens rights at the end of the
> > custom
> > action, just at the point that the update would be prompting the user to
> > restart.
> > Any ideas why Windows Installer cannot handle the restart return code
from
> > the update? Up to about 6 months ago the patches used to just force a
> > restart and Windows Installer finished normally,
> > Thanks,
> > Anthony
> >
> >
>
>

"Success" from a custom action program is defined as an exit code of zero.
Maybe update.exe now returns non-zero for success. If some arbritrary
program like that returns non-zero for success, you can wrap it in another
custom action that launches it.
http://msdn.microsoft.com/library/de...urn_values.asp
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://www.amazon.com/exec/obidos/tg...id=1087915405/

"Anthony Yates" <anthony.yates@airno~spamdesk.com> wrote in message
news:(E-Mail Removed)...
> I can force a reboot using the REBOOT property in the msi, but the
> update.exe itself is returning an error. At the moment I just get round it
> by ignoring the return code. I am suprised that the update.exe reboot
> request is interpreted by Windows installer as an error,
> Anthony
>
>
>
>
> "David Randall [MS]" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> > I'm not sure about why MSI isn't handling the restart return code, but
can
> > you configure your program to "SMS Reboots Computer" ??
> >
> >
> > ----
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > SMS Technical FAQ at:
> >
>
http://www.microsoft.com/technet/pro...aq/default.msp
> x
> > ----
> > Dave Randall
> > SMS Software Distribution Team
> >
> >
> > "Anthony Yates" <anthony.yates@airno~spamdesk.com> wrote in message
> > news:ein%(E-Mail Removed)...
> > >I am using msi wrappers to execute Windows Updates. They work fine as
> long
> > > as the custom action to execute the update is run Synchronous, Ignore
> exit
> > > code. Without the "Ignore exit code" the update is executed
successfully
> > > but
> > > the msi execution fails. The failure happens rights at the end of the
> > > custom
> > > action, just at the point that the update would be prompting the user
to
> > > restart.
> > > Any ideas why Windows Installer cannot handle the restart return code
> from
> > > the update? Up to about 6 months ago the patches used to just force a
> > > restart and Windows Installer finished normally,
> > > Thanks,
> > > Anthony
> > >
> > >
> >
> >
>
>

Thanks,
I read somewhere that it returns an error code for "reboot required". I can
get round this by ignoring the return code, but obviously if there is an
error it will continue regardless,
Anthony



"Phil Wilson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Success" from a custom action program is defined as an exit code of zero.
> Maybe update.exe now returns non-zero for success. If some arbritrary
> program like that returns non-zero for success, you can wrap it in another
> custom action that launches it.
>
http://msdn.microsoft.com/library/de...us/msi/setup/c
ustom_action_return_values.asp
> --
> Phil Wilson
> [MVP Windows Installer]
> Definitive Guide to Windows Installer
> http://www.amazon.com/exec/obidos/tg...id=1087915405/
>
> "Anthony Yates" <anthony.yates@airno~spamdesk.com> wrote in message
> news:(E-Mail Removed)...
> > I can force a reboot using the REBOOT property in the msi, but the
> > update.exe itself is returning an error. At the moment I just get round
it
> > by ignoring the return code. I am suprised that the update.exe reboot
> > request is interpreted by Windows installer as an error,
> > Anthony
> >
> >
> >
> >
> > "David Randall [MS]" <(E-Mail Removed)> wrote in message
> > news:#(E-Mail Removed)...
> > > I'm not sure about why MSI isn't handling the restart return code, but
> can
> > > you configure your program to "SMS Reboots Computer" ??
> > >
> > >
> > > ----
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > SMS Technical FAQ at:
> > >
> >
>
http://www.microsoft.com/technet/pro...aq/default.msp
> > x
> > > ----
> > > Dave Randall
> > > SMS Software Distribution Team
> > >
> > >
> > > "Anthony Yates" <anthony.yates@airno~spamdesk.com> wrote in message
> > > news:ein%(E-Mail Removed)...
> > > >I am using msi wrappers to execute Windows Updates. They work fine as
> > long
> > > > as the custom action to execute the update is run Synchronous,
Ignore
> > exit
> > > > code. Without the "Ignore exit code" the update is executed
> successfully
> > > > but
> > > > the msi execution fails. The failure happens rights at the end of
the
> > > > custom
> > > > action, just at the point that the update would be prompting the
user
> to
> > > > restart.
> > > > Any ideas why Windows Installer cannot handle the restart return
code
> > from
> > > > the update? Up to about 6 months ago the patches used to just force
a
> > > > restart and Windows Installer finished normally,
> > > > Thanks,
> > > > Anthony
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>