MSSQL 2016: SQL Server could not allocate enough memory to start Service Broker task manager

Microsoft.SQLServer.2016.SQL_Server_could_not_allocate_enough_memory_to_start_Service_Broker_task_manager_5_Rule (Rule)

SQL Server Service Broker cannot start Service Broker task manager.

Knowledge Base article:

Summary

SQL Server Service Broker cannot start Service Broker task manager.

Causes

This error is recorded in the Windows application log as MSSQLSERVER event ID 9695. 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

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. On a 32-bit system, you can add more than 4 GB of physical memory if you use Microsoft Windows Address Windowing Extensions (AWE).

Overrideable Parameters

Name	Description	Default Value
Enabled	Enables or disables the workflow.	Yes
Priority	Defines Alert Priority.	1
Severity	Defines Alert Severity.	2

Element properties:

Target

Microsoft.SQLServer.2016.DBEngine

Category

EventCollection

Enabled

True

Event_ID

9695

Event Source

$Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$

Alert Generate

True

Alert Severity

Error

Alert Priority

Normal

Remotable

True

Alert Message

MSSQL 2016: SQL Server could not allocate enough memory to start Service Broker task manager

{0}

Event Log

Application

Comment

Mom2016ID='{E1C60E5E-168D-4436-862B-48DB57C97270}';MOM2016GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}

Member Modules:

ID	Module Type	TypeId	RunAs
_F6DA1507_12AF_11D3_AB21_00A0C98620CE_	DataSource	Microsoft.Windows.EventProvider	Default
GenerateAlert	WriteAction	System.Health.GenerateAlert	Default

Source Code:

<Rule ID="Microsoft.SQLServer.2016.SQL_Server_could_not_allocate_enough_memory_to_start_Service_Broker_task_manager_5_Rule" Target="SQL2016Core!Microsoft.SQLServer.2016.DBEngine" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2016ID='{E1C60E5E-168D-4436-862B-48DB57C97270}';MOM2016GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="_F6DA1507_12AF_11D3_AB21_00A0C98620CE_" Comment="{F6DA1507-12AF-11D3-AB21-00A0C98620CE}" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>Application</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>9695</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>$Target/Property[Type="SQL2016Core!Microsoft.SQLServer.2016.DBEngine"]/ServiceName$</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

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

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2016.SQL_Server_could_not_allocate_enough_memory_to_start_Service_Broker_task_manager_5_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>Event ID: $Data/EventDisplayNumber$. $Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>