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
Enabling the BAM Excel Add-In for Excel 2007
Aug 17, 2010
In BizTalk Server, Business Activity Monitoring (BAM) allows business users to view real-time data from their business processes The primary tool for defining
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
Announcing the Availability of the BizTalk ESB Toolkit 2.1
May 25, 2010
The BizTalk ESB Toolkit 21 has been released It is a collection of tools and libraries that extend BizTalk Server 2010's capabilities of supporting a loosely
BizTalk Server 2010 Beta Released
May 21, 2010
This post captures a historic moment in the BizTalk timeline: the launch of the 2010 Beta It highlights the shift toward NET 40 and the enhanced visual
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



