Last post Jun 04, 2015 04:15 PM by Siva Krishna Macha
Jun 04, 2015 10:57 AM|nissan|LINK
I am using a soap service. Everything works fine on my local m/c but when I push the same to the server. I get an error. What could I be missing?
This is the first time I am using a Soap Service. I cannot change the Soap Service, I did not write it, I am just consuming it.
The operation '..' could not be loaded because it has a parameter or return type of type System.ServiceModel.Channels.Message or a type that has MessageContractAttribute and other parameters of different types. When using System.ServiceModel.Channels.Message
or types with MessageContractAttribute, the method must not use any other types of parameters.
Jun 04, 2015 12:31 PM|Siva Krishna Macha|LINK
From your local machine, you might be pointing to a webservice url, hosted in X machine, which works fine. The webservice team might have deployed correct and working service here.
From your server machine, you might be pointing to webservice url hosted in Y machine (different machine, i.e., url is different). The deployed webservice may have an issue here. In such case, WebService team needs to look into that, if your (client) code
is same in both of the machines.
This generally happens when the input parameters of a web service's method contains not only MessageContract but also other parameters. It is then an issue.
Check both your client side code if the proxy class reflects so. And check with your web service team to cross check from their end as well.
See this very similar discussion
Jun 04, 2015 12:37 PM|nissan|LINK
Thank you for the reply. We don't have a separate webservices team.
Not sure what else could be different on local machine and the server.
Any more ideas please
Jun 04, 2015 01:04 PM|Siva Krishna Macha|LINK
Could you check if the webservice url is different while comparing both the machines?
Jun 04, 2015 04:07 PM|nissan|LINK
It is the same.
Jun 04, 2015 04:15 PM|Siva Krishna Macha|LINK
How about your "client" code, the code which accesses the service? Can you compare the timestamp of the dlls just to make sure you are using same code?