iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

  • Facebook
  • Instagram
  • LinkedIn
  • Phone
  • Twitter
  • YouTube

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

December 14, 2012 By Ana María Orozco Zuluaga 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:

 

 

Filed Under: BAM, Tracking Profile Editor Tagged With: BAM, BAMTraceException

Error: The BAM deployment failed. Another Element with ID xxxx has already been deployed. Change the ID and retry.
Error: The BAM deployment failed. Another Element with ID xxxx has already been deployed. Change the ID and retry. avatar

November 27, 2012 By Ana María Orozco Zuluaga Leave a Comment

In this post I am talking about an error which comes up when you try to deploy the activity you have defined previously.

When you create an activity using Add-Ins: BAM Activity and BAM View and you have created progress, time and data dimensions each item declared has a unique identifier (Id) that you can see when you export your activity definition to XML format as show below:

<Activity Name=”RNGDConsultaDaños” ID=”ID1E27DF7963924CBC829A5311B1F17CBD”>

<Checkpoint Name=”FechaInicio” ID=”ID043C75F6897244398EFB230C17DF9DCA” DataType=”DATETIME”/>

<Checkpoint Name=”FechaInconsistencia” ID=”ID9E5423FBE42249FFB335BBB5B3BAB752″ DataType=”DATETIME”/>

 

In my case I have two similar activities, the difference between the two was a progress dimension, so I decided to copy de first activity I have created before and chance only the dimension which I could do without any problem.

I deployed the first activity successfully as show the next print.

 

 When I tried to deploy the second activity using the console I got the following error:

 

So, to fix this problem we’ve got two ways:

 

The first one is modify the XML file which has the activity definition, we have to change every single Id. Be careful because if you define something like this, with this Id you have to change this Id for each one FechaInicio you find into the file (See the green highlight):

Example:

 

 

In the first Chechkpoint with name: FechaInicio that is below that Activity tag has the Id finished in “2E1C”. The tag call “Alias” down the text, below the activityView tag has another Id, but has the ChechpointRef that is the same which is in the beginning. So this context is to explain that if you decide to change the Ids in the activity has to be very careful changing those Ids because some of them appears in different part of the text.

The other way is to define a new activity in a new excel, like this we’ve got the unique ids and after that we can deploy without any problem. 🙂

 

 

Filed Under: BAM Tagged With: BAM, Deploy Failed

Wrong date is displayed on BAM Portal when using BAM API
Wrong date is displayed on BAM Portal when using BAM API avatar

September 6, 2012 By Juan Camilo Zapata Montúfar Leave a Comment

If your are using BAM API to update the values of the BAM milestones and the hours registered are wrong  , this can be caused by the UTC of the machine the query is running on . To fix this try not to use System.DateTime.Now but System.DateTime.UtcNow.

Example:

Microsoft.BizTalk.Bam.EventObservation.OrchestrationEventStream.UpdateActivity(“MyActivity”, myActivityInstance,”milestone”,System.DateTime.UtcNow);

Filed Under: BAM Tagged With: BAM, BAM API, BAM DATETIME OFFSET, BAM PORTAL DATE PROBLEM, BAM PORTAL DATETIME WRONG, BAM UTC, BAM UTC OFFSET, BAMAPI, datetime, hour offset, UTC, UTC offset

  • 1
  • 2
  • 3
  • Next Page »

Team


Marco
Antonio Hernández

Jaime
Alonso Páez

Luis
Carlos Bernal

Ana
María Orozco

Juan
Camilo Zapata

Carlos
Alberto Rueda

Sonia
Elizabeth Soriano

Diana
Díaz Grijalba

Bernardo
Enrique Cardales

Alexandra
Bravo Restrepo

Juan
Alberto Vélez

Diana
Paola Padilla

Jhon
Jairo Rodriguez

Yully
Arias Castillo

Carlos
Andrés Vélez

Brayan
Ruiz

Jesús
Javier Hernández

Alejandro
Garcia Forero

