I'm using a servic to periodically check a directory and Print to PDF any Word docs that get put there. This all worked fine on server 2003 with word xp. Now I'm using Server 2008 and Word 2007 and keep getting the same error. It works fine as an app, but fails as a service with: "This command is not available because no document is open"
Code below.
 
Imports Word = Microsoft.Office.Interop.Word
____________

Dim

wa = New Word.Application
Dim wd As Word.Document = wa.Documents.Open("c:\test.doc", False, True, False)
If Not wd Is Nothing Then wd.Activate()
wa.ActivePrinter = "CutePDF Writer"
wa.ActiveDocument.PrintOut(False)
wd.Close(False)

I would check out the following article. Office applications were never designed to run from unattended processes.

Considerations for server-side Automation of Office

---

Paul ~~~~ Microsoft MVP (Visual Basic)

Mike

can't help you directly

but there is also a Visual Studio Tools for Office (VSTO) Forum that might be a good place to post your question


http://social.msdn.microsoft.com/Forums/en-US/vsto/threads

I would check out the following article. Office applications were never designed to run from unattended processes.

Considerations for server-side Automation of Office

---

Paul ~~~~ Microsoft MVP (Visual Basic)

I was afraid of that. Since it worked fine in Server 2003, I had hoped it would also in 2008. I wonder why the interop class exists if you shouldn't use it?

Office automation is fine with apps that have a user interface but apps that don't provide one can't give feedback to the user in case of an error. Of course the main issue is the threading model limitation.

---

Paul ~~~~ Microsoft MVP (Visual Basic)