Software Deployment

It looks to me like the CA 'ExecOutlookFirewall_Create' is failing, since it seems to immediately roll it back ('ExecOutlookFirewall_InstallRollback'). I have *no* idea what that CA does but, on a failing machine, I'd try a manual install but with ProcMon running alongside.

BTW, this forum is designed for posts connected with errors returned by the Windows Installer engine (see the link 'MSI Errors' for examples). A moderator may well move this thread to the correct forum, viz. 'Package Development'

Thanks VBScab - I have an excerpt log from a PC Successfully installing Office as follows (by the way this only 9/10ths the way through):
[blockquote][blockquote]MSI(ACTIONSTART): 'Action 19:51:31: CreateFolders. Creating folders'
MSI(ACTIONSTART): 'Action 19:51:32: InstallFiles. Copying new files'
MSI(ACTIONSTART): 'Action 19:52:12: RegisterClassInfo. Registering Class servers'
MSI(ACTIONSTART): 'Action 19:52:12: RegisterExtensionInfo. Registering extension servers'
MSI(ACTIONSTART): 'Action 19:52:13: RegisterProgIdInfo. Registering program identifiers'
MSI(ACTIONSTART): 'Action 19:52:13: RegisterMIMEInfo. Registering MIME info'
MSI(ACTIONSTART): 'Action 19:52:13: CAMsInfo. '
MSI(INFO): 'CAMsInfo: MOF Compile succeeded.'
MSI(ACTIONSTART): 'Action 19:52:14: ExecOutlookFirewall_Create. '
MSI(ACTIONSTART): 'Action 19:52:14: ExecOutlookFirewall_InstallRollback. '
MSI(ACTIONSTART): 'Action 19:52:14: CADwSens.D0DF3458_A845_11D3_8D0A_0050046416B9. '
MSI(ACTIONSTART): 'Action 19:52:14: WriteRegistryValues. Writing system registry values'
MSI(ACTIONSTART): 'Action 19:52:35: Do_sqlVerIndependentProgID.BB9BCD10_C507_4374_A5FC_3F04C705A420. '
MSI(INFO): '<Func Name='LaunchFunction'>'
MSI(INFO): 'Function=Do_sqlVerIndependentProgID'
.................
.................
[/blockquote]Notice that the CA component successfully finishes with MOF Compile succeeded, and the OutlookFirewall stuffs looks like it supposed to happen. So I guess the line I need some understanding of is:
[blockquote]MSI(INFO): 'DwSens: Failed CoCreateInstance on EventSystem. hr: -2147023898

[/blockquote]Thanks, Steve
[/blockquote]

The same applies then, Steve. Run ProcMon alongside Setup.EXE manually (i.e., outside of SCCM's control0 on a failing machine.

Hi VBScab, Apologies for the delayed response... I have tried running ProcMon which has not given me clear enough evidence of root cause. I have instead decided to add a step prior to the Upgrade of Office 2007 and that is to UnInstall Office 2003. So far this has had no problems and it leaves existing user profiles in tact which from what I have seen does not cause any data loss.

Thanks for all your help on this problem.

Cheers, Steve.