I encountered a Microsoft Word error when opening every Word document. When I
open any Word document, Word will display a message saying:

This document could not be registered. It will not be possible to create
links from other documents to this document. (C:\MyReport.doc)

Repair and re-install do not work
I have tried repairing as well as re-installing Microsoft Office to resolve
this issue. No luck there.

Solutions found on Google do not work
I have also tried the solutions I managed to find on Google about the issue.

Apparently, some people have encountered the same error as I did.
Unfortunately, their solutions cannot solve my problem.

One solution I found (in several different sites) suggests setting certain
services (e.g. DCOM Server Process Launcher) startup type to "Automatic", and
ensuring that these services are running.

An example of a solution along this line can be found at:
http://techrepublic.com.com/5208-623...geID=21072 90


In my case, the several services mentioned in those suggested solutions have
all been set to "Automatic" startup type and are running. So this is not
where the problem lies.

Could someone enlighten me on this issue?

Thank you!

Are you using Norton Anti Virus? If so, disable the Office Plug-in option in
NAV under Preferences, Advanced.

I am having the same problem as well. I have checked the DCOM Server
Launcher Service, which has been a headache also....not finding the right
answer to its problem either....of wanting to reboot my computer. I've been
able to stop that, but still haven't found the right fix from anyone
yet...going through every suggestion offered.
I am not using Norton, finding it was a pain in the rear...using AVG now.
I do not have any installation CDs. All my software ( XP Home Edition) was
on PC, D: drive, when I bought it.


"Terry Farrell" wrote:
[..]

I am not using Norton Anti Virus. I am using Trend Micro OfficeScan.

This is not the cause of the issue, as all the PCs in this office run Trend
Micro OfficeScan, and the only PC that gets this Word error is the one giving
me trouble here.

Some thing must have changed when some system or software maintenance was
carried out.



"Terry Farrell" wrote:
[..]

Try reregistering Word. From Start, Run type in

winword /r

and press enter. Does that sort it?

Terry

"youngloc" <youngloc> wrote in message
news:35a7
[..]

No, followed your advice and ran "winword /r". It did not work.


For the information of other readers:

Running "winword /r" in Windows command line "Starts Word, starts Setup,
makes changes in the Windows registry, and then quits. This switch forces a
re-register of Word in the Windows registry."

See:

http://support.microsoft.com/kb/210565



"Terry Farrell" wrote:
[..]

What happens if you start in Safe Mode, From Start, Run, type in

winword /a

and press enter. Are you able to open documents correctly now?

Terry

"youngloc" <youngloc> wrote in message
news:7c2f
[..]

Starting Word in Safe Mode using the command line "winword /a" does not solve
the problem. The same error message still appears.

If Microsoft Office has been repaired and re-installed, can it be that the
problem does not lie with Word at all? Can it be that some service or some
registry stuff Word relies on is not working correctly?



"Terry Farrell" wrote:
[..]

I am wondering if this is some weird profile problem. Have you tried logging
in to the problem PC using a login for someone that works OK from another
PC?

Terry

"youngloc" <youngloc> wrote in message
news:7640
[..]

I tried your suggestion. Got someone else to log into this server that is
having the issue.

He also got the same error.

What else can I try - short of re-installing the server OS and all software
(which is going to take days)?


Thank you for your time!

Really appreciate it.



"Terry Farrell" wrote:
[..]

Are you saying this is not a PC but a server? What OS is running?

Terry

"youngloc" <youngloc> wrote in message
news:4502
[..]

Sorry, I didn't make this clear upfront.

The server is running Windows Server 2003 Enterprise Edition, Service Pack 1.


"Terry Farrell" wrote:
[..]

Sorry, I didn't realise either. So virtually everything I have told you to
try is probably irrelevant. I'd suggest checking this on an appropriate
server NG as this may be a server setup related problem.

Terry

"youngloc" <youngloc> wrote in message
news:75a5
[..]

Got my System Admin guy to do a repair on Windows Server 2003 in the
problematic system (ran installer CD, picked Repair option).

Problem solved!

Good news. Thanks for letting us know.

Terry

"youngloc" <youngloc> wrote in message
news:cbb8
[..]