none
App Event Error: 1022 There was a failure initializing profiling API attach infrastructure.

    Question

  • All of a sudden all of our Win 7, Win 8, Win 2008 R2 & Win 2012 machines are all encountering this error:

    Log Name:      Application
    Source:        .NET Runtime
    Event ID:      1022
    Keywords:      Classic
    Description:
    .NET Runtime version 4.0.30319.18408 - There was a failure initializing profiling API attach infrastructure.  This process will not allow a profiler to attach.  HRESULT: 0x80004005.  Process ID (decimal): 8304.  Message ID: [0x2509].
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1022</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-06T22:29:00.000000000Z" />
        <EventRecordID>132152</EventRecordID>
        <Channel>Application</Channel>
        <Security />
      </System>
      <EventData>
        <Data>.NET Runtime version 4.0.30319.18408 - There was a failure initializing profiling API attach infrastructure.  This process will not allow a profiler to attach.  HRESULT: 0x80004005.  Process ID (decimal): 8304.  Message ID: [0x2509].</Data>
      </EventData>
    </Event> 

    Is this from a bad WSUS update of some sort?  We don't typically install .NET 4.0 for anything specifically, but we run a variety of Microsoft software.  Thanks.

    Thursday, February 06, 2014 11:17 PM

Answers

  • Hi Gtrapp,

    This issue is due to an application which is depending on .NET Framework corrupt and use .NET to report the failure. Please check when you got this error and check which process caused this error. If you have no idea, please turn off the running application one by one to see the result. We have to know the corrupt application name before troubleshoot. If it is not a Microsoft Product, you may have to consult your vendor.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, February 07, 2014 5:46 AM
    Moderator

All replies

  • Hi Gtrapp,

    This issue is due to an application which is depending on .NET Framework corrupt and use .NET to report the failure. Please check when you got this error and check which process caused this error. If you have no idea, please turn off the running application one by one to see the result. We have to know the corrupt application name before troubleshoot. If it is not a Microsoft Product, you may have to consult your vendor.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, February 07, 2014 5:46 AM
    Moderator
  • Barry - Thanks for the reply.  In looking through my Application Event Logs, I see the .NET runtime error occurring just about every hour, at the half-hour mark.  I can check the errors for the Process ID, but none of the Process ID's mentioned in the last 4 errors are running at this time.  We have nothing scheduled on our WS to run every hour....  
    Monday, February 10, 2014 5:56 PM
  • Sorry Gtrapp for the late track.

    >>We have nothing scheduled on our WS to run every hour

    However, .NET won't do this either. Have you closed unneeded programs to check first?

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, February 17, 2014 1:00 PM
    Moderator
  • I have tracked down the process that is causing this or that is referred to in the event. It is Microsoft Windows Search Filter Host.
    Friday, October 10, 2014 11:23 AM
  • What was the fix?
    Wednesday, December 31, 2014 1:39 PM
  • We had the same error and I searched a lot of time but did not find any answer. I tracked down the problem to the Windows search filter host as well. In my case, the problem was file specific. Do you use SolidWorks? In my case the problem was the indexing filter for DWG and DXF files installed by SolidWorks Software. In the indexing options I switched at the DWG and DXF files not to index the hole file with the "SolidWorksIFilter", but only the file properties.

    The background was that our SolidWorks Support denied of giving support because our .Net is corrupt. We installed it many, many times. The error occured sometimes in a delay of 2 minutes, everytime a dxf or dwg file was tried to be indexed.

    Friday, May 13, 2016 10:44 AM