iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

Copyright © 2025 · iT Synergy·

Failed to load the current WSDL. An XML error has ocurred. (Microsoft.BizTalk.TrackingCompiler) (BAM)
Failed to load the current WSDL. An XML error has ocurred. (Microsoft.BizTalk.TrackingCompiler) (BAM) avatar

By Leave a Comment

When we work with BAM, we have to ways to deploy the activities (XML) and the Tracking’s we have made. One of them is doing it by console using the following commands:

You have to be in this directory: C:\Program Files (x86)\Microsoft BizTalk Server 2010\Tracking.

Once you are there you can apply them:

  • To deploy activity: bm.exe deploy-all -DefinitionFile
  • To deploy tracking: bttdeploy.exe

The other way to deploy the tracking file (.btt) is using the graphic interface call: Tracking Profile Editor (TPE).

The error which is showed in the title and in the next figures happens when you have made the .btt before and you want to open it for any reason.

This errors is shows up because the interface cannot load the orchestration assemblies that have interceptor in the activity.

The process you can follow is: without load the tracking profile, open the event source and select the orchestration schedule, select at least one of the assemblies which are involve in the tracking profile you tried to open before. After that, open the tracking profile normally and everything is going to work fine and is going to be loaded just as the follow figure shows:

 

 

xlang/s engine event log entry: Exceptions.Types.InterceptorException. No events are expected after completion
xlang/s engine event log entry: Exceptions.Types.InterceptorException. No events are expected after completion avatar

By Leave a Comment

With this title I am making reference to an error we have when we try to track data from some shapes in a BizTalk application. The following code is a complement of an additional information that we got with this error.

Exception type: BAMTraceException

Source: Microsoft.BizTalk.Bam.EventObservation

Target Site: Microsoft.BizTalk.Bam.EventObservation.BAMTraceFragment CreateTraceFragment()

The following is a stack trace that identifies the location where the exception occured

at Microsoft.BizTalk.Bam.EventObservation.TraceInstanceToken.CreateTraceFragment()

at Microsoft.BizTalk.Bam.EventObservation.TraceReferenceTrackPoint.Execute(EventStream eventStream, IBAMDataExtractor extractor, Object location, Object data)

at Microsoft.BizTalk.Bam.EventObservation.BAMInterceptor.Microsoft.BizTalk.Bam.EventObservation.IRawStreamInterceptor.OnStep(IBAMDataExtractor extractor, Object location, Object data, Stream eventStream)

at Microsoft.XLANGs.Mozart.BIWrapperInterceptor.TrackEventHandler(Location loc, EventData data, Stream trackData)

at Microsoft.XLANGs.Core.Events.FireEvent(Location location, EventData args, ITrackStreamDispenser trackData)

 

Before explain what the reason is to get this error when we are tracking data from BizTalk I would like to give a little bit more context about BAM (Business Activity Monitoring) and TPE (Tracking Profile Editor) to get a better understanding of it. The TPE is a developer tool. Basically it is a graphical tool use to specify the orchestrations, ports and messages that are sources of the data captured by BAM.

 

I will place particular emphasis in something very important to know about TPE: The TPE  is only used when we are going to capture data from BizTalk application. This special emphasis is because BAM is a very powerful tool, with this one we can monitor WCF (Windows Communication Foundation), .NET Application and WF (Windows Workflow Foundation) as well, but we have to know which is the tool to do it, which for those cases is not the TPE.

 

When we use the TPE the following data sources types are displayed and we can use to track:

  1. Orchestrations
  2. Message payload schemas
  3. Context property schemas
  4. Message property schema

In another way, some message such a string type or System.XML.XMLDocument can’t be tracked with TPE. Only we can track messages that have a schema that is known at design time.

We can’t track any of the following orchestration shapes:

  1. Group (Task)
  2. Loop (While)
  3. Message assignment
  4. Suspend
  5. Terminate
  6. Throw exception
  7. Transform

In this stage when I have written about what we can do and don’t with the TPE, I will come back to the beginning of this post, the error I got doing a tracking!!. I got this error because I was trying to put and interceptor in a send shape (this shape allows us to track data without any problem), the real problem was that the send shape was inside the Group shape, and how we saw before in this post we can’t track data from this shape. This is a BAM limitation – Tracking data from some BizTalk application shapes!