Why is CLR Requesting to resolve an assembly via BDC over and over?

 

 

Symptoms

 

Under a heavy client load a performance problem develops in your SharePoint 2010 or SharePoint 2013 farm's WFEs. It's hard to figure out what is and what isn't affected by the perf problem. Workflows that once took 30 seconds to run might take six minute to run and then timeout. Deploying a solution to the sandbox might fail with a timeout. Sometimes just opening a form dialogue box might take a long time and timeout. It's hard to connect the dots. The problem goes away after an IISRESET or an application pool recycle but after load increases, eventually the problem returns. You can't seem to figure out what the first cause is. You can't seem to trigger it.

So of course you amp up the ULS logging to verbose and notice a pattern you haven't seen before. CLR is requesting to resolve one or more assemblies over and over. And over and over. There is no pattern to which assembly is attempting to be resolved. Just when you think you can predict that it's going to be something related to XML Serialization (System.Xml.XmlSerializers, mscorlib.XmlSerializers, Nintex.Workflow.XmlSerializers, SharePointUI.WebParts.XmlSerializers, Microsoft.Office.Search.XmlSerializers, Microsoft.SharePoint.AddGallery.Server.XmlSerializers) that needs resolution, your beautiful theory gets dashed to pieces. Next time you visit the uls logs after seeing the problem maybe the assembly in focus turns out to be Microsoft.ReportingServices, Microsoft.Office.Excel.Server.HostExtensionWac, Microsoft.Rtc.ServerConfiguration, Microsoft.Rtc.InternalMedia, Microsoft.SharePoint, BihConsumerInterop, VJSharpCodeProvider, or something else. After searching for these messing assemblies you realize that these assemblies aren't actually dlls that live on the file system of the WFE. They're not in the GAC, they're not in a Bin folder, and they're not in an asp.net temp folder.

