"Tyler Allbritton" <ta*********@newsgroups.nospamwrote in message
news:0D**********************************@microsof t.com...
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.
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!
Best of luck - you're really going to need it!