Nebular Blog

We had some issues with slow message processing on a BizTalk server due to throttling and I was just about to write a long blog post about this, when I stumbled upon this blog-entry :-)

This is a great post detailing which performance counters to use and how to determine if throttling occurs and what the cause (state) is.

http://blogs.msdn.com/b/biztalkcpr/archive/2009/05/27/throttling.aspx

Christian Staerk  

BizTalk Server

This is a great tool to use when you are inspecting a BizTalk Server installation.

Simply run it, and it will generate a HTML-report with a detailed summary of the entire setup. Additionaly it will also check for a large number of problems including if nescessary hotfixes have been applied, sql-jobs not running, throttling etc. etc.

The latest version can be found here:

http://blogs.technet.com/b/jpierauc/

Christian Staerk  

BizTalk Server

We have multiple versions of our BizTalk applications running simultaneously and when constantly upgrading, you end up with a bunch of receive- and sendports that are no longer used by any orchestrations and should be cleaned up.

As a help to determine which ports that are candidates for deletion, you can use the SQL below.

Note: Any direct bound ports and ports that only rely on a filter will also show up here.

/******                 

******  Script to determine which send- and receiveports are not bound
******  to any orchestrations

******/

 

select 'Sendport: ' + nvcName as [ ]

from BizTalkMgmtDb..bts_sendport SP

left outer join BizTalkMgmtDb..bts_orchestration_port_binding OPB

            on SP.nID = OPB.nSendPortID

where OPB.nSendPortID is null

 

union

 

select 'ReceivePort: ' + nvcName

from BizTalkMgmtDb..bts_receiveport RP

left outer join BizTalkMgmtDb..bts_orchestration_port_binding OPB

            on RP.nID = OPB.nReceivePortID

where OPB.nReceivePortID is null

 

order by 1

Christian Staerk  

BizTalk Server

Sometimes you need to call gacutil or other SDK tools from build-events and in order to do this, they need to be added to the path.

Not exactly rocket science, but I always forget the macro and for future reference the following line will do the trick:

call "$(DevEnvDir)..\..\VC\vcvarsall.bat" x86

Christian Staerk  

Visual Studio 2010, .Net