UnauthorizedAccessException when creating Word doc

VerbatimBOT · October 27th, 2008, 09:55 AM

Hi all,

I'm having troubles with generating Word documents from a predefined Word template. Since I have found on the Net it's not recommended for Word docs to be generated from within ASP.NET app, I have created a small console application which will do the work.
The thing is, when I start this console app manually, it works fine, but when ASP.NET app tries to call it, it returns an UnauthorizedAccessException.

Here is the calling code

Code:

        Process objGenDoc = new Process();
        objGenDoc.StartInfo.FileName = Server.MapPath("~/GenerateDocument.exe");

        objGenDoc.Start();
        objGenDoc.WaitForExit(8000);

I'ld also like to mention I have no such thing as "Microsoft Word Application" or something similar which would point to Word application in my Component Service (dcomcnfg) from which I could set launching or accessing permissions.

I'm running 64bit Vista, Office 2007 and IIS7.
Word and Office references have been added to web.config file.

Thanks in advance.

Aleksandar Dragosavac
Belgrade, Serbia

pankajmk · November 3rd, 2008, 04:32 PM

Hi,
Have you given the permission for aspnet user to access dcom word object if not then try giving

"Computer" -> "My Computer" -> "DCOM config".
Now, search for a "Microsoft Word Document" -> right click ->Properties, Security

Also modify your web.confile file by adding identity tag

<identity impersonate="true" userName="domainName\userName" password="yourPassword" / >

Hope this will help you

Pankaj
www.dotnetspark.com

VerbatimBOT · November 3rd, 2008, 06:56 PM

Hi, thank you for replying.
I've heard about DCOM config settings, but I do not have "Microsoft Word Document" in it. I do have Office 2007 installed though.
The real problem was that Word docs generating code did not work on 64bit Server 2008 for some reason. The exact same code works perfectly well on 64bit Server 2003! Another interesting thing is that it does not work if the app is impersonating a machine local account, but it works if it's impersonating a domain account. Do you know why is that? :)

Thanks.

Aleksandar Dragosavac
Belgrade, Serbia