Hello,
I have an issue with EDI batching and tracking in BizTalk Server 2006 R2.
I use full-tracking for all our send ports, receive ports and orchestrations (we track message bodies and message properties before/after port/orchestration). Everything works fine till I start EDI batching. When I start EDI batching on a party (EDI properties / X12 Properties / Interchange Batch Creation Settings / Start button), batching works, but new issues appear:
1) BizTalk Server and SQL Server permanently consume a lot of CPU time
2) All messages (including batched ones) are processed correctly, but they are not tracked correctly. If I have a look at HAT, some information is missing and it seems that BizTalk has a problem with spreading tracking info about processed messages to BizTalk tracking database. There is no rule what is missing, sometimes incoming message, sometimes outgoing message, sometimes everything is tracked correctly.
I had a look at problem why BizTalk Server and SQL server consume a lot of CPU time. I checked SQL server profiler and found that the following 3 stored procedures are started repeatedly in infinite loop maybe hundreds times per second:
dtasp_CtxBegin
dtasp_CtxInsert
dtasp_CtxEnd
I tried to re-configure BizTalk and re-created all BizTalk databases and jobs.
I tried to clean-up BizTak message box (http://technet.microsoft.com/en-us/library/bb727781.aspx)
I tried to archive and clean-up all old data from BizTalk tracking DB using DTA Purge and Archive (BizTalkDTADb) job
… but without success.
I tried to switch off all tracking on ports and orchestration, restart biztalk host and batching and then BizTalk doesn’t consume CPU. But when I turn tracking on again, the same problem appears.
Thanks a lot,
Petr Janda