Retrieving the COM class factory for component with CLSID{ XXX} ERROR: 80040154

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rani1984
    New Member
    • Sep 2010
    • 2

    #1

    Retrieving the COM class factory for component with CLSID{ XXX} ERROR: 80040154

    It was working fine until last week. When I removed and added reference to my project I started getting this error.

    I registered the DLL using regsvr32. It was successful. But when I looked for the CLSID in registery couldn't find any.
    Please help me I am stuck here.

    Any comments will be appreciated.
    Thank you
  • Frinavale
    Recognized Expert Expert
    • Oct 2006
    • 9749

    #2
    I see this problem all the time.
    I just fixed this issue earlier today actually...
    1. Unregister the DLL
    2. Restore the old DLL
    3. Use the regsvr32 tool to unregister it.
    4. Reregister the new DLL.
    5. Open your project, remove the reference and then re add the reference by browsing to the directory with the DLL into it (don't use the "most recent" option)


    If this doesn't fix the problem,
    1. Unregister the DLL
    2. Open Regedit (hit the windows key + "r" and type regedit)
    3. Search the registry for your DLL and delete anything that has to do with it.
    4. Then reregister the DLL
    5. Then open your project, remove the reference and then re add the reference by browsing to the directory with the DLL into it (don't use the "most recent" option)


    -Frinny

    Comment

    • rani1984
      New Member
      • Sep 2010
      • 2

      #3
      I tried all the steps you suggested. But so far no luck. I still get the same "Retrieving the COM class factory" ERROR, when i try to access the page. However I did find the CLSID in Wow6432Node Directory in registry.

      Comment

      • irina45
        New Member
        • Oct 2011
        • 4

        #4
        I had the same problem running C# code with reference to a COM dll.
        Changing platform from AnyCPU to x86 didn't help.
        Changing the reference property "Isolated" to True inside the C# project, solved the problem.
        Also, all the files created by compilation should be copied together with exe:
        *.exe.manifest
        *.pdb
        *.dll
        Interop.*.dll

        Comment

        • Frinavale
          Recognized Expert Expert
          • Oct 2006
          • 9749

          #5
          The "pdb" file is not needed in the released enfironment.
          It contains debugging information.
          See the MSDN article about PDB Files.

          Comment

          Working...