And they're certainly not in your BDC catalog. What? BDC? Yeah, if it doesn't seem weird that CRL is trying to resolve these assemblies (isn't that what CLR always does?) you realize that it's making calls to the BDC catalog to resolve them. The ULS logs make that clear. It dawns on you that the "CLR requesting to resolve assembly" (uls tag 9uq0) means that CLR already tried to resolve the assembly from the normal local places, gave up on that, and began attempting to find them in the BDC catalog. That in and of itself isn't necessarily weird if you've run the powershell cmdlet Import–SPBusinessDataCatalogDotNetAssembly in the past. That opens the door to allowing .net to use BDC as something of a probing path. But of course those assemblies aren't going to exist in your BDC catalog. So that's is a significant part of the problem.

As you peer deeper into the ULS logs you notice a new pattern. You see GetServiceApplicationID#1. A little further down in the log you see GetServiceApplicationID#2. You trace it out 3, 4, 5, 6, 7… 56, 57, 58, 59… 94, 95, 96, 97, 98, 99. There is clear iteration one by one up the list. And every time it is attempting to talk across the wire to one of your BDC servers. It gets worse. It doesn't stop at 99. You think CLR might give up on the BDC catalog after trying 99 times but it doesn't. It does it several more times and repeats GetServiceApplicationID#99 over and over and over until there is a thread abort exception and SharePoint removes the BDC server from the sharepoint load balance. Yep, that's also a facet of this multi-faceted performance problem. Multiply this times a bunch of users and your WFEs are well on their way to being overwhelmed. Maybe your BDC servers are getting pushed to their limits too.

Under a light load, the problem doesn't seem to occur. It only happens during a heavy load on the WFEs. It may also only happen if there is a significant amount of communication going on between WFE and BDC servers. Also the problem might not happen until a dynamically generated assembly (like an xml serializer for example).

 

 

Screenshots

 

Here are some images of what the 9uq0's look like, as filtered in ULSviewer.exe. Note how you have several resolve requests for the same assembly on the same correlation ID. . .

 

 

 

 

 

ULS Excerpts of one Correlation ID

 

We reproduced the problem one time when it was at its worst and used a very simple Nintex workflow as our victim. (To be clear, Nintex was not the cause of the problem but was one of the many victims.) What should have taken a few seconds to run took six minutes of slow, painful, futile running before the looping ended with an exception. I don't think many people are going to see this problem, but if you do, recognizing the pattern in the ULS logs is probably going to be the thing that leads you to this blog. After filtering in ULSViewer to a single correlation ID (the ID we got when the page timed out) the log file occupied 1,300 pages of a word document. No exaggeration there. I'm just going to give a few excerpts of that log file as an example.

05/05/2014 17:47:31.13    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Logging Correlation Data    xmnv    Medium    Name=Request (GET:https://MyGreatWebApplication:443/7g/LogicalAccess/_layouts/NintexWorkflow/StartWorkflow.aspx?TemplateID=%7B6bc8d4a9-31e2-4e07-af45-2ddf36af1dfd%7D&Source=https%3A%2F%2FMyApplication%2Efrb%2Eorg%2F7g%2FLogicalAccess%2F%5Flayouts%2Fworkflow%2Easpx)    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:31.70    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    9uq0    Medium    CLR Requesting to resolve assembly : System.Xml.XmlSerializers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:31.70    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4u    Verbose    Entering Bdc

loadBalancer.BeginOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:31.70    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4v    Verbose    Completed Bdc loadBalancer.BeginOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:31.70    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4w    Verbose    Entering Bdc proxy.GetChannel()    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:31.70    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4x    Verbose    Completed Bdc proxy.GetChannel()    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:31.70    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4y    Verbose    Entering Bdc 'GetServiceApplicationId' in BdcServiceApplicationProxy.    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:31.70    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Topology    e5mc    Medium    WcfSendRequest: RemoteAddress: 'https://ServerName003:32843/50d8547d1c894ca99b11a7ac533b6441/BdcService.svc/http' Channel: 'Microsoft.SharePoint.BusinessData.SharedService.IBdcServiceApplication' Action: 'https://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetServiceApplicationId' MessageId: 'urn:uuid:89bdfe36-e820-4e9d-ac84-0febc78dcc3d'    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:31.94    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (ExecuteWcfOperation:https://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetServiceApplicationId). Execution Time=219.651170749355    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:32.37    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4z    Verbose    Completed Bdc 'GetServiceApplicationId' in BdcServiceApplicationProxy.    df635b9b-104d-4fef-9e88-a351d604a4ce

 

 

05/05/2014 17:47:32.37    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (Bdc ExecuteOnChannel: GetServiceApplicationId#2). Execution Time=218.291221370314    df635b9b-104d-4fef-9e88-a351d604a4ce

 

Skipping a bit. . .

 

05/05/2014 17:47:33.26    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (Bdc ExecuteOnChannel: GetServiceApplicationId#6). Execution Time=218.146580082105    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:33.26    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    9uq0    Medium    CLR Requesting to resolve assembly : System.Xml.XmlSerializers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089    df635b9b-104d-4fef-9e88-a351d604a4ce

 

Skipping a lot. . .

 

05/05/2014 17:47:54.09    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (Bdc ExecuteOnChannel: GetServiceApplicationId#98). Execution Time=217.661392718907    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.09    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    9uq0    Medium    CLR Requesting to resolve assembly : System.Xml.XmlSerializers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (Bdc ExecuteOnChannel: GetServiceApplicationId#99). Execution Time=218.146370558269    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    9uq0    Medium    CLR Requesting to resolve assembly : System.Xml.XmlSerializers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4u    Verbose    Entering Bdc loadBalancer.BeginOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4v    Verbose    Completed Bdc loadBalancer.BeginOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4w    Verbose    Entering Bdc proxy.GetChannel()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4x    Verbose    Completed Bdc proxy.GetChannel()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4y    Verbose    Entering Bdc 'GetServiceApplicationId' in BdcServiceApplicationProxy.    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.31    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Topology    e5mc    Medium    WcfSendRequest: RemoteAddress: 'https://ServerName003:32843/50d8547d1c894ca99b11a7ac533b6441/BdcService.svc/http' Channel: 'Microsoft.SharePoint.BusinessData.SharedService.IBdcServiceApplication' Action: 'https://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetServiceApplicationId' MessageId: 'urn:uuid:3af45f1d-d121-4170-8bff-70406b926145'    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.53    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (ExecuteWcfOperation:https://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetServiceApplicationId). Execution Time=217.203233930569    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.53    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4z    Verbose    Completed Bdc 'GetServiceApplicationId' in BdcServiceApplicationProxy.    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.53    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff51    Verbose    Entering loadBalancer.EndOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.53    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff52    Verbose    Completed loadBalancer.EndOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:47:54.53    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (Bdc ExecuteOnChannel: GetServiceApplicationId#99). Execution Time=218.343811853182    df635b9b-104d-4fef-9e88-a351d604a4ce

 

Skipping a bit. . .

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (Bdc ExecuteOnChannel: GetServiceApplicationId#99). Execution Time=217.00397676241    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    9uq0    Medium    CLR Requesting to resolve assembly : Nintex.Workflow.XmlSerializers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4u    Verbose    Entering Bdc loadBalancer.BeginOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4v    Verbose    Completed Bdc loadBalancer.BeginOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4w    Verbose    Entering Bdc proxy.GetChannel()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4x    Verbose    Completed Bdc proxy.GetChannel()    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff4y    Verbose    Entering Bdc 'GetServiceApplicationId' in BdcServiceApplicationProxy.    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.22    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Topology    e5mc    Medium    WcfSendRequest: RemoteAddress: 'https://ServerName004:32843/50d8547d1c894ca99b11a7ac533b6441/BdcService.svc/http' Channel: 'Microsoft.SharePoint.BusinessData.SharedService.IBdcServiceApplication' Action: 'https://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetServiceApplicationId' MessageId: 'urn:uuid:e0202381-e587-4863-b0c5-a8e6b37cdd1c'    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.43    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (ExecuteWcfOperation:https://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetServiceApplicationId). Execution Time=219.366497697333    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.45    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff50    Unexpected    Logging unknown/unexpected client side exception: ThreadAbortException. This will cause this application server to be removed from the load balancer queue. Exception: System.Threading.ThreadAbortException: Thread was being aborted. at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.ServiceModel.Channels.DelegatingStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.PreReadStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.HttpInput.WebResponseHttpInput.WebResponseInputStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.DelegatingStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.MaxMessageSizeStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.DelegatingStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.DetectEofStream.Read(Byte[] buffer, Int32 offset, Int32 count) at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count) at System.Xml.EncodingStreamWrapper.Read(Byte[] buffer, Int32 offset, Int32 count) at System.Xml.XmlBufferReader.TryEnsureBytes(Int32 count) at System.Xml.XmlBufferReader.GetBuffer(Int32 count, Int32& offset, Int32& offsetMax) at System.Xml.XmlUTF8TextReader.ReadText() at System.Xml.XmlUTF8TextReader.Read() at System.Xml.XmlDictionaryWriter.WriteNode(XmlDictionaryReader reader, Boolean defattr) at System.ServiceModel.Channels.BufferedHeader..ctor(MessageVersion version, XmlBuffer buffer, XmlDictionaryReader reader, XmlAttributeHolder[] envelopeAttributes, XmlAttributeHolder[] headerAttributes) at System.ServiceModel.Channels.MessageHeaders..ctor(MessageVersion version, XmlDictionaryReader reader, XmlAttributeHolder[] envelopeAttributes, XmlAttributeHolder[] headerAttributes, Int32& maxSizeOfHeaders) at System.ServiceModel.Channels.StreamedMessage..ctor(XmlDictionaryReader reader, Int32 maxSizeOfHeaders, MessageVersion desiredVersion) at System.ServiceModel.Channels.Message.CreateMessage(XmlDictionaryReader envelopeReader, Int32 maxSizeOfHeaders, MessageVersion version) at System.ServiceModel.Channels.TextMessageEncoderFactory.TextMessageEncoder.ReadMessage(Stream stream, Int32 maxSizeOfHeaders, String contentType) at System.ServiceModel.Channels.HttpInput.ReadStreamedMessage(Stream inputStream) at System.ServiceModel.Channels.HttpInput.ParseIncomingMessage(Exception& requestException) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.SharePoint.BusinessData.SharedService.IBdcServiceApplication.GetServiceApplicationId() at Microsoft.SharePoint.BusinessData.SharedService.BdcServiceApplicationProxy.<GetServiceApplicationId>b__9(IBdcServiceApplication serviceApplication) at Microsoft.SharePoint.BusinessData.SharedService.BdcServiceApplicationProxy.Execute[T](String operationName, UInt32 maxRunningTime, ExecuteDelegate`1 operation, Boolean performCanaryCheck, Boolean isChannelThatDelegatesIdentity)    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.45    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Business Data    8085    Critical    The BDC Service application Business Data Connectivity Service Application is not accessible. The full exception text is: Thread was being aborted.    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.45    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff51    Verbose    Entering loadBalancer.EndOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

05/05/2014 17:53:35.50    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Topology    umbj    Verbose    Deserializing the type named Microsoft.SharePoint.SPTopologyWebServiceProxy, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c and with id abe953a6-438c-4fef-ac20-a6336bd6e493.    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.54    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Topology    8313    Critical    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure Process Name: w3wp Process ID: 5392 AppDomain Name: /LM/W3SVC/2130799115/ROOT-1-130437916205655691 AppDomain ID: 2 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:50d8547d1c894ca99b11a7ac533b6441#authority=urn:uuid:b0c0f92dc498475482033c35e3fa646b&authority=https://ServerName003:32844/Topology/topology.svc Active Endpoints: 1 Failed Endpoints:1 Affected Endpoint: https://ServerName004:32843/50d8547d1c894ca99b11a7ac533b6441/BdcService.svc/http    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.54    w3wp.exe (0x1510)    0x2238    Business Connectivity Services    Business Data    ff52    Verbose    Completed loadBalancer.EndOperation()    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.54    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    High    Leaving Monitored Scope (Bdc ExecuteOnChannel: GetServiceApplicationId#99). Execution Time=329.925870466777    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.54    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Runtime    tkau    Unexpected    System.Web.HttpException: Request timed out.    df635b9b-104d-4fef-9e88-a351d604a4ce

 

05/05/2014 17:53:35.54    w3wp.exe (0x1510)    0x2238    SharePoint Foundation    Monitoring    b4ly    Medium    Leaving Monitored Scope (Request (GET:https://MyGreatWebApplication:443/7g/LogicalAccess/_layouts/NintexWorkflow/StartWorkflow.aspx?TemplateID=%7B6bc8d4a9-31e2-4e07-af45-2ddf36af1dfd%7D&Source=https%3A%2F%2FMyApplication%2Efrb%2Eorg%2F7g%2FLogicalAccess%2F%5Flayouts%2Fworkflow%2Easpx)). Execution Time=364415.900973448    df635b9b-104d-4fef-9e88-a351d604a4ce

 

 

The Fix

 

There is a fix for this as of May 2014. You can either open a case with Microsoft Support to get it or wait for it to be included in either the June 2014 cumulative update.

 

 

 

 

 

 

    
 

Additional key words:

Publish a .NET Connectivity Assembly to the BDC Metadata Store LobSystem BDCM System.ResolveEventHandler AppDomain AssemblyResolve Initialize 9upy Release 9upz