|
| 1 | +--- |
| 2 | +title: Updating ODBC Driver for SQL Server to 18.6.1.1 causes issues in Configuration Manager |
| 3 | +description: Discusses issues that appear after you update ODBC Driver for SQL Server to version 18.6.1.1 in Configuration Manager, and explains how to work around these issues. |
| 4 | +ms.date: 01/30/2026 |
| 5 | +ms.reviewer: kaushika, payur, v-tappelgate |
| 6 | +ms.custom: sap:Configuration Manager Setup, High Availability, Migration and Recovery\Site Installation or Prerequisites |
| 7 | +--- |
| 8 | +# Updating ODBC Driver for SQL Server to version 18.6.1.1 causes issues in Configuration Manager |
| 9 | + |
| 10 | +*Applies to*: Configuration Manager |
| 11 | + |
| 12 | +## Summary |
| 13 | + |
| 14 | +After you update Microsoft ODBC Driver for Microsoft SQL Server to version 18.6.1.1, Configuration Manager site installations might fail, and Client Notification features might stop working. This article provides information about these issues and explains how to work around them until a permanent fix becomes available. |
| 15 | + |
| 16 | +## Symptoms |
| 17 | + |
| 18 | +After you install [Microsoft ODBC driver for SQL Server on Windows, version 18.6.1.1](/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows#186), you experience the following symptoms. |
| 19 | + |
| 20 | +### Symptom 1: You can't install a new ConfigMgr site |
| 21 | + |
| 22 | +You try to install a new ConfigMgr site, but the operation fails. The ConfigMgrSetup.log file reports an error that resembles the following example: |
| 23 | + |
| 24 | +```output |
| 25 | + INFO: Database watermark: |
| 26 | + ERROR: Failed parsing the watermark from the database: 80070057. |
| 27 | + INFO: Could not retrieve and process both watermarks, will import all tables from disk. |
| 28 | + INFO: On disk watermark is newer than the one in the database. All tables will be imported. |
| 29 | + INFO: Starting data import data to table: LU_LicensedProduct |
| 30 | + *** MERGE [dbo].[LU_LicensedProduct] AS TARGET ~ using (select [LicensedProductID], [ProductPool], [ProductName], ~ [FamilyName], [VersionSequence], [VersionCode], ~ GETUTCDATE() , N'$CD' ~ from tempdb.dbo.temp_LU_LicensedProduct) ~ as SOURCE ( [LicensedProductID], [ProductPool], [ProductName], ~ [FamilyName], [VersionSequence], [VersionCode], ~ [LastUpdated], [SourceSite]) ~ ON SOURCE.[LicensedProductID] = TARGET.[LicensedProductID] ~ when matched and (~ TARGET.[ProductPool] != SOURCE.[ProductPool] OR ~ TARGET.[ProductName] != SOURCE.[ProductName] OR ~ TARGET.[FamilyName] != SOURCE.[FamilyName] OR ~ TARGET.[VersionSequence] != SOURCE.[VersionSequence] OR ~ TARGET.[VersionCode] != SOURCE.[VersionCode] OR ~ TARGET.[SourceSite] != SOURCE.[SourceSite]) ~ then ~ UPDATE SET ~ [ProductPool] = SOURCE.[ProductPool], ~ [ProductName] = SOURCE. |
| 31 | + *** [23000][515][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Cannot insert the value NULL into column 'VersionCode', table 'CM_TS1.dbo.LU_LicensedProduct'; column does not allow nulls. UPDATE fails. |
| 32 | +... |
| 33 | + ERROR: FAILED to import data to table LU_LicensedProduct |
| 34 | + ERROR: Failed to import data from CSV files |
| 35 | + ERROR: Failed to import Asset Intelligence data into the site database. |
| 36 | +``` |
| 37 | + |
| 38 | +### Symptom 2: Client Notification stops working |
| 39 | + |
| 40 | +In existing environments, the **Currently Logged on User** column in the Configuration Manager console doesn't populate. You also see the following error entry in the BGBMgr.log file on the Site Server: |
| 41 | + |
| 42 | +```output |
| 43 | +BCP queued 18 rows for currently logged on users |
| 44 | +*** [23000][515][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Cannot insert the value NULL into column 'CurrentLogonUser', table 'CM_P01.dbo.BGB_LiveDataLogonUsersPending'; column does not allow nulls. INSERT fails. |
| 45 | +*** [01000][3621][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]The statement has been terminated. |
| 46 | +*** bcp_batch() failed |
| 47 | +ERROR: Failed to send batched rows |
| 48 | +ERROR: Failed to execute task class LiveDataBcp |
| 49 | +ERROR: Failed to bcp file |
| 50 | +ERROR: Failed to execute task class LiveDataProcessTask |
| 51 | +WARNING: Failed to process file Bgbtdhs3.BLD, move it to bad inbox |
| 52 | +Begin to move file from E:\Microsoft Configuration Manager\inboxes\bgb.box\Bgbtdhs3.BLD to E:\Microsoft Configuration Manager\inboxes\bgb.box\bad\Bgbtdhs3.BLD |
| 53 | +``` |
| 54 | + |
| 55 | +## Cause |
| 56 | + |
| 57 | +ODBC Driver for SQL Server version 18.6.1.1 includes a change that enforces stricter handling of NULL values for non-nullable columns. This change can cause failures in Configuration Manager operations that try to insert NULL values into such columns. Such failures generate errors during Site Installation and "Currently Logged on User" reporting. |
| 58 | + |
| 59 | +## Workaround |
| 60 | + |
| 61 | +To work around this issue, make one of the following changes to ODBC Driver for SQL Server: |
| 62 | + |
| 63 | +- Downgrade the driver to [version 18.5.2.1](/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows#1852). |
| 64 | +- Downgrade the driver to [version 18.4.1.1](/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows#184). Configuration Manager version 2503 and later versions include this version of the driver as redistributable content. |
| 65 | + |
| 66 | +> [!NOTE] |
| 67 | +> ODBC Driver for SQL Server version 18.6.1.1 doesn't contain security updates. Therefore, rolling back the driver doesn't introduce vulnerabilities. |
| 68 | +
|
| 69 | +## More information |
| 70 | + |
| 71 | +Microsoft plans to resolve this issue in an upcoming ODBC Driver for SQL Server release. For more information, see [Support lifecycle for Microsoft ODBC Driver for SQL Server](/sql/connect/odbc/support-lifecycle). |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments