Skip to main content

Error : System.Runtime.InteropServices.COMException (0x800A03EC): Exception from HRESULT: 0x800A03EC

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)

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

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)

Follow the Below steps:

Setp 1 :

On Web.config File Add the below in <system.web>Tag

<identity impersonate="true"

userName="domain\username"

password="userpassword"/>

UserName : Login Id who loged on the Machine(or server)

Password : Password who loged on the machine(or server)

Setp 2:

1. Go to Start->Run

2. Type “DCOMCNFG

3. Open Console Root->Component Service->Computer->My Computer->DCOM Config

4. Right Click Property on “Microsoft Excel Application

5. Go to Identity Tab

6. Select “This User

a. User : Logged User Name

b. Password : Logged user Password



Comments

Popular posts from this blog

HTTPHandler and HTTPModule in ASP.NET

If you want to implement pre-processing logic before a request hits the IIS resources. For instance you would like to apply security mechanism, URL rewriting, filter something in the request, etc. ASP.NET has provided two types of interception HttpModule and HttpHandler .   The web server examines the file name extension of the requested file, and determines which ISAPI extension should handle the request. Then the request is passed to the appropriate ISAPI extension.  For Example When an .aspx page is requested it is passed to ASP.Net page handler. Then Application domain is created and after that different ASP.Net objects like Httpcontext, HttpRequest, HttpResponse. HTTPModule: -    It's just like a filter. The Modules are called before and after the handler executes . -    HTTP Modules are objects which also participate the pipeline but they work before and after the HTTP Handler does its job, and produce additional serv...

Connected and disconnected architecture in ADO.Net with Example

Connected Architecture of ADO.NET The architecture of ADO.net, in which connection must be opened to access the data retrieved from database is called as connected architecture. Connected architecture was built on the classes connection, command, datareader and transaction.  Connected architecture is when you constantly make trips to the database for any CRUD (Create, Read, Update and Delete) operation you wish to do. This creates more traffic to the database but is normally much faster as you should be doing smaller transactions. Disconnected Architecture in ADO.NET The architecture of ADO.net in which data retrieved from database can be accessed even when connection to database was closed is called as disconnected architecture. Disconnected architecture of ADO.net was built on classes connection, dataadapter, commandbuilder and dataset and dataview. Disconnected architecture is a method of retrieving a r...

Using SQL self join Find Upper level manager in Employee table

A self-join is a query in which a table is joined (compared) to itself. Self-joins are used to compare values in a column with other values in the same column in the same table . You can use a self-join to simplify nested SQL queries where the inner and outer queries reference the same table . These joins allow you to retrieve related records from the same table. The most common case where you'd use a self-join is when you have a table that references itself I have the employee detail table, In that i want to find the manager for each Employee . The employee nam e and manager column are present in same table Consider the following Employee table CREATE TABLE Employee (     Emp_Id INT IDENTITY ( 1 , 1 ) NOT NULL PRIMARY KEY ,     Emp_Name VARCHAR ( 100 ),     Manager_Id INT NULL ) INSERT INTO Employee ( Emp_Name , Manager_Id ) VALUES ( 'a' ,null) INSERT INTO Employee ( Emp_Name , Manager_Id ) ...