Question

[Update] Solved the Problem by generating a new web.config. Possible error was the second endpoint ("mex"). [Update/]

I have a webservice in IIS.

I'm trying to call a function but i get an errormessage like:

There was no channel that could accept the message with action 'http://Datenlotsen.Cyquest/ICyquestService/ValidateSelfAssessment'

I'm hosting it in an IIS in the standard website. There I created a virtual directory named "CyQuestwebservice". For the client side config i'm using Soap UI. That Tool generates the client config from the wsdl.

my webconfig looks like this, can you help me?:

<system.serviceModel>
    <extensions>
      <behaviorExtensions>
        <add name="wsdlExtensions" type="WCFExtras.Wsdl.WsdlExtensionsConfig, WCFExtras, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
      </behaviorExtensions>
    </extensions>
    <services>
      <service behaviorConfiguration="CyquestWebService.Service1Behavior"
        name="CyquestWebService.CyquestService">
        <endpoint address="" behaviorConfiguration="EndPointBehavior"
          binding="wsHttpBinding" bindingNamespace="http://Datenlotsen.Cyquest"
          contract="CyquestWebService.ICyquestService">
          <identity>
            <dns value="localhost" />
          </identity>
        </endpoint>
        <endpoint address="mex" binding="mexHttpBinding" bindingNamespace="http://Datenlotsen.Cyquest"
          contract="IMetadataExchange" />
      </service>
    </services>
    <behaviors>
      <endpointBehaviors>
        <behavior name="EndPointBehavior" >
          <wsdlExtensions location="http://wssdev04.datenlotsen.intern/Cyquestwebservice/CyquestService.svc" singleFile="True"/>
        </behavior>
      </endpointBehaviors>  
      <serviceBehaviors>
        <behavior name="CyquestWebService.Service1Behavior">
          <serviceMetadata httpGetEnabled="true" />
          <serviceDebug includeExceptionDetailInFaults="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
  </system.serviceModel>
    <system.diagnostics>
      <sources>
        <source name="System.ServiceModel"
                switchValue="Information, ActivityTracing"
                propagateActivity="true">
          <listeners>
            <add name="traceListener"
                type="System.Diagnostics.XmlWriterTraceListener"
                initializeData= "c:\log\Traces.svclog" />
          </listeners>
        </source>
      </sources>
    </system.diagnostics>
</configuration>
Was it helpful?

Solution

Solved the Problem by generating a new web.config. Possible error was the second endpoint ("mex").

OTHER TIPS

Try setting "Skip SOAP Action" to true in the "Request Properties".

I had a similar issue testing wsHttpBinding using SoapUI.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top