DX Application Performance Management

Expand all | Collapse all

9.7 .NET Agent | SharePoint 2013 | Windows 2012

Jump to Best Answer
  • 1.  9.7 .NET Agent | SharePoint 2013 | Windows 2012

    Posted 12-17-2015 05:31 AM

    Hi,

    I'm having some trouble to put the 9.7 .NET Agent (IntroscopeDotNetAgentInstall64_9.7.1.16.exe) working for SharePoint 2013 over Windows 2012 R2 x64.

    I have installed the CA APM for Microsoft SharePoint and CA APM Microsoft SharePoint Monitor, the CA APM Microsoft SharePoint Monitor is working fine.

    After installing the 9.7 .NET Agent i start having some errors:

     

    Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96

    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737

    Exception code: 0xe0434352

    Fault offset: 0x0000000000008b9c

    Faulting process id: 0x47e0

    Faulting application start time: 0x01d138b4c21a8ef9

    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe

    Faulting module path: C:\Windows\system32\KERNELBASE.dll

    Report Id: 1f2322d9-a4a8-11e5-80f8-005056b772c9

     

    Any ideia?

     

    Thanks,

    Tiago



  • 2.  Re: 9.7 .NET Agent | SharePoint 2013 | Windows 2012
    Best Answer

    Posted 12-17-2015 05:43 AM

    Hello Tiago,

    Can you try to disable socket instrumentation in the toggles-typical.pbd?

    #TurnOn: SocketTracing

     

    If the problem persists, open a support case and attach the TRACE Agent logs and Windows Event viewer logs

    Regards,

    Sergio



  • 3.  Re: 9.7 .NET Agent | SharePoint 2013 | Windows 2012

    Posted 12-17-2015 06:16 AM

    Hi Sergio,

    Its working now!!

    Any clue why SocketTracing crash the w3wp process?

     

    Thanks,

    Tiago



  • 4.  Re: 9.7 .NET Agent | SharePoint 2013 | Windows 2012

    Posted 12-17-2015 06:59 AM

    Hello Tiago,

    I am glad to hear it is working now. It seems a conflict between Sharepoint application and socket tracing, you can further narrow down the issue and identify which socket tracer is trigger the conflict by disabling each of the lines in the dotnet.pbd.

     

    TraceOneMethodWithParametersIfFlagged: SocketTracing Connect SocketConnectTracer "SocketConnectTracer"

    TraceOneMethodWithParametersIfFlagged: SocketTracing InternalConnect SocketConnectTracer "SocketConnectTracer"

    TraceOneMethodWithParametersIfFlagged: SocketTracing Send SocketSendTracer "SocketSendTracer"

    TraceOneMethodWithParametersIfFlagged: SocketTracing Receive SocketReceiveTracer "SocketReceiveTracer"

    TraceOneMethodWithParametersIfFlagged: SocketTracing Accept SocketAcceptTracer "SocketAcceptTracer"

    TraceOneMethodWithParametersIfFlagged: SocketTracing Close   SocketCloseTracer "SocketCloseTracer"

    ..

     

    Once you identify the problematic line, open a support case, attach DEBUG agent logs, windows event viewer app logs and you need to capture a series of dump upon having the problem, this will help us find out the root cause.

    Thank you,

    Sergio