BizTalk：我应该关心这个吗：“无法从先前的错误中恢复。”数据库：BizTalkMsgBoxDb”
BizTalk Server 时不时地抱怨：
Reading error. Failed to recover from previous error. SQLServer: XXX, Database: BizTalkMsgBoxDb.
我应该关心这个，还是干脆忽略它？
BizTalk Server complains from time to time:
Reading error. Failed to recover from previous error. SQLServer: XXX, Database: BizTalkMsgBoxDb.
Should I care this, or simply ignore it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
看起来与 MessageBox 的连接暂时丢失。不好，但只要连接恢复得足够快，也并不重要。具体错误信息与BAM有关，如果不使用可以将其关闭。然而，该问题会影响整个BizTalk。
您必须找出导致连接丢失的原因并解决该问题。请注意，这可能并不容易，我在 DEV 设备上看到过这种情况，BizTalk 和 SQL Server 都在同一个设备上...
BizTalk Server 2006：BAM 常见问题解答
Looks like a temporary loss of connectivity to the MessageBox. Not good, but also not critical as long as connectivity is restored quickly enough. The specific error message relates to BAM, which you can switch off if not being used. However, the problem will affect BizTalk as a whole.
You would have to find out what's causing the loss of connectivity and address that. Might not be easy, mind you, I have seen this happening on DEV boxes with both BizTalk and SQL Server on the same box...
BizTalk Server 2006: BAM FAQ
根据 Fabio 的说法，您收到的消息可能是 BAM 特有的。
如果 BizTalk 主机和 ENTSSO 确实失去与 SQL 的连接，则在事件日志中出现的错误类型将列出 此处
这些错误更为严重，可能会导致消息丢失（主机和接收位置通常停止）。
这些错误可能会间歇性地发生，然后一两分钟后您会看到
BizTalk 的常见原因：列出了 SQL 连接问题 此处
我们发现连接问题的常见罪魁祸首是TCP/IP SynAttackProtect SQL 上的安全功能服务器主机 - BizTalk 可以占用大量 SQL 连接，尤其是在长期空闲期后出现一批消息时所需的连接“增加”期间。
As per Fabio, the message you received is likely to be specific to BAM.
The types of error that you get in your eventlog if BizTalk hosts and ENTSSO does lose connectivity with SQL are listed here
These errors are more serious and can result in the loss of messages (Hosts and Receive Locations are usually stopped).
These errors can occur intermittently and then a minute or two later you see
Common causes of BizTalk : SQL Connectivity issues are listed here
We've found the usual culprit of connectivity issues to be the TCP/IP SynAttackProtect security feature on the SQL Server host - BizTalk can hog a lot of SQL Connections, especially during a 'ramp up' of connections required when a batch of messages comes in after a protacted idle period.