FIX: Host instance of BizTalk Server 2010 does not resume operation after the connection for a BizTalk database resumes

Article translations Article translations
Article ID: 2587237 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You install a host instance of Microsoft BizTalk Server 2010 on a computer.
  • The connection to a BizTalk-related database is lost. The connection is resumed after the connection is lost for a period of one minute.
In this scenario, the host instance of BizTalk Server does not resume operation. Additionally, the following events are logged in the Application log or in the System log:

Log Name: Application
Source: BizTalk Server
Event ID: 5410
Task Category: BizTalk Server
Level: Error
Keywords: Classic
Description:
A failure occurred when executing a Windows service request.
Service request: Start
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplication
Additional error information:
Error code: 0x80131604
Error source: mscorlib
Error description: Exception has been thrown by the target of an invocation.

Log Name: System
Source: Service Control Manager
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
Description:
The BizTalk Service BizTalk Group : BizTalkServerApplication service entered the running state.

Log Name: System
Source: Service Control Manager
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
Description:
The BizTalk Service BizTalk Group : BizTalkServerApplication service entered the stopped state.

Note This issue does not occur in earlier versions of BizTalk Server.

CAUSE


This issue occurs because BizTalk Server 2010 does not report an unexpected termination to Service Control Manager (SCM).

When the database connection is lost, the host instance enters a stopped state and then tries to restart within one minute. However, the restart operation fails, and BizTalk Server 2010 does not report the unexpected termination to SCM. Additionally, SCM handles the unexpected termination as a user-initiated service stop operation. Therefore, SCM does not resume the host instance of BizTalk Server 2010 from the stopped state.

RESOLUTION

Cumulative update information

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2010.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2573000 Cumulative update package 2 for BizTalk Server 2010

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For more information about service packs and cumulative update packages for BizTalk Server, visit the following Microsoft website: For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information about BizTalk Server hotfixes

Properties

Article ID: 2587237 - Last Review: August 31, 2011 - Revision: 1.0
APPLIES TO
  • Microsoft BizTalk Server Branch 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Standard 2010
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew kbbtsadmin KB2587237

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com