Gustavo
Adolfo Echeverry

Josué
Leonardo Bohórquez

Oscar
Alberto Urrea

Odahir
Rolando Salcedo

Jimmy
Quejada Meneses

Natalia
Zartha Suárez

Mario
Andrés Cortés

Eric
Yovanny Martinez

Carolina
Torres Rodríguez

Juan
Mauricio García

Tag Cloud

.NET (9) 940px (1) Analysis Services mdx (1) An attempt was made to load a program with an incorrect format. (1) ASP.NET MVC (1) Azure (3) Backup (1) BAM (7) BAM API (1) BAMTraceException (2) BI (3) BizTalk (24) Business Intelligence (6) C# (2) caracteristicas de publicacion (2) Content Editor (3) ESB (15) ESB Toolkit (3) General (4) habilitar caracteristicas (3) indexes (2) Integration Services (2) Master Page (3) MDX (2) MSE (11) net.tcp (2) Office 365 (2) Oracle (2) Performance Point (2) Public Website (2) Receive Location (2) SDK (2) Servicio Web (2) Sharepoint 2010 (2) SharePoint 2013 (4) SharePoint Online (2) SOA (8) Soap Fault (2) Sort Months MDX (2) SQL Server (2) Visual (2) Visual Studio 2010 (2) WCF (19) Windows (3) Windows 8 (17)

Categories

  • .NET (33)
  • Analysis Services (1)
  • ASP.NET MVC (2)
  • Azure (7)
  • BAM (9)
  • BAM PrimaryImport (3)
  • BigData (1)
  • BizTalk (77)
  • BizTalk 2010 configurations (57)
  • BizTalk Application (60)
  • BizTalk Services (13)
  • Business Intelligence (4)
  • Cloud (3)
  • CMD (1)
  • CodeSmith – NetTiers (2)
  • CommandPrompt (1)
  • CRM OptionSet mapping component (1)
  • Desarrollo de software (6)
  • develop (6)
  • developers (3)
  • DropBox (1)
  • Dynamics (1)
  • Enterprise Architect (1)
  • Entity Framework (1)
  • Errores BizTalk (2)
  • ESB (27)
  • ETL (1)
  • Event Viewer (1)
  • Excel Services (1)
  • Foreach loop container (1)
  • General (4)
  • Gerencia de Proyectos (2)
  • Google (1)
  • Grouped Slices (1)
  • Human Talent (1)
  • IIS (4)
  • Integración (6)
  • Integration Services (3)
  • KingswaySoft (1)
  • Lync (1)
  • MSE (13)
  • Office 365 (2)
  • Oracle Data Adapter (2)
  • Performance Point (4)
  • Picklist (1)
  • Pivot Table (1)
  • Procesos (1)
  • Pruebas (1)
  • Public Website (2)
  • Reports (1)
  • SCRUM (1)
  • SDK (2)
  • SEO (1)
  • Servicios (2)
  • Sharepoint (9)
  • SharePoint 2010 (10)
  • SharePoint 2013 (4)
  • SharePoint Online (2)
  • SharpBox (1)
  • Shortcuts (1)
  • Sin categoría (1)
  • SOA (50)
  • SQL (5)
  • SQL Server (3)
  • SQL Server Management Studio (1)
  • SSIS (3)
  • SSL (1)
  • SSO (1)
  • Tracking Profile Editor (2)
  • Twitter (1)
  • Uncategorized (1)
  • Virtual Network (2)
  • Visual Studio 11 (1)
  • Visual Studio 2010 (2)
  • Visual Studio Online (1)
  • VMware (2)
  • WCF (24)
  • Web (1)
  • Web Api (1)
  • Windows (5)
  • Windows 8 (11)
  • Windows Azure (2)
  • Windows Live Write (1)
  • Windows Phone (7)
  • Windows Phone 8 (1)
  • Windows Scheduler (1)
  • windows8 (2)
  • WindowsRT (3)
  • WP7 SDK (1)

Manage

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org