Prev: code error 80072EFE
Next: windows movie maker
From: Tomas Nugis Stockholm Sweden Tomas Nugis Stockholm on 14 Mar 2010 07:31

2010-03-14 from Tomas Nugis Stockholm Sweden
Failed updates Excel 2003 kb978474
Discovered friday Mars 11 2009. I try to update

Hello. I have the same problem. I can"t update this file. kb 978474
It says.Failed. Code 779 = UNKNOWN wrong ?

Facts: I use Vista Business. Office Standard Edition 2003. (An OLDER version)
Note:The Office 2003 is before the time of Vista. It should NOT impact
but I dont know for sure ? Only Microsoft can answere.Office 2003 is made
for XP
but it has worked out on my Vista since july 2009. All updates are OK since
then.
All of the ohters updates did function. But not kb 978474 ? Why ?

Reflexion: The Office excel is from 2003. Maybe ( I don"t have FACTS )
it causes a CONFLICT in one or another way ? Only Microsoft can tell.
Maybe we should use a Office from 2007 ? My belive (only belive) not facts,
is that Office 2003 should work out. All of the other uppdatesmhas worked
out. Security MS10-017.So my belive is that Office 2003 should work out.

At friday mars 11-2009 I contacted Microsoft free support about updates,
to try to get some information about this update kb 978474. Whats wrong ?
I"ve been searching all over the internet and Microsoft.
Maybee ohters have the same problem ? Or is it " unique " for a few Vista pc ?
I don"t know .Only Microsoft can tell. I"m waiting for reply/ anweres.
Normally this update kb 978474 should work out.
It"s a " mystery " ?

Information:When I googled with: Fail update Microsoft excel 2003 kb 978474
I found this information and your question Mr Bandicot.

And the answeres from Mr PA Bear MS MVP.
All his information is very good. I "ve used it.
This is the only way we can try to solve the problem.
I do hope that Microsoft support can help us ?

It feels good that I"m not the only one that has this problem

Best regards from Stockholm Sweden
Tomas Nugis


"bandicoot" wrote:

> Hi,
>
> Does anybody have any idea why the recent update from MS for Excel
> (KB978474) would not update and what can I do to get this update through?
>
> I keep getting the below message and not much of any description what I
> could do.
> The problem is that:
> 1. After failure, the Windows Update does not stop (unless I turn it off
> manually) and still tries to install this update
> 2. After each update Excel is somehow corrupted or uninstalled. After
> attempt to start it, it reinstalls and than runs seemingly OK.
>
> I seem to be unable to break this vicious circle.
> I tried to reinstall Excel 2003 but this did not change a thing.
> I also tried to install Excel 2007 on this PC to replace Excel 2003 but this
> did not stop attempts to update the Excel 2003 either!!!
> So I uninstalled Excel 2007 and re-installed Excel 2003.
> Still same thing. It tries to update it, but it fails. And Excel after that
> must be reinstalled (does not take a lot of time but it is just wrong).
>
> Interesting thing is that other updates in this recent batch from MS went
> through OK (I think there were tow more).
>
> On my other PC all of these updates went OK.
> But I cannot find any difference in how it is installed on both computers. I
> would swear it is identical installation, but obviously I must be wrong.
> Something is different.
>
> Would anyone have an idea what that could be?
>
>
> +++++++++++
> Failed Updates
>
> For help installing an update successfully, see the solution under each
> problem description.
>
> Problem: Please check your update history for a description.
>
> Microsoft Office 2003
> Security Update for Microsoft Office Excel 2003 (KB978474)
>
> ++++++++++++
>
> ..and under description page I can only see the Failed Status for update
> with no description of the problem.
> --
>
> hooroo
>
From: Robert Aldwinckle on 14 Mar 2010 11:55


"Tomas Nugis Stockholm Sweden" <Tomas Nugis Stockholm
Sweden(a)discussions.microsoft.com> wrote in message
news:0FBB2698-EBC7-49F3-92D1-DFE35978861B(a)microsoft.com...
>
> 2010-03-14 from Tomas Nugis Stockholm Sweden
> Failed updates Excel 2003 kb978474
> Discovered friday Mars 11 2009. I try to update
>
> Hello. I have the same problem. I can"t update this file. kb 978474
> It says.Failed. Code 779 = UNKNOWN wrong ?


Not if you are giving us a hex value...

<cmd_output OS="W7">
C:\>set /a c = 0x779
1913
C:\>net helpmsg %c%

Some data remains to be sent in the request buffer.
</cmd_output>

But more important than the code's value is its context. Where are you
seeing this? Can you find either the 779 you are reporting or 1913 (that
string's decimal equivalent if the code you are reporting is a hex value) in
any log files the install creates or changes? And if you are not getting
good diagnostics from running an update automatically, try downloading it
and installing it manually. You may find that you have additional options
for increasing the diagnostics (e.g. adding /verbose to the command line if
that is available) and in any case could supplement any and all diagnostics
that you are getting by running ProcMon when you do the install attempt.


HTH

Robert Aldwinckle
---

From: Tomas Nugis Stockholm Sweden on 17 Mar 2010 16:20


"Robert Aldwinckle" wrote:

>
>
> "Tomas Nugis Stockholm Sweden" <Tomas Nugis Stockholm
> Sweden(a)discussions.microsoft.com> wrote in message
> news:0FBB2698-EBC7-49F3-92D1-DFE35978861B(a)microsoft.com...
> >
> > 2010-03-14 from Tomas Nugis Stockholm Sweden
> > Failed updates Excel 2003 kb978474
> > Discovered friday Mars 11 2009. I try to update
> >
> > Hello. I have the same problem. I can"t update this file. kb 978474
> > It says.Failed. Code 779 = UNKNOWN wrong ?
>
>
> Not if you are giving us a hex value...
>
> <cmd_output OS="W7">
> C:\>set /a c = 0x779
> 1913
> C:\>net helpmsg %c%
>
> Some data remains to be sent in the request buffer.
> </cmd_output>
>
> But more important than the code's value is its context. Where are you
> seeing this? Can you find either the 779 you are reporting or 1913 (that
> string's decimal equivalent if the code you are reporting is a hex value) in
> any log files the install creates or changes? And if you are not getting
> good diagnostics from running an update automatically, try downloading it
> and installing it manually. You may find that you have additional options
> for increasing the diagnostics (e.g. adding /verbose to the command line if
> that is available) and in any case could supplement any and all diagnostics
> that you are getting by running ProcMon when you do the install attempt.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
> .
>
 | 
Pages: 1
Prev: code error 80072EFE
Next: windows movie maker