WSDL: Instantiating the dispatch object - XML SOAP

This is a discussion on WSDL: Instantiating the dispatch object - XML SOAP ; Points to check.... 1. Make a note of all CLSIDs / ProgIDs relating to the DLL 2. UnRegister the DLL 3. Go through the registry looking for all entries relating to DLL which are still in the registry and manually ...

+ Reply to Thread
Results 1 to 7 of 7

WSDL: Instantiating the dispatch object

  1. Default WSDL: Instantiating the dispatch object

    Points to check....

    1. Make a note of all CLSIDs / ProgIDs relating to the DLL

    2. UnRegister the DLL

    3. Go through the registry looking for all entries
    relating to DLL which are still in the registry and
    manually deleted them. (There may be some left lurking,
    even though the app has been unregistered)

    4. Re-Register the DLL.


    The main CLSIDs just removed (via regsvr32.exe -u) where
    re-created exactly as before. You would expect this if
    you specified binary compatibility.

    However various proxystub interface CLSIDs (in
    hkey_classes_root\interface\{clsid} - which had been
    deleted manually) had changed when the DLL was re-
    registered.

    Perhaps this \interface element in the registry and in the
    SOAP toolkit needs further investigation......


    Craig




    >-----Original Message-----
    >
    >I have created a VB (v6) DLL which can be called over
    >SOAP. This dll has been working fine for months. Now I
    >have received the message "WSDLOperation: Instantiating
    >the dispatch object for method <methodname> failed" after
    >re-creating the WSDL file.
    >
    >The IIS permissions, NT file permissions, IIS anonymous
    >access and DLL binary compatibility have all been checked
    >and are fine. A backup copy of the old WSDL and WSML
    >files work perfectly ok. Why has the newly created WSDL
    >file stopped working. This was created using the Soap
    >Toolkit v2.
    >
    >Any ideas???????
    >
    >(I have have seen this error message crop up on various
    >newsgroups, but without a definitive answer or a number

    of
    >points to check.)
    >
    >
    >.
    >


  2. Default RE: WSDL: Instantiating the dispatch object

    Hello
    Set binary compatibility for the DLL to none. Then rebuild the dll and run
    the WSDL generator on the new version of the dll and see if it works
    correctly. Remember to unregister the DLL before you do this.

    Thanks
    Brian [MS]
    Microsoft Developer Support
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Content-Class: urn:content-classes:message
    | From: "Craig Duxbury" <craig.duxbury@uhb.nhs.uk>
    | Sender: "Craig Duxbury" <craig.duxbury@uhb.nhs.uk>
    | References: <12e301c37eb9$000dcda0$a301280a@phx.gbl>
    | Subject: WSDL: Instantiating the dispatch object
    | Date: Mon, 22 Sep 2003 09:01:40 -0700
    | Lines: 57
    | Message-ID: <033f01c38122$cf496230$a101280a@phx.gbl>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="iso-8859-1"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    | Thread-Index: AcOBIs9J63jwGMsaS5ylJoWxQaal8A==
    | Newsgroups: microsoft.public.xml.soapsdk
    | Path: cpmsftngxa06.phx.gbl
    | Xref: cpmsftngxa06.phx.gbl microsoft.public.xml.soapsdk:11062
    | NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    | X-Tomcat-NG: microsoft.public.xml.soapsdk
    |
    | Points to check....
    |
    | 1. Make a note of all CLSIDs / ProgIDs relating to the DLL
    |
    | 2. UnRegister the DLL
    |
    | 3. Go through the registry looking for all entries
    | relating to DLL which are still in the registry and
    | manually deleted them. (There may be some left lurking,
    | even though the app has been unregistered)
    |
    | 4. Re-Register the DLL.
    |
    |
    | The main CLSIDs just removed (via regsvr32.exe -u) where
    | re-created exactly as before. You would expect this if
    | you specified binary compatibility.
    |
    | However various proxystub interface CLSIDs (in
    | hkey_classes_root\interface\{clsid} - which had been
    | deleted manually) had changed when the DLL was re-
    | registered.
    |
    | Perhaps this \interface element in the registry and in the
    | SOAP toolkit needs further investigation......
    |
    |
    | Craig
    |
    |
    |
    |
    | >-----Original Message-----
    | >
    | >I have created a VB (v6) DLL which can be called over
    | >SOAP. This dll has been working fine for months. Now I
    | >have received the message "WSDLOperation: Instantiating
    | >the dispatch object for method <methodname> failed" after
    | >re-creating the WSDL file.
    | >
    | >The IIS permissions, NT file permissions, IIS anonymous
    | >access and DLL binary compatibility have all been checked
    | >and are fine. A backup copy of the old WSDL and WSML
    | >files work perfectly ok. Why has the newly created WSDL
    | >file stopped working. This was created using the Soap
    | >Toolkit v2.
    | >
    | >Any ideas???????
    | >
    | >(I have have seen this error message crop up on various
    | >newsgroups, but without a definitive answer or a number
    | of
    | >points to check.)
    | >
    | >
    | >.
    | >
    |


  3. Default RE: WSDL: Instantiating the dispatch object

    Hello
    Remember VB does not always play fair with binary Compatibility. For
    example when you add new methods to your class VB will keep the same GUID
    and progID and add information to forward old clients to the new class.
    According to COM when you change the interface you should change the name
    and GUID of the object. So I don't know if this is part of what is causing
    the problem or not. If the old WSDL and WSML work I would compare the old
    with the new to see if there are any difference. The WSML will have progID
    and dispID of the method. If the two are different then you have a problem.
    And my guess would be with the way VB is building the DLL with binary
    compatibility.

    Thanks
    Brian [MS]
    Microsoft Developer Support
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Content-Class: urn:content-classes:message
    | From: "Craig Duxbury" <craig.duxbury@uhb.nhs.uk>
    | Sender: "Craig Duxbury" <craig.duxbury@uhb.nhs.uk>
    | References: <12e301c37eb9$000dcda0$a301280a@phx.gbl>
    <033f01c38122$cf496230$a101280a@phx.gbl>
    <7edpLjSgDHA.2556@cpmsftngxa06.phx.gbl>
    | Subject: RE: WSDL: Instantiating the dispatch object
    | Date: Tue, 23 Sep 2003 05:44:43 -0700
    | Lines: 122
    | Message-ID: <109b01c381d0$761a1f70$a401280a@phx.gbl>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="iso-8859-1"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    | Thread-Index: AcOB0HYahcdLZgVGQG682utPdFvBEg==
    | Newsgroups: microsoft.public.xml.soapsdk
    | Path: cpmsftngxa06.phx.gbl
    | Xref: cpmsftngxa06.phx.gbl microsoft.public.xml.soapsdk:11071
    | NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
    | X-Tomcat-NG: microsoft.public.xml.soapsdk
    |
    | Thanks for the post.
    |
    |
    | Setting Binary Compatibility to NONE would cause existing
    | apps to fail. So not a good idea, in this case.
    |
    |
    |
    | Craig
    |
    |
    |
    |
    | >-----Original Message-----
    | >Hello
    | >Set binary compatibility for the DLL to none. Then
    | rebuild the dll and run
    | >the WSDL generator on the new version of the dll and see
    | if it works
    | >correctly. Remember to unregister the DLL before you do
    | this.
    | >
    | >Thanks
    | >Brian [MS]
    | >Microsoft Developer Support
    | >This posting is provided "AS IS" with no warranties, and
    | confers no rights.
    | >--------------------
    | >| Content-Class: urn:content-classes:message
    | >| From: "Craig Duxbury" <craig.duxbury@uhb.nhs.uk>
    | >| Sender: "Craig Duxbury" <craig.duxbury@uhb.nhs.uk>
    | >| References: <12e301c37eb9$000dcda0$a301280a@phx.gbl>
    | >| Subject: WSDL: Instantiating the dispatch object
    | >| Date: Mon, 22 Sep 2003 09:01:40 -0700
    | >| Lines: 57
    | >| Message-ID: <033f01c38122$cf496230$a101280a@phx.gbl>
    | >| MIME-Version: 1.0
    | >| Content-Type: text/plain;
    | >| charset="iso-8859-1"
    | >| Content-Transfer-Encoding: 7bit
    | >| X-Newsreader: Microsoft CDO for Windows 2000
    | >| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    | >| Thread-Index: AcOBIs9J63jwGMsaS5ylJoWxQaal8A==
    | >| Newsgroups: microsoft.public.xml.soapsdk
    | >| Path: cpmsftngxa06.phx.gbl
    | >| Xref: cpmsftngxa06.phx.gbl
    | microsoft.public.xml.soapsdk:11062
    | >| NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
    | >| X-Tomcat-NG: microsoft.public.xml.soapsdk
    | >|
    | >| Points to check....
    | >|
    | >| 1. Make a note of all CLSIDs / ProgIDs relating to the
    | DLL
    | >|
    | >| 2. UnRegister the DLL
    | >|
    | >| 3. Go through the registry looking for all entries
    | >| relating to DLL which are still in the registry and
    | >| manually deleted them. (There may be some left
    | lurking,
    | >| even though the app has been unregistered)
    | >|
    | >| 4. Re-Register the DLL.
    | >|
    | >|
    | >| The main CLSIDs just removed (via regsvr32.exe -u)
    | where
    | >| re-created exactly as before. You would expect this if
    | >| you specified binary compatibility.
    | >|
    | >| However various proxystub interface CLSIDs (in
    | >| hkey_classes_root\interface\{clsid} - which had been
    | >| deleted manually) had changed when the DLL was re-
    | >| registered.
    | >|
    | >| Perhaps this \interface element in the registry and in
    | the
    | >| SOAP toolkit needs further investigation......
    | >|
    | >|
    | >| Craig
    | >|
    | >|
    | >|
    | >|
    | >| >-----Original Message-----
    | >| >
    | >| >I have created a VB (v6) DLL which can be called over
    | >| >SOAP. This dll has been working fine for months. Now I
    | >| >have received the message "WSDLOperation:
    | Instantiating
    | >| >the dispatch object for method <methodname> failed"
    | after
    | >| >re-creating the WSDL file.
    | >| >
    | >| >The IIS permissions, NT file permissions, IIS
    | anonymous
    | >| >access and DLL binary compatibility have all been
    | checked
    | >| >and are fine. A backup copy of the old WSDL and WSML
    | >| >files work perfectly ok. Why has the newly created
    | WSDL
    | >| >file stopped working. This was created using the Soap
    | >| >Toolkit v2.
    | >| >
    | >| >Any ideas???????
    | >| >
    | >| >(I have have seen this error message crop up on
    | various
    | >| >newsgroups, but without a definitive answer or a
    | number
    | >| of
    | >| >points to check.)
    | >| >
    | >| >
    | >| >.
    | >| >
    | >|
    | >
    | >.
    | >
    |


  4. Default RE: WSDL: Instantiating the dispatch object

    hi there.

    2Brian Combs: I have same thing, but my COM dll was built with Delphi 6.

    This thing approached after new server installation.

    SOAPTK3 works well with "lib.dll" as library app, but

    raises the error in server app mode.


    What should I do?



    *** Sent via Developersdex http://www.developersdex.com ***
    Don't just participate in USENET...get rewarded for it!

  5. Default RE: WSDL: Instantiating the dispatch object

    Hello
    I don't know anything about Delphi. However you can do basic trouble
    shooting. Use OLE View to make sure WSML file matches the COM info in your
    DLL. Can ASP page call Server.CreateObject on your COM dll and call methods
    with no errors? If you are using SOAP ISAPI listener try Soap ASP listener.

    Remember Soap toolkit use COM to try and call your COM dll. It pulls the
    method name from the WSDL, it then uses the WSML to see how to call invoke
    from IDispatch interface on your COM component. If any of this information
    does not match up it will fail. I always keep a simple Hello World sample
    around that I can use to test and make sure environment and toolkit is
    working correctly. Then if my real app is failing I know if it is
    environment or not. Also check to make sure you don't have more then on
    version of your DLL registerd.

    Thanks
    Brian [MS]
    Microsoft Developer Support
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | From: Max Nemkov <ice_croft@mail.ru>
    | References: <7edpLjSgDHA.2556@cpmsftngxa06.phx.gbl>
    | X-Newsreader: AspNNTP 1.50 (ActionJackson.com)
    | Subject: RE: WSDL: Instantiating the dispatch object
    | Mime-Version: 1.0
    | Content-Type: text/plain; charset="us-ascii"
    | Content-Transfer-Encoding: 7bit
    | Message-ID: <OIAk#h7jDHA.1960@TK2MSFTNGP12.phx.gbl>
    | Newsgroups: microsoft.public.xml.soapsdk
    | Date: Fri, 10 Oct 2003 22:28:23 -0700
    | NNTP-Posting-Host: actionjackson133.dsl.frii.net 216.17.147.133
    | Lines: 1
    | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
    | Xref: cpmsftngxa06.phx.gbl microsoft.public.xml.soapsdk:11183
    | X-Tomcat-NG: microsoft.public.xml.soapsdk
    |
    | hi there.
    |
    | 2Brian Combs: I have same thing, but my COM dll was built with Delphi 6.
    |
    | This thing approached after new server installation.
    |
    | SOAPTK3 works well with "lib.dll" as library app, but
    |
    | raises the error in server app mode.
    |
    |
    | What should I do?
    |
    |
    |
    | *** Sent via Developersdex http://www.developersdex.com ***
    | Don't just participate in USENET...get rewarded for it!
    |


  6. Default Re: WSDL: Instantiating the dispatch object

    "Brian Combs" <Brian@online.microsoft.com> a écrit dans le message de
    news:k7A7qGfgDHA.2632@cpmsftngxa06.phx.gbl...
    > Hello
    > Remember VB does not always play fair with binary Compatibility. For
    > example when you add new methods to your class VB will keep the same GUID
    > and progID and add information to forward old clients to the new class.


    True. But when you're developing, components change all the time until
    released. This messes up everything with VB. Creators of VB should have
    assumed - just like VC++ creators - developers know what they are doing. But
    it's off topic.

    Vince C.



  7. Default RE: WSDL: Instantiating the dispatch object

    Hello
    It sounds like the issue is a COM config one not a Soap issue. You may try
    posting to one of the COM groups to see if someone can answer your COM+
    config questions.

    Thanks
    Brian [MS]
    Microsoft Developer Support
    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | From: Max Nemkov <ice_croft@mail.ru>
    | References: <Un30SNmkDHA.1716@cpmsftngxa06.phx.gbl>
    | X-Newsreader: AspNNTP 1.50 (ActionJackson.com)
    | Subject: RE: WSDL: Instantiating the dispatch object
    | Mime-Version: 1.0
    | Content-Type: multipart/mixed; boundary="----=_NextPart_000_33218780"
    | Message-ID: <#FGkdXHlDHA.1800@TK2MSFTNGP10.phx.gbl>
    | Newsgroups: microsoft.public.xml.soapsdk
    | Date: Thu, 16 Oct 2003 23:14:02 -0700
    | NNTP-Posting-Host: actionjackson133.dsl.frii.net 216.17.147.133
    | Lines: 1
    | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
    | Xref: cpmsftngxa06.phx.gbl microsoft.public.xml.soapsdk:11220
    | X-Tomcat-NG: microsoft.public.xml.soapsdk
    |
    | hi there
    |
    | advice was good, it really works
    |
    | I configured iis directiry for anonymous access, set COM+ object
    | identity to me (as Administrator).
    |
    | That worked well.
    |
    | So, I need IIS "basic" dir security, and COM+ "interactive" identity -
    | and it's not working.
    |
    | I need my users log on through IIS, and so on.
    |
    | Now I'm suspect that there's something wrong with COM+ security, because
    | same configuration (basic + interactive) works well on my winXP, but
    | raises "subj" error on productive Win2000Adv, when COM+ is in "server"
    | mode.
    |
    | Where should I check through, Brian?
    |
    |
    |
    |
    |
    |
    | *** Sent via Developersdex http://www.developersdex.com ***
    | Don't just participate in USENET...get rewarded for it!
    |
    |


+ Reply to Thread

Similar Threads

  1. Replies: 0
    Last Post: 01-02-2007, 04:23 AM
  2. Is Double Dispatch really object-oriented?
    By Application Development in forum Theory and Concepts
    Replies: 69
    Last Post: 10-24-2006, 10:27 AM
  3. ERROR - WSDLOperation:Instantiating the dispatch object for method
    By Application Development in forum XML SOAP
    Replies: 0
    Last Post: 06-02-2005, 07:27 AM
  4. WSDLOperation:Instantiating the dispatch ..
    By Application Development in forum XML SOAP
    Replies: 0
    Last Post: 05-17-2004, 03:21 PM
  5. WSDL: Instantiating the dispatch object failed
    By Application Development in forum XML SOAP
    Replies: 0
    Last Post: 10-11-2003, 12:28 AM