MSSQL 2016: Service Broker was not able to allocate memory for cryptographic operations

Microsoft.SQLServer.2016.Service_Broker_was_not_able_to_allocate_memory_for_cryptographic_operations_5_Rule (Rule)

The rule triggers an alert when SQL Server Service Broker is not able to allocate memory for cryptographic operations.

Knowledge Base article:

Summary

Service Broker was unable to allocate memory for cryptographic operations. This message is a symptom of another problem.

Note : Some cryptographic operation failures that are not related to low memory may be reported as allocation failures.

Causes

This error is logged to the Windows application log as MSSQLSERVER event ID 9634.

Resolutions

Check the SQL Server error log for additional messages, and address the underlying problem.

Increase the available memory and restart the server. 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

9634

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: Service Broker was not able to allocate memory for cryptographic operations

{0}

Event Log

Application

Comment

Mom2016ID='{80FD1A3B-1CBC-451A-850E-234279CE3CAE}';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.Service_Broker_was_not_able_to_allocate_memory_for_cryptographic_operations_5_Rule" Target="SQL2016Core!Microsoft.SQLServer.2016.DBEngine" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2016ID='{80FD1A3B-1CBC-451A-850E-234279CE3CAE}';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>9634</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.Service_Broker_was_not_able_to_allocate_memory_for_cryptographic_operations_5_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

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

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>