Microsoft Hotfix BizTalk Server 2009 – Orchestration Designer incorrectly indicates that th...
Problem In Microsoft Visual Studio, you create a Microsoft BizTalk Server 2009 project by working in BizTalk Server 2009 Orchestration Designer A red
Microsoft Hotfix BizTalk Server 2009 – Schema References broken
Problem On a computer that is running Microsoft BizTalk Server 2009, you use Microsoft Visual Studio to develop a BizTalk application In your BizTalk project,
BizTalk XSLT Reuse (xsl:include and xsl:import): Resolving of external URIs was prohibited error
A client of mine, use a strategy for re-use XSL, basically, they have custom XSLT with external XSLT’s that contain global functions that can be used inside
BizTalk Mapper – Cannot load source/destination schema
Recently I try to test a BizTalk map the test fails and for my surprise, it gives me the following error: "Cannot load source/destination schema:
Debug BizTalk Custom Pipelines Components using Pipeline.exe utility – Pipeline file name i...
While trying to debug custom pipeline component using “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)
In complex maps is usual to have scripting functoid with custom inline XSLT, and sometimes is useful to call custom NET components directly from XSLT So,
Deploy BizTalk Applications using MSI files – Concept and Best practices
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...
We can debug, for example, external assembly’s 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...
I have an orchestration process that dynamic send email notifications: When I first try to compile the orchestration I receive back the following error
BAM Portal Configurations – Configure BAM Alerts (SQL Notification Services) on SQL Server ...
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 2008