DX Application Performance Management

Expand all | Collapse all

Introscope 9.1.6.0 Agent for .NET breaking Web Service

Jump to Best Answer
  • 1.  Introscope 9.1.6.0 Agent for .NET breaking Web Service

    Posted 05-28-2013 12:42 PM
    Hello,

    Has anyone else ran into an issue with Introscope 9.1.6.0 breaking Web Service functionality, partiuclarly for .NET 4.0 Framework? I've narrowed it down to a problem with one specific MS patch, KB2742613. Once I uninstall this patch, the web service responds accordingly again. Or I can uninstall APM completely, and the issue also does not occur. The problem is with this security patch AND the introscope agent. I remember reading of a possible fix in 9.2 for this issue, however, is there a work around for the 9.1.6.0 version? Any help or information would be greatly appreiciated.

    OS: Windows 2008 R2
    Framework: .NET v4.0.30319.17929

    Stack Trace:
    WebHost failed to process a request.
    Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/40054951
    Exception: System.ServiceModel.ServiceActivationException: The service '/Services/services.svc' cannot be activated due to an exception during compilation. The exception message is: Common Language Runtime detected an invalid program.. ---> System.InvalidProgramException: Common Language Runtime detected an invalid program.
    at System.ServiceModel.Dispatcher.DispatchRuntime..ctor(EndpointDispatcher endpointDispatcher)
    at System.ServiceModel.Dispatcher.EndpointDispatcher..ctor(EndpointAddress address, String contractName, String contractNamespace, Boolean isSystemEndpoint)
    at System.ServiceModel.Dispatcher.EndpointDispatcher..ctor(EndpointAddress address, String contractName, String contractNamespace)
    at System.ServiceModel.Dispatcher.EndpointDispatcher..ctor(EndpointAddress address, String contractName, String contractNamespace, String id, Boolean isSystemEndpoint)
    at System.ServiceModel.Description.DispatcherBuilder.BuildDispatcher(ServiceHostBase service, ServiceDescription serviceDescription, ServiceEndpoint endpoint, ContractDescription contractDescription, EndpointFilterProvider provider)
    at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
    at System.ServiceModel.ServiceHostBase.InitializeRuntime()
    at System.ServiceModel.ServiceHostBase.OnBeginOpen()
    at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open()
    at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
    at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
    --- End of inner exception stack trace ---
    at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
    at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
    Process Name: w3wp
    Process ID: 6348


  • 2.  RE: Introscope 9.1.6.0 Agent for .NET breaking Web Service
    Best Answer

    Posted 05-28-2013 01:06 PM
    This is a known issue.

    The fix is slated for 9.1.7.0, but if you need to fix this temporarily, disable correlation ID tracing on WCF classes:
    Open webservices.pbd
    Disable the following classes by placing a "#" in front of the directive
    
    #TraceOneMethodWithParametersIfFlagged: WCFRuntimeTracing .ctor WCFCorIDTracer "WebServices"


  • 3.  RE: Introscope 9.1.6.0 Agent for .NET breaking Web Service

    Posted 05-30-2013 10:00 AM
    That worked as a great work-around, thank you. We'll be sure to upgrade to 9.1.7.0 when available. Thank you again!

    hdavis wrote:

    This is a known issue.

    The fix is slated for 9.1.7.0, but if you need to fix this temporarily, disable correlation ID tracing on WCF classes:
    Open webservices.pbd
    Disable the following classes by placing a "#" in front of the directive
    
    #TraceOneMethodWithParametersIfFlagged: WCFRuntimeTracing .ctor WCFCorIDTracer "WebServices"