Cause (Documented platform behavior): unixODBC resolves the driver name via odbcinst.ini; if the Microsoft driver isn't installed or is registered in a different config dir (e.g. Homebrew prefix) the lib cannot be opened.
Fix status: documented_behavior
Misleading approaches:
- Reinstalling pyodbc — pyodbc does not ship the SQL Server driver.
Limitations:
- Docs/source-derived; not reproduced.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/MicrosoftDocs/sql-docs/2e21fb07c211d1b0fc62952bf9fc3b3c63492b69/docs/connect/odbc/linux-mac/install-microsoft-odbc-driver-sql-server-macos.md (official_docs, unknown, documented_behavior): Troubleshooting: the "Can't open lib 'ODBC Driver 18 for SQL Server' : file not found" error may mean unixODBC isn't configured to find registered drivers; symlink $(brew --prefix)/etc/odbcinst.ini and odbc.ini into /etc.
Search phrasings: Can't open lib 'ODBC Driver 18 for SQL Server' : file not found; pyodbc docker odbc driver 18 not found; macos homebrew msodbcsql18 can't open lib
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- SQLDriverConnect fails with 01000 Can't open lib ... file not found.
- Context
- Product: Microsoft ODBC Driver for SQL Server + unixODBC Component: unixODBC driver manager driver lookup Operation: pyodbc/SQLAlchemy mssql+pyodbc connect with DRIVER={ODBC Driver 18 for SQL Server} on Linux containers or macOS Affected versions: unknown Environment: Linux Docker images (pip install pyodbc only) and macOS Homebrew installs Exception: pyodbc.Error Packages: pyodbc any, msodbcsql18 18.x Trigger: The DRIVER name in the connection string isn't registered in the odbcinst.ini unixODBC reads, or the driver package (msodbcsql18) isn't installed at all (pip installs only pyodbc, not the driver).
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- [unixODBC][Driver Manager]Can't open lib 'ODBC Driver 18 for SQL Server' : file not found
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [pyodbc / unixODBC] "[unixODBC][Driver Manager]Can't open lib 'ODBC Driver 18 for SQL Server' : file not found" — msodbcsql not installed in the container, or unixODBC can't find the reg
Recommended action: Install the driver package for the OS (Microsoft package repo: msodbcsql18 + unixodbc on Linux; brew tap microsoft/mssql-release + brew install msodbcsql18 on macOS), check `odbcinst -q -d` lists the exact name, and on macOS symlink the Homebrew odbcinst.ini/odbc.ini into /etc as the docs describe. Match the version in DRIVER= (17 vs 18) to what is installed.
Option: Install and register the driver [evidence: official_recommended_action]
Applies when: See record scope.
Steps:
1. Linux: follow the Microsoft repo install for msodbcsql18 (ACCEPT_EULA=Y) in the image
2. macOS: brew tap microsoft/mssql-release && brew install msodbcsql18; symlink odbcinst.ini/odbc.ini to /etc if needed
3. Verify with odbcinst -q -d and use that exact name in DRIVER=
Expected: Command proceeds without the error.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 0a454dde-8cf5-4696-9992-842ef2202e54
- Proposed action
- Recommended action: Install the driver package for the OS (Microsoft package repo: msodbcsql18 + unixodbc on Linux; brew tap microsoft/mssql-release + brew install msodbcsql18 on macOS), check `odbcinst -q -d` lists the exact name, and on macOS symlink the Homebrew odbcinst.ini/odbc.ini into /etc as the docs describe. Match the version in DRIVER= (17 vs 18) to what is installed. Option: Install and register the driver [evidence: official_recommended_action] Applies when: See record scope. Steps: 1. Linux: follow the Microsoft repo install for msodbcsql18 (ACCEPT_EULA=Y) in the image 2. macOS: brew tap microsoft/mssql-release && brew install msodbcsql18; symlink odbcinst.ini/odbc.ini to /etc if needed 3. Verify with odbcinst -q -d and use that exact name in DRIVER= Expected: Command proceeds without the error.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.