Free Game Downloads -- Sodaware.net

Free Game Downloads -- Role Playing Games, Puzzle Games and Action Games.

14 comments

Fixing the Office 2007 error – “Document could not be registered”

As I’ve mentioned before, I’m currently running the Office 2007 beta. Recently I’ve been getting the error “The document could not be registered” every time I create a new document, change the style set and at other times.

Here’s how I fixed the problem.

As I’ve mentioned before, I’m currently running the Office 2007 beta. Recently I’ve been getting the error “The document could not be registered” every time I create a new document, change the style set and at other times.

Apparently the problem is due to the “DCOM Server Process Launcher” service not starting. I was unable to start it manually, but after setting it to start automatically I was able to repair the Office installation and get things running as normal. It also fixed a problem I was having with the MSI installer service, which had stopped me from updating Windows as well as running most installers.

Fixing the DCOM Server Process Launcher

First of all, you need to open the “Services” manager. You can do this either by selecting “run” in the start menu and typing “services.msc”, or going to “Control Panel”, then “Administrative Tools” and selecting “Services”.

You should see a window similar to the following:

Windows XP - Services Manager

Select the item named “DCOM Server Process Launcher”, right click and select “Properties”. This should bring up the following dialog:

Windows XP - Enable Services Dialog

Select “Automatic” from the “Startup type” drop down, and then select “OK”. Close the service manager, and then you’ll need to reboot.

Repairing the Office 2007 Installation

Once you’ve rebooted, you should be able to repair your Office installation. Go to the control panel, select “Add or Remove Programs” and select the entry named “Microsoft Office Professional Plus 2007 (Beta)”. Click the button called “change”, and then select “repair” from the options. This should then start the repair process. It took quite a while for me, so you might want to make a cup of tea or knit a jumper whilst you’re waiting.

Once it’s finished, it’ll ask you to reset. Once you’re reset your machine, everything should be back to normal. Phew!

Update: Jack and Mike have both found that giving the document file a shorter name can solve this problem too. Cheers!

Updated 2: Al Simon also encountered this problem, which was caused by a corrupted file. You can view his solution in the comments below.


These icons link to social bookmarking sites where readers can share and discover new web pages.

Article Info

Date: July 7, 2006

Author: Phil Newton


Categories:

Hot Game Downloads

Fatal Hearts

Fatal Hearts

Solve the mysteries behind your dreams in Fatal Hearts!


