Skip to content

Commit 8862159

Browse files
authored
Re-write several sections
1 parent a66a429 commit 8862159

1 file changed

Lines changed: 13 additions & 2 deletions

File tree

support/sql/database-engine/startup-shutdown/sql-server-agent-crashes-upon-start.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ If there are many job entries because you unintentionally set up many subscripti
9090

9191
## Cause 2: ODBC driver missing or corrupted
9292

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.
9494

9595
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).
9696

@@ -103,7 +103,7 @@ For information about the ODBC driver requirements for different versions of SQL
103103
odbcad32.exe
104104
```
105105
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.
107107
108108
1. PowerShell:
109109
@@ -144,6 +144,17 @@ For information about the ODBC driver requirements for different versions of SQL
144144
1. Check if the ODBC driver for SQL Server is present
145145
1. If the driver is missing, go to the next step.
146146
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
147158
1. [Download the ODBC Driver for SQL Server](/sql/connect/odbc/download-odbc-driver-for-sql-server).
148159
1. Install the driver by using the GUI or a silent installation.
149160
1. To perform a silent installation, run the following command:

0 commit comments

Comments
 (0)