Share via

SCCM 2403/2509 installation fails with ODBC Driver 18.6.1 (LU_LicensedProduct NULL insert)

Ahmet Kurt 20 Reputation points
2026-01-12T08:48:52.7966667+00:00

SCCM (Microsoft Endpoint Configuration Manager) installation fails during

Asset Intelligence data import after the site database is created successfully.

Error message

  • Cannot insert the value NULL into column 'VersionCode'
  • Invalid cursor state
  • Failed parsing the watermark from the database (80070057)

Specifications

  • SCCM versions: 2403, 2509
  • SQL Server versions: 2017, 2019
  • SQL and SCCM installed on separate servers
  • Clean database installations
  • Correct SQL collation

Cause/Problem

The issue is reproducible when Microsoft ODBC Driver 18.6.1 is installed.

Workaround

Downgrading Microsoft ODBC Driver 18 from version 18.6.1 to 18.5.1 or 18.5.2.1

resolves the issue and SCCM installation completes successfully.

Notes

This appears to be a regression in ODBC Driver 18.6.1 affecting cursor handling

during SCCM Asset Intelligence (LU_LicensedProduct) import.

Reference

Detailed analysis:

https://www.ahmetkurt.com.tr/error-received-while-installing-sccm-version-24032509-error-code-cannot-insert-the-value-null-into-column-and-lu_licensedproduct/

Microsoft System Center | Other

Answer accepted by question author

AI answer

2026-01-12T08:49:01.1933333+00:00

The issue you are experiencing with the SCCM installation failing during the Asset Intelligence data import is related to the Microsoft ODBC Driver 18.6.1. The error messages indicate that there is a problem with inserting a NULL value into the 'VersionCode' column and issues with cursor handling during the import process. This appears to be a regression in the ODBC Driver 18.6.1.

As a workaround, downgrading the ODBC Driver from version 18.6.1 to either 18.5.1 or 18.5.2.1 resolves the issue, allowing the SCCM installation to complete successfully. This suggests that the newer driver version has introduced changes that affect the cursor handling required by SCCM during the import process.

If you continue to face issues, consider checking for updates or patches from Microsoft regarding the ODBC driver or SCCM that may address this regression in future releases.

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gideon Paitu Yawson 0 Reputation points
    2026-03-04T15:23:37.18+00:00

    ERROR: FAILED to import data to table LU_LicensedProduct $$<Configuration Manager Setup><03-04-2026 13:49:08.957+00><thread=5584 (0x15D0)>

    ERROR: Failed to import data from CSV files $$<Configuration Manager Setup><03-04-2026 13:49:08.957+00><thread=5584 (0x15D0)>

    ERROR: Failed to import Asset Intelligence data into the site database.~ $$<Configuration Manager Setup><03-04-2026 13:49:09.128+00><thread=5584 (0x15D0)>

    Not recovery mode or not top level site. Skip restoring client piloting packages. $$<Configuration Manager Setup><03-04-2026 13:49:09.128+00><thread=5584 (0x15D0)>

    ~~===================== Completed Configuration Manager Server Setup ===================== $$<Configuration Manager Setup><03-04-2026 13:49:09.128+00><thread=5584 (0x15D0)>

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.