Re: Outlook 2003 Junk Mail Filter Update Fails

(cross-post added to Office Update)
"pvdg42" <pvdg42@newsgroups.nospam> wrote in message
news:eM64ewNaHHA.3612@TK2MSFTNGP04.phx.gbl...
>
> "Robert Aldwinckle" <robald@techemail.com> wrote in message
> news:eTLe8HFaHHA.3272@TK2MSFTNGP05.phx.gbl...

>>
>> What does the log say? If there aren't enough clues that way
>> try installing it manually using a /verbose command-line switch
>> or Run... ProcMon to supplement whatever the default log shows.
>>
> According to the message received when I try to use /verbose,
> that is not a supported option of the patch installer.


I don't have the update and didn't stop to check the details.
If the update is an msi package there is a different syntax.
From the link in the update's KB article:

http://office.microsoft.com/en-us/or...402381033.aspx

<quote>
msiexec.exe /p [path\name of update MSP file]/a [path\name of MSI file] /qb /lv* [path\name of log file]
</quote>

Generally if you don't have a command-line syntax documented most packages
will give you some clues if you add a /help or /? switch to them.
Unfortunately though sometimes diagnostic options are omitted then
even when they are available.


>
> Where would the log be? Searches for anything with "931764" don't reveal a
> log.


Various update technologies use their own peculiar procedures when creating
diagnostics. I usually use a Windows Explorer search for all files changed
during the interval that the update was running (e.g. all files changed
on a particular day and then sorted by Date Modified) in order to make sure
that I am aware of all possible diagnostics it created. Another newer alternative
is running ProcMon and looking at what it captures.

Cross-posting to Office Update in case someone who actually has installed
the update can explain what diagnostics are available.


HTH

Robert
---

1st Rename Office subkeys


Note: Removing the following registry keys may reset customized user
settings for your Microsoft Office programs.


1. Close all the applications.
2. Click on Start->Run, type in REGEDIT and click on OK.
3. Locate and select the following registry subkeys:


HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0


4. Right click on 11.0 and rename them to Old11.
5. Close the Registry Editor.


2nd. Detect and Repair Office 2003


1. On the Windows taskbar, click Start, point to and click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Change/Remove Programs on the left pane.
4. Highlight Microsoft Office Professional Edition 2003 on the right pane
and click Change.
5. Insert the correct version of CD when it requires.
6. Select "Reinstall and Repair" and click Next.
7. Select "Detect and Repair errors in my Office installation".
8. Click Install and wait the process to end.


3rd. Install the Updates




--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Robert Aldwinckle" <robald@techemail.com> wrote in message news:u1EgM5PaHHA.5044@TK2MSFTNGP05.phx.gbl...
> (cross-post added to Office Update)
> "pvdg42" <pvdg42@newsgroups.nospam> wrote in message
> news:eM64ewNaHHA.3612@TK2MSFTNGP04.phx.gbl...
>>
>> "Robert Aldwinckle" <robald@techemail.com> wrote in message
>> news:eTLe8HFaHHA.3272@TK2MSFTNGP05.phx.gbl...
>
>>>
>>> What does the log say? If there aren't enough clues that way
>>> try installing it manually using a /verbose command-line switch
>>> or Run... ProcMon to supplement whatever the default log shows.
>>>
>> According to the message received when I try to use /verbose,
>> that is not a supported option of the patch installer.
>
>
> I don't have the update and didn't stop to check the details.
> If the update is an msi package there is a different syntax.
> From the link in the update's KB article:
>
> http://office.microsoft.com/en-us/or...402381033.aspx
>
> <quote>
> msiexec.exe /p [path\name of update MSP file]/a [path\name of MSI file] /qb /lv* [path\name of log file]
> </quote>
>
> Generally if you don't have a command-line syntax documented most packages
> will give you some clues if you add a /help or /? switch to them.
> Unfortunately though sometimes diagnostic options are omitted then
> even when they are available.
>
>
>>
>> Where would the log be? Searches for anything with "931764" don't reveal a
>> log.
>
>
> Various update technologies use their own peculiar procedures when creating
> diagnostics. I usually use a Windows Explorer search for all files changed
> during the interval that the update was running (e.g. all files changed
> on a particular day and then sorted by Date Modified) in order to make sure
> that I am aware of all possible diagnostics it created. Another newer alternative
> is running ProcMon and looking at what it captures.
>
> Cross-posting to Office Update in case someone who actually has installed
> the update can explain what diagnostics are available.
>
>
> HTH
>
> Robert
> ---
>
>

