new draft info

haywoodsloan · haywoodsloan · commit d64f9fd03e7f · 2025-12-12T13:36:48.000-05:00
diff --git a/support/sql/database-engine/agent/job-failed-error-258.md b/support/sql/database-engine/agent/job-failed-error-258.md
@@ -12,7 +12,7 @@ This article provides troubleshooting guidance for an issue where SQL Agent jobs
 
 ## Symptoms
 
-The SQL Agent service runs, but scheduled SQL Agent jobs don't execute. The SQL Server and Agent logs show network and authentication timeouts as well as failed sign-ins.
+The [SQL Agent service](/ssms/agent/sql-server-agent#sql-server-agent-components) runs, but scheduled SQL Agent jobs don't execute. The SQL Server and Agent logs show network and authentication timeouts as well as failed sign-ins.
 
 The following example shows the error message that's added to the logs:
 
@@ -27,36 +27,59 @@ Logon to server '<ServerName>' failed (ConnLogJobHistory)
 
 This issue can be caused by any of the following underlying problems:
 
-- Blocking on `msdb` system tables used by Agent, which prevents job metadata reads and writes.
+- Blocking on [msdb](/sql/relational-databases/databases/msdb-database) system tables used by Agent, which prevents job metadata reads and writes.
   - Example system tables: `dbo.sysjobs`, `dbo.sysjobschedulers`, and `dbo.jobsteps`.
 - Hangs inside important SQL Server Agent threads or other process-level problems.
 - Worker thread exhaustion in SQL Server (no workers available), making the Agent unable to connect or process schedules.
 
 ## Solution
 
-1. Confirm that the SQL Server Agent service is running by using the following PowerShell command:
+1. Confirm that the SQL Server Agent service is running by using one of the following PowerShell commands:
 
-    ```powershell
-    Get-Service -Name "SQLSERVERAGENT"
-    ```
+    1. For default SQL instances:
+
+        ```powershell
+        Get-Service -Name "SQLSERVERAGENT"
+        ```
+
+    1. For named SQL instances:
+
+        ```powershell
+        Get-Service -Name "SQLSERVERAGENT$<InstanceName>"
+        ```
+
+1. If the SQL Server Agent service isn't running, start it by using one of the following commands:
+
+    1. For default SQL instances:
+
+        ```powershell
+        Start-Service -Name "SQLSERVERAGENT"
+        ```
+
+    1. For named SQL instances:
 
-1. If the SQL Server Agent service isn't running, start it.
+        ```powershell
+        Start-Service -Name "SQLSERVERAGENT$<InstanceName>"
+        ```
+
+1. If jobs continue to fail after starting the SQL Server Agent service, continue to the next step. If jobs are completing successfully, the issue is resolved and no further action is needed.
 1. Check the jobs and schedules in `msdb` by opening [SQL Server Management Studio (SSMS)](/ssms/install/install) and running the following query:
   
     ```tsql
     USE msdb;
     GO
-    
     -- List enabled jobs
-    SELECT name, enabled, description FROM msdb.dbo.sysjobs WHERE enabled = 1;
+    SELECT name, enabled, description 
+    FROM msdb.dbo.sysjobs 
+    WHERE enabled = 1;
     GO
-    
-    -- Show job schedules and next run
-    SELECT s.name AS ScheduleName,
-            j.name AS JobName,
-            s.enabled AS ScheduleEnabled,
-            s.active_start_date,
-            s.active_end_time
+    -- List schedules and next run information
+    SELECT 
+        s.name AS ScheduleName,
+        j.name AS JobName,
+        s.enabled AS ScheduleEnabled,
+        s.active_start_date,
+        s.active_end_time
     FROM msdb.dbo.sysjobs j
     JOIN msdb.dbo.sysjobschedules js ON j.job_id = js.job_id
     JOIN msdb.dbo.sysschedules s ON js.schedule_id = s.schedule_id
@@ -66,46 +89,154 @@ This issue can be caused by any of the following underlying problems:
 
     Analyze the query output for any jobs which are enabled but have failed. Investigate the job history and job-step outputs for any problematic jobs to identify and fix underlying issues.
 
-1. Detect blocking on `msdb` Agent system tables by running the following query in SSMS:
+1. Detect blocking sessions on `msdb` Agent system tables by running the following query in SSMS:
 
     ```tsql
     USE msdb;
     GO
-    
-    SELECT session_id, blocking_session_id, wait_type, wait_duration_ms, resource_description
+    SELECT 
+        session_id, 
+        blocking_session_id, 
+        wait_type, 
+        wait_duration_ms, 
+        resource_description
     FROM sys.dm_os_waiting_tasks
     WHERE resource_description LIKE '%sysjobs%'
        OR resource_description LIKE '%sysjobschedulers%'
        OR resource_description LIKE '%jobsteps%';
-    GO
+    GO 
     ```
 
-1. If blocking sessions are found, investigate the blocking query using `sys.dm_exec_requests` and `sys.dm_exec_sql_text`. Then, resolve or kill the blocking session.
-1. Check the `system_health` Extended Events session for any worker, thread, or resource issues by running the following query in SSMS:
+    1. To identify the query associated with a blocking session run the following query in SSMS:
+
+        ```tsql
+        SELECT 
+            wt.session_id,
+            wt.blocking_session_id,
+            wt.wait_type,
+            wt.wait_duration_ms,
+            wt.resource_description,
+            er.status,
+            er.command,
+            er.cpu_time,
+            er.total_elapsed_time,
+            txt.text AS sql_text
+        FROM sys.dm_os_waiting_tasks wt
+        LEFT JOIN sys.dm_exec_requests er 
+               ON wt.session_id = er.session_id
+        CROSS APPLY sys.dm_exec_sql_text(er.sql_handle) AS txt
+        WHERE wt.resource_description LIKE '%sysjobs%'
+           OR wt.resource_description LIKE '%sysjobschedulers%'
+           OR wt.resource_description LIKE '%jobsteps%';
+        ```
+
+1. Resolve or terminate any blocking sessions you identified in the previous step. To terminate a session run the following query in SSMS:
 
     ```tsql
-    SELECT CAST(xet.target_data as xml) AS target_data
-    FROM sys.dm_xe_session_targets xet
-    JOIN sys.dm_xe_sessions xe
-    ON xe.address = xet.event_session_address
-    WHERE xe.name = 'system_health'
+    Kill <Blocking_Session_ID>
     ```
 
-   Inspect the query results for `QUERY_PROCESSING`, `RESOURCE`, and `SYSTEM` components. Look for thread exhaustion, memory pressure, or CPU issues. If you identify any issues resolve them by following the guidance provided in [Troubleshooting SQL Agent Issues](/to-do). <!--Fill in this link one the doc is published -->
-
+    Once all blocking sessions are resolved or terminated, proceed to the next step.
 
-1. If you can't resolve blocking, hangs, or worker exhaustion, restart the SQL Server Agent by running the following commands in PowerShell:
+1. Check for any worker, thread, or resource health issues by running the following query in SSMS:
 
-    ```powershell
-    Restart-Service -Name "SQLSERVERAGENT" -Force
-    net stop "SQL Server Agent (MSSQLSERVER)"
-    net start "SQL Server Agent (MSSQLSERVER)"
+    ```tsql
+    /* ============================================================
+       HEALTH CHECK (Worker, CPU, Memory)
+       ============================================================ */
+    
+    SELECT 
+        Section,
+        Metric,
+        Value,
+        ExtraInfo
+    FROM (
+    
+        /* ===============================
+           WORKER THREAD STATUS
+           =============================== */
+        SELECT 
+            CAST('WORKER THREAD STATUS' AS VARCHAR(MAX)) AS Section,
+            CAST(CONCAT('Scheduler ', scheduler_id) AS VARCHAR(MAX)) AS Metric,
+            CAST(CONCAT('Workers: ', active_workers_count, '/', current_workers_count) AS VARCHAR(MAX)) AS Value,
+            CAST(CONCAT('WorkQueue=', work_queue_count, ', Idle=', is_idle) AS VARCHAR(MAX)) AS ExtraInfo
+        FROM sys.dm_os_schedulers
+        WHERE scheduler_id < 255
+    
+        UNION ALL
+    
+        /* ===============================
+           CPU PRESSURE
+           =============================== */
+        SELECT
+            CAST('CPU PRESSURE' AS VARCHAR(MAX)) AS Section,
+            CAST(CONCAT('Scheduler ', scheduler_id) AS VARCHAR(MAX)) AS Metric,
+            CAST(CONCAT('RunnableTasks=', runnable_tasks_count) AS VARCHAR(MAX)) AS Value,
+            CAST(CONCAT('PendingIO=', pending_disk_io_count) AS VARCHAR(MAX)) AS ExtraInfo
+        FROM sys.dm_os_schedulers
+        WHERE scheduler_id < 255
+    
+        UNION ALL
+    
+        /* ===============================
+           MEMORY STATUS (System)
+           =============================== */
+        SELECT
+            CAST('MEMORY STATUS' AS VARCHAR(MAX)) AS Section,
+            CAST('SystemMemoryState' AS VARCHAR(MAX)) AS Metric,
+            CAST(system_memory_state_desc AS VARCHAR(MAX)) AS Value,
+            CAST(CONCAT('TotalMB=', total_physical_memory_kb/1024, 
+                        ', AvailableMB=', available_physical_memory_kb/1024) AS VARCHAR(MAX)) AS ExtraInfo
+        FROM sys.dm_os_sys_memory
+    
+        UNION ALL
+    
+        /* ===============================
+           PAGE LIFE EXPECTANCY
+           =============================== */
+        SELECT
+            CAST('PAGE LIFE EXPECTANCY' AS VARCHAR(MAX)) AS Section,
+            CAST('PLE' AS VARCHAR(MAX)) AS Metric,
+            CAST(cntr_value AS VARCHAR(MAX)) AS Value,
+            CAST(NULL AS VARCHAR(MAX)) AS ExtraInfo
+        FROM sys.dm_os_performance_counters
+        WHERE counter_name = 'Page life expectancy'
+          AND object_name LIKE '%Buffer Manager%'
+    
+    ) AS x
+    ORDER BY Section, Metric;
     ```
 
-   > [!IMPORTANT]
-   > Restarting the SQL Server Agent interrupts any currently running jobs.
+    Investigate the output of the health check query for any of the following issues using the given symptoms:
+
+    1. Worker thread pressure:
+        1. Worker exhaustion, for example `Workers: 512/512`.
+        1. `WorkQueue` is greater than zero, indicating that tasks are waiting and the system is overloaded.
+    1. CPU pressure:
+        1. `RunnableTasks` is greater than zero, indicating there is a CPU bottleneck.
+    1. Memory pressure:
+        1. `Memory state` is `LOW`, indicating the overall system is low on memory.
+        1. A low value for `AvailableMB`, indicating high memory usage for SQL Server.
+        1. A `PLE` value less than 300, indicating high memory churn.
+1. If you identified any worker, CPU, or memory issues in the previous step reduce your current workload to resolve them. If no worker, CPU, or memory issues were identified, proceed to the next step.
+1. Restart the SQL Server Agent by running one of the the following PowerShell commands:
+
+    > [!IMPORTANT]
+    > Restarting the SQL Server Agent interrupts any currently running jobs.
+
+    1. For default SQL instances:
+
+        ```powershell
+        Restart-Service -Name "SQLSERVERAGENT"
+        ```
+
+    1. For named SQL instances:
+
+        ```powershell
+        Restart-Service -Name "SQLAgent$<InstanceName>"
+        ```
 
-   After the SQL Server Agent restarts, verify that jobs are now being executed by using the [Job Activity Monitor](/ssms/agent/monitor-job-activity#job-activity-monitor).
+1. After the SQL Server Agent restarts, verify that jobs are now being executed by using the [Job Activity Monitor](/ssms/agent/monitor-job-activity#job-activity-monitor).
 
 ## Related content
 
