<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Fixing the Office 2007 error - &#8220;Document could not be registered&#8221;</title>
	<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/</link>
	<description>Adventures in shareware.</description>
	<pubDate>Sat, 06 Sep 2008 00:52:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Sam</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-67598</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Thu, 17 Apr 2008 11:23:12 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-67598</guid>
		<description>Al's solution worked for me. Strangely, there were atleast half a dozen applications whose entries were corrupt. Its working fine though. Thanks.</description>
		<content:encoded><![CDATA[<p>Al&#8217;s solution worked for me. Strangely, there were atleast half a dozen applications whose entries were corrupt. Its working fine though. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary C-L</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-66709</link>
		<dc:creator>Mary C-L</dc:creator>
		<pubDate>Tue, 08 Apr 2008 13:00:09 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-66709</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>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&#8230;</p>
<p>Thanks anyway!</p>
<p>Mary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al Simon</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-66497</link>
		<dc:creator>Al Simon</dc:creator>
		<pubDate>Sat, 05 Apr 2008 19:15:45 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-66497</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Hi Mary -</p>
<p>By &#8220;configuration permissions&#8221;, do you mean the DCOM Access permissions?</p>
<p>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.</p>
<p>If it is, great. If not, you&#8217;ll have to look elsewhere.</p>
<p>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&#8217;s a server or workstation, what other apps you run, etc.</p>
<p>I hope this helps.</p>
<p>Al Simon<br />
<a href="http://www.virtualmarketingbiz.com" >http://www.virtualmarketingbiz.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary C-L</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-65538</link>
		<dc:creator>Mary C-L</dc:creator>
		<pubDate>Thu, 27 Mar 2008 13:15:28 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-65538</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Guys,</p>
<p>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&#8217;m the only one who uses it. Would resetting that to Default help?</p>
<p>Thanks,</p>
<p>Mary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Newton</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-53445</link>
		<dc:creator>Phil Newton</dc:creator>
		<pubDate>Fri, 21 Dec 2007 22:16:17 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-53445</guid>
		<description>Thanks Al, I've updated the post to suggest your solution :)</description>
		<content:encoded><![CDATA[<p>Thanks Al, I&#8217;ve updated the post to suggest your solution :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al Simon</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-53050</link>
		<dc:creator>Al Simon</dc:creator>
		<pubDate>Wed, 19 Dec 2007 19:55:58 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-53050</guid>
		<description>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 &#62; Run, enter Dcomcnfg and hit OK.

2. Find the entry for Word under Computers &#62; My Computer &#62; 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
www.virtualmarketingbiz.com</description>
		<content:encoded><![CDATA[<p>I had this same problem too on a Windows 2003 server for one of my clients. I found a bunch of different &#8220;fixes&#8221; on the web. </p>
<p>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 &#8230; and still nothing worked. Even the filename length wasn&#8217;t the problem.</p>
<p>Finally, I found the problem. The DCOM Access List for the Word executable somehow (during a Windows service update) became corrupted.</p>
<p>The solution that worked for me:</p>
<p>1. Choose Start &gt; Run, enter Dcomcnfg and hit OK.</p>
<p>2. Find the entry for Word under Computers &gt; My Computer &gt; DCOM Config.</p>
<p>This entry might say &#8220;Microsoft Word Document&#8221;, &#8220;Word Document&#8221;, &#8220;Document&#8221;, or might just be the GUID for Winword.exe - in my case, it was the GUID {00020906-0000-0000-C000-000000000046}</p>
<p>3. Right-click on this entry and choose Properties.</p>
<p>4. Click on the Security tab</p>
<p>5. Under Access Permissions, if you currently have Customized access permissions, and you still need them, click on the &#8220;Edit&#8221; button, write down all the custom ones you have set. So you can reset them after the next step.</p>
<p>6. Now under Access Permissions, click &#8220;Use Default&#8221; and then the Apply Button. This will clear all the access permissions.</p>
<p>7. Now click &#8220;Customize&#8221; and the Edit button. Re-enter all the customized entries you wrote down in step #5 above.</p>
<p>That&#8217;s what fixed this problem for me.</p>
<p>Al Simon<br />
<a href="http://www.virtualmarketingbiz.com" >http://www.virtualmarketingbiz.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Newton</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-40852</link>
		<dc:creator>Phil Newton</dc:creator>
		<pubDate>Wed, 19 Sep 2007 08:07:50 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-40852</guid>
		<description>Thanks Jack &#038; Mike, I've updated the article slightly to reflect your findings. Cheers!</description>
		<content:encoded><![CDATA[<p>Thanks Jack &#038; Mike, I&#8217;ve updated the article slightly to reflect your findings. Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-40815</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 19 Sep 2007 01:18:32 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-40815</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>After trying the DCOM services fix (it didn&#8217;t work) I discovered the same solution. Filename was too long. I renamed it to a shorter name and it fixed the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jack</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-39969</link>
		<dc:creator>jack</dc:creator>
		<pubDate>Mon, 10 Sep 2007 11:04:36 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-39969</guid>
		<description>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!!</description>
		<content:encoded><![CDATA[<p>Hi guys,<br />
Ran into this problem today&#8230;on serveral computers&#8230;Some say its services and other corrupted registry&#8230;</p>
<p>I rename it to a shorter filename and everything was back to normal.</p>
<p>Hope it helps Yang!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Newton</title>
		<link>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-35998</link>
		<dc:creator>Phil Newton</dc:creator>
		<pubDate>Sun, 15 Jul 2007 22:07:19 +0000</pubDate>
		<guid>http://www.sodaware.net/blog/2006/07/fixing-the-office-2007-error-document-could-not-be-registered/#comment-35998</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Hi yang,</p>
<p>The DCOM server solved the problem for me, so I don&#8217;t know of any other solutions. Perhaps restarting the service would help, but I don&#8217;t really know.</p>
<p>Sorry I couldn&#8217;t be more help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
