Posts Tagged ‘BizTalk’

After installing some upgrades in the BizTalk Server machine, in this particular case after installing Internet Explorer 10 I started to receive the following error message when I try to access BAM Portal:

“Failed to get data. If available, errors returned from the provider are listed below”


However without no error was listing… so what’s the problem and how can I solve it?

Additional I also get this error messages and bad behaviors:




Sometimes a website you’re visiting, in this case BAM Portal, doesn’t look like you expect it to. Images might not show up, menus might be out of place, and text boxes could be jumbled together. This can be caused by a compatibility problem between Internet Explorer and the site you’re on. When a site is incompatible with Internet Explorer, you’ll see the Compatibility View button in the Address bar.

Note: Not all website display problems are caused by browser incompatibility. Interrupted Internet connections, heavy traffic or network connections can also affect how a page is displayed.


To solve this problem you must turn on Compatibility View for BAM Portal in the IE10. You can do this by:

  • Clicking in the “Compatibility View” button that appears in the Address bar to display the site in Compatibility View.


Note: If you don’t see the button, there’s no need to turn on Compatibility View.

Once you turn on Compatibility View, Internet Explorer will automatically show that site in Compatibility View each time you visit. You can turn it off by tapping or clicking the button again. Or, you can clear the entire list of sites using Compatibility View by deleting your browsing history.

After one year and together again with the usual suspects: Steef-Jan Wiggers, Nino Crudele, Saravana Kumar and of course the host of the event Tord Glad Nordahl, BizTalk Innovation Day is back to Norway! This year also with 2 extra special guest speakers: MVP Kent Weare is coming all the way from Canada and we are hoping to have Microsoft BizTalk Product Group member to hold the key notes about BizTalk 2013 and Azure BizTalk Services.

BizTalk Innovation Day is a one-day (sometimes two) community driven event focused purely on Microsoft BizTalk Server related topics that has been conducted in several major European cities since Feb 2011: Amsterdam (Netherland), Milan (Italy), Stavanger (Norway), London (UK) and Porto (Portugal).


As happened last year this will be a two day event dedicated to BizTalk Server and all-around of Integration world and will occur on 25 and 26 September at the Clarion Hotel in Stavanger, one of the most exclusive hotels in Stavanger.

And we invite you all to join us where you can count with the following agenda:


08:30: Registration;

09:00: Welcome and Introduction;

10:45: Exposing Line of Business (LOB) services to mobile devices
by Kent Weare [Microsoft Integration MVP];

In this session Kent will demonstrate some of the different ways to expose SAP Line of Business data to mobile devices using BizTalk 2013 and the Azure Service Bus. The core principle that will be demonstrated will take a real world On-Premise BizTalk integration scenario and expose its functionality to external consumers using the aforementioned technologies.

10:00: Break;

10:15: BizTalk Server 2013 and the Windows Azure Service Bus: Hybrid Solutions
by Steef-Jan Wiggers [Microsoft Integration MVP];

BizTalk Server 2013 will bring on-premise systems closer to the cloud. This latest version of BizTalk Server will bring more capabilities and features to build hybrid solutions. In this session you will learn how to leverage BizTalk Server 2013 and Windows Azure Service Bus to create hybrid solutions. Real-world scenario’s will be featured with demo’s and code samples.

11:00: Key Notes of BizTalk 2013
by Microsoft

11:45: Lunch;

12:45: Management and Monitoring of BizTalk Server using BizTalk360
by Saravana Kumar [Microsoft Integration MVP]

Some of you might have attended the BizTalk innovation day in Stavanger last year and watched my session on BizTalk360. You may be thinking, you don’t want to hear the same story again. But, it’s pretty much 12 months since you heard the story and BizTalk360 is drastically advancing product with one simple objective "Increase the efficiency of day-to-day BizTalk Server operations". There were 2 major releases (5.0 and 6.0) since my last presentation and possibly a big announcement by the time I present the session in Stavanger again this year. So I can assure you, you’ll not be disappointed by this session.

13:30: BizTalk Mapping Patterns and Best Practices
by Sandro Pereira [Microsoft Integration MVP]

This presentation will explain how maps are processed internally by the engine of the product as we explore the map editor and will provide you with common mapper problems and solutions, i.e., some BizTalk Mapper Patterns specifying best practices and some of the best ways to address some of your needs within the context of message transformation and also to enhance your skills when using the BizTalk Server Mapper.

14:15: Break;

14:30: Proactivity in BizTalk
by Tord Glad Nordahl [Microsoft Integration MVP]

