Due to Microsoft .NET Framework Security Updates, some BizTalk Server installations may be affected. Access denied or Class not registered errors.

BizTalk engine will still process messages, including sending and receiving them.

The symptoms:

• You can’t see, stop or start host instances
• You can’t refresh applications
• Gives access denied or Class not registered errors while trying to load some panels inside BizTalk Server Administration Console
• Random errors in BizTalk Server Administration Console while browsing
• Other weird issues while deploying applications via Deployment Framework for BizTalk (BTDF)

.NET Framework (4.6.2) has received some security updates on 20th July 2018. These updates refresh some assemblies that are in use by BizTalk Server! Microsoft states that a fix is coming mid July 2018, but, at this moment, I’m not seeing these “fixes” in my machine…

The actual fix;

You need to uninstall ALL your .NET Framework updates for version 4.6.2 that were installed after 19th of July 2018! Follow these simple steps to uninstall them (if you don’t know how to do it):

1. Open Control Panel
2. Select Program and Features
3. On the left pane, select “View installed updates”
4. Uninstall every update that targets .NET Framework 4.6.X that were installed AFTER 19th July 2018

IMPORTANT NOTE: Uninstalling some of them may require a reboot. DO NOT REBOOT UNTILL ALL UPDATES ARE UNINSTALLED!

Below are some updates that were identified by users as source of their problems:

• BizTalk Server 2013 R2: KB4338600, KB4338601
• BizTalk Server 2010: KB4338602
• Other versions: KB4338600, KB4338605, KB4338613, KB4338814, KB4338424, KB4338419

The one that was causing my BizTalk Server Administration Console to fail was KB4338606. As you can see, this update isn’t listed above. Those updates were identified by other users, they may not, by any means, be the origin of your problems. This is why I prefer to uninstall them all! Remember, your mileage my vary.

If you have any questions or if you need help to figure this out, feel free to post a comment! I’ll try my best to help you out!

The post [FIX] BizTalk Server 2010, 2013, 2013 R2 & 2016 errors “Class not registered (WinMgmt)” or “Access denied” appeared first on Blog IT.

All HL7 must be multipart messages consisting of three segments:

• Body segment – The HL7 message (marked as message body part)
• MSH segment – The HL7 header
• Z Segment – HL7 custom segment

To generate the ORM HL7 message, the BTAHL72XSendPipeline requires that the “message type” property be promoted, otherwise the error “Body schema is missing” will be thrown.
This property cannot be directly set, because is a reserved property used by BizTalk, the only way is to copy from other message.
If your orchestration receives the same HL7 message type, it’s easy to fix this issue, just set the multipart properties from the inbound message using the “(*)” syntax. In this way, the “message type” property will be copied.
HL7MultipartMessage(*)=InputMsgForHl7BodyPart(*);

There are several posts with this fix like https://blogs.msdn.microsoft.com/biztalknotes/2013/03/06/biztalk-hl7-error-failure-executing-btahl72xsendpipeline-error-details-body-schema-is-missing/ and https://social.technet.microsoft.com/wiki/contents/articles/16181.how-to-execute-btahl72xsendpipeline-in-an-orchestration.aspx

If you do not have an incoming  HL7  message, the solution is a little bit tricky.

1. Create an BizTalk ORM message (you can use other HL7 message type or versions depending of the business requirements);
2. Force the “message type” promotion executing the XmlReceive pipeline (inline in orchestration);
3. Set the message created in1) to the multipart BodySegments segment;
4. Copy the ORM properties to the multipart message ( HL7MultipartMessage(*)=ORMMessage(*) )

Hope this helps!

The post BizTalk Server – HL7 Error: Failure executing BTAHL72XSendPipeline “Body schema is missing” appeared first on Blog IT.

The HL7 message will also be created with the same break line, generating an invalid HL7 message.

It’s easy to deal with it, just set PreserveWhitespace property in XmlDocument with “true”, before assigning it to the HL7 MSHSegment.

…
xmlDocument.PreserveWhitespace = true;
hl7msg.MSHSegment = xmlDocument;

You can get more info in https://msdn.microsoft.com/en-us/library/system.xml.xmldocument.preservewhitespace(v=vs.110).aspx.

The post BizTalk Server HL7 – Strange break lines in MSH segment appeared first on Blog IT.

Pic1. Exception: “Could not enlist Send Port – HRESULT: 0xC00CE557”

So, after some debugging, me and my teammate noticed an issue with some port filters inside a WCF Custom Send Port in the bindings XML, originally exported by BizTalk. Time to check the XML now!

Here’s how you can trace errors in XML:

• Open exported ports binding XML file:

Pic2. Origin of the exception selected

