initial draft

Author: haywoodsloan

support/sql/database-engine/agent/job-failed-error-258.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot SQL Agent Job Failures with Error 258
-description: Learn how to troubleshoot and resolve repeated crashes of the SQL Agent service. Follow step-by-step solutions to fix registry issues and improve stability.
+description: Troubleshoot SQL Agent job failures with error 258. Learn how to resolve timeout issues, fix registry problems, and ensure stable job execution.
 ms.date: 12/04/2025
 ms.custom: sap:SQL Agent (Jobs, Alerts, Operators)\Job failures, job scheduling and monitoring
 ms.reviewer: prmadhes, v-shaywood
@@ -27,11 +27,83 @@ Logon to server '<ServerName>' failed (ConnLogJobHistory)
 
 This issue can be caused by any of the following underlying problems:
 
-- Blocking of `msdb` system tables used by Agent, which prevents job metadata reads and writes.
+- Blocking on `msdb` 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:
 
+    ```powershell
+    Get-Service -Name "SQLSERVERAGENT"
+    ```
+
+1. If the SQL Server Agent service is not already running, start it.
+1. Check the jobs and schedules in `msdb` by opening [SQL Server Management Studio (SSMS)](/ssms/install/install) and running the following query: <!-- Check with SME, what the user should do with the output of this query -->
+  
+    ```tsql
+    USE msdb;
+    GO
+    
+    -- List enabled jobs
+    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
+    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
+    WHERE j.enabled = 1;
+    GO
+    ```
+
+1. Detect blocking on `msdb` Agent system tables by running the following query is SSMS:
+
+    ```tsql
+    USE msdb;
+    GO
+    
+    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
+    ```
+
+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 for any worker, thread, or resource issues by running the following query is SSMS:
+
+    ```tsql
+    ?????
+    ```
+
+   Inspect the query results for `QUERY_PROCESSING`, `RESOURCE`, and `SYSTEM` components, look for thread exhaustion, memory pressure, or CPU issues.
+
+   <!-- Check with SME what the user should do if they identify any thread exhaustion, memory pressure, or CPU issues -->
+
+1. If blocking, hangs, or worker exhaustion can't be resolved, restart SQL Server Agent by running the following commands in PowerShell:
+
+    ```powershell
+    Restart-Service -Name "SQLSERVERAGENT" -Force
+    net stop "SQL Server Agent (MSSQLSERVER)"
+    net start "SQL Server Agent (MSSQLSERVER)"
+    ```
+
+   > [!IMPORTANT]
+   > Restarting the SQL Server Agent will interrupt any currently running jobs.
+
+   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
+
+- [SQL Server Agent overview](/ssms/agent/sql-server-agent)
+- [View the SQL Server Agent error log](/ssms/agent/view-sql-server-agent-error-log-sql-server-management-studio)
+- [Create a SQL Server Agent job](/ssms/agent/create-a-job)