By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,092 Members | 1,597 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,092 IT Pros & Developers. It's quick & easy.

Problems when try to launch word in server 2003

P: n/a
I hope I'm in the correct forum for this, as the problem is hard to categorize.

I have a VS 2005 application that invokes Word 2003 to opean and
read a word document. the aplication have <identity impersonate="true"/.
The application works fine on my machine (Win XP SP2 and Office 2003 SP2) but
when I deploy the app to a server (Server 2003, Office 2003 SP2) everything
works fine except when I try to launch Word. The application receives the
following error:

Retrieving the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following error:

I have modified the DCOM (via DCOMCNFG) to give full control for Microsoft
word document to my personals groups
The code invoking word is simply this:

Dim AplicacionWord As New Microsoft.Office.Interop.Word.Application()
Dim DocWord As Microsoft.Office.Interop.Word.Document


Edgardo Alvarez, Honduras
Nov 1 '06 #1
Share this Question
Share on Google+
2 Replies

P: n/a
Hi Edgardo,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you're currently using a server-side
automation in an ASP.NET app. The code returns an 80070005 error which
means Access denied. If there is any misunderstanding, please feel free to
let me know.

Developers can use Automation to Microsoft Office to build custom solutions
that utilize the capabilities and features that are built into the Office
product. While such programmatic development can be implemented on a client
system with relative ease, there are a number of complications that can
occur if Automation is to take place from server-side code such as Active
Server Pages (ASP), DCOM, or an NT Service.

Microsoft does not currently recommend, and does not support, Automation of
Microsoft Office applications from any unattended, non-interactive client
application or component (including ASP, DCOM, and NT Services), because
Office may exhibit unstable behavior and/or deadlock when run in this

Microsoft recommends a number of alternatives that do not require Office to
be installed server-side, and that can perform most common tasks more
efficiently and quickly than Automation

For more information about this, you can check the following KB article. It
fully explain why the server-side automation is not recommended.;[LN];257757

If anything is unclear, please feel free to reply to the post.

Kevin Yu
Microsoft Online Community Support

Get notification to my posts through email? Please refer to
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at

(This posting is provided "AS IS", with no warranties, and confers no

Nov 2 '06 #2

P: n/a
Hi Edgardo,

I'd like to know if this issue has been resolved yet. Is there anything
that I can help. I'm still monitoring on it. If you have any questions,
please feel free to post them in the community.

Kevin Yu
Microsoft Online Community Support


(This posting is provided "AS IS", with no warranties, and confers no

Nov 6 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.