Retrieving the COM class factory for component with CLSID {60434CA9-132A-11D5-B14F-00C04F79D784} failed due to the following error: 80040154.
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: Retrieving the COM class factory for component with CLSID {60434CA9-132A-11D5-B14F-00C04F79D784} failed due to the following error: 80040154.
I am having this problem with my site. I moved it from one machine to another, it works on the original and does not on the backup.
Please have a look at this to check if it suits your need:
When you run the .net Code in X64 Environment you will get the following error message.
" Failed --Retrieving the COM class factory for component with CLSID ...."
E.g. in CMS Export / Import server side .net code = "ExportSiteContentIncremental(...) Failed --Retrieving the COM class factory for component with CLSID {CA0752B3-021C-4F99-82E3-2C0F19C5E953} failed due to the following error: 80040154."
WORKAROUND:
The possible workaround is modify your project's platform from 'Any CPU' to 'X86' (in Project's Properties, Build/Platform's Target)
ROOTCAUSE
The VSS Interop is a managed assembly using 32-bit Framework and the dll contains a 32-bit COM object. If you run this COM dll in 64 bit environment, you will get the error message.
NOTE:If you find my response contains a reference to a third party World Wide Web site, I am providing this information as a convenience to you.Microsoft does not control these sites and has not tested any software or information found on these sites; therefore,Microsoft cannot make any representations regarding the quality,safety, or suitability of any software or information found there.
__________________________________________________
Sincerely,
Young Fang
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
right click on the Setup package you created for it
Then, Click on the Configuration manager button
Under Platform, there's a dropdown where you'll see it says Any CPU - click on the dropdown - if you don't see X86, then create a New one - it will bring up a small form that should get you where you want.
Also - in the project Properties - click on compile, and then the Advanced compile optiions and set the target platform there.
OK where in the world do you see this x86? I am using VS2008 and I built a website not an exe app. I don't see property but I do see Property Pages. That has nothing at all about x86
Me, I have exactly the same problem; An ASP.NET application that was running correctly on Windows server 2003 but does not work anymore (Showing above famous message) as soon
as I transferred it on Windows Server 2008. The DLL is Interop.Encryption which is a higher level consumer of Encryption.DLL. I have installed a DLL dependency detector (Dependency Walker) application toolkit and finally find out that the problematic DLL
that caused all these issues is MSVBM60.DLL which is Microsoft Visual Basic 6 run time ActiveX installed on new server.
Does anybody knows the easy step by step solution for this problem? Please help me out! but not with referral articles, I'm not interested for any hightech paper to read and
add my knowledge about the advanced Microsoft VB6 compatibility structure on 64 bit machines with COM object fan outs, etc. [I believe this problem must not not happen at all for a 2004 Dll running on 2008 OS version; is Microsoft's job to read its DLLs' issues and
upgrade them as they must…]
Mattaul
0 Points
1 Post
Retrieving COM class factory failed due to the following error: 80040154
Jun 06, 2007 03:53 PM|LINK
Retrieving the COM class factory for component with CLSID {60434CA9-132A-11D5-B14F-00C04F79D784} failed due to the following error: 80040154.
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: Retrieving the COM class factory for component with CLSID {60434CA9-132A-11D5-B14F-00C04F79D784} failed due to the following error: 80040154.
I am having this problem with my site. I moved it from one machine to another, it works on the original and does not on the backup.
Young Fang -...
All-Star
17147 Points
1620 Posts
Re: Retrieving COM class factory failed due to the following error: 80040154
Jun 11, 2007 07:00 AM|LINK
Hi,
Please have a look at this to check if it suits your need:
When you run the .net Code in X64 Environment you will get the following error message.
" Failed --Retrieving the COM class factory for component with CLSID ...."
E.g. in CMS Export / Import server side .net code = "ExportSiteContentIncremental(...) Failed --Retrieving the COM class factory for component with CLSID {CA0752B3-021C-4F99-82E3-2C0F19C5E953} failed due to the following error: 80040154."
WORKAROUND:
The possible workaround is modify your project's platform from 'Any CPU' to 'X86' (in Project's Properties, Build/Platform's Target)
ROOTCAUSE
The VSS Interop is a managed assembly using 32-bit Framework and the dll contains a 32-bit COM object. If you run this COM dll in 64 bit environment, you will get the error message.
__________________________________________________
Sincerely,
Young Fang
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
dailywake
Member
5 Points
6 Posts
Re: Retrieving COM class factory failed due to the following error: 80040154
Oct 15, 2007 01:35 PM|LINK
Hello,
I have same porblem, but i have Microsoft Visual Studio .NET 2003 , i can't found choose in build x86 or any CPU
what soluation.
SuiteMac
Member
2 Points
1 Post
Re: Retrieving COM class factory failed due to the following error: 80040154
Nov 15, 2007 04:57 PM|LINK
YF,
I have had a similar error, and tried your solution, but the error persists. Could this result from not having the COM object installed or registered?
augustwind
All-Star
35860 Points
4900 Posts
ASPInsiders
Moderator
Re: Retrieving COM class factory failed due to the following error: 80040154
Nov 15, 2007 09:12 PM|LINK
right click on the Setup package you created for it
Then, Click on the Configuration manager button
Under Platform, there's a dropdown where you'll see it says Any CPU - click on the dropdown - if you don't see X86, then create a New one - it will bring up a small form that should get you where you want.
Also - in the project Properties - click on compile, and then the Advanced compile optiions and set the target platform there.
All Things Dot Net
Stored Procs and Code in a Flash!
ASP.Net Sitemap Creator
sandeep2020
Member
2 Points
1 Post
Re: Retrieving COM class factory failed due to the following error: 80040154
Dec 15, 2007 10:39 AM|LINK
Hi, we did the same(Changed the platform to X86) still we are getting same error.
Please help us.
Thanks in advance
Regards
Sandeep
dajohnson
Member
2 Points
1 Post
Re: Retrieving COM class factory failed due to the following error: 80040154
Jul 10, 2010 07:38 AM|LINK
This did work for my app, give it a try, might not work for all.
daranee
Member
2 Points
1 Post
Re: Retrieving COM class factory failed due to the following error: 80040154
Jul 19, 2010 08:57 PM|LINK
This works!
rontap1969
Member
2 Points
3 Posts
Re: Retrieving COM class factory failed due to the following error: 80040154
Sep 22, 2010 04:49 PM|LINK
OK where in the world do you see this x86? I am using VS2008 and I built a website not an exe app. I don't see property but I do see Property Pages. That has nothing at all about x86
a.Oveissian
Member
6 Points
6 Posts
Re: Retrieving COM class factory failed due to the following error: 80040154
May 24, 2011 06:04 PM|LINK
Me, I have exactly the same problem; An ASP.NET application that was running correctly on Windows server 2003 but does not work anymore (Showing above famous message) as soon as I transferred it on Windows Server 2008. The DLL is Interop.Encryption which is a higher level consumer of Encryption.DLL. I have installed a DLL dependency detector (Dependency Walker) application toolkit and finally find out that the problematic DLL that caused all these issues is MSVBM60.DLL which is Microsoft Visual Basic 6 run time ActiveX installed on new server.
Does anybody knows the easy step by step solution for this problem? Please help me out! but not with referral articles, I'm not interested for any hightech paper to read and add my knowledge about the advanced Microsoft VB6 compatibility structure on 64 bit machines with COM object fan outs, etc. [I believe this problem must not not happen at all for a 2004 Dll running on 2008 OS version; is Microsoft's job to read its DLLs' issues and upgrade them as they must…]
Thanks