Unable to integrate latest Outlook junk mail filter KB936677 for Office 2003

Hello, I can not manually install (normal or unattended/quiet mode) or
slipstream (using the msiexec to integrate the MSP into an admin
install source) the latest Outlook 2003 junk mail filter (hotfix
KB936677). Starting the Office Source Engine does not help (somebody
with a similar problem suggested this). The only method that seems to
work is to use Microsoft Update or Office Update, which is
unacceptable to me since my goal is to have a completely updated
office install with SP3 and any new hotfixes already integrated - so
the end result is nothing required to download on either MU or OU.

It appears there is a version mismatch incorrectly coded into this
hotfix. When running a manual install of this hotfix (by simply
downloading and executing) on a computer with Office 2003 w/ SP3
already installed, I get an error saying "The expected version of the
product was not found on your system." When I extract the OUTLFLTR.msp
file from the hotfix package and execute that file or attempt to
integrate to an admin install source using msiexec, I get an error
saying "The upgrade patch cannot be installed by the Windows Installer
service because the program to be upgraded may be missing, or the
upgrade patch may update a different version of the program." The .log
files indicate a 1642 error code.

I'm not the only one with this problem:
http://www.msfn.org/board/Latest_Out...tml&pid=694939
http://www.spotlight.de/zforen/mie/m...051-25263.html (use
babelfish if you do not understand German)

I do integrate SP3 in my office source beforehand in the same manner I
did SP2 previously, detailed here: http://unattended.msfn.org/unattended.xp/view/web/48/
and both MU and OU detect it as properly installed, so other than the
outlook filter hotfix, it's a "clean slate" otherwise on both
websites. I've been doing this for years, never a problem.

On a side note, I want to point out that Microsoft Update has never
properly detected slipstreamed office 2003 hotfixes (using msiexec to
integrate the msp file to an admin install source) whereas Office
Update always has. The only way to convince Microsoft Update is to run
unattended/quiet installs of Office 2003 hotfixes in RunOnceEx of a XP
unattended install (therefore consuming more time to finish), or to
slipstream the office hotfixes as normal, and then export the registry
of the office hotfix section of a computer updated through MU to
refrain it from telling me I need to download fixes that are already
properly integrated. Very annoying.

Hello lifesim,

We have been seeing some issues with this patch.

Could you please provide a verbose log from the failed install for review?
This will help us get to the bottom of it. Here is how to get a verbose log
that you can paste here.

1. Please download the patch to your local machine from here.
Http://www.microsoft.com/downloads/i...llFile-ENU.exe

2. Create a folder in the c:\ named Patch. Place
office2003-KB936677-FullFile-ENU.exe in that folder.

3. goto start, then run. In the run box type "cmd" (without the quotes). hit
enter

4. in the black window that comes up type "cd\" (without the quotes). hit
enter then type "cd patch" (without the quotes). hit enter

5. type "office2003-KB936677-FullFile-ENU.exe /c /t:c:\patch /q" (without
the quotes). hit enter

6. type "msiexec /p OUTLFLTR.msp /l*v c:\patch\Log.txt /qb" (without the
quotes). hit enter

7. It will fail or not. Either way please locate the file c:\patch\Log.txt
and paste the contents here. You may need to break it up over a couple posts
if it is very large.

Thanks
--
Eric Palm
MSFT Office Setup


"" wrote:

> Hello, I can not manually install (normal or unattended/quiet mode) or
> slipstream (using the msiexec to integrate the MSP into an admin
> install source) the latest Outlook 2003 junk mail filter (hotfix
> KB936677). Starting the Office Source Engine does not help (somebody
> with a similar problem suggested this). The only method that seems to
> work is to use Microsoft Update or Office Update, which is
> unacceptable to me since my goal is to have a completely updated
> office install with SP3 and any new hotfixes already integrated - so
> the end result is nothing required to download on either MU or OU.
>
> It appears there is a version mismatch incorrectly coded into this
> hotfix. When running a manual install of this hotfix (by simply
> downloading and executing) on a computer with Office 2003 w/ SP3
> already installed, I get an error saying "The expected version of the
> product was not found on your system." When I extract the OUTLFLTR.msp
> file from the hotfix package and execute that file or attempt to
> integrate to an admin install source using msiexec, I get an error
> saying "The upgrade patch cannot be installed by the Windows Installer
> service because the program to be upgraded may be missing, or the
> upgrade patch may update a different version of the program." The .log
> files indicate a 1642 error code.
>
> I'm not the only one with this problem:
> http://www.msfn.org/board/Latest_Out...tml&pid=694939
> http://www.spotlight.de/zforen/mie/m...051-25263.html (use
> babelfish if you do not understand German)
>
> I do integrate SP3 in my office source beforehand in the same manner I
> did SP2 previously, detailed here: http://unattended.msfn.org/unattended.xp/view/web/48/
> and both MU and OU detect it as properly installed, so other than the
> outlook filter hotfix, it's a "clean slate" otherwise on both
> websites. I've been doing this for years, never a problem.
>
> On a side note, I want to point out that Microsoft Update has never
> properly detected slipstreamed office 2003 hotfixes (using msiexec to
> integrate the msp file to an admin install source) whereas Office
> Update always has. The only way to convince Microsoft Update is to run
> unattended/quiet installs of Office 2003 hotfixes in RunOnceEx of a XP
> unattended install (therefore consuming more time to finish), or to
> slipstream the office hotfixes as normal, and then export the registry
> of the office hotfix section of a computer updated through MU to
> refrain it from telling me I need to download fixes that are already
> properly integrated. Very annoying.
>
>

On Sep 28, 2:04 pm, Eric A. <Er...@discussions.microsoft.com> wrote:
> Hello lifesim,
>
> We have been seeing some issues with this patch.
>
> Could you please provide a verbose log from the failed install for review?
> This will help us get to the bottom of it. Here is how to get a verbose log
> that you can paste here.
>
> 1. Please download the patch to your local machine from here.
> Http://www.microsoft.com/downloads/i...ayLang=en&SrcC...
>
> 2. Create a folder in the c:\ named Patch. Place
> office2003-KB936677-FullFile-ENU.exe in that folder.
>
> 3. goto start, then run. In the run box type "cmd" (without the quotes). hit
> enter
>
> 4. in the black window that comes up type "cd\" (without the quotes). hit
> enter then type "cd patch" (without the quotes). hit enter
>
> 5. type "office2003-KB936677-FullFile-ENU.exe /c /t:c:\patch /q" (without
> the quotes). hit enter
>
> 6. type "msiexec /p OUTLFLTR.msp /l*v c:\patch\Log.txt /qb" (without the
> quotes). hit enter
>
> 7. It will fail or not. Either way please locate the file c:\patch\Log.txt
> and paste the contents here. You may need to break it up over a couple posts
> if it is very large.
>
> Thanks
> --
> Eric Palm
> MSFT Office Setup

