Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

KBAlertz.com: (841334) - Explains possible causes and resolutions for the Reading error. Exception information: TDDS failed to read from source database. SQLServer: SQLSERVER, Database: BizTalkMsgBoxDb. error message on a server that is running BizTalk Server 2004.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]






Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You receive a "TDDS failed to read from source database." error message in the application log of a computer that is running BizTalk Server 2004

View products that this article applies to.
Article ID:841334
Last Review:December 4, 2007
Revision:2.4
On This Page

SYMPTOMS

You receive an error message that is similar to the following in the application log of a server that is running Microsoft BizTalk Server 2006 or Microsoft BizTalk Server 2004:
Reading error. Exception information: TDDS failed to read from source database. SQLServer: SQLSERVER, Database: BizTalkMsgBoxDb.
You may also receive one of the following error messages in the application event log:
Error message 1
Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. SQL Server: SQLSERVER Database: BizTalkMsgBoxDb
Error message 2
Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. Cannot open database requested in login 'Login'. Login fails.
Error message 3
Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock.The ConnectionString property has not been initialized. SQLServer: SQLSERVER, Database: BizTalkMsgBoxDb
NoteSQLSERVER represents the name of the computer that is running SQL Server that houses the BizTalk MessageBox database, Login is a placeholder for a user name, and BizTalkMsgBoxDb is a placeholder for the name of the BizTalk Server MessageBox database.

Back to the top

CAUSE

You may receive this error message for the following reasons:
•The user account that is specified as the Logon for a BizTalk Server Host instance that tracking is enabled for is not a member of the BizTalk Application Users group on the computer that is running SQL Server that houses the Health and Activity Tracking, Business Activity Monitoring, and MessageBox databases.
•An orphaned SQL Session is preventing the Tracking Data Decode Service (TDDS), also known as the BAM Event Bus Service, from starting.

Back to the top

RESOLUTION

To resolve this problem, check the text of the error description that immediately follows the error text that is listed in the Symptoms section. Depending upon the text of the error description that immediately follows the error text, follow these steps:
•If the error text that appears is similar to the following error message:
EXECUTE permission denied on object 'TDDS_Lock', table 'xxx', owner 'xxx'. SQLServer: xxx, Database: xxx.
Make sure that the user account that is specified as the Logon for a BizTalk Server Host instance for which tracking is enabled is a member of the BizTalk Application Users group on the computer that is running SQL Server that houses the Health and Activity Tracking, Business Activity Monitoring, and MessageBox databases. Also make sure no other BizTalk servers process the same tracking data from the same BizTalk MessageBox database.

Note xxx is a placeholder for the actual name of the table, the database owner, the computer that is running SQL Server, and the database name.
•If the error text that appears is similar to the following error message:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Follow the steps that are listed in the following Microsoft Developer Network (MSDN) article for troubleshooting orphaned SQL sessions:
http://msdn2.microsoft.com/en-us/library/aa275788(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa275788(SQL.80).aspx)

Back to the top

STATUS

This behavior is by design.

Back to the top

MORE INFORMATION

The "Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock" error message indicates that more than one Tracking Data Decode Service (TDDS) is processing at the same time and on the same data. This behavior locks the data and prevents access to the data. If you receive this error message in a clustered or multi-node BizTalk Server environment, follow these steps to make sure that your domain groups are added to the correct SQL Server database roles that are created when BizTalk Server is installed.

Note You must follow these steps on each instance of SQL Server on which BizTalk Server is installed.

Back to the top

Microsoft SQL Server 2005

Configure the BAMArchive database

1.Open SQL Server Management Studio.
2.Expand the instance of SQL Server that you want to configure, expand Databases, expand BAMArchive, expand Security, expand Roles, and then click Database Roles.
3.Double-click BTS_ADMIN_USERS. If the BizTalk Server Administrators group is not a member of this role, add the BizTalk Server Administrators group to the role, and then click OK.
4.Click Users. If the BizTalk Isolated Host Users group is not a login for this database, add the BizTalk Isolated Host Users group login to the database, and then click OK.
5.Click Database Roles, and then double-click BTS_HOST_USERS. If the BizTalk Isolated Host Users group is not a member of the BTS_HOST_USERS role, add the BizTalk Isolated Host Users group login to the BTS_HOST_USERS role, and then click OK.

Configure the BAMPrimaryImport database

1. Under Databases, expand BAMPrimaryImport.
2.Expand Security, and then click Users.
3.Add the BizTalk Service Account (BtsService) account as a user. This step is not performed automatically when you run the BizTalk Server Configuration Wizard (Configuration.exe). To do this, right-click Users, and then click New User, add the user, and then click OK.
4.Expand Roles, and then click Database Roles.
5.Double-click BAM_EVENT_WRITER, add the BizTalk Service Account and the BizTalk Server Administrators group logins to the BAM_EVENT_WRITER role, and then click OK.
6.Double-click BAM_ManagementWS, add the BizTalk Service Account and the BizTalk Server Administrators group logins to the BAM_ManagementWS role, and then click OK.

Configure the BizTalkDTADb database

1. Under Databases, expand BizTalkDTADb.
2.Expand Security, expand Roles, and then click Database Roles.
3.Double-click BAM_EVENT_WRITER. Add the BizTalk Server Administrators group login and the BizTalk Service Account login to the BAM_EVENT_WRITER role, and then click OK.
4.Double-click HM_EVENT_WRITER. Add the BizTalk Server Administrators group login and the BizTalk Service Account login to the HM_EVENT_WRITER role, and then click OK.

Configure the BizTalkMgmtDb database

1.Under Databases, expand BizTalkMgmtDb.
2.Expand Security, expand Roles, and then click Database Roles.
3.Double-click BAM_CONFIG_READER. Add the BizTalk Server Administrators group login and the BizTalk Service Account login to the BAM_CONFIG_READER role, and then click OK.

Configure the BizTalkMsgBoxDb database

1.Under Databases, expand BizTalkMgmtDb.
2.Expand Security, and then click Users.
3.Right-click the right pane, click New User, add the BizTalk Service account as a login to this database, and then click OK.
4.Expand Roles, and then click Database Roles.
5.Double-click BAM_EVENT_READER, add the BizTalk Service account login to the BAM_EVENT_WRITER role, and then click OK.

Back to the top

Microsoft SQL Server 2000

Configure the BAMArchive database

1.Open SQL Server Enterprise Manager.
2.Expand the instance of SQL Server that you want to configure, expand Databases, expand BAMArchive, and then click Roles.
3.Double-click BTS_ADMIN_USERS.

If the BizTalk Server Administrators group is not a member of this role, click Add to add the group, and then click OK.

Note If the BizTalk Server Administrators group is not available, follow these steps:
a. Click Cancel.
b. Click Logins.
c. Add the BizTalk Server Administrators group as a new login for the database, and then click OK.
d. Click Roles.
e. Click Add to add the BizTalk Server Administrators group to the role.
f. Click OK.
4.Click Users.

If the BizTalk Isolated Host Users group is not a login for this database, right-click the right pane, click New User, add the BizTalk Isolated Host Users group login to the database, and then click OK.
5.Click Roles, and then double-click BTS_HOST_USERS.

If the BizTalk Isolated Host Users group is not a member of the BTS_HOST_USERS role, click Add to add the BizTalk Isolated Host Users group login to the BTS_HOST_USERS role, and then click OK

Configure the BAMPrimaryImport database

1.Under Databases, expand BAMPrimaryImport.
2.You must add the BizTalk Service Account (BtsService) as a user. This step is not performed automatically when you run the BizTalk Server Configuration Wizard (ConfigFramework.exe). To do this, follow these steps:
a. Click Users.
b. Right-click the right pane, click New User, and then add the BizTalk Service Account login to this database.
c. Click OK.
3.Click Roles, and then double-click BAM_EVENT_WRITER.
4.Add the BizTalk Service Account and the BizTalk Server Administrators group logins to the BAM_EVENT_WRITER role.
5.Click OK.
6.In BizTalk Server 2003, double-click BAMQueryWS under Roles. In BizTalk Server 2006, double-click ManagementWS under Roles.
7.Add the BizTalk Service Account and the BizTalk Isolated Host Users group logins to the BAMQueryWS role.
8.Click OK.

Configure the BizTalkDTADb database

1.Under Databases, expand BizTalkDTADb.
2.Click Roles, and then double-click BAM_EVENT_WRITER.
3.Add the BizTalk Server Administrators group login and the BizTalk Service Account login to the BAM_EVENT_WRITER role.
4.Click OK.
5.Under Roles, double-click HM_EVENT_WRITER.
6.Add the BizTalk Server Administrators group and the BizTalk Service Account login to the HM_EVENT_WRITER role.
7.Click OK.

Configure the BizTalkMgmtDb database

1.Under Databases, expand BizTalkMgmtDb.
2.Click Roles, and then double-click BAM_CONFIG_READER.
3.Add the BizTalk Service Account to the BAM_CONFIG_READER role.
4.Click OK.

Configure the BizTalkMsgBoxDb database

1.Under Databases, expand BizTalkMsgBoxDb.
2.Click Users.
3.Right-click the right pane, click New User, and then add the service account as a login to this database.
4.Click OK.
5.Under Roles, double-click the BAM_EVENT_READER role.
6.Add the BizTalk Service Account to the BAM_EVENT_READER role.
7.Click OK.
Important By default, these database security settings are already set when you configure BizTalk Server 2004.

For more information about orphaned sessions, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/aa275788(SQL.80).aspx (http://msdn2.microsoft.com/en-us/library/aa275788(SQL.80).aspx)

Back to the top

APPLIES TO
•Microsoft BizTalk Server 2004 Developer Edition
•Microsoft BizTalk Server 2004 Partner Edition
•Microsoft BizTalk Server 2004 Standard Edition
•Microsoft BizTalk Server 2006 Developer Edition
•Microsoft BizTalk Server 2006 Enterprise Edition
•Microsoft BizTalk Server 2006 Standard Edition

Back to the top

Keywords: 
kbprb KB841334

Back to the top

    

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name
(Optional) Public URL Or Email
Comments
No HTML -- Text Only Please

 



Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting