System Runtime InteropServices COMException 0x800A03EC

Question

Microsoft Office Interop Excel WorkbookClass SaveAs   method is working fine on Windows server 2003 and also on XP but not on Windows server 2008  I copied it as it is gave all Dll s and permissions  I have also tried all the solutions given on the net  such as Culture settings and DCOM permission   Getting following error      System Runtime InteropServices COMException  0x800A03EC   Exception   from HRESULT  0x800A03EC   at      Microsoft Office Interop Excel WorkbookClass SaveAs Object Filename    Object FileFormat  Object Password  Object WriteResPassword  Object   ReadOnlyRecommended  Object CreateBackup  XlSaveAsAccessMode   AccessMode  Object ConflictResolution  Object AddToMru  Object   TextCodepage  Object TextVisualLayout  Object Local    Please help

User · Answer

Some googling reveals that potentially you've got a corrupt file:

http://bitterolives.blogspot.com/2009/03/excel-interop-comexception-hresult.html

and that you can tell excel to open it anyway with the CorruptLoad parameter, with something like...

Workbook workbook = excelApplicationObject.Workbooks.Open(path, CorruptLoad: true);

User · Answer

It  a permission problem when IIS is running I had this problem and I solved it in this way   I went on folders   C  Windows  System32 config SystemProfile   and   C  Windows SysWOW64 config SystemProfile   are protected system folders  they usually have the lock    Right-click-  Card security-  Click on Edit-  Add untente  Autenticadet User  and assign permissions    At this point everything is solved  if you still have problems try to give all permissions to  Everyone

User · Answer

Found Answer                Officially Microsoft Office 2003 Interop is not supported on Windows server 2008 by Microsoft    But after a lot of permutations  amp  combinations with the code and search  we came across one solution which works for our scenario   The solution is to plug the difference between the way Windows 2003 and 2008 maintains its folder structure  because Office Interop depends on the desktop folder for file open save intermediately  The 2003 system houses the desktop folder under systemprofile which is absent in 2008   So when we create this folder on 2008 under the respective hierarchy as indicated below  the office Interop is able to save the file as required  This Desktop folder is required to be created under   C  Windows System32 config systemprofile  AND  C  Windows SysWOW64 config systemprofile  This worked for me      Also do check if  NET 1 1 is installed because its needed by Interop and ot preinstalled by Windows Server 2008  Or you can also Use SaveCopyas   method ist just take onargument as filename string   Thanks Guys

User · Answer

I was seeing this same error when trying to save an excel file  The code worked fine when I was using MS Office 2003  but after upgrading to MS Office 2007 I started seeing this  It would happen anytime I tried to save an Excel file to a server or remote fie share   My solution  though rudimentary  worked well  I just had the program save the file locally  like to the user s C   drive  Then use the  System IO File Copy File  Destination  Overwrite   method to move the file to the server  Then you can delete the file on the C   drive   Works great  and simple  But admittedly not the most elegant approach   Hope this helps  I was having a ton of trouble finding any solutions on the web till this idea popped into my head

User · Answer

In my case  the problem was styling header as  Header 1  but that style was not exist in the Word that I get the error because it was not an Office in English Language

User · Answer

Try this as it worked for me      Go to  Start  -   Run  and enter  dcomcnfg  This will bring up the component services window  expand out  Console    Root  -   Computers  -   DCOM Config  Find  Microsoft Excel Application  in the list of components  Right click on the entry and select  Properties  Go to the  Identity  tab on the properties dialog  Select  The interactive user     courtesy of Last paragraph mentioned in here

User · Answer

For all of those  who still experiencing this problem  I just spent 2 days tracking down the bloody thing   I was getting the same error when there was no rows in dataset  Seems obvious  but error message is very obscure  hence 2 days

[.net] System.Runtime.InteropServices.COMException (0x800A03EC)

Examples related to .net

Examples related to iis

Examples related to com

Examples related to excel-interop