MS Office 2003 - Updates: Err during attempted update (KB936507)

[Jim]

I have MS Office 2003 Professional installed on Windows Vista Business x64
and all was well up to this point.

During a routine MS update scan and install operation, the install failed
for the Excel 2003 product. The failure is apparently error:
WindowsUpdate_00000779 WindowsUpdate_dt000.

The error is reported at time of update as: Code 779. The link called "Get
Help" is no help.

Examination of the version for Excel.exe indicates: v11.0.8134.0.

Further research found reference to file MAPISVC.INF, indicating that this
file may need full rights for the Administrator. Examination of the
properties for this file found that Administrator group only had read
ability. Attempts to change to FULL ability have failed.

I don't know if this is, in fact the problem, but so far thats the only
information I've found.

Has anyone else encountered this issue, and if so, how was it resolved?
(FYI: Installing profile = member of Administrators group. Only group that
appears to have FULL authority to this file is: TrustedInstaller. Attempts
to join this group have failed as it does not appear in the list of valid
group ids or user ids. Attempts to add this group to the list, then join the
group also fail.)

Thank you for your help.

 

[Jim]

Well, I think I solved my own problem - and wanted to share with the rest.

The issue was in fact an authority issue with MAPISVC.INF. While the
"issue" probably isn't an issue during normal, secured use of Windows Vista
Business x64, there was the need to "work-around" the ability to post the
update.

Specifically:
1) My profile took "ownership" of the file.
2) Once ownership was set, then, rights to the Administrator group was
granted to "full".
3) After granting the full rights to administrator, the profile also
retained full rights.
4) Executed the security update (KB936507) to the Excel application of MS
Office 2003 professional.

While I applaud Microsoft's commitment to security, and I am very glad that
through this effort, viruses are slowed or rendered ineffective against the
operating system key files, this type of security issue should not be
occuring from Microsoft.

Of course, as vast as Microsoft is, it is difficult at times to ensure that
all the pieces "fit" together 100% of the time. This specific error does
appear to be somewhat of a rudementery type error though - and at the basic
core of how MS deployes updates/corrections.

Oh well - there it is, and the only way I was able to "workaround" the issue.

- Jim

 

[Naomi]

Thanks Jim,
I had exactly the same problem on Vista Ultimate whilst trying to update to
Office 2003 SP3. Your solution worked. Its been a fustrating process trying
to find the error and i agree with you that it shouldn't be happening.

Thanks

 

[Ricardo]

Very good Jim!
Thanks a lot!

Well, I think I solved my own problem - and wanted to share with the rest.

The issue was in fact an authority issue with MAPISVC.INF. While the
"issue" probably isn't an issue during normal, secured use of Windows Vista
Business x64, there was the need to "work-around" the ability to post the
update.

Specifically:
1) My profile took "ownership" of the file.
2) Once ownership was set, then, rights to the Administrator group was
granted to "full".
3) After granting the full rights to administrator, the profile also
retained full rights.
4) Executed the security update (KB936507) to the Excel application of MS
Office 2003 professional.

While I applaud Microsoft's commitment to security, and I am very glad that
through this effort, viruses are slowed or rendered ineffective against the
operating system key files, this type of security issue should not be
occuring from Microsoft.

Of course, as vast as Microsoft is, it is difficult at times to ensure that
all the pieces "fit" together 100% of the time. This specific error does
appear to be somewhat of a rudementery type error though - and at the basic
core of how MS deployes updates/corrections.

Oh well - there it is, and the only way I was able to "workaround" the issue.

- Jim