Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 949298 - Last Review: March 4, 2008 - Revision: 1.2
The BizTalk host instance may recycle unexpectedly under high-load conditions in BizTalk Server 2006
In Microsoft BizTalk Server 2006, the BizTalk host instance may recycle unexpectedly under high-load conditions. When this problem occurs, you may receive an error message in the Application log. The error message resembles one of the following:
Error message 1
An error occurred that requires the BizTalk service to terminate. The most
common causes are the following:
1) An unexpected out of memory error.
OR
2) An inability to connect or a loss of connectivity to one of the BizTalk
databases.
The service will shutdown and auto-restart in 1 minute. If the problematic
database remains unavailable, this cycle will repeat.
Error message: Error message: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your
network documentation.
Error source:
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplication
Error message 2
An error occurred that requires the BizTalk service to terminate. The most
common causes are the following:
1) An unexpected out of memory error.
OR
2) An inability to connect or a loss of connectivity to one of the BizTalk
databases.
The service will shutdown and auto-restart in 1 minute. If the problematic
database remains unavailable, this cycle will repeat.
Error message: Error message: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Error source:
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplication
Error message 3
An error occurred that requires the BizTalk service to terminate. The most
common causes are the following:
1) An unexpected out of memory error.
OR
2) An inability to connect or a loss of connectivity to one of the BizTalk
databases.
The service will shutdown and auto-restart in 1 minute. If the problematic
database remains unavailable, this cycle will repeat.
Error message: [DBNETLIB][ConnectionOpen (Invalid Connection()).]Invalid connection.
Error source:
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplication
Error message 4
An error occurred that requires the BizTalk service to terminate. The most
common causes are the following:
1) An unexpected out of memory error.
OR
2) An inability to connect or a loss of connectivity to one of the BizTalk
databases.
The service will shutdown and auto-restart in 1 minute. If the problematic
database remains unavailable, this cycle will repeat.
Error message: Timeout expired
Error source:
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplication
Error message 5
Reading error. Exception information: TDDS failed to read from source database. SQLServer: SQLServer,
Database: BiztalkMsgboxdb. Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding.
Additionally, you may receive an error message in the Microsoft SQL Server logs that resembles the following.
Note You receive this error message when trace flag 4029 is enabled.
Network error code 0x2746 occurred while establishing a connection; the connection has been closed.
This may have been caused by client or server login timeout expiration. Time spent during login: total
881 ms, enqueued 551 ms, network writes 330 ms, network reads 3 ms.
Additionally, the lost connection to the server that is running SQL Server may cause other symptoms. For example, a Microsoft Distributed Transaction Coordinator (MS DTC) transaction may be stopped. If an MS DTC transaction is stopped, you may receive an error message that resembles one of the following:
Error message 1
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action is required.
Error message 2
Error: 8510, Severity: 20, State: 2.
Enlist operation failed: 0x8004d00e(XACT_E_NOTRANSACTION). SQL Server could not register with Microsoft
Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The
transaction may have been stopped by the client or the resource manager.
This problem may occur because of one of the problems that are documented in the following articles in the Microsoft Knowledge Base:
927396Â
(http://kbalertz.com/Feedback.aspx?kbNumber=927396/
)
Queries take a longer time to finish running when the size of the TokenAndPermUserStore cache grows in SQL Server 2005
933564Â
(http://kbalertz.com/Feedback.aspx?kbNumber=933564/
)
FIX: A gradual increase in memory consumption for the USERSTORE_TOKENPERM cache store occurs in SQL Server 2005
To resolve this problem, follow these steps:
- Download and then install Microsoft SQL Server 2005 Service Pack 2.
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089Â
(http://kbalertz.com/Feedback.aspx?kbNumber=913089/
)
How to obtain the latest service pack for SQL Server 2005
- Download and then install the latest cumulative update for SQL Server 2005 Service Pack 2.
For more information about how to obtain the latest cumulative package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137Â
(http://kbalertz.com/Feedback.aspx?kbNumber=937137/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
To work around this problem, turn on trace flag 4618 for the instance of SQL Server that hosts the BizTalk databases. To do this, follow these steps:
- Click Start, click Run, type sqlservermanager.msc, and then click OK.
- Click SQL Server 2005 Services.
- Right-click SQL Server (InstanceName), and then click Properties.
- At the end of the existing string in the Startup Parameters box on the Advanced tab, type -T4618, and then click OK.
- Restart the SQL Server service.
To troubleshoot this problem, run the following command against the instance of SQL Server that hosts the BizTalk databases:
SELECT SUM(single_pages_kb + multi_pages_kb) AS
"CurrentSizeOfTokenCache(kb)"
FROM sys.dm_os_memory_clerks
WHERE name = 'TokenAndPermUserStore'
If the value that is returned increases when you run the command again, you may be experiencing one of the problems that are described in the Microsoft Knowledge Base articles that are listed in the "Cause" section. Refer to those articles to determine the problem that you are experiencing.
APPLIES TO
- Microsoft BizTalk Server 2006 R2 Standard Edition
- Microsoft BizTalk Server 2006 R2 Enterprise Edition
- Microsoft BizTalk Server 2006 R2 Developer Edition
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Enterprise Edition
| kbbts kbtshoot kbprb KB949298 |
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