Im using a 3rd party dll for CC processing. To use this dll, I had to install WSE 3.0. All is good locally, but it didnt work when I uploaded to the testing server. I asked by boss to install WSE 3.0 on the server so that I could use the dll. He installed
it and I get the following error:
Retrieving the COM class factory for component with CLSID {698BFD43-76AA-4D13-98FE-5BE9FF5E05B8} failed due to the following error: 80040154.
[COMException (0x80040154): Retrieving the COM class factory for component with CLSID {698BFD43-76AA-4D13-98FE-5BE9FF5E05B8} failed due to the following error: 80040154.] CyberSource.WSSecurity.Signature..cctor() in S:\ccviews\eolano_laptop\icswsclients\security\dotnet2\Signature.cs:14
Any ideas? I havent been able to find anything to really help me out. Did he possibly forget to do something additional when installing? I've never worked with COM before so im kinda lost.
Yes. This is what their(cybersource) support guy is telling me also. I handed this off to our server admins' to register the .dll and its not registering. It says the specified module cannot be found and I'm in the directory. I didnt think that dll's required
registration to the server in .NET?
It works fine locally, but error-ing out on development server.
Here is some of the responses I got from their techincal support that helped me solve this. I didnt solve this personally b/c the IT guy was installing the client/dll's and not me, but I helped them through the proccess with the following:
The stack trace appears to reference problems with the CybsWSSecurity.dll. This dll may not have been registered on the server correctly. To register the dll, go to Start > Run and then type the following:
regsvr32 "<pathToDll>\CybsWSSecurity.dll"
The dll should be located in the client's lib folder within the client's installation directory.
CybsWSSecurity.dll will need to be registered on the server for the client to work. The "specified module could not be found" error happens if the dll doesn't exist in the directory where regsvr32 is pointed. This may be because the dll name is misspelled
(note that it is case-sensitive) or that the directory path itself is incorrect.
I think the problem was that it wasnt being registered from the right path. I can find out more info for you on Monday and ask exactly what he did if this doesnt work for you.
In case somebody still need help, here are two things which have to be done.
1. Install the WSE 3, download the msi from microsoft
2. Install the cybersource simple api, copy over from other box and reg32 will not work, you have to install it from the SDK downloaded from cybersource
after install the simapi-net2.0-5.0.2.msi then you can copy over the dlls if not done yet
CSharpSean
Contributor
5464 Points
917 Posts
COM problem - - Retrieving the COM class factory for component
Feb 05, 2007 01:57 PM|LINK
Im using a 3rd party dll for CC processing. To use this dll, I had to install WSE 3.0. All is good locally, but it didnt work when I uploaded to the testing server. I asked by boss to install WSE 3.0 on the server so that I could use the dll. He installed it and I get the following error:
Retrieving the COM class factory for component with CLSID {698BFD43-76AA-4D13-98FE-5BE9FF5E05B8} failed due to the following error: 80040154.
[COMException (0x80040154): Retrieving the COM class factory for component with CLSID {698BFD43-76AA-4D13-98FE-5BE9FF5E05B8} failed due to the following error: 80040154.]CyberSource.WSSecurity.Signature..cctor() in S:\ccviews\eolano_laptop\icswsclients\security\dotnet2\Signature.cs:14
jcw14
Contributor
2919 Points
577 Posts
Re: COM problem - - Retrieving the COM class factory for component
Feb 12, 2007 04:18 PM|LINK
I'm pretty sure that cybswssecurity.dll is not registered properly. Try running Regsvr32 cybswssecurity.dll
My Blog: http://www.wintersfamily.plus.com/blogs/JamesWinters
CSharpSean
Contributor
5464 Points
917 Posts
Re: COM problem - - Retrieving the COM class factory for component
Feb 14, 2007 07:10 PM|LINK
Yes. This is what their(cybersource) support guy is telling me also. I handed this off to our server admins' to register the .dll and its not registering. It says the specified module cannot be found and I'm in the directory. I didnt think that dll's required registration to the server in .NET?
It works fine locally, but error-ing out on development server.
Harshal Chav...
Member
13 Points
14 Posts
Re: COM problem - - Retrieving the COM class factory for component
Mar 10, 2007 09:42 AM|LINK
hi
did u find any solution for it
because i am facing the same problem here with cybersource
CSharpSean
Contributor
5464 Points
917 Posts
Re: COM problem - - Retrieving the COM class factory for component
Mar 10, 2007 04:32 PM|LINK
Here is some of the responses I got from their techincal support that helped me solve this. I didnt solve this personally b/c the IT guy was installing the client/dll's and not me, but I helped them through the proccess with the following:
The stack trace appears to reference problems with the CybsWSSecurity.dll. This dll may not have been registered on the server correctly. To register the dll, go to Start > Run and then type the following:
regsvr32 "<pathToDll>\CybsWSSecurity.dll"
The dll should be located in the client's lib folder within the client's installation directory.
CybsWSSecurity.dll will need to be registered on the server for the client to work. The "specified module could not be found" error happens if the dll doesn't exist in the directory where regsvr32 is pointed. This may be because the dll name is misspelled (note that it is case-sensitive) or that the directory path itself is incorrect.
I think the problem was that it wasnt being registered from the right path. I can find out more info for you on Monday and ask exactly what he did if this doesnt work for you.
Harshal Chav...
Member
13 Points
14 Posts
Re: COM problem - - Retrieving the COM class factory for component
Mar 12, 2007 08:15 AM|LINK
hi i get solved the problem
i just uploaded the wssecurity.dll in the bin folder
and then registered it
thnx for reply
Somzy
Member
2 Points
1 Post
Re: COM problem - - Retrieving the COM class factory for component
Jun 25, 2007 10:56 PM|LINK
HI Harshal,
I am getting the same problme. I have added to the bin folder but when I try to register i get the Module NOt found error. Can you help. Its urgent.
chunyisong
Member
2 Points
1 Post
Re: COM problem - - Retrieving the COM class factory for component
Oct 06, 2007 12:38 PM|LINK
In case somebody still need help, here are two things which have to be done.
1. Install the WSE 3, download the msi from microsoft
2. Install the cybersource simple api, copy over from other box and reg32 will not work, you have to install it from the SDK downloaded from cybersource
after install the simapi-net2.0-5.0.2.msi then you can copy over the dlls if not done yet
WSE 3.0 Cybersource
thomhoward
Member
2 Points
1 Post
Re: COM problem - - Retrieving the COM class factory for component
Oct 16, 2007 08:55 PM|LINK
Also, once the DLL has been registered, you will probably have to restart IIS to get it to work properly.
mrtomcatthef...
Member
32 Points
8 Posts
Re: COM problem - - Retrieving the COM class factory for component
Nov 21, 2007 09:34 PM|LINK
I've been having the same problem but was able to get it to run on a 32bit machine.
the problem here is that we're trying to make it work on a 64bit machine and I have been completely unsuccesful on that level
Any advise on a 64 bit install?
Thanks