Automating Office via Windows Service on Server 20

Question

We have a Windows Service which runs on 2003 Server. It opens a source Word document using the Word Interop and then does some stuff with it. It also does likewise with Excel and PowerPoint files.

Recently we've tried moving this service onto a Windows 2008 Server machine and are having real problems with it.

COMException at Microsoft.Office.Interop.Excel.Workbooks.Open COMException at Microsoft.Office.Interop.Word.Documents.Open

I get the above exceptions when the windows service is running on 2008 Server. Looking at the Task Manager, the application does load ok, but then closes again shortly after.

I've read things about Vista and Server 2008 not having a Session0 anymore, and have tried changing the Office DCOM security properties accordingly, including changing the identity of the user running them to Integrated but to no avail.

Does anyone know if this is possible at all? This is a fundamental aspect of our system and so we need to be able to do this.

Thanks

Answer 1

If you are using Apache, you might also need to follow these steps to get MS Word working properly (along with everything outlined in other answers):

Below is a screenshot showing the two dialogs you'll need to bring up:

For Apache:

Services->Apache->Right Click (Properties)->Log On Tab

MS Word:

Launch dcomcnfg.exe->Console Root->Component Services->Computers->My Computer->DCOM Config->Find Microsoft Application->Right Click(Properties)->Identity Tab

**if you can't find the MS Word, make sure you are launching the correct DCOM Config (64 bit vs 32 bit) depending on what version of Office you have installed.

There are two options here, you can set Apache to use Local System Account and check the checkbox to ALLOW desktop interaction. If you do this then you need to set the Identity for MS Word to Interactive User.

Otherwise, you need to set both to the same user (Ideally the user that is logged in) like shown in the picture.

Answer 2

Well, you will need to run "MMC -32" (command prompt) to launch 32-bit MMC and then add Component Services (File > Add / Remove Snap-ins' menu)

then follow one of these instruction:

http://theether.net/download/Microsoft/kb/288366.html

Answer 3

I've had problems automating Office from a Windows Service under Windows Server 2008, even though that works fine under Windows Server 2003. The problem also occurs at the Open call, so it may be the same problem.

I tried following the advice given by H Ogawa in this MSDN thread, and it seemed to work. It's bizarre, but kudos to Mr. Ogawa for discovering it.

Summary of the 'Ogawa Hack': create a desktop folder for the system profile, as:

 C:\Windows\System32\config\systemprofile\Desktop

and, if running on a 64-bit machine, create another one, as:

 C:\Windows\SysWOW64\config\systemprofile\Desktop

Also, the folder(s) need write permission for whatever user is "driving" Office.

---

[Edit: corrected link URL]

[Edit 2: clarified that on 64-bit Windows, you need both folders, not just the WOW64 one]

Answer 4

This also happens on Vista with UAC enabled. You might want to try setting the DCOM identity to be an administrator account and test it again.

I also recently started having this problem on an XP box trying to open workbooks in Excel through interop services, but have not yet found a workaround. I myself would like any other insights the community might be able to throw out there...