There was no endpoint listening at http://domain.com/MXWebServices.asmx that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
<system.serviceModel> <bindings> <basicHttpBinding> <binding name="isMXTransfer Web ServicesSoap" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="65536" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true"> <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" /> <security mode="None"> <transport clientCredentialType="None" proxyCredentialType="None" realm="" /> <message clientCredentialType="UserName" algorithmSuite="Default" /> </security> </binding> </basicHttpBinding> </bindings> <client> <endpoint address="http://domain.com/MXWebServices.asmx" binding="basicHttpBinding" bindingConfiguration="isMXTransfer Web ServicesSoap" contract="WeblinkService.isMXTransferWebServicesSoap" name="isMXTransfer Web ServicesSoap" /> </client> </system.serviceModel>
To check the connectivity on test or UAT server I invoked the partner's web service method through Chrome's postman plugin and I got the proper response.
var
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)