Re: Office 2003 Professional after installing Win XP SP2 - problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Smokie (Smokie_at_discussions.microsoft.com)
Date: 10/03/04


Date: Sun, 3 Oct 2004 07:33:04 -0700

I have found the probelm.

The problem is not with Office itself - but rather a service that needs to
be running. The service is DCOM (DCOM Server Process Launcher).

Before SP2, many people regarded DCOM as a security risk - and no real need
for it to be running. So, DCOM on my machines was safely turned off. Upon
installing SP2 -- this was needed to be switched ON but remained OFF. This
was the cause of my problems (and I take back what I said about MS not
testing for things like this ;)).

Now in SP2, Microsoft have fixed any related vulnerabilties or weaknesess
(we hope) with DCOM and it seems also that DCOM is now being used.

Office 2003 PRO obviously needs it, and so do a few other third-party
programs including Notron Antivirus 2004 and their LiveUpdate application.

All-in-all, I must say SP2 is a pretty good service pack. Once enabling DCOM
here, I've had no problems at all. I don't like the Security Center though
and there are (regardless of Microsoft's view) vulnerablilites in SC. And
"improvements" in IE don't bother me because I don't use IE.

Thanks for the replies all -- take care.

"User" wrote:

>
>
>
> I had the same problem, reinstall SP2, that will take care of it.
>
>
> On Sat, 11 Sep 2004 06:51:02 -0700, Smokie
> <Smokie@discussions.microsoft.com> wrote:
>
> >Hi
> >
> >After installing XP's SP2, Office 2003 Pro comes up with a few problems.
> >First, Word pops up with a "!" message, of the following:
> >
> >"This document could not be registered. It will not be possible to create
> >links from this document to other documents."
> >
> >This pops up immediately after openning Word. Even a blank document or a
> >previously saved document.
> >
> >Secondly, Office Assistant no longer works. We get the following "!" message:
> >
> >"The Office Assistant could not be started. The assistant might not have
> >been disabled properly, there might be problems with your office setup, or
> >your computer might be low on memory".
> >
> >We have two Windows XP Home machines, and the problem started on both ONLY
> >after updating to Windows' Service Pack 2. One machine has been reverted back
> >to SP1 and once again, everything with Office is fine. The other, remaining
> >with SP2 is not. The SAME problems were encountered on BOTH machines after
> >SP2, although on the second machine the Office Assistant message was stating
> >that something needed to be installed, but I forget what that was now as I've
> >reverted it back to SP1.
> >
> >Has anyone else had this problem with Office 2003 after updating to XP's
> >SP2? If so is there a fix? Why does this happen with Office, don't they test
> >for things like this!?
>
>



Relevant Pages

  • Re: Office 2003 Professional after installing Win XP SP2 - problem
    ... I have found the cause of the problem on both machines here. ... Launcher) to be a security risk if left at its default state of constantly ... As this was my fault (took a while to realise it was DCOM) I take back what ... All-in-all SP2 is a decent service pack. ...
    (microsoft.public.office.misc)
  • Re: WinXP SP2 and ActiveSync
    ... I installed from a WinXP CD with SP2 ... Open Outlook, and then whatever sync'ing software, i.e. ActiveSync, ... Turned on/off the security center. ... If I use the hive clean up tool, it blames DCOM. ...
    (microsoft.public.pocketpc.activesync)
  • Re: XP sp2 blues
    ... implementation of the DCOM service. ... available in sp2. ... >> and the laptop is again a happy member of it's Windows ... >install SP2 successfully and how to troubleshoot if there ...
    (microsoft.public.windowsxp.general)
  • Cant configure anonymous DCOM with XPSP2(RC1) => 0x800706F7 (stub received bad data)
    ... thank you for your hint, ... >> unauthenticated DCOM like before SP2. ... >> After installing SP2 we didn't manage to configure our machines to allow ...
    (microsoft.public.platformsdk.security)
  • Cant configure anonymous DCOM with XPSP2(RC1) => 0x800706F7 (stub received bad data)
    ... thank you for your hint, ... >> unauthenticated DCOM like before SP2. ... >> After installing SP2 we didn't manage to configure our machines to allow ...
    (microsoft.public.windowsxp.security_admin)