As BizTalk evolves and matures over time the importance of the applications and its dependencies is getting more attention. We all know that business critical application only ends up as business critical when they run in production. As a BizTalk Expert it’s important to be aware of the different areas to monitor and follow to create a proactive solution. When it comes to performance counters, logs, databases, disks, hardware e.g. it’s important to be aware when and if they are approaching a possible failure.

15:15: BizTalk Hostage Situation
by Nino Crudele [Microsoft Integration MVP]

There are many bad implementations of BizTalk around the world created by consultants that do not understand BizTalk. The deployed solution takes the IT budget hostage. The speaker will tell the story of a SWAT team taking control of the situation and solving the problem of a bad implementation. He will provide best practices and approaches for a solid BizTalk implementation that is future proof, resilient and sustainable.

16:00: Q and A
with 6 MVPs and Microsoft Product Group

20:00: Dinner;


(All labs run simultaneously for 1 hours and you can go to the one you want you will have the option to attend all labs based on the presentations)

09:00: Startup

09:30: Labs

11:30: Lunch

12:30: Labs

16:30: Event ends

You can find all detail about this event here.

Reserve your ticket now and we are looking forward to see you in September!


When we try to access BAM Portal, sometimes Office Web Components Display Cross-Domain warning messages such as:

“This Web site uses a data provider that may be unsafe. If you trust the Web site, click OK, otherwise click Cancel.”


Or this other common warning messages

“This page accesses data on another domain. Do you want to allow this?”

Or even:

“Failed to get data. If available, errors returned from the provider are listed below… Safety settings on this machine prohibit accessing a data source on another domain.”


This are some of the normal warning message that the Microsoft Office 2003 Web Components displays when a user try to accesses to BAM Portal, some because a scripted Web page tries to run ADO code from an untrusted provider (accessing data from a domain other than the one from which the Web page originates)

For ADO 2.7 and earlier you may receive: “This page accesses data on another domain. Do you want to allow this?”

However, for ADO 2.8 and later, the preceding message no longer appears. Instead, the following message appears in this context: “This Web site uses a data provider that may be unsafe. If you trust the Web site, click OK, otherwise click Cancel.”

The purpose for the alert is to prevent a Web page author from directing users to a potentially malicious page that uses the security context of the user to access data for which the author does not have access.


To avoid this messages in Microsoft Internet Explorer, you can add a secure Web site to your Trusted Sites zone on the Security tab of the Internet Options dialog box:

  • In the Internet Explorer window, click “Tools”, then click “Internet Options”.
  • Click the “Security” tab, and then select the “Trusted sites” zone.


  • Click “Sites” button, and then “Add” the BAM Portal to the Trusted sites zone


For some reason after having migrated a BizTalk 2006/Visual Studio 2005 solution to BizTalk 2010/VS 2010 using Visual Studio Conversion Wizard, I got the following error:

"Cannot generate serialization assembly {AssemblyName}.XmlSerializers.dll because it already exists. Use /force to force an overwrite of the existing assembly"


The migration of this project was divided into two parts:

  • First part is to migrate the project as is to the new environment in order to discontinue the old platform;
  • The second part is to improve the project with new functionalities available in the new version (migrate SOAP adapter to WCF and so on);


The XML Serializer Generator creates an XML serialization assembly for types in a specified assembly in order to improve the startup performance of a XmlSerializer when it serializes or deserializes objects of the specified types.

However, some time if you have a traditional Web Service reference in your BizTalk Project this error may suddenly appear. It seems that when you try to build the solution the SGEN process is having some trouble deleting the original XMLSerializers.dll and in result will give you that error.


This problem can be solved by:

  • Going to the path “%windir%\Microsoft.NET\assembly\” (.NET 4.0) or “C:\WINDOWS\assembly” (if you use previous version of .NET) and uninstall the corresponding Project name DLL from there.
  • And then rebuild the Project.

Limitation: each time you deploy the DLL to the GAC, the next time you need to build the project you first need to uninstall the DLL from the GAC


You also can solve this error by choosing not to generate a Serializiation assembly from the Project Properties.

  • Right-click in the project name and select “Properties” option
  • On the left tree option choose “Build” tag
  • Under the Output properties, from the drop box “Generate serialization assembly” select “Off”


Are you planning to install BizTalk360 on a Windows Server 2012 machine? Check out Installing and Configuring BizTalk360 on Windows Server 2012 / BizTalk Server 2013 (user guide) available for download on BizTalk36o website.


This user guide will explain how to install and configure BizTalk360 in an existing Microsoft BizTalk Server 2013 standalone machine (single computer) running under Windows Server 2012. This information will help you plan the BizTalk360 installation and configuration process and components on which it depends.