=== Verbose logging started: 9/28/2007 19:15:19 Build type: SHIP
UNICODE 3.01.4000.4104 Calling process: C:\WINDOWS
\system32\msiexec.exe ===
MSI (c) (64:6C) [19:15:19:679]: Resetting cached policy values
MSI (c) (64:6C) [19:15:19:679]: Machine policy value 'Debug' is 0
MSI (c) (64:6C) [19:15:19:679]: ******* RunEngine:
******* Product: {90110409-6000-11D3-8CFE-0150048383C9}
******* Action:
******* CommandLine: **********
MSI (c) (64:6C) [19:15:19:679]: Client-side and UI is none or basic:
Running entire install on the server.
MSI (c) (64:6C) [19:15:19:679]: Grabbed execution mutex.
MSI (c) (64:6C) [19:15:19:809]: Cloaking enabled.
MSI (c) (64:6C) [19:15:19:809]: Attempting to enable all disabled
priveleges before calling Install on Server
MSI (c) (64:6C) [19:15:19:829]: Incrementing counter to disable
shutdown. Counter after increment: 0
MSI (s) (9C:1C) [19:15:20:460]: Grabbed execution mutex.
MSI (s) (9C:84) [19:15:20:460]: Resetting cached policy values
MSI (s) (9C:84) [19:15:20:460]: Machine policy value 'Debug' is 0
MSI (s) (9C:84) [19:15:20:460]: ******* RunEngine:
******* Product: {90110409-6000-11D3-8CFE-0150048383C9}
******* Action:
******* CommandLine: **********
MSI (s) (9C:84) [19:15:20:460]: Machine policy value
'DisableUserInstalls' is 0
MSI (s) (9C:84) [19:15:20:470]: End dialog not enabled
MSI (s) (9C:84) [19:15:20:490]: Original package ==> C:\WINDOWS
\Installer\2aec7a.msi
MSI (s) (9C:84) [19:15:20:490]: Package we're running from ==> C:
\WINDOWS\Installer\2aec7a.msi
MSI (s) (9C:84) [19:15:20:560]: APPCOMPAT: looking for appcompat
database entry with ProductCode
'{90110409-6000-11D3-8CFE-0150048383C9}'.
MSI (s) (9C:84) [19:15:20:560]: APPCOMPAT: no matching ProductCode
found in database.
MSI (s) (9C:84) [19:15:20:570]: MSCOREE already loaded, using loaded
copy
MSI (s) (9C:84) [19:15:20:600]: File will have security applied from
OpCode.
MSI (s) (9C:84) [19:15:20:640]: Original patch ==> C:\patch
\OUTLFLTR.msp
MSI (s) (9C:84) [19:15:20:640]: Patch we're running from ==> C:\WINDOWS
\Installer\29612.msp
MSI (s) (9C:84) [19:15:20:650]: SOFTWARE RESTRICTION POLICY: Verifying
patch --> 'C:\patch\OUTLFLTR.msp' against software restriction policy
MSI (s) (9C:84) [19:15:20:650]: Note: 1: 2262 2: DigitalSignature 3:
-2147287038
MSI (s) (9C:84) [19:15:20:650]: SOFTWARE RESTRICTION POLICY: C:\patch
\OUTLFLTR.msp is not digitally signed
MSI (s) (9C:84) [19:15:20:650]: SOFTWARE RESTRICTION POLICY: C:\patch
\OUTLFLTR.msp is permitted to run at the 'unrestricted' authorization
level.
MSI (s) (9C:84) [19:15:20:650]: SequencePatches starts. Product code:
{90110409-6000-11D3-8CFE-0150048383C9}, Product version: 11.0.8173.0,
Upgrade code: {00110000-6000-11D3-8CFE-0050048383C9}, Product language
1033
MSI (s) (9C:84) [19:15:20:711]: PATCH SEQUENCER WARNING: C:\patch
\OUTLFLTR.msp patch will not be sequenced because it does not contain
any transform that may apply to product!
MSI (s) (9C:84) [19:15:20:711]: SequencePatches returns success.
MSI (s) (9C:84) [19:15:20:711]: Final Patch Application Order:
MSI (s) (9C:84) [19:15:20:711]: Other Patches:
MSI (s) (9C:84) [19:15:20:711]: Unknown\Absent:
{DB7BA839-6E6D-4A32-8D8B-FA4816912E2C} - C:\patch\OUTLFLTR.msp
MSI (s) (9C:84) [19:15:20:711]: Product: Microsoft Office Professional
Edition 2003 - Update '{DB7BA839-6E6D-4A32-8D8B-FA4816912E2C}' could
not be installed. Error code 1642. Additional information is available
in the log file c:\patch\Log.txt.

MSI (s) (9C:84) [19:15:20:721]: Note: 1: 1708
MSI (s) (9C:84) [19:15:20:721]: Note: 1: 2729
MSI (s) (9C:84) [19:15:20:721]: Note: 1: 2729
MSI (s) (9C:84) [19:15:20:721]: Product: Microsoft Office Professional
Edition 2003 -- Installation failed.

MSI (s) (9C:84) [19:15:20:741]: Attempting to delete file C:\WINDOWS
\Installer\29612.msp
MSI (s) (9C:84) [19:15:20:741]: MainEngineThread is returning 1642
The upgrade patch cannot be installed by the Windows Installer service
because the program to be upgraded may be missing, or the upgrade
patch may update a different version of the program. Verify that the
program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
C:\WINDOWS\Installer\2aec7a.msi
MSI (c) (64:6C) [19:15:20:751]: Decrementing counter to disable
shutdown. If counter >= 0, shutdown will be denied. Counter after
decrement: -1
MSI (c) (64:6C) [19:15:20:751]: MainEngineThread is returning 1642
=== Verbose logging stopped: 9/28/2007 19:15:20 ===

Hello,

I also need to know the resolution to this. I ran the verbose logging
that was suggested and got 15K line long logfile (I'll post it if you
REALLY want me to), but the jest is this

MSI (s) (64:4C) [08:42:04:504]: Note: 1: 1728
MSI (s) (64:4C) [08:42:04:519]: Product: Microsoft Office Professional
Edition 2003 -- Configuration completed successfully.

