Home
  •  

MSSQL on Linux: Job step cannot be run because the subsystem failed to load

Microsoft.SQLServer.Linux.CollectionRule.Agent.Job_step_cannot_be_run_because_the_subsystem_failed_to_load_1_5_Rule (Rule)

A SQL Server job failed to run because the SQL Server Agent subsystem failed to load.

Knowledge Base article:

Summary

A SQL Server job failed to run because the SQL Server Agent subsystem failed to load.

Causes

The SQL Server Agent subsystem has been changed or corrupted.

Resolutions

Update the subsystem_dll in the msdb.dbo.syssubsystems table to point to the right location. For more information, see "syssubsystems (Transact-SQL)" in SQL Server Books Online.

Overrideable Parameters

Name

Description

Default Value

Enabled

Enables or disables the workflow.

Yes

Priority

Defines Alert Priority.

1

Severity

Defines Alert Severity.

1

Element properties:

TargetMicrosoft.SQLServer.Linux.Agent
CategoryEventCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
MSSQL on Linux: Job step cannot be run because the subsystem failed to load
{0}
CommentMom2017ID='{DA6B6DD4-A25C-4B19-95F5-4E48294B15F8}';MOM2017GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}

Member Modules:

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

Source Code:

<Rule ID="Microsoft.SQLServer.Linux.CollectionRule.Agent.Job_step_cannot_be_run_because_the_subsystem_failed_to_load_1_5_Rule" Target="SqlDiscL!Microsoft.SQLServer.Linux.Agent" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2017ID='{DA6B6DD4-A25C-4B19-95F5-4E48294B15F8}';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.EventCollectionFilteredAgent">

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

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

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

      <SqlTimeoutSeconds>15</SqlTimeoutSeconds>

      <TimeoutSeconds>200</TimeoutSeconds>

      <IntervalSeconds>300</IntervalSeconds>

      <SyncTime/>

      <EventDisplayNumber>212</EventDisplayNumber>

    </DataSource>

  </DataSources>

  <WriteActions>

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

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.Linux.CollectionRule.Agent.Job_step_cannot_be_run_because_the_subsystem_failed_to_load_1_5_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

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

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>