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 ..!

Whitmore

"The following code... " - what code? I think you forgot to post your code. – Pockmark

I also got this exception when exporting to a cell using worksheet.Cells[rowIndex, excelColumn] = "Weird Charcters Here" . I found that the data I was trying to place in the cell had many "special characters" that was causing it. – Torino

Answer 1

Found Answer.......!!!!!!!

Officially Microsoft Office 2003 Interop is not supported on Windows server 2008 by Microsoft.

But after a lot of permutations & 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..!

Whitmore

I have just used SaveCopyas() instead of SaveAs() and added impersonate in web.config and its working! – Piggin

How do you used SaveCopyAs() instead of SaveAs() when the methods have differents parameters for example save format ? – Blakely

I've created the desktop folders and it is working perfectly again. Thanks so match, I whould have never found the issue myself – Dhammapada

Also be sure to set appropriate Write/Create Permissions on the created Desktop folders. – Juncture

Worked (almost) like a charm: images in my Excel file were missing. Solved it by dealing with the existence/persmission of INetCache in the same folder https://mcmap.net/q/410546/-why-would-the-excel-interop-remove-an-image-after-processing-a-file – Iyre

please add desktop in the path to make it more explicit at first glance – Gown

Answer 2

Try this as it worked for me...

1. Go to "Start" -> "Run" and enter "dcomcnfg"
2. This will bring up the component services window, expand out "Console Root" -> "Computers" -> "DCOM Config"
3. Find "Microsoft Excel Application" in the list of components.
4. Right click on the entry and select "Properties"
5. Go to the "Identity" tab on the properties dialog.
6. Select "The interactive user."

courtesy of Last paragraph mentioned in here

Delighted

10q my friend, I've tried everything and nothing worked in my case except your answer. – Dhammapada

I am stuck at step 3, where the Micosoft Excel Application is not available in: Console Root > Computers > My Computer. Is there an updated location? – Unitarian

Answer 3

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);

Senzer

I had this same issue. The was garbage data in the excel file. Opening it up manual in excel and removed the bad data any everything worked. I also tried with the CorruptLoad as well. This worked – Servetnick

Answer 4

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.

Devon

Answer 5

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.

Redo

@daniele3004 If I remember correctly, the problem was that I was getting zero number of rows. So I added check for numberOfRows > 0 and the problem got fixed. – Redo

Answer 6

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"

Quenchless

Answer 7

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.

Swarm

Answer 8

I had this problem due to the path of an excel file and whenever I tried to open the excel file I got the error message (i.e. my excel file had a long path like C:\Users\Blabla\Blabla\MyVeryLongFolderHierarchyPath\MyExcelFile.xlsx)

The solution was to carry my excel file under a shorter filepath (like C:\MyExcelFile.xlsx) directly. I can not believe such a stupid problem occurs due to long file paths in year 2021

Cupreous

Answer 9

A strange solution I stumbled upon is to see if there are any Excel processes running in the background. Make sure code is in fact cleaning up after itself and closing all Excel processes.

Photomontage

Answer 10

I got this exception when writing to my workbook cells. The problem was that the cells are indexed from 1 and not 0:

Bad:

activeSheet.Cells[0, 0].Value = 1;

Good:

activeSheet.Cells[1, 1].Value = 1;

Electroform

Answer 11

I found the same issue in my code being caused by entering faulty formulas. My system is set to german but in this case i actually have to input the excel formula in english. Opening the document afterwards, shows the formula back in german.

Stanwinn