By default, the Startup type property of BizTalk Windows Services, Enterprise Single Sign-On Service, Microsoft UDDI Notification Service, and the new BAMAlerts service are set to Automatic. Some of these Windows Services may not start automatically after a system restart. To avoid this behavior, you must configure the Startup type to the Automatic (Delayed Start) option in these services:
- BAMAlerts.
- Microsoft UDDI Notification Service.
- Rule Engine Update Service.
📝 One-Minute Brief
By default, several BizTalk 2013 Windows services are set to “Automatic,” but they may fail to start after a system reboot because their dependencies (like SQL Server) aren’t ready yet. This guide explains how to fix this by switching key services—including BAMAlerts, UDDI Notification, and Rule Engine—to “Automatic (Delayed Start)” and configuring robust recovery options.
The previous version of BizTalk Server also had this problem:
- Enterprise Single Sign-On Service
- BizTalk Service BizTalk Group : BizTalkServerApplication Service
However, this problem has been resolved in this release. Despite being configured as Automatic, the Recovery properties are configured to restart the service after failures.
To properly configure the BAMAlerts and Microsoft UDDI Notification Service Windows service:
- Press the Windows key to switch to Metro UI, type Services, and click on the View local services option on the Settings menu.
- In the Services window, on the Services (Local) panel, select the BAMAlerts service, right-click, and select the Properties option.
- On the BAMAlerts Properties (Local Computer) window:
- On the General tab, apply the following configuration.
- Startup type: Automatic (Delayed Start).
- On the General tab, apply the following configuration.
- On the Recovery tab, apply the following configuration:
- First failure: Restart the Service.
- Second failure: Restart the Service.
- Subsequent failures: Restart the Service.
- Reset fail count after … day: 1.
- Restart service after … minutes: 1.
- Click OK to apply the changes and close the window.
Related links
- BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
- BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
- BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
- BizTalk 2013 Installation and Configuration – Install and configure SMTP Server Feature (Part 4)
- BizTalk 2013 Installation and Configuration – Install Microsoft Office Excel 2013 (Part 5)
- BizTalk 2013 Installation and Configuration – Install Visual Studio 2012 (Part 6)
- BizTalk 2013 Installation and Configuration – Install SQL Server 2012 (Part 7)
- BizTalk 2013 Installation and Configuration – Configure SQL Server Database Mail feature (Part 8)
- BizTalk 2013 Installation and Configuration – Install and Configure BizTalk Server 2013 (Part 9)
- BizTalk 2013 Installation and Configuration – Configure SQL Server Network Configuration protocols (Part 10)
- BizTalk 2013 Installation and Configuration – Validate Mail account used by BizTalk to send BAM Alerts (Part 11)
- BizTalk 2013 Installation and Configuration – Installing BizTalk Adapter Pack (Part 12)
- BizTalk 2013 Installation and Configuration – Install and Configure Microsoft UDDI Services (Part 13)
- BizTalk 2013 Installation and Configuration – Install and Configure the Microsoft BizTalk ESB Toolkit (Part 14)
- BizTalk 2013 Installation and Configuration – Configure BizTalk Server SQL Jobs (Part 15)
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
2 thoughts on “BizTalk 2013 Installation and Configuration – Configure BizTalk Server Windows Services (Part 16)”