HighTechTalks DotNet Forums  

Word Interop and Server 2003

Dotnet Framework (Interop) microsoft.public.dotnet.framework.interop


Discuss Word Interop and Server 2003 in the Dotnet Framework (Interop) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
TJHerman
 
Posts: n/a

Default Word Interop and Server 2003 - 03-29-2007 , 05:32 PM






I have a problem in deploying an ASP.NET web project with
Microsoft.Interop.Word on a server with Windows Server 2003.

From the developing PC, my program opens a Word template, replaces bookmarks
with some text from the web page and then saves and closes the file. As many
others say, it works fine from the developing PC but when I try to put is on
the web server, it fails with the error:
- - - - - -
Retrieving the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following error:
8000401a.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Retrieving
the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following error:
8000401a.

Source Error:

Line 185: Dim word As New Microsoft.Office.Interop.Word.Application
Line 186: Dim wobj As Microsoft.Office.Interop.Word.Document
Line 187:
- - - - - - -

The server is running Windows Server 2003. I have tried setting the DCom
permissions (on the component labeled My Computer) so that the ASPNET,
INTERACTIVE and NETWORK SERVICE accounts have Launch and Activation
permissions. I have also gone to the Microsoft Document component under DCom
and added the same permissions. My DCom settings for the Word document are to
run as Interactive User, authentical level to “Connect”, Location to “Run
application on this computer”. I have tried adding permissions to the
Assembly folder underneath Windows and have checked the registry to ensure
that DCom was enabled.

I’m really at a loss here. Does anyone have any suggestions? This has run
flawlessly on a Windows 2000 server for months. But I cannot get it deployed
properly to this server with 2003.

Reply With Quote
  #2  
Old   
Ornette
 
Posts: n/a

Default Re: Word Interop and Server 2003 - 04-01-2007 , 11:10 AM






Is Word installed on the server ?? You must.

Ornette.

"TJHerman" <TJHerman (AT) discussions (DOT) microsoft.com> wrote

Quote:
I have a problem in deploying an ASP.NET web project with
Microsoft.Interop.Word on a server with Windows Server 2003.

From the developing PC, my program opens a Word template, replaces
bookmarks
with some text from the web page and then saves and closes the file. As
many
others say, it works fine from the developing PC but when I try to put is
on
the web server, it fails with the error:
- - - - - -
Retrieving the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following error:
8000401a.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about
the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Retrieving
the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following error:
8000401a.

Source Error:

Line 185: Dim word As New
Microsoft.Office.Interop.Word.Application
Line 186: Dim wobj As Microsoft.Office.Interop.Word.Document
Line 187:
- - - - - - -

The server is running Windows Server 2003. I have tried setting the DCom
permissions (on the component labeled My Computer) so that the ASPNET,
INTERACTIVE and NETWORK SERVICE accounts have Launch and Activation
permissions. I have also gone to the Microsoft Document component under
DCom
and added the same permissions. My DCom settings for the Word document are
to
run as Interactive User, authentical level to "Connect", Location to "Run
application on this computer". I have tried adding permissions to the
Assembly folder underneath Windows and have checked the registry to ensure
that DCom was enabled.

I'm really at a loss here. Does anyone have any suggestions? This has run
flawlessly on a Windows 2000 server for months. But I cannot get it
deployed
properly to this server with 2003.



Reply With Quote
  #3  
Old   
TJHerman
 
Posts: n/a

Default Re: Word Interop and Server 2003 - 04-01-2007 , 12:04 PM



Yes, Word is installed on the server

"Ornette" wrote:

Quote:
Is Word installed on the server ?? You must.

Ornette.

"TJHerman" <TJHerman (AT) discussions (DOT) microsoft.com> wrote in message
news:44044A9B-E1F4-4081-97F4-52F4F210316C (AT) microsoft (DOT) com...
I have a problem in deploying an ASP.NET web project with
Microsoft.Interop.Word on a server with Windows Server 2003.

From the developing PC, my program opens a Word template, replaces
bookmarks
with some text from the web page and then saves and closes the file. As
many
others say, it works fine from the developing PC but when I try to put is
on
the web server, it fails with the error:
- - - - - -
Retrieving the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following error:
8000401a.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about
the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Retrieving
the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following error:
8000401a.

Source Error:

Line 185: Dim word As New
Microsoft.Office.Interop.Word.Application
Line 186: Dim wobj As Microsoft.Office.Interop.Word.Document
Line 187:
- - - - - - -

The server is running Windows Server 2003. I have tried setting the DCom
permissions (on the component labeled My Computer) so that the ASPNET,
INTERACTIVE and NETWORK SERVICE accounts have Launch and Activation
permissions. I have also gone to the Microsoft Document component under
DCom
and added the same permissions. My DCom settings for the Word document are
to
run as Interactive User, authentical level to "Connect", Location to "Run
application on this computer". I have tried adding permissions to the
Assembly folder underneath Windows and have checked the registry to ensure
that DCom was enabled.

I'm really at a loss here. Does anyone have any suggestions? This has run
flawlessly on a Windows 2000 server for months. But I cannot get it
deployed
properly to this server with 2003.




Reply With Quote
  #4  
Old   
Ornette
 
Posts: n/a

Default Re: Word Interop and Server 2003 - 04-01-2007 , 11:10 PM



OK.

I'm using the same and it works (except for printing, see message above).
So, are you using impersonation or not ? Do you autenticate you users or not
?
Do you run your app in a specific pool ? If so which user runs the pool ?
Did you install Office PIA separatly or with Office ?
Wich version of Office do you use ? Wich version of PIA do you use ?

I know this is several question but everything should be known for this kind
of question !

Hope I will help you, because I solved this problem !!! (except for network
pinters !!).

Ornette.

"TJHerman" <TJHerman (AT) discussions (DOT) microsoft.com> wrote

Quote:
Yes, Word is installed on the server

"Ornette" wrote:

Is Word installed on the server ?? You must.

Ornette.

"TJHerman" <TJHerman (AT) discussions (DOT) microsoft.com> wrote in message
news:44044A9B-E1F4-4081-97F4-52F4F210316C (AT) microsoft (DOT) com...
I have a problem in deploying an ASP.NET web project with
Microsoft.Interop.Word on a server with Windows Server 2003.

From the developing PC, my program opens a Word template, replaces
bookmarks
with some text from the web page and then saves and closes the file. As
many
others say, it works fine from the developing PC but when I try to put
is
on
the web server, it fails with the error:
- - - - - -
Retrieving the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following
error:
8000401a.
Description: An unhandled exception occurred during the execution of
the
current web request. Please review the stack trace for more information
about
the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException:
Retrieving
the COM class factory for component with CLSID
{000209FF-0000-0000-C000-000000000046} failed due to the following
error:
8000401a.

Source Error:

Line 185: Dim word As New
Microsoft.Office.Interop.Word.Application
Line 186: Dim wobj As Microsoft.Office.Interop.Word.Document
Line 187:
- - - - - - -

The server is running Windows Server 2003. I have tried setting the
DCom
permissions (on the component labeled My Computer) so that the ASPNET,
INTERACTIVE and NETWORK SERVICE accounts have Launch and Activation
permissions. I have also gone to the Microsoft Document component under
DCom
and added the same permissions. My DCom settings for the Word document
are
to
run as Interactive User, authentical level to "Connect", Location to
"Run
application on this computer". I have tried adding permissions to the
Assembly folder underneath Windows and have checked the registry to
ensure
that DCom was enabled.

I'm really at a loss here. Does anyone have any suggestions? This has
run
flawlessly on a Windows 2000 server for months. But I cannot get it
deployed
properly to this server with 2003.






Reply With Quote
  #5  
Old   
Abha
 
Posts: n/a

Default Re: Word Interop and Server 2003 - 04-23-2007 , 05:30 AM



You need to disable anti-Virus software on the server.

Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.