Notice this property, “Filter”. It has break lines and white spaces. BizTalk refuses to import bindings like this, and generates an exception. Worst part is that this exception is generic, and meaningless.

To fix this, you must remove all white spaces and all break lines inside this field. This problem appears because these filters have an “AND” relationship between them, and BizTalk can’t understand those mathematical relationships with all these white spaces and break lines among them.

The final and fixed XML property should look like this:

<SomePropertyName>all lines here without spaces or break lines</SomePropertyName>

If you run into some exceptions importing port bindings, you should analyze the bindings file and look for a XML property with spaces and break lines. Re-arrange and you should be OK importing bindings and enlisting ports now!

The post How to fix BizTalk Server Administration Exception 0xC00CE557: Could not enlist Send Port appeared first on Blog IT.

There’s not much information how to properly add a BRE rule in a BTDF deployment script.
It’s very easy to put it to work, but not so easy to get it there.

Just follow the below instructions :

1. Create the rule in Business Rule Composer.
   
2. Use the Rules Engine Deployment Wizard to export the created policy or vocabulary xml.
   
   
   
   
3. Put the exported policy or vocabulary xml in a VS project folder (I advise to put in Deployment/BRE/Policies folder).
   
4. Edit btdfproj file (if you dont’t know how to set this file, check codeplex BTDF site https://biztalkdeployment.codeplex.com).
   
5. Set “IncludeVocabAndRules” element with the value “true”.
   
6. Add the following elements  (set the policy or vocabulary xml name and location).
   
7. The BRE rules are always updated after MSI or VS deploy by executing the options “Deploy BizTalk solution” or “Deploy Rules or Vocabularies”.
   

This configuration also works with environment settings variables (${variablename}), allowing us for example to set different policy data in quality and production environments.

The post BTDF – How to config BRE policies or vocabularies appeared first on Blog IT.

If you don’t know what is BTDF, go to  https://biztalkdeployment.codeplex.com.

This Framework allow us to create an MSI deployment package directly  from Visual Studio or Command Line.
It also has a great feature that allow us to maintain only one binding file concerning all environments.
That binding template files are replaced for the correct environment data in the MSI generation.
The specific environment data is configured in a XML file that can be opened in Excel.

Sometimes there are releases that only have binding changes, and you want to use the best practice of always use BTDF generated data in your deployments.
So… how can you deal with this in BTDF.!! The VS menu does not have an option to generate environment bindings.

The BTDF installation give us a tool called xmlpreprocess, which is used in the MSI generation by the BTDF engine.
Xmlpreprocess tool allow us to merge a specific environment configuration with the binding template (normally named master binding), resulting in the transformed deployment binding.

It’s very easy to use.

1. Open a Command Line Prompt
2. Navigate to the  BTDF install folder “..\Framework\DeployTools” (normally  C:\Program Files (x86)\Deployment Framework for BizTalk 5.6\Framework\DeployTools)
3. Execute xmlpreprocess.exe /v /c /noDirectives /i:”PORT_BINDINGS_MASTER_XML_PATH” /o:” OUTPUT_BINDING_FILE_PATH” /d:CurDir=”MAIN_SOLUTION_FOLDER” /s:”ENVIRONMENT_TO_GENERATE_BINDING_CONFIG_XML”

For example

xmlpreprocess.exe /v /c /noDirectives /i:”C:\Projects\MyProject\Deployment\PortBindingsMaster.xml” /o:”C:\Projects\MyProject\GeneratedBindings\OutputBinding.xml” /d:CurDir=”C:\Projects\MyProject” /s:”C:\Projects\MyProject\Deployment\EnvironmentSettings\Exported_ProdSettings.xml”

The generated environment (Local, QA, PRD, …) is defined in xml file path after the “/s” parameter.

Hope this helps.

The post BTDF – Generate specific environment binding appeared first on Blog IT.

A Better ReadPropertyBag in BizTalk Pipeline components

Why full NuGet support for BizTalk projects is important!

Azure App Service: BizTalk Server PaaS Done Right

BizTalk Integration API Apps in Microsoft Azure App Service

Logic Service BizTalk Connectors

Azure App Services: BizTalk Rules

Azure App Services: Transform XML documents

London BizTalk Summit 2015 – Day 1 Recap

London BizTalk Summit 2015 – Day 2 Recap

BizTalk Server 2013 R2 for Low-Latency Scenarios

All about BAM!

Code and Tutorials

BizTalk Server 2013 – Perform a Function in Oracle 11g XE using the BizTalk Adapter Pack

BizTalk: How to (un)deploy Oracle PL/SQL scripts with BTDF

BizTalk: How to (un)deploy T-SQL scripts with BTDF

Configuring BizTalk Server infrastructure in High Availability on Microsoft Azure IaaS

BizTalk Orchestration handling webHttp REST GET requests

Build and generate MSI for BizTalk Server using Team Foundation Build Services

BizTalk IOC Autofac

BizTalk Server 2013 R2 Instrumenting BAM Activity Tracking with ETW

Managing and Cleaning BizTalk Server Marklog DB Best Practices

Tools

PowerShell to Configure BizTalk Server 2013/2013 R2 Host and Host Instances

BSTG NOS Addin

Upcoming Events

BizTalk Events Calendar  (RSS)

The post BizTalk News – Issue #15 appeared first on Blog IT.

To configure and set configuration data, Microsoft has an MMC Snap-In called “SSO Configuration Application”, that allow us to create and manipulate applications and their properties (http://www.microsoft.com/en-us/download/details.aspx?id=14524).

From the community there are several tools to set SSO configuration. The most well know was created by Richard Seroter in 2007 that allow us to manipulate previously created properties in an easy way (http://seroter.wordpress.com/2007/09/21/biztalk-sso-configuration-data-storage-tool/).  There are also some Richard Seroter tool improvements, like a version from Mark Burch in http://biztorque.net/archive/2010/06/07/74.aspx, that allow us to create new SSO properties.

BizTalk Deployment Framework also include an SSO module, that use a different approach of using the Excel to set SSO config data in each environment (http://biztalkdeployment.codeplex.com/).

To get configuration from SSO by code, you can use “SSOConfigHelper.cs” included in Microsoft BizTalk Server 2006 SDK, but still working with the latest Biztalk server versions (http://www.getcodesamples.com/src/2B2085E1/C4A921B1).
Just get the code and include “Microsoft.BizTalk.Interop.SSOClient.dll” in SSO install folder (for example C:\Program Files\Common Files\Enterprise Single Sign-On\Interop1.1\Microsoft.BizTalk.Interop.SSOClient.dll) and call the read method, setting the previous create application and property name.

Hope that 4 posts about SSO will help you to use SSO more frequently in BizTalk programming.

The post BizTalk Server Single Sign On – Save config data in SSO appeared first on Blog IT.

I’ve been reading all the stuff being written and it’s clear: the Microservices architecture has brought a big wave of surprise and enthusiasm around the BizTalk community! I leave you with some links and quotes I found relevant about the topic.

Edit: integrate videos available here

Integrate 2014

“Simply sit back, relax and watch this space for next few months!! there are tons of things happing, all good for people coming from Microsoft integration background” – Saravana Kumar

Integrate 2014 – RECAP

“Integration is no longer a vertical solution, it’s core to the application platform” – Kent Weare

Microsoft making big bets on Microservices

Integrate 2014 – Final Thoughts

“Microservices is not the name of the product, it’s a way you can build Stuff”

“BizTalk Services Isn’t Going Away, It’s Being Aligned to a Microservices Architecture”

“It’s a Good Day To Be a BizTalk Dev”

Integration and Microservices

“I cannot resist the temptation to call this new world ‘microPaaS’, or µPaaS” – Charles Young

BizTalk Microservices, Integrate 2014 and all my thoughts

“I’m pretty sure that what Power BI covers will replace our Business Activity Monitoring” – Nino Crudele

BizTalk Server, Microservices & APIs

Integrate 2014: Thoughts on the Announcement of the BizTalk Microservices Platform

“My immediate reaction was: this is Docker!” – James Corbould

Docker and Microsoft Partner to Drive Adoption of Distributed Applications to Every Enterprise Operating System and Cloud

“Microsoft and Docker share a common vision that multi-container applications should be assembled using both Dockerized Windows and Dockerized Linux components.”

 

About Microservices

Microservices (by Martin Fowler)

Microservices Relax

WaveMaker Unveils New API Designer for Enterprise Developers Using Microservices Architecture

Upcoming Events

BizTalk Events Calendar  (RSS)

The post BizTalk News – SPECIAL – Integrate 2014 appeared first on Blog IT.

The SSO configuration to support this feature is very easy.
First enter SSO Administration tool, and create a new affiliate application with the above settings (you can put any name in the application name):

In BizTalk Server Administration, when setting the receive location configuration, set the use SSO option, and use an isolated host with a running account that belongs to the SSO application administrators group (images above).

In the send port adapter configuration set the affiliate application created earlier.

To finalize the configuration, you must set SSO to allow ticket usage (by default is not allowed).
Execute the following instruction in the command prompt “ssomanage -tickets yes” (http://msdn.microsoft.com/en-us/library/aa559512.aspx)

The credential mapping is working without any “hand made” code creation.

The post BizTalk Server Single Sign On – Using SSO with adapters appeared first on Blog IT.