title: Getting "Unrecognized error 109 (0x6d)" which can be "fixed" by changing web.config
body: <p>I have a WCF service hosted in IIS using WAS. When I try to access this service using a net.tcp binding I get the following error:</p>
  
  <blockquote>
    <p>There was an error reading from the pipe: Unrecognized error 109 (0x6d).</p>
  </blockquote>
  
  <p>When using basicHttp I do not encounter the problem.</p>
  
  <p>The strange thing is that I can "fix" the problem by randomly changing the web.config and saving it. The problem just vanishes until I do an IISReset or an Application Pool Recycle. It is then broken again until I change (or just save) the web.config again...</p>
  
  <ul>
  <li>I have enabled tracing but that just gives the unrecognize error. </li>
  <li>Rebooting doesn't help. </li>
  <li>I have increased the thresholds in WCF but that didn't change anything. </li>
  </ul>
  
  <p>The contract is really really simple with no complex types, so no serialization problems. The return message size is a string of only 12 characters</p>