Hey Mark,
This is kind of a random suggestion, but since the Office Interop works
better in a Windows environment, you might try setting up a Windows Service
that watches a database table for information about "jobs" to pickup. Make
it synchronous (only one job at a time because running Word COM is just like
using it manually; you can only edit one document at a time per Word
application). Let the service pickup jobs and generate the word docs for you
with the information submitted from the website. You can tag the job records
with some kind of status so you can see the status on the website. Then when
it's done, make the end result word doc available to the site via its
status.
Just an idea. You also might check out using a third party utility like
Aspose (aspose.com) or TXTextControl Server (textcontrol.com) which will
give you an API to manipulate word docs without using Office COM to do it.
Then you could do it directly in the site or in a windows service easily.
But it comes with a cost.
Good luck!
-Nathan
"Mark Rae [MVP]" <> wrote in message
news:%23v7zC78%...
> <> wrote in message
> news: oups.com...
>
>> Retrieving the COM class factory for component with CLSID
>> {00020906-0000-0000-C000-000000000046} failed due to the following
>> error: 80080005
>>
>> Any ideas? I'm sure it has to do with how I added the assembly
>
> Nope - it has nothing to do with that... It's simply that server-side
> Office automation doesn't work because Office just wasn't designed to run
> in that environment - Microsoft won't support any solution which even
> tries to use it:
> http://support.microsoft.com/default...US;q257757#kb2
>
> See the "MORE INFORMATION" section, particularly the bold paragraph...
>
> If you need to manipulate Word documents server-side, you need this:
> http://www.aspose.com/Products/Aspos...s/Default.aspx
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net