MSSQL on Linux: Cannot start service broker activation manager

Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_activation_manager_5_Rule (Rule)

The rule triggers an alert when service broker fails to start the activation manager.

Knowledge Base article:

Summary

Service Broker activation helps applications to scale dynamically to manage the message traffic. In general, an application uses activation if traffic to the service varies unpredictably or if the service must dynamically scale to handle the traffic the service receives.

The Service Broker activation process consists of two steps. First, Service Broker determines whether activation is necessary. Second, Service Broker determines whether activation occurs. Although the exact process differs between internal activation and external activation, the overall concepts involved are the same for either strategy.

In this case, the Service Broker activation manager determined that activation was necessary and tried to start a Service Broker application, but failed to do so.

Causes

This error is recorded in the Linux application log as MSSQLSERVER event ID 9701. This could be caused by a lack of memory during server startup. This is probably connected to one or more other hardware or software problems in the computer.

Resolutions

Investigate the Linux application log to find errors caused by other problems.

Diagnose this as you would any low-memory condition. Increase the available memory by removing less critical applications or by adding virtual or physical memory.

Consider the following solutions to increase available memory:

Increase the size of the paging file.
Restart the server with the -g memory_to_reserve option to increase the amount of memory that SQL Server will leave available for memory allocations within the SQL Server process.
Add physical memory.

Overridable Parameters

Name	Description	Default Value
Enabled	Enables or disables the workflow.	Yes
Interval (seconds)	The recurring interval of time in seconds in which to run the workflow.	300
Priority	Defines Alert Priority.	1
Severity	Defines Alert Severity.	2
Synchronization Time	The synchronization time specified by using a 24-hour format. May be omitted.
Timeout (seconds)	Specifies the time the workflow is allowed to run before being closed and marked as failed.	200
Timeout for query execution (seconds)	The workflow will fail and register an event, if the query execution takes longer than the specified period.	60
Timeout for database connection (seconds)	The workflow will fail and register an event, if it cannot access the database during the specified period.	15

Element properties:

Target

Microsoft.SQLServer.Linux.DBEngine

Category

EventCollection

Enabled

True

Alert Generate

True

Alert Severity

Error

Alert Priority

Normal

Remotable

True

Alert Message

MSSQL on Linux: Cannot start service broker activation manager

{2}

Comment

Mom2017ID='{679F7701-5328-45B1-A617-B88F211E4E77}';MOM2017GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}

Member Modules:

ID	Module Type	TypeId	RunAs
_F6DA1507_12AF_11D3_AB21_00A0C98620CE_	DataSource	Microsoft.SQLServer.Linux.DataSource.EventCollectionFiltered	Default
GenerateAlert	WriteAction	System.Health.GenerateAlert	Default

Source Code:

<Rule ID="Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_activation_manager_5_Rule" Target="SqlDiscL!Microsoft.SQLServer.Linux.DBEngine" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2017ID='{679F7701-5328-45B1-A617-B88F211E4E77}';MOM2017GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="_F6DA1507_12AF_11D3_AB21_00A0C98620CE_" Comment="{F6DA1507-12AF-11D3-AB21-00A0C98620CE}" TypeID="Microsoft.SQLServer.Linux.DataSource.EventCollectionFiltered">

      <MachineName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</MachineName>

      <NetbiosComputerName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/NetbiosComputerName$</NetbiosComputerName>

      <InstanceName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</InstanceName>

      <ConnectionString>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/ConnectionString$</ConnectionString>

      <InstanceVersion>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Version$</InstanceVersion>

      <InstanceEdition>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Edition$</InstanceEdition>

      <SqlExecTimeoutSeconds>60</SqlExecTimeoutSeconds>

      <SqlTimeoutSeconds>15</SqlTimeoutSeconds>

      <TimeoutSeconds>200</TimeoutSeconds>

      <IntervalSeconds>300</IntervalSeconds>

      <SyncTime/>

      <EventDisplayNumber>9701</EventDisplayNumber>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.Linux.EventRule.DBEngine.Cannot_start_service_broker_activation_manager_5_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</AlertParameter1>

        <AlertParameter2>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</AlertParameter2>

        <AlertParameter3>Event ID: $Data/Property[@Name='EventID']$. $Data/Property[@Name='Message']$</AlertParameter3>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>