I have developed a .NET COM object to talk to a Web Service. I can create an object using CreateObject(“COM.Class”) in domino designer 5.0.8 and VB 6 (Both are non .NET envs) and access interface methods. For some reason, in Designer 6.0.2CF2, I get an error “Cannot create automation object”. I can view the component in Ole Classes list in the designer. Am I missing something? I have spent more than 8 hours on this problem and haven’t found any answer. Hope some one has an answer!
Subject: RE: Cannot create .NET COM object - a bug - Notes Support?
First, this forum has absolutely nothing to do with support. Second, the problem has been reported in this forum before, and a solution given. Many times. You need to register the COM server for Notes, nlsxbe.dll, using regsvr32.
Subject: RE: Cannot create .NET COM object - a bug - Notes Support?
I have looked at similar problems, but unfortunately none of them offered any solution. I am aware of nlxbe.dll and I re-registered it. I think COM object would not have worked if that was the problem. My problem is only with .NET Components and is specific to 6.0. Everything works fine on 5…x.x version.
Anyway I did not mean to waste anybody’s time. Thank you very much for your reply. I have noticed that in the past some of the Notes staff used to reply to messages (ex. Julie K), hence thought, if somebody has any known bug information, they would post it.
Thanks again and I would appreciate if anybody share any more info on this problem.
Subject: RE: Cannot create .NET COM object - a bug - Notes Support?
Sorry – my misread. Is the Framework available on all of the machines where the code is used (not just the taget machine)? (You shouldn’t need the SDK, just the runtime.)
Subject: RE: Cannot create .NET COM object - a bug - Notes Support?
Hi Stan,
Yes, .NET 1.1 runttime files are installed on the machine that is trying to instantiate the component. I had SoapConnect installed and had replaced the existing xml4j.jar files with the soapconnect ones. I even revertd these back. But, no luck so far.
SoapConnect failed miserably to connect with .NET service. The SoapClient object does not create a blank string for soapaction property and fails to connect to the webservice. Right now I am totally frustrated.
6.x can create COM objects without any problem. So, I created another COM component in VB6 and wrapped my .NET component in it. This one too works fine on domino 5.x.x and fails on 6.0. This time it does not say “cannot create an automation object” but says that file or assembly name or one of its dependencies cannot be found. Actually when I trace it, it fails on CreateObject method for .NET component. Is this a bug? It would save me my sanity if someone confirms that it is a bug or otherwise.