2 min read
BizTalk Compilation problem – Compiler for file type ‘*.xsd’ failed. Value cann...
Sandro Pereira
Jul 21, 2010
Every BizTalk developer has a favorite "weird" error Near the top of that list is the infamous "Parameter name: pUnk" error It sounds like a joke, but it’s
2 min read
Microsoft Hotfix BizTalk Server 2009 – Orchestration Designer incorrectly indicates that th...
Sandro Pereira
May 11, 2010
If you are maintaining a BizTalk Server 2009 environment, you have likely encountered the "Ghost Error" phenomenon: you open an orchestration, and several
2 min read
Microsoft Hotfix BizTalk Server 2009 – Schema References broken
Sandro Pereira
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
2 min read
BizTalk XSLT Reuse (xsl:include and xsl:import): Resolving of external URIs was prohibited error
Sandro Pereira
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
3 min read
BizTalk Mapper – Cannot load source/destination schema
Sandro Pereira
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
2 min read
Debug BizTalk Custom Pipelines Components using Pipeline.exe utility – Pipeline file name i...
Sandro Pereira
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
3 min read
BizTalk Orchestration Error Message – property ‘Microsoft.XLANGs.BaseTypes.Address...
Sandro Pereira
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
3 min read
EDI Experience – Common errors and solutions
Sandro Pereira
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
3 min read
Problem with Edifact Interchange and loopback adapter Receive Pipeline – Transation Set Err...
Sandro Pereira
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
