Intermittent "Instantiating the dispatch object for method ... failed" Messages
Bert
functions for testing purposes. The functions themselves are no
different from the DocSample1 functions. I've compiled the DLL,
registering it in the process, used the WSDL Generator from the SOAP
Toolkit 2, edited the wsdl file to correct any URL problems, then
created a simple VB client app.
The client app is pretty much the same as the DocSample1 client.
However, when run, I notice some odd behaviour:
When run and initialised, the first function call works ok.
A second function call also works fine.
The third fails with the "Instantiating ..." message mentioned above.
The fourth call works fine.
So does the fifth.
The sixth call fails again.
I've run the application and tried calling the functions any number of
times and EVERY third call fails!!!
Can anyone explain this???
Thanks,
Bert
Roger Wolter
by the ISAPI on a single proc machine. You might want to change this to see
if it makes a difference. Also try some of the example applications to see
if this behavior is reproducible.
"Bert" <be...@manchurianmedia.com> wrote in message
news:30244002.01082...@posting.google.com...
Raj T. Mana
following steps in the VB code will reproduce the problem.
1) Create the SoapClient object
2) Initialize the SoapClient with he WSDL file for the COM component
3) Call a method in the component
It is giving the following error message
----------------------------Error
Start-------------------------------------------
Run-time Error '-2147024891 (80070005)':
WSDLOperation: Instantiating the dispatch object for method ReceiveFileData
failed
----------------------------Error
End---------------------------------------------
NOTE:- This was working perfectly couple of days ago. The only change went
into this was the rebuilding
of the component and the corresponding WSDL and related files.
When I try to do the same stuff through an ASP page, I am getting the
following error message
-----------------------------Error
Start------------------------------------------
Error Type:
SOAP-ENV:Server (0x800A13BA)
Connector - Bad request to the server.
/Xpediator/TDS/Pages/PostMessage/TDS_UIPostMsg.asp, line 810
Browser Type:
Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Page:
POST 22699 bytes to /Xpediator/TDS/Pages/PostMessage/TDS_UIPostMsg.asp
POST Data:
error '80020009'
Exception occurred.
/iisHelp/common/500-100.asp, line 192
----------------------------Error
End----------------------------------------------
"Bert" <be...@manchurianmedia.com> wrote in message
news:30244002.01082...@posting.google.com...
Laurence Everitt
You are getting what I have received a few times...
Check your VB Project settings. If you have "No compatability" set on the
component, then the COM object will be recreated with different ID's every
time that you recompile the COM object and you have to rerun the WSDL
Generator over the COM object and use this new WSDL for the SOAP Service.
To get round this is very simple. All you have to do is Make a copy of your
COM object with "No Compatibility" set in the Project settings and name
the file something like BaseMyCOMObject.DLL - where MyCOMObject
is the name of your COM object. SAVE THIS FILE and KEEP IT SAFE.
This is the base DLL that you create to be compatible with. Next, you change
the VB Project settings for your COM object to be "Binary Compatible" with
your BaseMyCOMObject.DLL file and Make your COM Object, naming
it as MyCOMObject.DLL, etc. You can then use the WSDL Generator to
Generate the WSDL/WSML files that will work with this COM object.
This means that every time you Make your COM object, you need not regenerate
the WSDL/WSML files. However, if you EVER need to change any interfaces
or add extra methods, etc, you will need to go through the above process
again
and regenerate the WSDL/WSML files (as I have found to my cost!)
Regards,
Laurence Everitt
"Raj T. Mana" <pri...@nospam.com> wrote in message
news:#rd4FRKPBHA.1524@tkmsftngp05...