This usually happens when there is a mismatch between the generated code and the xml returned by the web service, so it cannot be deserialized.
Run wsdl again, restore all proxy classes, and try again. Make sure you send the correct dummy data.
Update:
This often happened to me because my services were not controlled by web services, and we did not receive notifications about changes made to this service. We have completed the capture of soap messages in the web services pipeline for debugging. Here is a great resource to help you along the way.
You do not need to change anything in the pipeline, just take soap messages and save them so that you can debug later. In most cases, this was exactly the case, a change in contract. In other cases, we would not have a contract, so there would be no way to find out about the changes without catching up with the envelopes.
In any case, even if it’s not your problem, I think it’s good.
source share