/build/static/layout/Breadcrumb_cap_w.png

SMS with chain updates problem

I'm trying to push out Publisher 2003 along with any updates and SP's using Microsoft's SMS in conjunction with ohotfix.exe to chain the updates to the SMS install of the product. Everything appears to work but SMS indicates the job failed. From best I can tell it is because of a return of Lasterror = 32 (see bold in log below).

Any Ideas?

Thanks
--Howie
===============
End of Log:
.
.
.
MSI (s) (E4:40) [16:02:51:047]: Product: Microsoft Office Publisher 2003 - Update 'Security Update for Publisher 2003 (KB894542): MSPUB' installed successfully.

MSI (s) (E4:40) [16:02:51:047]: Note: 1: 1728
MSI (s) (E4:40) [16:02:51:047]: Product: Microsoft Office Publisher 2003 -- Configuration completed successfully.

MSI (s) (E4:40) [16:02:51:062]: Attempting to delete file C:\WINDOWS\Installer\3354159.msp
MSI (s) (E4:40) [16:02:51:062]: Unable to delete the file. LastError = 32
MSI (s) (E4:40) [16:02:51:078]: Cleaning up uninstalled install packages, if any exist
MSI (s) (E4:40) [16:02:51:078]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\3354159.msp'
MSI (s) (E4:40) [16:02:51:078]: MainEngineThread is returning 0
MSI (s) (E4:D4) [16:02:51:078]: Destroying RemoteAPI object.
MSI (s) (E4:64) [16:02:51:078]: Custom Action Manager thread ending.
=== Logging stopped: 10/12/2006 16:02:51 ===
MSI (c) (90:94) [16:02:51:078]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (90:94) [16:02:51:078]: MainEngineThread is returning 0
=== Verbose logging stopped: 10/12/2006 16:02:51 ===

0 Comments   [ + ] Show comments

Answers (1)

Posted by: H.Richburg 14 years ago
Senior Yellow Belt
0
Here's an update to my oriignla problem. It doesn't appear to be the error 32 that was causing the problem:

I'm attempting to distribute Microsoft Publisher 2003 along with SP1 and its
hotfixes on a PC that has Outlook 2002 installed using a Local Installation
Source.

The SMS Package appears to run sucessfully but SMS shows that the job
failed, exceeding time. What appears to happen is that SMS hands off to the
Ohotfix Chained Updates but Ohotfix never returns control back to the SMS
stream, see below:
............
.
.
Successfully launched MsiExec....
11/20/2006 3:28:34 PM Chained install return code: 0

Looking for setup tasks to process.
11/20/2006 3:28:34 PM WaitForMsiExecDone...
11/20/2006 3:28:34 PM WaitForMsiExecDone exits
11/20/2006 3:28:34 PM
Executing Task:
Ohotfix Chained Updates
"\\SCENI1.SYSADMIN.SUNY.EDU\SMSPKGD$\SUP0001A\ohotfix\ohotfix.exe"
Type: exe
Ignore Return Values: False
Reboot: False

Successfully launched chained task....
...........

The ohotfix log shows the fixes were applied sucecessfully which is
substantiated by the Event Log. The Event log also indicates that Publisher
was installed successfully. However immeidately following the good news are
two additional entries. One identifying an MSinstaller Event ID: 1015 with
the following message, "Failed to connect to server. Error: 0x800401F0". And
the second an SMSClinet Event ID: 10070 stating "The program for
advertisement "SUP20076" ("SUP0001A" - "Quiet") exceeded the maximum allowed
run time of 30 minute(s)......" My assumption is that the packlage
eventually times out unable to connect to the server (what server?)?

Does nayone have any thoughts on what might be wrong or possibly run into
this before?

Any thoughts or suggestions would greatly be appreciated.

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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