COM class factory for component with CLSID {EFAC2D80-175B-11D2-9927-006097C27C31} failed due to the following error: 800040005.
Hi,
I am developing an ASP/C#.NET solution in Visual Studio 2013 Ultimate. A client of mine has requested to validate users and connect my system to their existing document management database through a 32bit library called DFC.DLL (Documentum Foundation Classes), so when users type their user and password they are validated in their Documentum user and password ('inline').
I installed the libraries from the DFC packages, and then added the library as a COM reference.
I don't understand why it is not working, since the client have an easy and working sample, in a different machine, wich I have copied almost exactly the code.
Please yur help, almost urgently.
Thanks a lot!
I am developing an ASP/C#.NET solution in Visual Studio 2013 Ultimate. A client of mine has requested to validate users and connect my system to their existing document management database through a 32bit library called DFC.DLL (Documentum Foundation Classes), so when users type their user and password they are validated in their Documentum user and password ('inline').
I installed the libraries from the DFC packages, and then added the library as a COM reference.
I don't understand why it is not working, since the client have an easy and working sample, in a different machine, wich I have copied almost exactly the code.
Please yur help, almost urgently.
Thanks a lot!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
sorry my delay.
I don't have a Syswow64 folder, it is a Windows 7 32 bits.
At the Path level I do have the right folder path.
I don't have a Syswow64 folder, it is a Windows 7 32 bits.
At the Path level I do have the right folder path.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sara, I think your answers were helpfull, I learned from them and potentially can bring people to get the solution to similar or the same problem but I don't know how should I assign points in this case (I resolved in a different way), can you make a suggestion?
Jose, thank you. you may close the question and choose your own comment (0 points) as the accepted solution. then give an assist to comments which have helped.
Sara
and the problem magically got fixed... don't know why, but it worked.i read the article and it seems that they started visual studio as administrator. that could be necessary for visual studio older than vs2008 and to successfully register an active-x control once for a new user. if you followed that advice, it could explain why it suddenly worked and since registration normally is a one-off, it now worked also when starting visual studio as a normal user.
Sara
ASKER
No, I am using Visual Studio 2013 and I tested that activating the "Build/Exception" part worked as a charm for 2 development computers we have (Windows 7 Professional 32 bits English version).
I tested that activating the "Build/Exception" part worked as a charm
interesting. thanks for the information.
Sara
ASKER
Thank you Sara.
Have a great day!
Have a great day!
ASKER
Finally I resolved as I explain above: "I tested that activating the "Build/Exception" part in Visual Studio 2013 worked as a charm"
ASKER