title: .NET Runtime version 4.0.30319.0. There was a failure initializing profiling API attach infrastructure.
body: <p>Lately I started noticing "<strong>.NET Runtime version 4.0.30319.0 - There was a failure initializing profiling API attach infrastructure.  This process will not allow a profiler to attach.  HRESULT: 0x80004005.  Process ID (decimal): 10288.  Message ID: [0x2509].</strong>" on our production Windows Server R2.</p>
  
  <p>This server is mainly used for IIS hosted WCF service. I googled about the error and found multiple solutions and I tried below.</p>
  
  <p>1) Verified .NET framework with Microsoft's utility and no issues found. That means one of the application is firing this .NET error.</p>
  
  <p>2) Tried tracking process id, but everytime error message has different process id. And I cannot find the pid from all available pid. My assumption is, it recycles the process after error and assign new pid.</p>
  
  <p>What is the best technique to find source of this error? Is there anyway I can get pid history logs?</p>