BizTalk Mapper – Cannot load source/destination schema
Apr 26, 2010
There is nothing more frustrating than opening a complex BizTalk Map only to find a blank screen and an error message stating that the Source or Destination
Debug BizTalk Custom Pipelines Components using Pipeline.exe utility – Pipeline file name i...
Apr 8, 2010
While trying to debug a custom pipeline component using the Pipelineexe utility, I keep getting the following error message: Pipeline file name is already
Calling an external assembly from Custom XSLT – Custom Extension XML (Grid Property)
Apr 6, 2010
While the BizTalk Mapper provides many functoids, complex business logic is often best handled in a custom XSLT file However, XSLT alone sometimes needs the
Deploy BizTalk Applications using MSI files – Concept and Best practices
Apr 6, 2010
A complete solution built on the BizTalk Server engine can contain several items (sometimes referred to as artifacts): orchestrations, pipelines, message
Debugging External assembly’s or pipeline components – Attach to Process – which BizT...
Mar 29, 2010
We can debug, for example, external assemblies that are called from within a BizTalk process or debugging pipeline components in run-time mode In Visual
BizTalk Orchestration Error Message – property ‘Microsoft.XLANGs.BaseTypes.Address...
Mar 12, 2010
When designing a BizTalk Orchestration, you might need to determine the destination of a message at runtime (for example, sending to a specific URL found
BAM Portal Configurations – Configure BAM Alerts (SQL Notification Services) on SQL Server ...
Mar 5, 2010
If you are using BizTalk Server 2009 and want to use BAM alerts, you will still need notification services Business Notification can run on SQL Server
EDI Experience – Common errors and solutions
Mar 4, 2010
Working with EDI in BizTalk Server can be challenging Because the EDI engine is strictly standards-compliant, the smallest configuration mismatch will cause a
Problem with Edifact Interchange and loopback adapter Receive Pipeline – Transation Set Err...
Mar 4, 2010
Using a Loopback adapter is a common pattern in BizTalk for testing or internal message routing However, when dealing with EDIFACT interchanges, this often