....and yet it still shows in Office Updates.

Thanks
Gregory

On Sep 28, 1:04 pm, Eric A. <Er...@discussions.microsoft.com> wrote:
> Hello lifesim,
>
> We have been seeing some issues with this patch.
>
> Could you please provide a verbose log from the failed install for review?
> This will help us get to the bottom of it. Here is how to get a verbose log
> that you can paste here.
>
> 1. Please download the patch to your local machine from here.
> Http://www.microsoft.com/downloads/i...ayLang=en&SrcC...
>
> 2. Create a folder in the c:\ named Patch. Place
> office2003-KB936677-FullFile-ENU.exe in that folder.
>
> 3. goto start, then run. In the run box type "cmd" (without the quotes). hit
> enter
>
> 4. in the black window that comes up type "cd\" (without the quotes). hit
> enter then type "cd patch" (without the quotes). hit enter
>
> 5. type "office2003-KB936677-FullFile-ENU.exe /c /t:c:\patch /q" (without
> the quotes). hit enter
>
> 6. type "msiexec /p OUTLFLTR.msp /l*v c:\patch\Log.txt /qb" (without the
> quotes). hit enter
>
> 7. It will fail or not. Either way please locate the file c:\patch\Log.txt
> and paste the contents here. You may need to break it up over a couple posts
> if it is very large.
>
> Thanks
> --
> Eric Palm
> MSFT Office Setup
>
>
>
> "life...@gmail.com" wrote:
> > Hello, I can not manually install (normal or unattended/quiet mode) or
> > slipstream (using the msiexec to integrate the MSP into an admin
> > install source) the latest Outlook 2003 junk mail filter (hotfix
> >KB936677). Starting the Office Source Engine does not help (somebody
> > with a similar problem suggested this). The only method that seems to
> > work is to use Microsoft Update or Office Update, which is
> > unacceptable to me since my goal is to have a completely updated
> > office install with SP3 and any new hotfixes already integrated - so
> > the end result is nothing required to download on either MU or OU.
>
> > It appears there is a version mismatch incorrectly coded into this
> > hotfix. When running a manual install of this hotfix (by simply
> > downloading and executing) on a computer with Office 2003 w/ SP3
> > already installed, I get an error saying "The expected version of the
> > product was not found on your system." When I extract the OUTLFLTR.msp
> > file from the hotfix package and execute that file or attempt to
> > integrate to an admin install source using msiexec, I get an error
> > saying "The upgrade patch cannot be installed by the Windows Installer
> > service because the program to be upgraded may be missing, or the
> > upgrade patch may update a different version of the program." The .log
> > files indicate a 1642 error code.
>
> > I'm not the only one with this problem:
> >http://www.msfn.org/board/Latest_Out..._filter_won_t1...
> >http://www.spotlight.de/zforen/mie/m...25263.html(use
> > babelfish if you do not understand German)
>
> > I do integrate SP3 in my office source beforehand in the same manner I
> > did SP2 previously, detailed here:http://unattended.msfn.org/unattended.xp/view/web/48/
> > and both MU and OU detect it as properly installed, so other than the
> > outlook filter hotfix, it's a "clean slate" otherwise on both
> > websites. I've been doing this for years, never a problem.
>
> > On a side note, I want to point out that Microsoft Update has never
> > properly detected slipstreamed office 2003 hotfixes (using msiexec to
> > integrate the msp file to an admin install source) whereas Office
> > Update always has. The only way to convince Microsoft Update is to run
> > unattended/quiet installs of Office 2003 hotfixes in RunOnceEx of a XP
> > unattended install (therefore consuming more time to finish), or to
> > slipstream the office hotfixes as normal, and then export the registry
> > of the office hotfix section of a computer updated through MU to
> > refrain it from telling me I need to download fixes that are already
> > properly integrated. Very annoying.- Hide quoted text -
>
> - Show quoted text -

This patch has an issue.

It has been brought to the attention of the patch team. They are aware of
the issue, but the new junk mail filter patch comes out in 6 days. So there
is a really good chance that this current patch will not be fixed before the
next junk mail filter patch that supercedes it comes out. Hopefully the new
patch will not have the same issues but if it does it will be addressed right
away.





--
Eric Palm
MSFT Office Setup


"WMI&ADSI" wrote:

