Microsoft Hotfix BizTalk Server 2009 – Schema References broken
May 11, 2010
Maintaining legacy BizTalk environments requires knowing exactly where the "landmines" are buried One of the most notorious issues in BizTalk Server 2009 is
BizTalk XSLT Reuse (xsl:include and xsl:import): Resolving of external URIs was prohibited error
Apr 26, 2010
A client of mine uses a strategy for re-use XSL, basically, they have a custom XSLT with external XSLTs that contain global functions that can be used inside
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
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
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
Uninstall on BizTalk Beta and SQL tables – Cannot drop database “BizTalkMsgBoxDb̶...
Mar 2, 2010
Recently, I uninstalled the beta version of BizTalk 2009 Enterprise I have to remove BizTalk SQL tables because they were not compatible with the development
Internal SOAP Processing Failure
Feb 24, 2010
Recently, I tried to invoke an orchestration publish as a Web Service, and if you are working with the BizTalk SOAP adapter, you have likely encountered the