What is BizTalk360?

BizTalk360 ( is a web based (RIA) designed primarily to perform monitoring and support for BizTalk Server environments (Production, Test, Development). It addresses some of the common problems customers face today like governance/auditing, fine grained authentication, remote access and so on. It also makes life easy for people who support production BizTalk systems by providing various dashboard and greater visibility.

This tool is developed by Kovai Limited, based in London UK, but everyone knows this tool through its CTO Saravana Kumar, Microsoft BizTalk Server MVP since 2007 and a well-recognized member of the BizTalk community. Version is available for download here, give it a try!

You can download user guide from:

Installing and Configuring BizTalk360 on Windows Server 2012 / BizTalk Server 2013 (user guide)

This week I published 73 modern flat shape that will help you representing BizTalk Server physical architectures, Integration architectures (Cloud or Hybrid scenarios) or solutions diagrams in Visio 2013. However I found out that many people are still using Visio 2010, so I thought it would be a good idea to provide these new shapes also for Visio 2010… The result was 63 new modern flat shapes that are now joining the 35 shapes that already existed (two of them were remove from this version) making a total of a total of 98 shapes, representing:

  • BizTalk topologies (Standalone and Clustering)
  • BizTalk Runtime Architecture and ESB Toolkit
  • Receive and Send Pipelines, Inbound and Outbound Maps, Adapters and Filters
  • Receive Ports and Receive Locations (One-way and Request Response)
  • Send Ports (One-way and Solicit-Response)
  • BizTalk Out-of-box Adapters shapes
    • SMTP, SQL, File, FTP, SFTP, MSMQ, …
  • Windows Azure BizTalk Services and Cloud shapes
  • And many more…



Note: Not all the shapes that are available for Visio 2013 will be in this version but you can use this new shapes and resize them without losing quality.

You can download Visio 2010 Stencil for BizTalk Server (or Visio icons for BizTalk Server) from:

Collection of Visio 2010 Stencil for BizTalk Server (18.2 MB)
Microsoft | TechNet Gallery


Other Resources:

BizTalk Server database databases and their health are very important for a successful BizTalk Server database messaging environment. This is nothing new and everybody knows!

Although there can be many settings that we can configure, like auto-growth settings for BizTalk Databases (you can learn more here), there are two main things that we must understand and be aware, especially the database administrators:

  • Execution of the BizTalk Server SQL Agent jobs are crucial for managing the BizTalk Server databases and for maintaining optimal performance.
  • The Backup BizTalk Server job is the only supported method to backup the BizTalk Server databases and requires that all of the BizTalk Server databases are configured to use the SQL Server full recovery model.

BizTalk Server 2010/2013 is shipped out with a total of 13 SQL Agent jobs. 2 of these jobs must be configured. The two jobs that needs configuration are the two most important jobs:

  • The “Backup BizTalk Server“: This is the job provided by Microsoft to do a best practice backup of the BizTalk databases.
  • And the “DTA Purge and Archive“: This SQL Agent job purges and archives information from the tracking database, you do need to configure this job in order for it to work.

However what many times we forget is that this two jobs, by default, don’t provide functionalities for deleting backup files that have accumulated over time on our file system and we normally forget to create a “process” or a “job” to accomplish this until is too late. The result of that is… lots of times we just remember when disks are full and everything stop to work!

We can for example implementing your custom “sp_ DeleteBackupHistoryAndFiles” as you can see in my post: BizTalk 2013 Installation and Configuration – Configure BizTalk Server SQL Jobs (Part 15), however I personally don’t like this approach for two reasons:

  • I don’t like to change the scripts of the standard BizTalk jobs
  • And I also believe that this approach is very limited and doesn’t allow the flexibility that we all want.

Instead I prefer to create an SQL Server Maintenance Plan to delete BizTalk Database Backups to accomplish this task.

Maintenance Plan to clean BizTalk Database backup’s files

Maintenance Plans allows DBA’s to have flexibility to create a workflow to execute several tasks required to make sure that database are optimized, regularly backed up, and free of inconsistencies. However almost all of these tasks are warranted by the existing BizTalk jobs and I will not use them. The only thing we need is to create a task to clean BizTalk Database backup’s files from our file system.

The main advantage of this approach is that will allow us more flexibility for further changes and we can also use them to other backup’s that we have.

How to create a Maintenance Plan to clean BizTalk Database backup’s files

As a personal note, you should ensure that SQL Server Agent service is running because the maintenance plans depend on the Microsoft SQL Server Agent in order to run on a regular basis.

Important Note: this example is created to run in a developer machine, so if you are implementing this approach in production environments make sure to keep the backups for the time you see that fit your requirements or make sure the backups are save in an external storage before you delete this files from the file system.

To create the maintenance plan you need to:

  • Open the SQL Server Management Studio by choosing Start > Programs > Microsoft SQL Server [edition] > SQL Server Management Studio.


  • Press the “Windows key” to switch to Windows Server 2012 Start Screen and type “SQL Management” or “SQL” and click in “SQL Server Management Studio” option on Apps menu.
  • Expand the server and then the “Management” folder.
  • Right-click “Maintenance Plans” and select “Maintenance Plan Wizard”. This launches the wizard and you can now step through and create a plan customized to meet your maintenance requirements.


  • On the SQL Server Maintenance Plan Wizard page, click “Next”.


  • On the “Select Plan Properties” page:
    • In the “Name”: enter the name of the maintenance plan you are creating.
    • In the “Description”: enter a briefly describe your maintenance plan.
    • In the “Run as”: specify the credential that Microsoft SQL Server Agent uses when executing the maintenance plan – leave the default.
    • Select “Single schedule for the entire plan or no schedule” to specify the recurring schedule of the maintenance plan.


    • Under Schedule, click “Change…”
      • Under “Frequency”, on the “Occurs” list, select “Daily” and in the “Recurs every” box, enter how often the job schedule repeats in days: 1 Day.
      • Under “Daily frequency”, select “Occurs once at” and specific the time of day when the job schedule should run: 12:00:00
      • Leave the default values in the rest of the properties and click “OK”


  • Back to the Select Plan Properties page, click “Next”
  • On the “Select Maintenance Tasks” page, select “Maintenance Cleanup Task” from the list and click “Next”


  • On the “Select Maintenance Task Order” page, click “Next” to continue
  • On the “Define Maintenance Cleanup Task” page, specify the following properties:
    • Under “Delete files of the following type”: select “Backup files”
    • Select “Search folder and delete files based on an extension” to delete all files with the specified extension in the specified folder
      • Under “Folder”: specify the path and name of the folder containing the files to be deleted.
      • Under “File extension”: Provide the file extension of the files to be deleted.
      • Select also “Include first-level subfolders” option if to want to delete the files also from first-level subfolders under the folder specified in Folder.
    • Select “Delete files based on the age of the file at task run time” and specify the minimum age of the files that you want to delete under “Delete files older than the following” property
      • Specify 1 Day
    • Click “Next”


  • On the “Select Report Options“ page, click “Next”.
  • On the “Complete the Wizard” page, verify the choices made on the previous pages, and click Finish.


  • On the Maintenance Wizard Progress page, verify if every action where successful executed and then click “Close”


Finally I’m happy with the final result and ready to release the first version of this new version of Visio 2013 Stencils for BizTalk Server… This is a collection of 73 modern flat Visio 2013 shapes that will help you representing BizTalk Server physical architectures, Integration architectures (Cloud or Hybrid scenarios) or solutions diagrams in Visio 2013:

  • BizTalk Servers shapes
    • BizTalk, SQL, BAM, IIS and so on…
  • Common BizTalk artifacts:
    • Orchestrations, Receive and Send Pipelines, Transformations and Filters
  • BizTalk Out-of-box Adapters shapes
    • SMTP, SQL, File, FTP, SFTP, MSMQ, …
  • Business Activity Monitoring, Business Rules Engine, BizTalk Console Administration and BizTalk360
  • Windows Azure BizTalk Services and Cloud shapes
  • Common Integration Servers shapes
    • SMTP, Active Directory, Web, Mainframe, …
  • Certificates, RFID, Gateway, Secure Message and many more…


As I said in my previous post, this is a major upgrade, apart from improve some of the existing shapes, several shapes were removed (like logo types and “static” receive port representations)… but many new ones were created for example: “Cloud” and “Bridges and other to provide better representation of receive and send ports. For you to have a good perspective we went from 37 to 73 available shapes that you can use and resize without losing quality!

Another big complaints that existed in the previous version was:

  • The size of the stencil file – 26,5MB
  • And the lack parameterization or flexibility on some of the shapes, specially receive and send ports shapes available

Well this two issues were solved this version. The size of the file is now 822KB! And all the shapes can be modify or reconfigured and you can apply different design templates.

There are still some points that could be improved as well as adding new stencil and I expect next month to release a new version with some of these improvements.


  • Download the file and copy to the folder “C:\Users\you_user\Documents\My Shapes” (that is the default folder for the Visio custom shapes)
  • To access the shapes in Visio, select from the Shapes Windows: “More Shapes -> My Shapes -> BizTalkServerStencilsForVisio2013.vssx”


You can download Visio 2013 Stencil for BizTalk Server (or Visio icons for BizTalk Server) from:

Collection of Visio 2013 Stencil for BizTalk Server (822 KB)
Microsoft | TechNet Gallery


Other Resources:

It was just over two years since I published the first release of my Visio stencils for BizTalk Server and after many downloads, feedback, suggestions and some complaints :)… I decided that it was time to make a new upgrade!

