Databases
StackOverflow2013
Postsdbo
POWhy isn't my invalid WCF message being logged?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy isn't my invalid WCF message being logged?
    primarykey
    data
    text
    <p>I've got a WCF client communicating with a WCF service using <code>[DataContract]</code> types, and I'm getting a serialization error:</p> <blockquote> <p>The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter <a href="http://www.example.com/2007/09/Example:ExampleResult" rel="nofollow">http://www.example.com/2007/09/Example:ExampleResult</a>. The InnerException message was 'Deserialized object with reference id 'i3' not found in stream.'. Please see InnerException for more details.</p> </blockquote> <p>Normally, I'd simply crank up the tracing and see exactly what happened, but in this case, I can't get the offending (response) message to appear in the log.</p> <p>My configuration looks like this:</p> <pre><code>&lt;system.serviceModel&gt; ... (more stuff) &lt;diagnostics&gt; &lt;messageLogging logEntireMessage="true" logMalformedMessages="true" logMessagesAtServiceLevel="false" logMessagesAtTransportLevel="true" maxMessagesToLog="10000" maxSizeOfMessageToLog="81920000" /&gt; &lt;/diagnostics&gt; &lt;/system.serviceModel&gt; &lt;system.diagnostics&gt; &lt;trace autoflush="true" /&gt; &lt;sources&gt; &lt;source name="System.ServiceModel" switchValue="Information, ActivityTracing" propagateActivity="true"&gt; &lt;listeners&gt; &lt;add name="wcf_listener" /&gt; &lt;/listeners&gt; &lt;/source&gt; &lt;source name="System.ServiceModel.MessageLogging"&gt; &lt;listeners&gt; &lt;add name="wcf_listener" /&gt; &lt;/listeners&gt; &lt;/source&gt; &lt;/sources&gt; &lt;sharedListeners&gt; &lt;add name="wcf_listener" initializeData="tracelog.svclog" type="System.Diagnostics.XmlWriterTraceListener" /&gt; &lt;/sharedListeners&gt; &lt;/system.diagnostics&gt; </code></pre> <p>In the resulting log file, I get the outbound message logged, and then the exception logged. I never see the incoming message. What am I doing wrong here?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMark
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy isn't my invalid WCF message being logged?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy isn't my invalid WCF message being logged?
      1. USFrédéric Hamidi
      1. VTFavorite
    3. VO
      singulars
      1. POWhy isn't my invalid WCF message being logged?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTry specifying 'Order' parameter in your DataMember attribute. If, for some reason, elements get mixed up during serialization/deserialization process, this is supposed to take care of it. For instance: `[DataMember(Order=1)] public string Something { get; set; }` It might help.
      singulars
      1. POWhy isn't my invalid WCF message being logged?
      1. USVex
    2. COI'm not looking to solve the deserialization error (indeed, it's already solved...), I'm looking to solve the logging problem.
      singulars
      1. POWhy isn't my invalid WCF message being logged?
      1. USMark
    3. CODid you try changing the `switchValue` to `"All"` and see if the message is then logged?
      singulars
      1. POWhy isn't my invalid WCF message being logged?
      1. USsinelaw
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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