COM Interop Via Web

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a basic web app that is using Word (I know, big no no) to fill out a
Word Template based on form input and save the resulting document to
SharePoint. When I'm running the application locally (logged onto Windows
Server) it works great. Remotely, it hangs when opening the Word application
instance. I assume I have some DCOM or other security issue. Any ideas on
where it may be?

Thanks!
Tyler Allbritton
 
I have a basic web app that is using Word (I know, big no no)
Click to expand...

Hmm - just to be clear, you already *know* that what you're doing is a "big
no no", and now you're wondering why it doesn't work...?
I assume I have some DCOM or other security issue.
Click to expand...

Who knows - it could be any number of things...

The simple fact is that server-side Office automation is not supported by
Microsoft because it's not designed to work this way:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q257757#kb2

Use this instead: http://www.aspose.com/Products/Aspose.Words
 
Mark - Thanks for the comment.

If anyone is interested in an actual solution though, Word and other Office
apps need to run under normal user accounts as opposed to a built-in accounts
like LOCAL SERVICE. This is why it worked when I was logged in, but not
remotely. Microsoft outlines how to do this specifically for Office/COM here:
http://support.microsoft.com/default.aspx/kb/288367.

In my case I set the Idenity for Word to the new OfficeAutomationUser
account via DCOMCNFG. It works great!
 
If anyone is interested in an actual solution though, Word and other
Office
apps need to run under normal user accounts as opposed to a built-in
accounts
like LOCAL SERVICE. This is why it worked when I was logged in, but not
remotely. Microsoft outlines how to do this specifically for Office/COM
here:
http://support.microsoft.com/default.aspx/kb/288367.
Click to expand...

Sigh... Did you actually *read* that article...? Specifically, the bits
saying things like "We do not recommend or support...", "...risky and
unstable...", "stop responding (hang)", "...corrupt data...", "...crash the
calling process...", "...bring down your Web server...", "Office was not
designed, and is not safe, for unattended execution on a server. Developers
who use Office in this manner do so at their own risk."

Etc.
In my case I set the Idenity for Word to the new OfficeAutomationUser
account via DCOMCNFG. It works great!
Click to expand...

Best of luck - you're really going to need it!
 
Back
Top