An error is reported when the VC sample samples30_adotm_client of Microsoft soap3.0 is run. m_psoapclient-> invoke directly fails.

I server U, the boss of Microsoft. The soap toolkit used by VC has never been smooth.

Let's try again today. It's completely follow.Setup instructions 
After configuring my Windows 2003,
With the explanation of the local domain name mssoapsampleserver, Ping
Registered samples \ adotm \ common \ CPP \ releasemindependency \ adotmcpp. dll

Right?

Check the ISAPI ing of the samples30 virtual directory of IIS. WSDL ing c: \ progra ~ 1 \ common ~ 1 \ mssoap \ binaries \ soapis30.dll
No problem, right?

Then open the Windows Firewall. All ports are free. No doubt?

Copy adotm. WSDL, adotm. wsml, and samplerecordset. adtg to the DEBUG directory (and then the upper-level copy), all right?

Run ---> error raise!

M_psoapclient-> invoke: an error is returned.

Sorry... Microsoft does not seem to support VC ++ very much. The documents are messy, there are few, and there are many errors. It is no wonder that people have been educated since childhood: beginners should not use VC.

The reason for this error is still to be found. In fact, I just want to use a client to download the data set on the server to the client's local XML file. This easy thing is wrong in VC. It's depressing !....

Which of the following has used VC and soap toolkit3.0 to call Web Services successfully? Can you give me a tip?

-----------------------
2005-5-17
In csdn, 9 of the 10 questions I asked are fruitless, while in msdn, I searched for VC ++, basically, the "filter" is useless. Because the "filter basis" is Visual C ++, a lot of C # search results are still found.

Again, it is only self-reliant to survive.

An error occurred when I traced it to isoapclient: mssoapinit2 today. However, the error message displayed is_ Com_error @ 0x0012f928, Basically, it doesn't make any sense (is there any tool or method to view what is recorded in 0x0012f928 ?), The client instance of soap cannot be instantiated. But how can this problem be solved? Continue fishing...

10: 24
Coinitialize (0)-> OK
Initializesoap-> OK
Memset (& __ Params, 0x00, sizeof (_ Params ));
_ Params. tablename = tablename; garbled characters found when setting parameters ??! Type conversion error?

10: 30
Sure enough, the type conversion problem occurs. The parameter type of the services written in C # Is string, and the conversion of C ++ to BSTR is required (BSTR) (_ bstr_t. stretch your waist and continue...

RelatedArticle:
1. vc6 Web Services Client development
2. The Microsoft soap sample is incorrect!