There was a failure executing the send pipeline: “Please ensure that exsmime.dll has been r...
Oct 8, 2010
For no reason, one of my BizTalk 2006 R2 Lab environment begin to display the following error: “message sent to adapter "FILE" on send port
BAM – Why are the times for my tracking data in the BAM portal incorrect?
Aug 18, 2010
BAM captures milestones for objects derived from MicrosoftBizTalkBamEventObservationEventStream in Coordinated Universal Time (UTC) format When you send
BAM Excel Add-In for Excel 2007 – This workbook has lost its VBA project, ActiveX controls and an...
Aug 17, 2010
I have installed and enabled the BAM Excel Add-in in Excel 2007 Now, when I start Excel, I get the following error message: "Repairs to BAMxla'Excel was
BizTalk Pipeline Component – The specified module could not be found. (Exception from HRESU...
Jul 29, 2010
You’ve deployed your custom pipeline component, added it to the GAC, and configured your receive location But when a message arrives, the process fails with
Fixing BizTalk ENTSSO – Could not create SSOSQL. To fix the problem, reinstall SSO or try &...
Jul 21, 2010
The Enterprise Single Sign-On (ENTSSO) service is the backbone of BizTalk Server security When it fails, the entire BizTalk environment can grind to a halt
BizTalk Compilation problem – Compiler for file type ‘*.xsd’ failed. Value cann...
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
Microsoft Hotfix BizTalk Server 2009 – Orchestration Designer incorrectly indicates that th...
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
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

