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

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
Have a look at http://blogs.msdn.com/windows_installer_team/archive/2005/09/19/470980.aspx, it will explain why this occur.
Search for Unable to delete the file. LastError = 32.
Answered 11/02/2006 by: AngelD
Red Belt

Please log in to comment
0
Answered 11/02/2006 by: AngelD
Red Belt

Please log in to comment
0
Thanks for the reply!

Since this isn't deamed a fatal error, wouldn't you think the SMS status would indicate a successful status instead of job failed? Or; is there an option that I'm missing that would communicate this to SMS?
Answered 11/02/2006 by: H.Richburg
Senior Yellow Belt

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