471,075 Members | 720 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,075 software developers and data experts.

Invoking Excel COM object with CLSID is either not valid

rjn
Hi

I'm invoking the excel object from ASP.Net application. My development
machine is Windows 2000 and MS Office is installed on my m/c. I have
added reference to the Excel COM object, I have given Access and launch
permissions to ASPNET user in DCOMCNFG and the identity set to launch
user. But I get the following error, moment I try to create the Excel
object: Dim oexcel As New Excel.Application

"COM object with CLSID {00024500-0000-0000-C000-000000000046} is either
not valid or not registered"

The same DCOM config settings work fine in Windows xp.

Also I have observed that (in xp), the excel objects are still in memory
even after the application is terminated and I could see multiple such
objects in task manager. I close the excel object by calling quit. How
do I destroy the objects?

Regards

rjn

Apr 8 '06 #1
4 1685
Ummm... Using Excel automation and ASP .net, is not recommended by Microsoft:

http://support.microsoft.com/kb/257757/en/

If you want to generate excel files, have you think about using something
more lightweight like XMLSS (Excel XML) or ADO .net ?

Good luck
Braulio
--
/// ------------------------------
/// Braulio DÃ*ez Colaborador DNM
///
/// http://www.dotnetmania.com
/// My Site (.net Tips): http://www.bdiez.com
/// ------------------------------


"rjn" wrote:
Hi

I'm invoking the excel object from ASP.Net application. My development
machine is Windows 2000 and MS Office is installed on my m/c. I have
added reference to the Excel COM object, I have given Access and launch
permissions to ASPNET user in DCOMCNFG and the identity set to launch
user. But I get the following error, moment I try to create the Excel
object: Dim oexcel As New Excel.Application

"COM object with CLSID {00024500-0000-0000-C000-000000000046} is either
not valid or not registered"

The same DCOM config settings work fine in Windows xp.

Also I have observed that (in xp), the excel objects are still in memory
even after the application is terminated and I could see multiple such
objects in task manager. I close the excel object by calling quit. How
do I destroy the objects?

Regards

rjn

Apr 8 '06 #2
RJN
Thanks for your reply. Can you give more inputs on generating excel
using XMLSS and ADO.Net?

*** Sent via Developersdex http://www.developersdex.com ***
Apr 8 '06 #3
Here you have some material,

About ADO and Excel:

http://www.dotnetjohn.com/articles.aspx?articleid=36
http://www.dotnetjohn.com/articles.aspx?articleid=54
http://www.c-sharpcorner.com/Code/20...essExcelDb.asp

About XMLSS:

http://www.codeproject.com/csharp/ex...preadsheet.asp

Good Luck
Braulio

--
/// ------------------------------
/// Braulio DÃ*ez Colaborador DNM
///
/// http://www.dotnetmania.com
/// My Site (.net Tips): http://www.bdiez.com
/// ------------------------------


"RJN" wrote:
Thanks for your reply. Can you give more inputs on generating excel
using XMLSS and ADO.Net?

*** Sent via Developersdex http://www.developersdex.com ***

Apr 10 '06 #4
Your first issue is about backwards compatability in .NET Interop, not
permissions.
Your second issue is probably permission related.
Please see the following articles which solve both issues, respectively:
1. "Achieving Backward Compatibility with .NET Interop: Excel as Case
Study" - http://www.devcity.net/Articles/163/1/article.aspx
2. "50 Ways to Kill Excel" -
http://www.devcity.net/Articles/239/1/article.aspx

--scott

"rjn" wrote:
I'm invoking the excel object from ASP.Net application. My development
machine is Windows 2000 and MS Office is installed on my m/c. I have
added reference to the Excel COM object, I have given Access and launch
permissions to ASPNET user in DCOMCNFG and the identity set to launch
user. But I get the following error, moment I try to create the Excel
object: Dim oexcel As New Excel.Application

"COM object with CLSID {00024500-0000-0000-C000-000000000046} is either
not valid or not registered"
The same DCOM config settings work fine in Windows xp.
Also I have observed that (in xp), the excel objects are still in memory
even after the application is terminated and I could see multiple such
objects in task manager. I close the excel object by calling quit. How
do I destroy the objects?

Jun 19 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Jane | last post: by
reply views Thread by Prasad Patil | last post: by
4 posts views Thread by Ahmed | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.