COM object with CLSID is either not valid or registered issue with ASP.NET not Windows.

Discussion in 'ASP .Net' started by Jen, Feb 19, 2004.

  1. Jen

    Jen Guest


    I'm having an issue calling a dll from an ASP.NET page. The code that
    tries to instantiate a COM dll (class) is in a Class Library. I can
    call the code successfully from a windows application in the same
    solution but if I try to call the code from the web application I get
    the error:

    COM object with CLSID {E0BCDB1B-6B9B-4FD0-A61C-1AB848DB0720} is either
    not valid or not registered.
    Description: An unhandled exception occurred during the execution of
    the current web request. Please review the stack trace for more
    information about the error and where it originated in the code.

    Exception Details: System.Runtime.InteropServices.COMException: COM
    object with CLSID {E0BCDB1B-6B9B-4FD0-A61C-1AB848DB0720} is either not
    valid or not registered.

    It's happening on the instantiation line ie:

    I have tried:
    - changing "machine" to "SYSTEM" in the machine.config file
    - adding ASPNET user to the web directory, the windows app directory
    (where the class library is) and the directory where the dll is
    registered (under C:\Program Files\<Supplier>\ with read & execute,
    read, and write privileges.
    - creating a new project which only has one web page that tries to
    instantiate the class.

    I'm at a loss as to why it works for the windows application but not
    the web application. If anyone has any suggestions they would be
    greatly appreciated - I'm beginning to feel like I've tried all the
    standard responses that seem to be posted about this issue.

    Jen, Feb 19, 2004
    1. Advertisements

  2. Jen

    Jen Guest

    More Information..

    I has assumed that I needed to update the machine.config for the
    earlier framework as I was running this from VS.NET 2002 (and also
    have 2003 on my machine). So I updated the other machine.config and
    it works.

    However I'm at a loss to work out what I need to change security wise
    to make it work as I obviously can't be using the SYSTEM account in a
    production environment.

    I added ASPNET account to the web directory, to the bin subdirectory,
    to the other windows folders (for like the class libaries) and the
    directory where the dll is installed. I can't think what else to try.

    Any advice would be greatly appreciated!!

    Jen, Feb 20, 2004
    1. Advertisements

  3. Jen


    Feb 18, 2010
    Likes Received:
    Machine.config changes

    Hi Jen,

    I am having this problem, with .NET2.0 though. ASPNET user cannot instantiate a COM object, I gave ASPNET access to the folder the COM object resides, it did not help. Also, just in case, in Component Manager I added ASPNET to the list of default users who can have access or activate DCOM objects although this COM object is not listed there. None of these helped.

    Would you be able to let me know what exactly you changed in the machine.config?

    mehrbod, Feb 18, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.