"Robert Aldwinckle" <robald@techemail.com> wrote in message
news:u1EgM5PaHHA.5044@TK2MSFTNGP05.phx.gbl...
> (cross-post added to Office Update)
<snip>
> Cross-posting to Office Update in case someone who actually has
> installed
> the update can explain what diagnostics are available.
>
>
> HTH
>
> Robert
> ---
>
Yes! Thank you very much for crossposting. Peter's solution worked like a
charm.

"Peter Foldes" <okf22@hotmail.com> wrote in message
news:uqvXKOQaHHA.4520@TK2MSFTNGP06.phx.gbl...

1st Rename Office subkeys


Note: Removing the following registry keys may reset customized user
settings for your Microsoft Office programs.


1. Close all the applications.
2. Click on Start->Run, type in REGEDIT and click on OK.
3. Locate and select the following registry subkeys:


HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0


4. Right click on 11.0 and rename them to Old11.
5. Close the Registry Editor.


2nd. Detect and Repair Office 2003


1. On the Windows taskbar, click Start, point to and click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Change/Remove Programs on the left pane.
4. Highlight Microsoft Office Professional Edition 2003 on the right pane
and click Change.
5. Insert the correct version of CD when it requires.
6. Select "Reinstall and Repair" and click Next.
7. Select "Detect and Repair errors in my Office installation".
8. Click Install and wait the process to end.


3rd. Install the Updates

Thanks very much, Peter! It did the job for me.

YW. Thanks for posting back and letting us know

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"pvdg42" <pvdg42@newsgroups.nospam> wrote in message news:%231JcRtXaHHA.1508@TK2MSFTNGP06.phx.gbl...
>
> "Robert Aldwinckle" <robald@techemail.com> wrote in message
> news:u1EgM5PaHHA.5044@TK2MSFTNGP05.phx.gbl...
>> (cross-post added to Office Update)
> <snip>
>> Cross-posting to Office Update in case someone who actually has
>> installed
>> the update can explain what diagnostics are available.
>>
>>
>> HTH
>>
>> Robert
>> ---
>>
> Yes! Thank you very much for crossposting. Peter's solution worked like a
> charm.
>
>

Thanks Peter! It's very Helpful... I still have a question. Is it okay to
delete Old11 after finish installation.

Thanks again,
Eak!

"Peter Foldes" wrote:

