BizTalk 2010 Tracking issue: No tracking on ports

We’ve found a problem with the tracking on all of our ports in BizTalk. As well as the receive and send ports didn’t track any messages, although all proper tracking options were set according to the BizTalk admin console. However, when we did a binding export it only showed PipelineEvents as TrackingOption, so ServiceStartEnd and MessageSendReceive were missing.

When configuring all tracking options on the used pipelines, all was working correctly. So only the tracking options set on the ports itself seemed to be ignored.

The problem appeared to originate in the table StaticTrackingInfo of the BizTalkMgmtDB, where a value of 0x10000000 was present for some of the biztalk pipelines instead of 0x13000000. So to set these records straight, I used this T-SQL command:

begin transaction

update BizTalkMgmtDb.dbo.StaticTrackingInfo set imgData = 0x13000000 where strServiceName in(
 
‘Microsoft.BizTalk.DefaultPipelines.XMLTransmit’
,
‘Microsoft.BizTalk.DefaultPipelines.XMLReceive’,
 
‘Microsoft.BizTalk.DefaultPipelines.PassThruTransmit’,
 
‘Microsoft.BizTalk.DefaultPipelines.PassThruReceive’)

–commit

The problem was rather quickly located thanks to this blog.
Advertisements

BizTalk file mask difference for windows 7 and windows server 2008 r2

Problem
When defining a file mask for a specific extension for a file receive location on BizTalk, there’s a difference in which files will be processed depending on the installed OS.

For example, a file receive location on BizTalk 2010 in Windows 7 with extension *.xls will not only process xls files but also xlsx files. While the exact same file mask defined on a receive location in Windows Server 2008 R2 will only pickup files with extension xls.

Cause
This behaviour is caused by the Windows operating system and can be reproduced without BizTalk in a command prompt.

Create 2 files in a folder location: one with extension txt the other with extension txt1. When you type ‘DIR *.txt’ in the command prompt on Windows 7, 2 files will be found. When doing the same on Windows Server 2008 R2, only 1 file will be found.

BizTalk error: ‘The message found multiple request response subscriptions’

Problem

When trying to send a message to multiple request response ports you can receive the following error in BizTalk:

The message found multiple request response subscriptions. A message can only be routed to a single request response subscription.

Error

Solution

First of all, you’ll need to reconsider if it’s architecturally sound to route a message to two request response ports? if yes, read further

Pre-BizTalk 2010

hot fix available at location http://support.microsoft.com/kb/923632

BizTalk 2010

1) Inside the BizTalk administration console open the BizTalk Settings Dashboard

Open

2) Go to the tab for the hosts settings, and select the host used by the request response ports.

DB

3) Check the checkbox for property Allow Multiple Responses

Setting