22
votes

I am trying to open .docx file and convert to PDF using Interop.Word.Application. It works as console application but If I use the same in my web application it doesn't work. I tried to see the permissions on the folder. I gave 'Network Service' with full control, but still I get object reference not set at word.Documents.Open. Could you please let me know what could be the problem? I am stuck with this error. Please let me know. I appreciate any suggestions. Thank you.

    Microsoft.Office.Interop.Word.Application word = new Microsoft.Office.Interop.Word.Application();

    object oMissing = System.Reflection.Missing.Value;

    word.Visible = false;
    word.ScreenUpdating = false;
    string fileName = @"c:\OUTPUT\test.docx");
    Document doc = word.Documents.Open(filename, ref oMissing,
            ref oMissing, ref oMissing, ref oMissing, ref oMissing, ref oMissing,
            ref oMissing, ref oMissing, ref oMissing, ref oMissing, ref oMissing,
            ref oMissing, ref oMissing, ref oMissing, ref oMissing);
        doc.Activate();
7
Sorry, I can't help you exactly but I would heavily advise against using Office Interop in a web app, MS advise against it and as far as I am aware office is not licensed to be used on a web server. Apologies if that is irrelevant to you, there are a lot of third party components which would perform this for you but I've never used an open source one. - Paulie Waulie
Is there anything in the event log? - Paulie Waulie
There's a bug in that code. string fileName = @"c:\OUTPUT\test.docx"); <--- has a trailing ). please post the actual code that's in your application. - Eoin Campbell
There is nothing in the event log. - nav100
answer with creating Desktop folder helped for me: stackoverflow.com/questions/1006923/… - zchpit

7 Answers

67
votes

If you are still looking for the answer I have found it just a moment ago for my project.

Open DCOM Config Settings:

  1. Start -> dcomcnfg.exe
  2. Computer
  3. Local Computer
  4. Config DCOM
  5. Search for Microsoft Word 97-2003 Documents -> Properties

Tab Identity, change from Launching User to Interactive User

25
votes

Try this it may help you.

  • Create a new "Desktop" directory inside of "C:\Windows\SysWOW64\config\systemprofile\"

it works for me after a long long long day searching for the solution.

It seams to be a profile problem.

2
votes

I did the following steps and it worked all right:

  • Create the desktop folder
  • Change the DCOM element to login with a specific user instead of an launching/interactive user
  • Changed the service so it started as the same specific user

Edit on 2019-09-29. Due to a big windows update I had to do the exact progress all over again.

1
votes

To solve this I had to do both things:

  • Create the directories:

    • C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft \Windows\INetCac‌he
    • C:\Windows\System32\config\systemprofile\Desktop
  • Enable DCOM setting as @gianni-b says.

If you're struggling to find the DCOM entry because of a different language, you can do this:

  1. Start Menu > regedit
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{00020906-0000-0000-C000-000000000046}
  3. Right click > New > String value

    • For Key, put RunAs
    • For Value, put Interactive User

You can do the same for Excel on AppID {00020812-0000-0000-C000-000000000046}.

0
votes

As Paulie stated in his comment on OP, I think the issue is largely because of the libraries on the webserver. YOu might be able to hack to get this working on a web app, but I'd advise against it.

EDIT: Argh, I misread the post and just assumed Excel. That's what most people look for when using Office.Interop in my experience ;)

There is an open library that works with DocX formats (enter link description here). Unfortunately he admits on the page that conversions to formats like PDF is pretty much impossible without the Office.Interop libraries (http://cathalscorner.blogspot.com/2009/10/converting-docx-into-doc-pdf-html.html)

Here is a 'promising' alternative, but YMMV.

0
votes

It is most likely that you have a different word dll on your web server, perhaps an older one. I suggest that you reference a specific dll and copy it to the web server, so you can be sure that you are using the same word dll that you tested your code with and you know it works. There might be some problems when using interop, however, word interop is the only one which you can be sure will convert word files most correctly.