>
> 1st Rename Office subkeys
>
>
> Note: Removing the following registry keys may reset customized user
> settings for your Microsoft Office programs.
>
>
> 1. Close all the applications.
> 2. Click on Start->Run, type in REGEDIT and click on OK.
> 3. Locate and select the following registry subkeys:
>
>
> HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
> HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0
>
>
> 4. Right click on 11.0 and rename them to Old11.
> 5. Close the Registry Editor.
>
>
> 2nd. Detect and Repair Office 2003
>
>
> 1. On the Windows taskbar, click Start, point to and click Control Panel.
> 2. Double-click Add/Remove Programs.
> 3. Click Change/Remove Programs on the left pane.
> 4. Highlight Microsoft Office Professional Edition 2003 on the right pane
> and click Change.
> 5. Insert the correct version of CD when it requires.
> 6. Select "Reinstall and Repair" and click Next.
> 7. Select "Detect and Repair errors in my Office installation".
> 8. Click Install and wait the process to end.
>
>
> 3rd. Install the Updates
>
>
>
>
> --
> Peter
>
> Please Reply to Newsgroup for the benefit of others
> Requests for assistance by email can not and will not be acknowledged.
>
> "Robert Aldwinckle" <robald@techemail.com> wrote in message news:u1EgM5PaHHA.5044@TK2MSFTNGP05.phx.gbl...
> > (cross-post added to Office Update)
> > "pvdg42" <pvdg42@newsgroups.nospam> wrote in message
> > news:eM64ewNaHHA.3612@TK2MSFTNGP04.phx.gbl...
> >>
> >> "Robert Aldwinckle" <robald@techemail.com> wrote in message
> >> news:eTLe8HFaHHA.3272@TK2MSFTNGP05.phx.gbl...
> >
> >>>
> >>> What does the log say? If there aren't enough clues that way
> >>> try installing it manually using a /verbose command-line switch
> >>> or Run... ProcMon to supplement whatever the default log shows.
> >>>
> >> According to the message received when I try to use /verbose,
> >> that is not a supported option of the patch installer.
> >
> >
> > I don't have the update and didn't stop to check the details.
> > If the update is an msi package there is a different syntax.
> > From the link in the update's KB article:
> >
> > http://office.microsoft.com/en-us/or...402381033.aspx
> >
> > <quote>
> > msiexec.exe /p [path\name of update MSP file]/a [path\name of MSI file] /qb /lv* [path\name of log file]
> > </quote>
> >
> > Generally if you don't have a command-line syntax documented most packages
> > will give you some clues if you add a /help or /? switch to them.
> > Unfortunately though sometimes diagnostic options are omitted then
> > even when they are available.
> >
> >
> >>
> >> Where would the log be? Searches for anything with "931764" don't reveal a
> >> log.
> >
> >
> > Various update technologies use their own peculiar procedures when creating
> > diagnostics. I usually use a Windows Explorer search for all files changed
> > during the interval that the update was running (e.g. all files changed
> > on a particular day and then sorted by Date Modified) in order to make sure
> > that I am aware of all possible diagnostics it created. Another newer alternative
> > is running ProcMon and looking at what it captures.
> >
> > Cross-posting to Office Update in case someone who actually has installed
> > the update can explain what diagnostics are available.
> >
> >
> > HTH
> >
> > Robert
> > ---
> >
> >
>

Yes. Go ahead and go for it. :)

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

<Eak! <chwtp@thaigov.go.th> wrote in message news:72230EBE-4944-41E5-AB10-797F7CF14916@microsoft.com...
> Thanks Peter! It's very Helpful... I still have a question. Is it okay to
> delete Old11 after finish installation.
>
> Thanks again,
> Eak!
>

I am not an expert so it might be that Peter's solution does the same thing
as what I am about to write.

When atttempting to install the office update for the junk mail filter
(March 2007?) I kept getting a message "Installation failed".

I had used a registry cleaner the month before attempting to fix another
problem with Media player which was not working properly.

What worked for me is a solution found in article 884298. It involves going
into the registry, and adding a key so that the operating system knows the
original source of the Office software installation. For me, I simply added
"path=d:\" (my cd drive) and miraculously, the office update then worked.

I hope this helps somebody...

"Peter Foldes" wrote:

> YW. Thanks for posting back and letting us know
>
> --
> Peter
>
> Please Reply to Newsgroup for the benefit of others
> Requests for assistance by email can not and will not be acknowledged.
>
> "pvdg42" <pvdg42@newsgroups.nospam> wrote in message news:%231JcRtXaHHA.1508@TK2MSFTNGP06.phx.gbl...
> >
> > "Robert Aldwinckle" <robald@techemail.com> wrote in message
> > news:u1EgM5PaHHA.5044@TK2MSFTNGP05.phx.gbl...
> >> (cross-post added to Office Update)
> > <snip>
> >> Cross-posting to Office Update in case someone who actually has
> >> installed
> >> the update can explain what diagnostics are available.
> >>
> >>
> >> HTH
> >>
> >> Robert
> >> ---
> >>
> > Yes! Thank you very much for crossposting. Peter's solution worked like a
> > charm.
> >
> >
>