来自HRESULT的异常：0x800A03EC

Question

Any help is appreciated:

I'm developing a C#.Net app in VS2010 that interacts with Excel. The app works correctly on my local machine. Uploading to a remote Windows 2003 server however, breaks the app.

Originally, I received the following message

• Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80070005

After Googling the problem (which suggested a permissions problem) i tried this:

• Installing Excel 2007
• Going into Component Services on the remote server and following the instructions here: http://blog.crowe.co.nz/archive/2006/03/02/589.aspx

Now I get this message on the same operation:

• Exception from HRESULT: 0x800A03EC

Google searches seem to be suggesting that this is a version match error. However, both the local machine and the remote server use Excel 2007.

Any suggestions would be very welcome. Thanks in advance.

-Daniel

Answer 1

If you are trying to send a datagridview to an Excel spreadsheet, remember that Excel cells start at Cell (1,1) but datagridview.rows and datagridview.columns are indexed at 0. So if you try to send the contents of datagridviewcell(0,0) to the Excel Cell (0,0), you'll get Exception from HRESULT: 0x800A03EC

I was googling around frantically for a good 15 minutes before slamming my palm into my forehead for that one.

Excel.Cells(0,0)=Datagridviewcellvalue // throws HRESULT: 0x800A03EC error 
Excel.Cells(1,1) = Datagridviewcellvalue //no error

Answer 2

Delete the temporary ASP.Net files from "C:\\WINDOWS\\Microsoft.NET\\Framework\\v2.0.50727\\Temporary ASP.NET Files" this folder, Please check after this.

After checking also its not working then restart System and check... There is a chance to occur this because of corrupted files. So do a disc checking.

Thank you

Answer 3

Suggestions:

1. Control Excel from one thread and use the "en_US" culture. There are many properties triggering 0x800A03EC if a non english culture is used. Is per accident your windows 2003 using another system language, if yes then this is probably the issue. No need to reinstall windows! Just specify the culture for the thread in your app.
2. Check the length of the strings set using ranges. There is a limitation to 911 chars. You can set them separately for the cells having bigger strings. It is tedious but I could not find any other way to solve this.

Answer 4

I was able to resolve this problem by wholesale disabling of all add-ins, and restarting the app. Then I re-enabled the useful ones, watching Excel behavior. YMMV