Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>It's hard to tell what might be the problem. You could turn on WCF tracing and diagnostics which can give you some more details.</p> <p>To get you going quickly - in your web (or app) config:</p> <p>1) Add System.Diagnostics section anywhere under configuration element. You can replace path with which ever path you want the files to be stored at.</p> <pre><code>&lt;system.diagnostics&gt; &lt;sources&gt; &lt;source name="System.ServiceModel.MessageLogging" switchValue="Warning, ActivityTracing"&gt; &lt;listeners&gt; &lt;add type="System.Diagnostics.DefaultTraceListener" name="Default"&gt; &lt;filter type="" /&gt; &lt;/add&gt; &lt;add name="ServiceModelMessageLoggingListener"&gt; &lt;filter type="" /&gt; &lt;/add&gt; &lt;/listeners&gt; &lt;/source&gt; &lt;source name="System.ServiceModel" switchValue="Warning, ActivityTracing" propagateActivity="true"&gt; &lt;listeners&gt; &lt;add type="System.Diagnostics.DefaultTraceListener" name="Default"&gt; &lt;filter type="" /&gt; &lt;/add&gt; &lt;add name="ServiceModelTraceListener"&gt; &lt;filter type="" /&gt; &lt;/add&gt; &lt;/listeners&gt; &lt;/source&gt; &lt;/sources&gt; &lt;sharedListeners&gt; &lt;add initializeData="C:\temp\services_messages.svclog" type="System.Diagnostics.XmlWriterTraceListener, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" name="ServiceModelMessageLoggingListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack"&gt; &lt;filter type="" /&gt; &lt;/add&gt; &lt;add initializeData="C:\temp\services_tracelog.svclog" type="System.Diagnostics.XmlWriterTraceListener, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" name="ServiceModelTraceListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack"&gt; &lt;filter type="" /&gt; &lt;/add&gt; &lt;/sharedListeners&gt; &lt;/system.diagnostics&gt; </code></pre> <p>2) Under system.ServiceModel add following:</p> <pre><code>&lt;diagnostics wmiProviderEnabled="false"&gt; &lt;messageLogging logEntireMessage="true" logMalformedMessages="true" logMessagesAtServiceLevel="true" logMessagesAtTransportLevel="true" /&gt; &lt;/diagnostics&gt; </code></pre> <p>3) Under C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\ start SvcTraceViewer.exe. Load both message trace (services_messages.svclog) and service trace log (services_tracelog.svclog). You can either drag drop files in the tool or open one then add another</p> <p>4) Look for red bold letters for a problem.</p> <p>If you want to make your experience editing the WCF configuration more palatable you can use SvcConfigEditor.exe which is found under same folder as SvcTraceViewer.exe (#3). Just open the config file and you should see Diagnostics folder which will allow you to start/stop and configure diagnostics.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload