locked
calling a 32bits COM dll : COMException (0x8000401A) RRS feed

  • Question

  • Hello,

    I have an asp.net application that used an external COM library.
    On my 32bits server, there is no problem.
    On my 64bits server, I register the dll without any error, but if I execute my application, I have this error :
    System.Runtime.InteropServices.COMException (0x8000401A) : Retrieving the COM class factory for component with CLSID {D63891F1-E026-11D3-A6C3-005004055C6C} failed due to the following error: 8000401a.

    I try to isolate a dll into seperate process like it was said in this topic : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2364472&SiteID=1 but I still have the same problem.

    Is there a way for a .net 64bits application to call a COM 32bits dll?

    Thanks for your feedback.

    jb
    Friday, February 1, 2008 2:32 PM

All replies

  • This  is actually an security  issue. since 8000401a is a documented error code in WinError.h: CO_E_RUNAS_LOGON_FAILURE: The server process could not be started because the configured identity is incorrect.  Check the username and password.

    See here for how to set up sufficient privileges:

    Why do I get 8000401A errors?


    Monday, February 4, 2008 6:21 AM
  • Hello,

     

    I check the article you send me. I changed the identity (Instead of local account, I choose Network Services).

    I gave  access right to the folder containing the dll to Network Services but now I got this error :

     System.UnauthorizedAccessException: Retrieving the COM class factory for component with CLSID {D63891F1-E026-11D3-A6C3-005004055C6C} failed due to the following error: 80070005

     

    If I don't create the COM+ application i got this error :

    System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {D63891F1-E026-11D3-A6C3-005004055C6C} failed due to the following error: 80040154

     

    • Proposed as answer by RaiSukhdeep Wednesday, May 12, 2010 10:07 PM
    Monday, February 4, 2008 3:41 PM
  • Also Check Properties of your eConnect Com+Application services and check for Identity tab, if its "This User" change to System account. it should work.
    Wednesday, May 12, 2010 10:10 PM