This time will be a major upgrade, apart from improve some of the existing shapes, remove several and of course add new ones for example: "Cloud" and "Bridges", I also decided to use a more current design: metro style, similarly to what happens with the appearance of new shapes in Visio 2013.

Of course I’m not doing it all from scratch (I’m not a designer), instead I’m reusing many of the things that already exist today and join them.

So, if you want, now is the time to give your feedback and suggestion to what shapes you like to have… Take a look to the first scratch:


UPDATE: Here are some of the new shapes that will be available in the next version of Visio Stencils for BizTalk Server:

  • Certificates
  • Business Activity Monitoring
  • Business Rules Engine
  • BizTalk360 Server
  • SMTP Server
  • BizTalk Administration Console
  • Web Server
  • and Windows Azure BizTalk Virtual Machine


In the past I developer a demo on “How to Call Orchestration from another project or from another BizTalk Application” that you can read here and download the source code from Code Gallery here.

This demo was compose by one Visual Studio Solution with two different projects:

  • Project1
    • Orch1
    • Schema1
  • Project2
    • Orch2

However there were a few questions about how we can accomplished that using two different solutions… well is the exact same process, but to help clarify this topic and to better help the community members that placed the questions I decide to create a different demo.

In this demo we will create two Visual Studio Solution:

  • CallExternalOrchestrationCommonSolution with a common orchestration that will be called from others orchestrations
    • This will be deployed to a BizTalk Application called “CallExternalOrchestration.Common
  • CallExternalOrchestrationMainSolution with a main Orchestration that will call the common Orchestration using the “Call Orchestration” shape.
    • This will be deployed to a BizTalk Application called “CallExternalOrchestration

