Archive

Posts Tagged ‘2.2’

Tracing with ESB Toolkit 2.2

May 13, 2013 3 comments

Thanks to Tomasso Groenendijk for figuring this one out and sharing.

As with previous versions of the ESB Toolkit there is a minor change required to get tracing working. The switch name no longer has the version number appended to it. So instead of “BizTalkESBToolkit20” or “BizTalkESBToolkit21” as in previous versions, it is now “BizTalkESBToolkit”.

This should remain constant going forward removing the need to guess what the switch name is on each release!

Similar to ESB Toolkit 2.1, the full list of steps are:

  1. In Notepad openC:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config for 32-bit
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CONFIG\machine.config for 64-bit
  2. Locate the line with the closing configSections tag.
  3. Under that line paste the following section:
    <system.diagnostics>
          <switches>
              <add name="BizTalkESBToolkit" value="4"/>
          </switches>
    </system.diagnostics>
  4. Save and close machine.config.
  5. Start the DebugView program (Download)
  6. In DebugView, on the Capture menu, click Capture Global Win32 to make sure that it is checked.
  7. In the BizTalk Server Administration console, restart the BizTalkServerApplication host instance.
Advertisements

ESB Toolkit 2.2 Itinerary Designer Installation

April 22, 2013 4 comments

Brian Loesgen has a post on his blog describing an issue he ran into performing a clean build of BizTalk Server 2013 and ESB Toolkit 2.2, where the Itinerary Designer extension is not registered in Visual Studio 2012 after the ESB Toolkit 2.2 installation step.

I experienced this also so it may be more widespread than first thought. I’d be interested to hear how many other people run into it; it might be the case that this step will need to be added to installation instructions.

Before Brian pointed me to his post I had resolved this inadvertently when I installed the latest Visual Studio 2012 update, which would have resulted in a similar command being executed with the same outcome.