Home > ASP.NET > System.Runtime.InteropServices.COMException (0x800A03EC): Microsoft Office Excel cannot access the file

System.Runtime.InteropServices.COMException (0x800A03EC): Microsoft Office Excel cannot access the file

You may encounter this error when trying to run excel automation via IIS.

 

There are several links pointing to this issue with the resolution found at

http://social.msdn.microsoft.com/Forums/en-US/innovateonoffice/thread/b81a3c4e-62db-488b-af06-44421818ef91 by H Ogawa

 

I’m reproducing the same information here for ease of resolution

  1. Create directory “C:\Windows\SysWOW64\config\systemprofile\Desktop ” (for 64 bit Windows) or “C:\Windows\System32\config\systemprofile\Desktop ” (for 32 bit Windows)
  2. Set Full control permissions for directory Desktop (for example in Win7 & IIS 7 & DefaultAppPool set permissions for user
    “IIS AppPool\DefaultAppPool”)
Categories: ASP.NET
  1. Moslem
    December 29, 2010 at 2:29 pm

    Oh!!! very good.
    Thanks a lot. This resolve my problem After 1 week.
    Best regards.
    دمت گرم

    • Anonymous
      February 4, 2011 at 5:40 pm

      Thanks. Very helpful!

  2. Asim Saeed
    December 20, 2011 at 10:04 pm

    Awesome dude… just because of your post, my suicide plan is now canceled.

  3. February 9, 2012 at 10:32 am

    i just followed your steps but it’s not working well 😦
    my page respond too long….
    any solution??
    thanks 4 your help

  4. thoma
    May 29, 2012 at 9:46 pm

    Hey,

    Thanks for this post. I have a little problem though. I’ve created the folde as you said, and now my error isn’t the same. I think i don’t know how to Set Full control permissions for directory Desktop.

    Can you please help me on this one ?

    Thanks By Advance

  5. June 8, 2012 at 1:38 pm

    thoma, to set permissions on the folder, refer to http://support.microsoft.com/kb/308419 for actual steps. If you got a different error, chances are you have already set the required information, now it is something else that needs to be fixed

  6. September 28, 2012 at 7:45 pm

    Very good article! We will be linking to this particularly great post on our website.

    Keep up the great writing.

  7. Earnie
    November 24, 2013 at 4:35 pm

    Thanks a lot! This resolved our problem after one developer-week unsuccessful workaround…
    Best regards.

  8. Mayank Dua
    May 12, 2016 at 8:10 pm

    Thanks a lot man.
    After trying many workarounds we were just hitting the wall everytime but this resolved our problem.

    Best Regards,
    Mayank

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: