Small WebService Problems

WebService unexpectedly ends with "/*****" because of the URL, and the request format cannot be identified.

Cause:

The Web service connected to. NET supports http get, http post, and SOAP communication protocols. By default, in. NET Framework 1.0, these three communication protocols are enabled. In. NET Framework 1.1, http get and http post are disabled by default. This is based on security considerations.

When the Web Service is upgraded to. NET Framework 1.1, the application that uses http get or http post to call the Web service will fail. These applications will receive
System. Net. WebException
Error message, indicating that the required format cannot be identified.

Solution:

Therefore, you only need to enable http get and http post that are disabled by default in Webservice to solve the problem above. Add the <system. web> node in the web. config file of webservice

 

<WebServices> <protocols> <add name = "HttpPost"/> <add name = "HttpGet"/> </protocols> </webServices>

 

WebService finds multiple endpoints

Solution:

Open the app. config file of the project to check whether there are multiple nodes. If yes, delete other nodes and keep one node.