Portucal <> wrote:
> All 7 Office 2003 error codes are
> the same 0x80070643. The Windows XP .net framework error code is
> 0x643.
Code 643 is just a generic installer failure. The reasons are different in
each case. For the Office 2003 updates do this:
==== begin
First, try disabling any third-party anti-virus, anti-malware (e.g.
SpySweeper), anti-BHO, firewall, or download accelerator application.
(Enable Windows Firewall if you disabled a third-party fireall). Then try
the updates again.
If that doesn't work, then it seems likely that your Office 2003
installation is damaged. Have you at any time recently used a so-called
"Registry Cleaner"? If so, it is possible that your registry is now damaged
in respect of the Office 2003 entries.
For instance, the Windows Live Safety Center registry scan might cause these
problems.
If this case applies to you, you should back your system up to a time before
you used the registry cleaner.
To restore from the backup made by the Windows Live Safety Center, do the
following:
1. Use control panel "Folder Options", tab "View", to enable "Show hidden
files
and folders", and un-check "Hide extensions for known file types".
2. Close all Internet Explorer windows.
3. Use Windows Explorer to navigate to folder:
C:\Documents and Settings\<user>\Application Data\Windows Live Safety
Center\BackUp\
and double-click the .reg file previously created by the Microsoft Safety
registry cleanup.
Please report back whether this fixes your problem.
If the above does not work, you can try:
1. In any Office 2003 application, pull down Help, and select "Detect and
Repair" (it might require the Office installation CD-ROM).
2. Uninstall Office 2003 completely, and re-install, then apply the latest
Office 2003 Service Pack and all pending Office 2003 updates.
In addition, this might be relevant:
http://support.microsoft.com/kb/884298
==== end
For the .NET Framework problem, it is important to know what the update
number was and/or whether it related to .NET Framework 1.1 or .NET Framework
2.0. Assuming the latter 2.0, then do this:
==== begin
This fix will not install on top of beta versions of .NET Framework 2.0. It
will normally only install on the true release. So much depends on how your
PC first acquired its copy of .NET Framework 2.0. If you happen to know,
please let us know.
The following is a revised version of an earlier post by TKang:
Note:
a. Some ATI VGA users may need to disable/exit the Catalyst Control Center
(which uses .NET) before updating the framework.
b. Users of Windows Live OneCare must disable that application before
removing or updating the Framework.
1: Turn automatic updates off.
2: Download .NET 2.0 (for 32-Bit) at this link:
http://www.microsoft.com/downloads/d...displaylang=en
OR
2a: Download .NET 2.0 (for 64-Bit) at this link:
http://www.microsoft.com/downloads/d...displaylang=en
3: Use control panel Add/Remove Programs to uninstall Microsoft .NET
Framework, Version 2.0 and reboot. Do not touch .NET Framework 1.1.
3a: see note below at step 7.
4: Install Microsoft .NET Framework, Version 2.0 (for 32-bit: dotnetfx.exe
3/22/2006) or (for 64-bit: NetFx64.exe 3/30/2006) and reboot.
5: Then run MS Update (and install KB917283) then reboot.
6: Turn automatic updates on (assuming that is your preference).
7. If this procedure failed to allow update 917283 to work, then repeat the
procedure, adding the following at step 3a:
Download
http://astebner.sts.winisp.net/Tools...eanup_tool.zip and
unzip it. Run the enclosed application, and select to clean up .NET
Framework 2.0. Now continue above from step 4.
==== end
--
Robin Walker [MVP Networking]