In both of the solution I will describe the basic steeps (or the most important steeps) to accomplished

Creating the Common Solution: CallExternalOrchestrationCommonSolution

This project contain an orchestration that will receive two input string (however you can define other types of input like message or other types) and will construct a message that will be sent to folder on the file system.


Again, I will not explain all the steps to create the entire flow of the orchestration. The most important thing here is to define the “Type Modifier” property of the orchestration.

If we make an analogy with C#, we can say that this property is the same as the Accessibility Levels to C# members or types. The “Type Modifier” property defines the scope of an Orchestration, i.e., it indicates the access restrictions to this Orchestration. An Orchestration can be public, private, or internal.

  • If it is Public, it is visible to anyone interacting with the orchestration.
  • If it is Private, it is visible to other orchestrations within the same project and namespace.
  • If it is Internal, the port type is visible only within the project.

When we create an Orchestration, the default “Type Modifier” is “Internal”. So to be able to call this orchestration from a different Visual Studio Solution or different project we need to set the “Type Modifier” to “Public”.

To set the “Type Modifier” property for an orchestration to “Public” you need to:

  • Open the orchestration in Microsoft Visual Studio
  • Right-click somewhere in the orchestration designer (except in the shapes otherwise you will go to the shape properties), for example the green start shape at the top of the orchestration and select the “Properties Windows” option to display the Orchestration Properties dialog


  • Set the “Type Modifier” property to Public as you see in the picture.

Compile and deploy the solution.

Creating the Main Solution: CallExternalOrchestrationMainSolution

The second project, basically contains one orchestration that will receive an input message from a folder on the file system and will call a common (or external) orchestration.


Again, I will not explain all the steps to create the entire flow of the orchestration. The most important thing here is to import the reference (DLL) that contain the common orchestration that we want to call.

To import the reference to your project you need to:

  • In Solution Explorer, right-click in “References” and select “Add Reference”.
  • In the “Add Reference” dialog box, select the “Browse” tab that enables you to browse for a component in the file system.
  • Select the components you want to reference, and then click OK.
    • You can select multiple components by holding down the CTRL key, provided the components are all on the same tab.

Now if you drag a “Call Orchestration” shape to your orchestration you will be able to select the common orchestration that we create earlier, as you can see in the picture bellow:


Once again, compile and deploy the solution.

Download the sample:

How to Call Orchestrations developed in a different Visual Studio Solution (206.2 KB)
Microsoft | MSDN Code Gallery