> Hello,
>
> I also need to know the resolution to this. I ran the verbose logging
> that was suggested and got 15K line long logfile (I'll post it if you
> REALLY want me to), but the jest is this
>
> MSI (s) (64:4C) [08:42:04:504]: Note: 1: 1728
> MSI (s) (64:4C) [08:42:04:519]: Product: Microsoft Office Professional
> Edition 2003 -- Configuration completed successfully.
>
> ....and yet it still shows in Office Updates.
>
> Thanks
> Gregory
>
> On Sep 28, 1:04 pm, Eric A. <Er...@discussions.microsoft.com> wrote:
> > Hello lifesim,
> >
> > We have been seeing some issues with this patch.
> >
> > Could you please provide a verbose log from the failed install for review?
> > This will help us get to the bottom of it. Here is how to get a verbose log
> > that you can paste here.
> >
> > 1. Please download the patch to your local machine from here.
> > Http://www.microsoft.com/downloads/i...ayLang=en&SrcC...
> >
> > 2. Create a folder in the c:\ named Patch. Place
> > office2003-KB936677-FullFile-ENU.exe in that folder.
> >
> > 3. goto start, then run. In the run box type "cmd" (without the quotes). hit
> > enter
> >
> > 4. in the black window that comes up type "cd\" (without the quotes). hit
> > enter then type "cd patch" (without the quotes). hit enter
> >
> > 5. type "office2003-KB936677-FullFile-ENU.exe /c /t:c:\patch /q" (without
> > the quotes). hit enter
> >
> > 6. type "msiexec /p OUTLFLTR.msp /l*v c:\patch\Log.txt /qb" (without the
> > quotes). hit enter
> >
> > 7. It will fail or not. Either way please locate the file c:\patch\Log.txt
> > and paste the contents here. You may need to break it up over a couple posts
> > if it is very large.
> >
> > Thanks
> > --
> > Eric Palm
> > MSFT Office Setup
> >
> >
> >
> > "life...@gmail.com" wrote:
> > > Hello, I can not manually install (normal or unattended/quiet mode) or
> > > slipstream (using the msiexec to integrate the MSP into an admin
> > > install source) the latest Outlook 2003 junk mail filter (hotfix
> > >KB936677). Starting the Office Source Engine does not help (somebody
> > > with a similar problem suggested this). The only method that seems to
> > > work is to use Microsoft Update or Office Update, which is
> > > unacceptable to me since my goal is to have a completely updated
> > > office install with SP3 and any new hotfixes already integrated - so
> > > the end result is nothing required to download on either MU or OU.
> >
> > > It appears there is a version mismatch incorrectly coded into this
> > > hotfix. When running a manual install of this hotfix (by simply
> > > downloading and executing) on a computer with Office 2003 w/ SP3
> > > already installed, I get an error saying "The expected version of the
> > > product was not found on your system." When I extract the OUTLFLTR.msp
> > > file from the hotfix package and execute that file or attempt to
> > > integrate to an admin install source using msiexec, I get an error
> > > saying "The upgrade patch cannot be installed by the Windows Installer
> > > service because the program to be upgraded may be missing, or the
> > > upgrade patch may update a different version of the program." The .log
> > > files indicate a 1642 error code.
> >
> > > I'm not the only one with this problem:
> > >http://www.msfn.org/board/Latest_Out..._filter_won_t1...
> > >http://www.spotlight.de/zforen/mie/m...25263.html(use
> > > babelfish if you do not understand German)
> >
> > > I do integrate SP3 in my office source beforehand in the same manner I
> > > did SP2 previously, detailed here:http://unattended.msfn.org/unattended.xp/view/web/48/
> > > and both MU and OU detect it as properly installed, so other than the
> > > outlook filter hotfix, it's a "clean slate" otherwise on both
> > > websites. I've been doing this for years, never a problem.
> >
> > > On a side note, I want to point out that Microsoft Update has never
> > > properly detected slipstreamed office 2003 hotfixes (using msiexec to
> > > integrate the msp file to an admin install source) whereas Office
> > > Update always has. The only way to convince Microsoft Update is to run
> > > unattended/quiet installs of Office 2003 hotfixes in RunOnceEx of a XP
> > > unattended install (therefore consuming more time to finish), or to
> > > slipstream the office hotfixes as normal, and then export the registry
> > > of the office hotfix section of a computer updated through MU to
> > > refrain it from telling me I need to download fixes that are already
> > > properly integrated. Very annoying.- Hide quoted text -
> >
> > - Show quoted text -
>
>
>