Failed Due To The Following Error 80040154

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss failed due to the following error 80040154 excel the workings and policies of this site About Us Learn more about ssis failed due to the following error 80040154 Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions

Retrieving The Com Class Factory For Component With Clsid

Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other.

Failed Due To The Following Error 80070005

Join them; it only takes a minute: Sign up Retrieving the COM class factory for component with CLSID {XXXX} failed due to the following error: 80040154 up vote 219 down vote favorite 46 I developed a Windows service using C#.NET to generate PDF report. To generate PDF file I am using a third party dll. The application is ole error 80040154 running in my Windows XP platform. When I deployed the service in Windows Server 2008 64 bit version, I got this error: Retrieving the COM class factory for component with CLSID {46521B1F-0A5B-4871-A4C2-FD5C9276F4C6} failed due to the following error: 80040154. I registered the DLL using the regsvr32 command. I able to see this CLSID in the registry. But the problem persists. What could be the problem? .net windows-services com-interop 32bit-64bit share|improve this question edited Nov 2 '09 at 16:59 Randy Levy 19.1k44275 asked Jun 24 '09 at 7:22 gopal 1,33141423 1 A web application hosted in the same server is able to generate PDF file without any error. –gopal Jun 24 '09 at 7:59 Guys I tried every possible solution but still getting this error. I have assemblies and registered them successfully but still getting same error. Really need help... –newprogress Dec 23 '13 at 11:39 add a comment| 14 Answers 14 active oldest votes up vote 311 down vote accepted In VS - project properties - in the Build tab -

, .NET Framework > Visual Basic Question 1 Sign in to vote Greetings,     I have a VB.NET application that references a 3rd

Comexception 80040154

party Com component. The file is Interop.WINTSRRLIB.dll. My VB.NET application has a project error: 80040154 class not registered reference to the COM comonent which lives in the directory:  C:\WaveTracker.     The application runs fine. When I retrieving the com class factory for component with clsid 80040154 class not registered sent it to my customer, he installed in on his desktop machine. It runs fine. Then he copied all of the application files (which live in C:\WaveTracker) to his laptop. However, http://stackoverflow.com/questions/1036856/retrieving-the-com-class-factory-for-component-with-clsid-xxxx-failed-due-to-t on his laptop, he gets the error: "System.Runtime.InteropServices.COMException (0x80040154). Retrieving the COM class factory for component xxxx failed due to the following error: 80040154"     The customer swears he has the .NET 2.0 Framework installed properly on his laptop. Any ideas on how I can get over this problem??? Kind Regards,   Scott   Tuesday, September 26, 2006 10:44 PM Reply https://social.msdn.microsoft.com/Forums/vstudio/en-US/88a6ea68-f476-4231-822f-27fabe59f458/error-80040154-retreiving-com-class-factory?forum=vbgeneral | Quote Answers 1 Sign in to vote Make sure you look in the registry of a PC on which your app works.  Don't do a search, just look through the keys in HKCR\CLSID for the GUID, they are sorted alphabetically.  The fact that you can't find a DLL that can be registered with regsvr32 is a strange problem.  If might live in another folder, c:\windows\system32 perhaps.  Look at the properties of the WinTSRRapiLib reference in your project. Also, the component may itself use another ActiveX component that requires registration.  Like the VB6 runtime files for example.Another way to debug this problem is to use the RegMon utility, available for free at www.sysinternals.com.  It shows you how your app uses the registry.  Run it on yours and run it on the customer's and compare the two. Friday, September 29, 2006 12:55 AM Reply | Quote Moderator 0 Sign in to vote i went to www.sysinternals.com and downloaded a few utilities that led me to the problem...'listdlls' and 'procexp' were very useful. The problem was simply that the 3rd party dll required other d

and HTML Data Types Tutorials Home » COM Error » Retrieving the COM class factory for component failed due to the http://digioz.blogspot.com/2011/09/retrieving-com-class-factory-for.html following error: 80040154 Retrieving the COM class factory for component failed due https://intuitdeveloper.lc.intuit.com/questions/1017707-error-80040154-class-not-registered-exception-from-hresult-0x80040154-regdb_e_classnotreg-in-requestprocessor-2 to the following error: 80040154 in COM Error - on 9:35 AM - 2 comments Despite the fact that COM Components are considered legacy technology now, because Microsoft never made a clear cut decision to retire COM Components in newer versions of their Operating System these Libraries still failed due linger around in many Applications, and have made their way into many .NET based Applications through DLL Referencing. Here is an error I have come across from time to time that doesn't tell you a whole lot unfortunately:Retrieving the COM class factory for component with CLSID {XXXXXXXX-XX...} failed due to the following error: 80040154 There are several ways to resolve this failed due to issue. Here is a short list: Modify your project's platform from 'Any CPU' to 'X86' in Project Properties, Build/Platform's Target in Visual Studio If your Application is a Web-Based Application, try setting IIS to run in 32-bit mode. You can do this by going to IIS Manager, selecting the Application Pool, then choosing "Advanced Settings". The second option from the top is "Enable 32-bit Applications". If your Application is Web-Based, it could be that the com object was not configured to allow launch and access permissions for the aspnet user identity. Under administrative tools > Component services under the tree view, go to Component Services > Computers > My Computer > DCOM Config and find the registered com object. Right click for properties. Under the security tag, customize the Permissions to allow asp.net user Usually one of the above 3 methods solves this problem. Pete Soheil DigiOz Multimedia www.digioz.com Tweet Labels: COM Error 2 comments Manu V Nath mod June 18, 2013 at 3:17 AM I cant see "Enable 32-bit Applications" in iis. Can u check below post please.http://www.codeproject.com/Qu

RequestProcessor 2 Im using quickbook pro 2013 and my machine is 64bit windows 7,and using vs2010   i have installed QBFC 11.0 libraray and newly installed QBXMLRP2 and Quickbook sdk 13.0when im going to create object of a RequestProcessor 2 using c#  it throws Retrieving the COM class factory for component with CLSID {45F5708E-3B43-4FA8-BE7E-A5F1849214CB} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)) in RequestProcessor 2. Any one can help me? Comment Asked by roshan.onsurf Options Edit Ask for details Archive hide info × Close Why do you want to report this? Spam Profanity Threats/Abuse Inappropriate Virus/Danger Broken Links Other Answer Basically, you have installed a 32-bit class library on a 64-bit OS, and your .NET assembly is not marked as 32-bit only.  Refer to this article to correct your .NET assembly. http://stackoverflow.com/questions/7197506/how-to-repair-comexception-error-80040154 Was this answer helpful? Yes No wckiv Add a comment Comment No answers have been posted This post has been closed and is not open for comments or answers. More Actions Notify me of new answers I can answer People come to Intuit Developer Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines: Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English. Be clear and state the answer right up front. Ask yourself what specific information the person re