Error 0x80070643

I have been trying to update but keep recieving the error 0x80070643 what
should I do?

You receive an "Error 80070643" error message when you try to update Office 2003 by using Software
Update Services
http://support.microsoft.com/?id=903772

and/or

You cannot install some updates or programs
http://support.microsoft.com/default...b;EN-US;822798

Also see if you are trying to update Office 2003

Office 2003 Update fails to install with error 0x80070643
http://update.microsoft.com/windowsu...=en&IsMu=False
You receive error 0x80070643 when you are installing Office 2003 Updates. Updates fail to install
because ose service is disabled or cannot be started. Applicable Office versions: Office 2003

This happens frequently for me when installing updates and the following fix
corrects the problem.

I reset the OSE to "manual". However, at some point, it must get turnedback
to "disabled", because next update, I have to reset it.

Is this normal, or is this something I should be concerned about? If there
is something changing the status of the OSE service, could that harm my
system (either directly or indirectly)? If something setis it back to
"disabled", would that allow a back-door into my system? What is the best
setting for OSE for my protection?

Have you checked for spyware/malware/viruses lately?

Yep! Running MS Anti-Spyware which checks nightly and McAfee (for viruses)
which checks every other night. I *occasionally* run Spybot & AdAware (maybe
monthly) in case MS Anti-Spyware misses anything.

That was my first thought, too. But, since all scans come up good, it led
me to believe that it was some obscure Windows or Office setting that keeps
re-setting the OSE to disabled.

In my case I cleared this error by deleting Local Install Source (LIS). For
information on LIS and the tool needed to alter LIS refer to the article in
the link below. It will explain MSOCACHE, a cache of installation files that
should limit how often you need the original installation source (eg. Office
updates etc). It seems for MSOCACHE to retain in integrity the original
installation 'physical' source needs to exist, eg. perhaps external CD drive
was used to install and is no longer connected etc. However I just deleted
LIS which then allowed me to install Office 2003 SP2 and other Office updates
that were failing with the same error. This may explain why some people have
had success uninstalling/re-installing as MSOCACHE would be regen'ed by this
process.

Hope this helps.

http://support.microsoft.com/default...-us;830168#top

Thank you, thank you , thank you. I've had this same issue for months and
have tried the standard Microsoft fixes to no avail. Deleting the LIS is the
*only* thing that cleared this error. You my friend have made me a very
happy man. I wish there was a way to make this fix show up higher in the
list of messages (hint, hint to any Microsoft people that happen to read
this).

I also get this error, but only when updating the MS Outloook 2003 Filter.
This did not occur in past updates of security updates of Outlook 2003.

The Oulook 2003 update isconstantly displayed in the Windows Security
Center, and at each boot I have a warning for acritical update that can't be
installed.
My PC runs an antivirus which is also up to date (automatically updated each
day), and performs nightly checks against virus and spywares.

It is running Windows XP SP2 (French, retail version preinstalled on an Acer
notebook,configuredwith automatic updates, Office 2003 French version, was a
retail version bought separately). It also has successfully installed all the
past recommanded and optional updates for Windows and Office 2003.

There's also the latest IE7 Beta2 installed.

Note: OSE is already runningat at boot, and all other Office 2003
applications were updated correctly, including other updates for Outlook
2003. So I don't know what the Outlook email filter is trying to look for.

The only thing that is not running and which has been disabled is Windows
Messenger (and I did not want it: does Outlook 2003 needs it running for the
Email filter to be applied? Note that Outlook Express runsperfectly without
even needing Windows Messenger; I have no other thid-party messenger
application installed or running).

My antivirus is AVG. disabling it before applying the update still does not
allow this Outlook 2003 antispam email filter update to run successfully.
(Well in fact I don't use Outlook for emails on the Internet, I prefer
Outlook Express; outlook isonly when my notebook is connected at work to
connect to internal mail server of the company where I work and manage the
work schedules and is never used for Internet emails).

Outlook 2003 is running perfectly without this email filter update.

Against spam from the Internet, I have an external antispam running at my
ISP (but then I don't use Outlook2003). But may be there could be spam in my
professional mailbox when I connect to it at work (all external emails from
the Internet at work pass through the private Exchange server that runs the
antispam filter and it is itself feeded from the outside from an intermediate
SMTP/POP3 server on Linux running its own antivirus and antispyware, so
there's a double protection at work.

somay be Ishould disable this update. But I fear that without the update
applied, it willbe blocking other security fixes in Outlook 2003 or other
Office applications.

Note: on my case, if I run "sc qc ose", I get:

[SC] GetServiceConfig SUCCESS
SERVICE_NAME: ose
TYPE : 10 WIN32_OWN_PROCESS
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : "C:\Program Files\Fichiers communs\Microsoft
Shared\Source Engine\OSE.EXE"
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : Office Source Engine
DEPENDENCIES :
SERVICE_START_NAME : LocalSystem
So it is really running on demand and in manual mode

Anyway, the Outlook 2003 junk email filter is still not working and
returning this error, without more details about its cause (I did not find
anything logged about it, or I don't know where to look for)

Have you recently run a so-called "registry cleaner", such as the one at the
Windows Live Safety Centre?

If so, your registry might be damaged. You should restore the registry from
the back-up created by the registry cleaner. Then try the Office 2003
update again.

Is that the ListTools? I tried running it and got Error 0x80070002 instead!

Ditto - my MSOCache got corrupted after a crash and ListTool was the ONLY
thing that took care of it! Why isn't this among the TOP recommendations
when you get the 0x80070643 error? I've wasted so much time on this!

LISTool.exe fails with error message "The Local Installation Source Tool has
encountered an error: 0x80070002 ...."

Brilliant! Like everyone else (so it seems) this bedeviled me for a long
time. Presto -- deleting the LIS worked. Thanks a million.

I have the same problem (error: 0x8007002) after downloading the LISTool.exe.
Any advice / help will be much appreciated.

Robin I agree with you that it may be a damaged registry file.
I saw on another forum (Sorry I can not find the link again) that a guy who
had the same problem cured the problem.
The problem being the failure of all office 2003 updates with a 0x80070643
exit code.
He was using a Registry Cleaner called RegCure and when he restored his
registry back to before the first time he ran RegCure, everything was fine.
I use RegCure and I have looked at when I started to have this 0x80070643
problem and low and behold, the problem occurred
on the first office update after I ran RegCure.
This to me point to the fact that these updates arw failing due to a
currpt/missing registry entry.
Is there an easy way to check the registry for corrupt/missing entries
required for office 2003 updates?
Please note that I have posted this to several threads to make sure everyone
is aware of this potential issue.
Please note that I am not dissing RegCure, I am merely trying to shed some
light on this annoying issue.

Thanks for this information. I have been fiddling around with this for the
last three months and it works without me uninstalling/installing my Office
Product.

I have only Frontpage 2003 installed and Service Pack 2 installation for
Studio 2003 failed.
In my case I had to enable LIS by using LISTool.exe