Friday, June 09, 2006 1:44 AM
by
Paul Wu
BAM EventBus Service Error: TDDS lock...
|
The other day, I found this entry in the event log: |
|
|
Event Type: Error
Event Source: BAM EventBus Service
Event Category: None
Event ID: 25
Date: 4/2/2006
Time: 4:16:28 PM
User: N/A
Computer: SERVERNAME
Description:
Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock.Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. SQLServer: SERVERNAME\BIZTALK, Database: BAMPrimaryImport.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. | |
TDDS (Tracking Data Decode Service, also known as the BAM Event Bus Service) is responsible for moving data from the MessageBox to the tracking database as well as migrating collected data to the BAMPrimaryImport databases.
It turned out that I had added two additional Hosts with tracking turned on which was not an issue by itself. I then proceeded to create HostInstances and assigned different service accounts for logins. Effectivily, this caused the HostInstances to access SQL under different thread and increased the chances of locking. |
|
Solution:
-
Unchecking the "Allow Host Tracking" option on hosts that use a different service account.
-
If you need to track all hosts, run all the HostInstances under the same service account.
|
Comments
Anonymous comments are disabled
About Paul Wu
Paul Wu is a Principal Consultant @
RuleMasters. With over 18 years of experience in the software industry, Paul is a seasoned Software Architect and a Microsoft Certified Technical Specialist in BizTalk Server and SQL Server.
The opinions expressed in this blog are my own and in no way reflect the policies and viewpoint of my employer.