SQL Server 2017 Express (WINCC): patch and repair fail with error 29569 "failed to restore the instance id"

秋阳 孙 0 信誉分
2026-10-19T10:44:28.83+00:00

Please route to a Chinese-speaking engineer if available.

ENVIRONMENT

Windows 10 Pro 22H2 (10.0.19045) x64, no cluster. SQL Server 2017 Express, named instance WINCC (MSSQL14.WINCC), language 1033, current build 14.0.2056.2, setup bootstrap 14.0.2140.2. The instance was installed by Siemens SIMATIC WinCC; the original install source folder no longer exists.

SYMPTOM

Every GDR security update since October 2024 (KB5042217 through KB5128497) fails at the start of the MSI install, before any file is copied:

Component error code: 29569

Error description: SQL Server Setup failed to restore the instance id.

CustomAction RestoreSetupParams_64 returned actual error code 1603.

Windows Update reports this as 0x80070643.

The same failure occurs with (1) Windows Update, (2) manual /action=patch /instancename=WINCC, (3) ACTION=REPAIR from official SQL Server 2017 Express RTM media (14.0.1000.169). Only the Database Engine feature fails; SQL Browser, SQL Writer, Client Connectivity and Setup Support Files repair successfully.

EVIDENCE

  • MSI log: "Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Setup 3: 2" (instance segment empty)
  • Settings.xml: <Setting Id="INSTANCEID" Value="" Source="Default" />
  • Engine product {DED314CA-0EFE-4593-9D66-EF75E5289A4C}: Patches subkey has only 2 patches (2047, 2056), matching the build; there is NO uninstall registry key for this product (all other SQL 2017 products have one); InstallProperties.InstallSource points to a deleted Siemens folder.
  • 13 orphan patch registrations (KB5042217...KB5128497) exist in Add/Remove Programs although never applied.
  • C:\Windows\Installer\1786a.msi is byte-identical to the engine MSI in official media (SHA256 67C224D6A115BF8CE94D1D5E808240E91EB69DEA3FC533F1269EB3924A540C0F).

REQUEST

Per the documented guidance for error 29569 (instance metadata missing/inconsistent), please identify which InstanceId / uninstall metadata is missing or inconsistent for product {DED314CA-0EFE-4593-9D66-EF75E5289A4C}, and provide the supported way to restore it so that patching and repair succeed without reinstalling the instance. Please also advise whether the 13 orphan patch registrations should be removed.

  1. On the affected server, open an elevated command prompt.
  2. Run: SQLServer2017-KB5128497-x64.exe /action=patch /instancename=WINCC /IAcceptSQLServerLicenseTerms /INDICATEPROGRESS
  3. Setup stops after ~40 seconds with "SQL Server Setup failed to restore the instance id" (29569), MSI code 1603.
  4. Review C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log<timestamp>\Summary.txt and WINCC\sql_engine_core_inst_Cpu64_1.log.
  5. Alternative: run SETUP.EXE /ACTION=REPAIR /INSTANCENAME=WINCC from the RTM Express media - identical failure.

Security patching for this SQL Server 2017 instance has been impossible since October 2024. The instance remains at 14.0.2056.2 and is exposed to all vulnerabilities fixed in KB5042217 through KB5128497. The host is a Siemens SIMATIC WinCC station, so we cannot simply reinstall the SQL instance without vendor approval. Service is currently running; the impact is security/compliance, not an outage.

MS-case-dossier.pdf

SQL Server | 其他
0 个注释 无注释

你的答案

提问者可以将答案标记为“已接受”,审查方可以将答案标记为“已推荐”,这有助于用户了解答案是否解决了提问者的问题。