Bound Around Bound Around
A unique brick-breaking puzzle game.
Virtual Villagers Virtual Villagers
Build your own island colony!



  1. yang May 29, 2007
    1:54 am

    I am getting a similar error message from Word 2003. “This document could not be registered. It will not be possible to create links from other documents to this document. (C:\temp\myreport.doc)”

    I have checked the DCOM launcher mentioned in your article. It is started and set to Automatic.

    I wonder what can be other causes of this error.

    Any idea?

  2. Phil Newton July 15, 2007
    11:07 pm

    Hi yang,

    The DCOM server solved the problem for me, so I don’t know of any other solutions. Perhaps restarting the service would help, but I don’t really know.

    Sorry I couldn’t be more help.

  3. jack September 10, 2007
    12:04 pm

    Hi guys,
    Ran into this problem today…on serveral computers…Some say its services and other corrupted registry…

    I rename it to a shorter filename and everything was back to normal.

    Hope it helps Yang!!

  4. mike September 19, 2007
    2:18 am

    After trying the DCOM services fix (it didn’t work) I discovered the same solution. Filename was too long. I renamed it to a shorter name and it fixed the problem.

  5. Phil Newton September 19, 2007
    9:07 am

    Thanks Jack & Mike, I’ve updated the article slightly to reflect your findings. Cheers!

  6. Al Simon December 19, 2007
    8:55 pm

    I had this same problem too on a Windows 2003 server for one of my clients. I found a bunch of different “fixes” on the web.

    None of them worked. I already had all the proper services started, all the proper regkeys, I uninstalled and reinstalled Office (including removing all files and regkeys by hand), uninstalled Windows updates and fixes, reboot dozens of times … and still nothing worked. Even the filename length wasn’t the problem.

    Finally, I found the problem. The DCOM Access List for the Word executable somehow (during a Windows service update) became corrupted.

    The solution that worked for me:

    1. Choose Start > Run, enter Dcomcnfg and hit OK.

    2. Find the entry for Word under Computers > My Computer > DCOM Config.

    This entry might say “Microsoft Word Document”, “Word Document”, “Document”, or might just be the GUID for Winword.exe – in my case, it was the GUID {00020906-0000-0000-C000-000000000046}

    3. Right-click on this entry and choose Properties.

    4. Click on the Security tab

    5. Under Access Permissions, if you currently have Customized access permissions, and you still need them, click on the “Edit” button, write down all the custom ones you have set. So you can reset them after the next step.

    6. Now under Access Permissions, click “Use Default” and then the Apply Button. This will clear all the access permissions.

    7. Now click “Customize” and the Edit button. Re-enter all the customized entries you wrote down in step #5 above.

    That’s what fixed this problem for me.

    Al Simon
    http://www.virtualmarketingbiz.com

  7. Phil Newton December 21, 2007
    11:16 pm

    Thanks Al, I’ve updated the post to suggest your solution :)

  8. Mary C-L March 27, 2008
    2:15 pm

    Guys,

    I have tried ALL of these: making sure DCOM was set to Automatic (it already was) and checking default on Access Permissions (it already was). No help. What file name would have to be renamed to try that fix? Also, do the Configuration Permissions matter? Mine have been customized by people who set up my computer, but I’m the only one who uses it. Would resetting that to Default help?

    Thanks,

    Mary

  9. Al Simon April 5, 2008
    8:15 pm

    Hi Mary -

    By “configuration permissions”, do you mean the DCOM Access permissions?

    For the fix that worked for me, you *must* set it to Default and hit Apply. I would try: set them to default, hit Apply, shut down DCOMConfg, then test and see if the problem is fixed.

    If it is, great. If not, you’ll have to look elsewhere.

    After you test to see if the problem is fixed, then you can restore the original acesses permissions if you want. Whether you *should* restore them depends on too many factors to list here: whether this is a personal PC or part of a corporate environment, whether it’s a server or workstation, what other apps you run, etc.

    I hope this helps.

    Al Simon
    http://www.virtualmarketingbiz.com

  10. Mary C-L April 8, 2008
    2:00 pm

    Al, thanks, but I do have all that set up as you advise. This appears to be Glitch No. 486 I have to just live with since installing an HP All-in-One to a networked set up. The list just keeps growing…

    Thanks anyway!

    Mary

  11. Sam April 17, 2008
    12:23 pm

    Al’s solution worked for me. Strangely, there were atleast half a dozen applications whose entries were corrupt. Its working fine though. Thanks.

  12. Alex December 7, 2008
    11:07 am
  13. openen word documenten | hilpers January 18, 2009
    4:07 pm

    [...] koppelingen met dit document tot stand te brengen. >Wat te doen? Wellicht bruikbaar: http://www.sodaware.net/blog/2006/07…be-registered/ — [...]

  14. blank documents | keyongtech January 18, 2009
    5:44 pm

    [...] registered _ *_ *_ *etc. * Thanks for any help on how to correct things, * > Bill A And more: http://www.sodaware.net/blog/2006/07…be-registered/ « Word 2003 Printing Problem | Jumping Cursor While Typing [...]


Leave a comment [TrackBack URI]


Tags Allowed: a, abbr, acronym, b, blockquote, code, em, i, strike, strong

 


Browse By Date

Adventures in Shareware

Welcome to "Adventures in Shareware", the blog of an indie software business known only as "Sodaware". Learn all about indie games, the people that make them and how you can improve your own indie business.

Download Free Computer Games | Site Map | Links | Contact Us

© 2005-2007 Sodaware. All rights reserved. About Us | Privacy Policy