|
| | | Forum Newbie
Group: Forum Members
Last Login: 5/2/2007 11:22:00 AM
Posts: 8, Visits: 1 |
| Hi, I have developed a windows console application to do some sftp transfers using the secure wsftp pro SDK. I created a msi package which included the Interop.WsftpSDK.dll and WsftpSDK.dll along with my exe's. When I try to execute my console app to do the transfers, it is failing witht he following error msg: 3/12/2007 1:28:31 PM Error:ExitCode(0)MessageRetrieving the COM class factory for component with CLSID {DEB78591-FA51-45FB-A504-C68555177A5B} failed due to the following error: 80040154. any help in this regard will be appreciated. Thanks, Vinod |
| |
| | | 
Time Traveler
Group: Forum Members
Last Login: Yesterday @ 8:21:35 PM
Posts: 164, Visits: 160 |
| I was also getting this error after installing .net 3.0 x64 just now, had to revert back to 2.0. Unable to log into the system.
Reason: Retrieving the COM class factory for component with CLSID {hidden} failed due to the following error: 80040154.
This should be considered a bug as 3.0 is backwards compatible with 2.0 as far as I know.
Shawn Hyde
507 536-9556
Area51 Computers & Services
Consulting and Custom Internet Solutions
Rochester, MNYou know spam is bad when your cat won't eat it. Please don't feed it to my servers. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 4/15/2008 2:11:09 PM
Posts: 1, Visits: 4 |
| Does anyone have a solution to this? I have been recently encountering this too when attempting to use this with the .NET 2.0 framework; upgrading .NET projects from 1.1 to 2.0 framework. It works great with .NET 1.1 framework, but using the same code under .NET 2.0 framework, I get "COMException was unhandled" title, "Retrieving the COM class factory for component with CLSID{DEB78591-FA51-45FB-A504-C68555177A5B} failed due to the following error: 80040154." This iw with early binding. Using late-binding, "pApi = CreateObject("WsftpSDK.WsftpApi")", I get title "Exception was unhandled", "Cannot create ActiveX component." I have 64-bit machine, but that works with 1.1 framework, so see why it wouldn't work with 2.0 framework.
Does anyone have a solution to this? I have been recently encountering this too when attempting to use this with the .NET 2.0 framework; upgrading .NET projects from 1.1 to 2.0 framework. It works great with .NET 1.1 framework, but using the same code under .NET 2.0 framework, I get "COMException was unhandled" title, "Retrieving the COM class factory for component with CLSID{DEB78591-FA51-45FB-A504-C68555177A5B} failed due to the following error: 80040154." This iw with early binding. Using late-binding, "pApi = CreateObject("WsftpSDK.WsftpApi")", I get title "Exception was unhandled", "Cannot create ActiveX component." I have 64-bit machine, but that works with 1.1 framework, so see why it wouldn't work with 2.0 framework. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 8/7/2008 11:26:49 AM
Posts: 2, Visits: 3 |
| | I'm receiving this same error. Using VS 2008 .NET 3.5 64 bit. Doesn't look like a 64 bit issue, but rather a framework issue. Any updates/solutions? Retrieving the COM class factory for component with CLSID {DEB78591-FA51-45FB-A504-C68555177A5B} failed due to the following error: 80040154 |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 10/6/2008 4:48:39 PM
Posts: 2, Visits: 5 |
| rajjr_tx (8/1/2008)
I'm receiving this same error. Using VS 2008 .NET 3.5 64 bit. Doesn't look like a 64 bit issue, but rather a framework issue. Any updates/solutions? Retrieving the COM class factory for component with CLSID {DEB78591-FA51-45FB-A504-C68555177A5B} failed due to the following error: 80040154 Have a customer receiving the exact same error - initally thought it was because the DLL was not registered but now it appears to be a framework issue. Would love to hear about any updates or solutions. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 10/6/2008 4:48:39 PM
Posts: 2, Visits: 5 |
| | Update: IPSwitch recommended doing my build using the x86 option which allowed me to get farther but it was not until they sent me a new WsftpSDK.dll did my problem get solved. |
| |
|
|