|
| 1 | +--- |
| 2 | +title: Updating ODBC Driver for SQL Server to 18.6.1.1 update causes issues in Configuration Manager |
| 3 | +description: Describes issues that appear after updating to ODBC Driver for SQL Server to version 18.6.1.1 in Configuration Manager. |
| 4 | +ms.date: 01/16/2025 |
| 5 | +ms.reviewer: kaushika, payur |
| 6 | +ms.author: payur |
| 7 | +ms.custom: sap:Configuration Manager Setup, High Availability, Migration and Recovery\Site Installation or Prerequisites |
| 8 | +--- |
| 9 | +# Updating ODBC Driver for SQL Server to 18.6.1.1 update causes issues in Configuration Manager |
| 10 | + |
| 11 | +*Applies to*: Configuration Manager |
| 12 | + |
| 13 | +## Symptoms |
| 14 | + |
| 15 | +After you install the [Microsoft ODBC driver for SQL Server on Windows version 18.6.1.1](sql/connect/odbc/windows/release-notes-odbc-sql-server-windows#186), the installation of new ConfigMgr site fails with the following error in ConfigMgrSetup.log: |
| 16 | + |
| 17 | +```output |
| 18 | + INFO: Database watermark: |
| 19 | + ERROR: Failed parsing the watermark from the database: 80070057. |
| 20 | + INFO: Could not retrieve and process both watermarks, will import all tables from disk. |
| 21 | + INFO: On disk watermark is newer than the one in the database. All tables will be imported. |
| 22 | + INFO: Starting data import data to table: LU_LicensedProduct |
| 23 | + *** 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. |
| 24 | + *** [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. |
| 25 | +... |
| 26 | + ERROR: FAILED to import data to table LU_LicensedProduct |
| 27 | + ERROR: Failed to import data from CSV files |
| 28 | + ERROR: Failed to import Asset Intelligence data into the site database. |
| 29 | +``` |
| 30 | + |
| 31 | +In the existing environments, after updating the ODBC Driver for SQL Server to version 18.6.1.1, the Client Notification feature might stop working. You might see the following error message in the BGBMgr.log on the Site Server: |
| 32 | + |
| 33 | +```output |
| 34 | +BCP queued 18 rows for currently logged on users |
| 35 | +*** [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. |
| 36 | +*** [01000][3621][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]The statement has been terminated. |
| 37 | +*** bcp_batch() failed |
| 38 | +ERROR: Failed to send batched rows |
| 39 | +ERROR: Failed to execute task class LiveDataBcp |
| 40 | +ERROR: Failed to bcp file |
| 41 | +ERROR: Failed to execute task class LiveDataProcessTask |
| 42 | +WARNING: Failed to process file Bgbtdhs3.BLD, move it to bad inbox |
| 43 | +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 |
| 44 | +``` |
| 45 | + |
| 46 | +## Cause |
| 47 | + |
| 48 | +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 lead to failures in Configuration Manager operations that attempt to insert NULL values into such columns, resulting in errors during site installation and Client Notification processes. |
| 49 | + |
| 50 | +## Resolution |
| 51 | + |
| 52 | +Downgrade the ODBC Driver for SQL Server to [version 18.5.2.1](/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows?view=sql-server-ver17#1852) or use a [version 18.4.1.1](/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows?view=sql-server-ver17#184) being included with Configuration Manager version 2503 and later as Redistributable content. |
| 53 | + |
| 54 | +## More information |
| 55 | + |
| 56 | +There are no security updates in ODBC Driver for SQL Server version 18.6.1.1. Microsoft plans resolving the issue in the next ODBC Driver for SQL Server release expected in the middle of 2026. |
| 57 | + |
| 58 | +See also: [Support lifecycle for Microsoft ODBC Driver for SQL Server](/sql/connect/odbc/support-lifecycle) |
0 commit comments