2.1 and XSD NameSpace relationships?
You may have three versions of XSD namespaces in SOAP applications: 1999, 2000/10, and 2001. As long as the namespace in the message and the same WSDL, SOAP Toolkit 2.0 will accept any of the above three namespaces.
WSDLGEN has made changes to allow you to choose any of these three namespaces. If you don't need to use 1999 or 2000 namespace, we strongly recommend that you use the default 2001 namespace. Note that the name of some data types in the 2001 standard has changed, check the standard document to obtain details.
2.2 How to install SOAP at the client?
This is indeed a common problem. The correct answer to this question is to use the .msm file, it can be downloaded on the Toolkit download page. Of course, if you can put the corresponding DLL in the correct directory, you can process all registration items correctly, you may have your own installation; however, put the .msm to your installer is the safest and It is also the only way to support.
2.3 Why can't my client report not to find server components?
If your SOAP method uses a custom type mapping object, you may need a WSML file in your client. WSML files can tell SoapClient's Progid for your custom mapping object so that SOAPCLIENT can find it. If your WSML file contains the ProgID information of your server components, you can want to remove the information of the server component from you like this to make SOAPCLIENT no longer try to load your server components. .
(Note: This translation is a bit unknown, with the original text:
You may need to use a WSML file on the client if your Soap methods use custom type mappers. The WSML file specifies the progid of the custom mapper for the SoapClient to know where to find it. If your WSML file specifies the progid of your server Component (as it will if you use the wsml generated for the server) You May Want To Remove The Server Component Information So The SoapClient Doesn't Attempt To Load Your Server Component.)
2.4 Does the SOAP Toolkit support COM EXE as a server object?
Although COM EXE can be used in some cases, this configuration is not supported without testing. We recommend that in this case you use the DLL to make COM EXE again to apply.
2.5 Why can't WSDLREADER can be used in Script?
WSDLReader does not support IDSPATCH interfaces, so it cannot be used in Script.
2.6 Why can't my character encoding can be used in NT4?
WINDOWS NT 4.0 does not support CHS: GB2312 or Ar: ISO8859-6 encoding.
2.7 How to use the SOAP Toolkit underlying interface to write my XML to the message?
Serializer.WriteXML puts XML in the message, the document is regarded as a CDATA segment, but this is not a problem.
2.8 Why do I get an Access Denied error?
Remember a SOAP Toolkit app is also a web application. The web server will have a variety of different security measures to determine that users cannot access what he has no right to access. That is to say, Access Denied is often the default state for a Server application. You can check the content of the following aspects: Determine the user account used in your application runtime (such as IWAM _... or IUSR _... What is the WSDL and WSML files have read permissions - Check files Control list and IIS configuration. Determine the user account for the web application to read and execute the permissions to implement your SOAP service DLL file. Determine your SOAP service's virtual directory to read and execute permissions for the WSDL extension. This situation often occurs when you run your server components in the VB debugger: Anonymous users do not have enough permissions to activate the corresponding objects in the VB debugger.
The above list is not complete, but it should be able to give you some useful tips.
2.9 What is the meaning of HRESULT for SOAPCONNECTOR?
ErrorDecimalHexAMBIGUOUS50001388BAD_REQUEST505013BAACCESS_DENIED505113BBFORBIDDEN505213BCNOT_FOUND505313BDBAD_METHOD505413BEREQ_TIMEOUT505513BFCONFLICT505613C0GONE505713C1TOO_LARGE505813C2ADDRESS505913C3SERVER_ERROR510013ECSRV_NOT_SUPPORTED510113EDBAD_GATEWAY510213EENOT_AVAILABLE510313EFSRV_TIMEOUT510413F0VER_NOT_SUPPORTED510513F1BAD_CONTENT52001450CONNECTION_ERROR53001464BAD_CERTIFICATE_NAME53011465HTTP_UNSPECIFIED54001518HTTP_SENDRECV54011519HTTP_BAD_REQUEST5402151AHTTP_BAD_RESPONSE5403151BHTTP_BAD_URL5404151CHTTP_DNS_FAILURE5405151DHTTP_CONNECT_FAILED5406151EHTTP_SEND_FAILED5407151FHTTP_RECV_FAILED54081520HTTP_HOST_NOT_FOUND54091521HTTP_OVERLOADED54101522HTTP_FORCED_ABORT54111523HTTP_NO_RESPONSE54121524HTTP_BAD_CHUNK54131525HTTP_PARSE_RESPONSE54141526HTTP_TIMEOUT54151527HTTP_CANNOT_USE_PROXY54161528HTTP_BAD_CERTIFICATE54171529HTTP_BAD_CERT_AUTHORITY5418152AHTTP_SSL_ERROR5419152BWSDL_MUSTUNDERSTAND71001BBC
2.10 When I changed my address of my SOAP server, why is my client no longer work?
The most common reason is that you need to modify two different URLs. SOAPCLIENT.MSOAPINIT calls the path containing the WSDL (at the same time, also the path to the WSML file). When the address of the service changes, the address of these files is also changed, and the parameters call should also change. In the WSDL file, the address of the SOAP service is also the address of the SOAP service - in the service location attribute - often someone will forget to modify this URL.
2.11 How do I achieve my own SOAP Client on the client that does not install SOAP Toolkit?
There is a Script-based SOAP implementation that does not need to install SOAP Toolkit. You can download:
http://msdn.microsoft.com/downloads/samples/internet/behaviors/library/webservice/sample.asp.2.12 How to protect my SOAP app?
SOAP is inherently a web application, so security principles applied to web applications also apply to SOAP. In our FAQ already contains the most common questions about security. But in safety issues are too extensive, it is not suitable for discussion here. The following is an article about SOAP security:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsoap/html/soapsecurity.asp?frame=true. The best information about Web security I found is Michael Howard
Designing Secure Web-Based Applications for Microsoft Windows 2000, Microsoft Press; ISBN: 0735609950.
Asptoday also has a few good security articles, one of which is:
SECURING Windows 2000 IIS 5.0Applications.
2.13 Why is my client certificate not used?
A common problem with the client certificate is to include multiple names - Friendly Name and Subject Name in a certificate. Subject Name in the client certificate is used for SOAP clients. To find Subject Name, you have to use IE IE / Tools Menu / Internet Options Menu Item / Content, click the Certificate button. The name in the "issued to" column is Subject Name. This name is usually an X.500 name. If so, the CN part in the name is the name we need. See below for more detailed information:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsoap/html/soapsecurity.asp?frame=true.
2.14 Where can I get support about SOAP Toolkit 2.0?
Microsoft Support Services in the following Website:
http://support.microsoft.com/directory/overview.asp?sd=gn&fr=0. You can choose from phone support or web-based support:
Http://support.microsoft.com/directory/directory.asp?sd=gn.
2.15 Whether Windows 95 supports SOAP TOOLKIT?
Windows 95 does not support some system calls in SOAP Toolkit, so it does not support SOAP Toolkit.
2.16 Why can't I use the soap app that uses the underlying interface?
Some Marshalling issues occur when the underlying interface object is used across the trip boundary (such as the Application Protection in IIS, the COM Server program and VB debugger). Currently, the underlying object can only be used in Inproc. This issue will be resolved in the later service-pack.
2.17 What is the meaning of the HTTP status value returned by IIS Server?
See here:
Http://msdn.microsoft.com/Workshop/networking/wininet/reference/constants/statuscodes.asp.
2.18 Where should I ask questions about Web Service? SOAPSDK's news group is not a good place, you can send questions to the following address:
Iewctrls@microsoft.com.
2.19 When is the next version of SOAP Toolkit?
SOAP Toolkit 3.0 will release the first beta version in the fall of 2001.
2.20 Why can't the SOAP call sent by my SOAP client can't exceed 5?
You can modify the registry to close the Nagling latency of the ISAPI server. Nagling will add a time delay for each smaller TCP package from the ISAPI buffer, which is to be able to combine two smaller packages into one to reduce network traffic. The delay time is 200 ms, so most SOAP operations have additional 200ms delays caused by Nagling. This is why some simple reference test results for calling the Server-end method through a single client loop is much lower than that of the test results after the Nagling. Obviously, even if the client and server are not taken, a single-threaded client does not send more than 5 calls to the server within 1 second. In a reference test closer to the real situation, send requests to the server using thousands of clients in parallel, Nagling usually enhances the performance of the server due to the reduction of fewer numbers of packets. Usually, when you find that your test results are much lower than you want, you can try to close Nagling to see if it is helpful. To turn off the Nagling latency, you need to modify the "Nonagling" DWORD value under the registry key_local_machine / SOFTWARE / Microsoft / MSSOAP / SOAPISAP is (1).
2.21 Why can't SOAP Toolkit can't read some WSDL?
Check the WSDL file to see if there is an IMPORT statement. 2.0 version of Toolkit also does not support import. The only way is to download the WSDL file to the local, the information points to the information COPY to the WSDL file. Support for Import will be added to Toolkit 3.0.
