locked
Biztalk and SQL cluster failover RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi!
    I have Biztalk 2013 and a SQL cluster. Each time I failover the SQL cluster I get a failure of some services on Biztalk. It looks like they cant contact the SQL for that short time when the failover happens and then crashes.

    In the application log I can find the following:
    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: SHUTDOWN is in progress. Error source:   
     BizTalk host name: BizTalkServerProcessingHost
     Windows service name: BizTalkServerProcessingHost 

    Is there anyway to avoid these messages? Can I set a timeout so that it waits a little longer for the sql?


    Monday, October 3, 2016 1:50 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Ideally you should not worry about the above error messages, as BizTalk services are configured to restart on failure every 1 minute. So, after the above error, the services will attempt to come online again after a minute -

    https://sandroaspbiztalkblog.files.wordpress.com/2013/05/bts-2013-srvices-01-biztalk-service-biztalk-group-biztalkserverapplication-service.png

    However, you should not perform manual failover of SQL in production BizTalk environments as there may be active transactions in BizTalk. If there is a necessity to perform manual failover/auto-failover happens, the BizTalk services will go down for a while with error messages as the one you see above. As long as the failover duration is small, this should not be a concern, and BizTalk services will come online as soon as SQL is accessible. No manual action is needed on BizTalk side of things.

    Thanks Arindam






    Monday, October 3, 2016 2:19 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Ideally you should not worry about the above error messages, as BizTalk services are configured to restart on failure every 1 minute. So, after the above error, the services will attempt to come online again after a minute -

    https://sandroaspbiztalkblog.files.wordpress.com/2013/05/bts-2013-srvices-01-biztalk-service-biztalk-group-biztalkserverapplication-service.png

    However, you should not perform manual failover of SQL in production BizTalk environments as there may be active transactions in BizTalk. If there is a necessity to perform manual failover/auto-failover happens, the BizTalk services will go down for a while with error messages as the one you see above. As long as the failover duration is small, this should not be a concern, and BizTalk services will come online as soon as SQL is accessible. No manual action is needed on BizTalk side of things.

    Thanks Arindam






    Monday, October 3, 2016 2:19 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well this should not be a case of worry..as the error says the restart is going to happen in 1 minute..so as soon as the failover happens the Biztalk services will come back to started state as they are scheduled to retry restart after every 1 minute by default.

    Regards,

    Mandar Dharmadhikari

    Monday, October 3, 2016 2:50 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    What you are seeing is not unexpected.  By design, BizTalk Server is very chatty with SQL Server so any loss of connection is immediately noticed and the proper action is to log that event.  BizTalk Server has no knowledge that SQL Server is doing a failover.

    So long as the failover is successful and BizTalk reconnect automatically, you can ignore those specific warnings.

    Tuesday, October 4, 2016 12:20 PM
    Moderator