Biztalk does not track send / receive ports

Question

It seems that any new send or receive ports that I create do not display any tracking, even if I check all the tracking fields. I have an existing application and work with the reception and orchestration port, but sending tracking does not occur.

On the same computer, I also tried to create a new application. Created a port for sending and receiving and did not track at all. I did the same on a new biztalk installation on a different machine, and I got tracking so that I was not crazy.

I tried...

• Ticking each tracking window for receive, orh, send ports.
• creating a new host specifically for tracking
• recreation of the original host with a different name
• Sql service is running
• reboot system
• reload host instances
• restart biztalk services
• nothing is displayed in event logs
• all sql jobs are ok, except for the "monitor biztalk", which complains about 7 orphaned dta.
• does not see anything special that stands out from mbv, with the exception of the aforementioned dapha ophan.

Answer 1

In addition to Mike:

• You need to make sure that at least one of your hosts is enabled for tracking. In BizTalk Administrator, in the "Platform Settings", "Hosts", "Select a Host" section and enable tracking (the list of hosts also shows which hosts (hosts) support current tracking).

• You can also check if the SQL tracking agent job is running by looking directly in the database

  select count(*) from BizTalkMsgBoxDb.dbo.Spool (NOLOCK)

  select count(*) from BizTalkDTADb.dbo.Tracking_Parts1 (NOLOCK)

Basically, the coil should be a fairly low number (<10,000) and should return to a static level after a burst of messages, unless your suspended orcs are growing. And new messages should be copied from MessageBox to DtaDb.TrackingParts every minute, so Tracking_Parts1 should grow several records every 60-120 seconds after processing new messages, although they will eventually be cleared / archived according to your archiving / clearing tracking strategy.

In a Dev environment, more is more fun to track, since the HAT (orchestration debugger) will give you more information than the more you track. However, in a PROD environment, you typically want to minimize tracking to improve performance and reduce disk overhead. We simply track one instance, namely: “before processing” at the reception and “after processing” at the sending ports to our partners, and generally nothing at the internal ports and orcs. This allows us to provide sufficient evidence of the data received and sent.

Answer 2

This post may help some people: http://learningcenter2.eworldtree.net:7090/Lists/Posts/Post.aspx?ID=78

To track messages, among other factors, make sure that the "Send and receive messages" checkbox in the corresponding pipeline is enabled.

Answer 3

Please take a look at these two articles, What is Message Tracking? and Acumen in BizTalk Server Message Tracking . The first article has an interesting subject, and I will give it below, and the second should simply consolidate what you are trying to do.

The SQL Server Agent service must run on all MessageBox databases. The TrackedMessages_Copy_ job allows message organizations to track requests and WMI. To effectively copy message bodies, they remain in the MessageBox database and are periodically copied to the BizTalk Tracking database (BizTalkDTADb) using the TrackedMessages_Copy_ job. Using SQL Server Agent service is also a prerequisite for the archiving and cleaning process to work properly.

Answer 4

Do you use the default pipeline? Have you checked the tracking flags on them? There is some error in which pipeline tracking is disabled for standard pipelines.

More details here: http://blog.ibiz-solutions.se/integration/biztalk-global-pipeline-tracking-disabled-unexpectedly/

Answer 5

Ensure that the required tracking is enabled in the properties of the send pipeline used by your mail port. If message tracking is disabled in the send pipeline, nothing is tracked on the send port.