You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/sql/database-engine/startup-shutdown/sql-server-agent-crashes-upon-start.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ If there are many job entries because you unintentionally set up many subscripti
90
90
91
91
## Cause 2: ODBC driver missing or corrupted
92
92
93
-
This issue can occur if the Open Database Connectivity (ODBC) driver is removed or becomes corrupted (often after system updates). SQL Server requires the ODBC driver as a core dependency.
93
+
This issue can occur if the SQL Server Open Database Connectivity (ODBC) driver is removed or becomes corrupted (often after system updates). SQL Server Agent uses the SQL Server ODBC driver to connect to SQL Server and if the driver is missing or not functioning, a SQL Server Agent fails to start.
94
94
95
95
For information about the ODBC driver requirements for different versions of SQL Server, see [Hardware and software requirements for SQL Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025).
96
96
@@ -103,7 +103,7 @@ For information about the ODBC driver requirements for different versions of SQL
103
103
odbcad32.exe
104
104
```
105
105
106
-
This command opens the _ODBC data source Administrator_ window. In that window, open the **Drivers** tab, and check whether the ODBC driver is missing.
106
+
1. Check if the expected SQL Server ODBC driver is there by comparing to the following table [SQL Server versions and ODBC and OLE DB drivers](/sql/connect/connect-history#sql-server-versions-and-odbc-and-ole-db-drivers). The table lists the SQL Server ODBC driver version shipped with each SQL Server engine and used by SQL Server Agent to connect to SQL Server engine.
107
107
108
108
1. PowerShell:
109
109
@@ -144,6 +144,17 @@ For information about the ODBC driver requirements for different versions of SQL
144
144
1. Check if the ODBC driver for SQL Server is present
145
145
1. If the driver is missing, go to the next step.
146
146
1. If the driver is missing, go to [ODBC driver is missing](#sql-server-odbc-driver-is-missing)
147
+
148
+
#### SQL Server ODBC driver is present
149
+
150
+
1. If the ODBC driver is present, open **Add or Remove Programs** in Windows and locate the **Microsoft ODBC Driver XX for SQL Server** where XX is the expected version for your SQL Server.
151
+
1. Click on the three dots and choose **Modify**
152
+
1. In the wizard that start choose the **Repair** option and finish the steps to repair the driver.
153
+
1. After you complete the repair steps, you can test a connection to SQL Server by configuring a test DSN with the repaired SQL Server driver. For more information, see [ODBC Data Source Administrator DSN options](/sql/connect/odbc/windows/odbc-administrator-dsn-creation)
154
+
155
+
156
+
157
+
#### SQL Server ODBC driver is missing
147
158
1. [Download the ODBC Driver for SQL Server](/sql/connect/odbc/download-odbc-driver-for-sql-server).
148
159
1. Install the driver by using the GUI or a silent installation.
149
160
1. To perform a silent installation, run the following command:
0 commit comments