Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Could it be that you're selecting a lot more entries today compared to yesterday? Could it be that your service method takes longer than the default of 60 seconds to return the data? Or could it be that the data size is going beyond 64K for the entities returned?</p> <p>I would do two things:</p> <p>1) Turn on the exception details, so that you can get a detailed exception message on the client - that should hopefully point you in the right direction</p> <p>2) Turn on WCF message logging to see what goes across the wire</p> <p>For point 1, you need to enable the <code>serviceDebug</code> behavior:</p> <pre><code> &lt;system.serviceModel&gt; &lt;behaviors&gt; &lt;serviceBehaviors&gt; &lt;behavior name="debug"&gt; &lt;serviceDebug includeExceptionDetailInFaults="true"/&gt; &lt;/behavior&gt; &lt;/serviceBehaviors&gt; &lt;/behaviors&gt; &lt;services&gt; &lt;service behaviorConfiguration="debug" name="YourWCFService"&gt; </code></pre> <p>This should give you details in the client, when a call fails.</p> <p>For point no. 2, you need to do a few steps:</p> <p>Inside <code>&lt;system.serviceModel&gt;</code>, you need to add this diagnostics tag:</p> <pre><code>&lt;diagnostics&gt; &lt;messageLogging logMessagesAtServiceLevel="true" logMessagesAtTransportLevel="true" logEntireMessage="true" logMalformedMessages="true" maxMessagesToLog="2500" maxSizeOfMessageToLog="256000" /&gt; &lt;/diagnostics&gt; </code></pre> <p>and then you also need to add this to your app.config or web.config:</p> <pre><code> &lt;system.diagnostics&gt; &lt;sources&gt; &lt;source name="System.ServiceModel" switchValue="Information, ActivityTracing" propagateActivity="true"&gt; &lt;listeners&gt; &lt;add name="default" type="System.Diagnostics.XmlWriterTraceListener" initializeData="C:\yourlogfile.svclog" /&gt; &lt;/listeners&gt; &lt;/source&gt; &lt;/sources&gt; &lt;trace autoflush="true" /&gt; &lt;/system.diagnostics&gt; </code></pre> <p>There are a couple of predefined trace listener types in the <code>System.Diagnostics</code> namespace - use any of those ready-made ones, or create your own (e.g. to log to a database or such).</p> <p>Check out those additional information sources on how to enable tracing in WCF:</p> <ul> <li><a href="http://msdn.microsoft.com/en-us/library/ms733025.aspx" rel="nofollow noreferrer">Configuring Tracing</a></li> <li><a href="http://mkdot.net/blogs/dejan/archive/2008/10/23/wcf-tracing-and-message-logging.aspx" rel="nofollow noreferrer">WCF Tracing and Message Logging</a></li> </ul> <p>You can view those XML-based svclog files using the <a href="http://msdn.microsoft.com/en-us/library/ms732023.aspx" rel="nofollow noreferrer">WCF Trace Viewer Tool</a> - very handy!</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