Resolving SQL Server 2017 Setup Crash in PCS 7 V9.1 Caused by Truncated Configuration DLL in Installation Media

During SIMATIC PCS 7 V9.1 installation on Windows 10 Enterprise LTSC 2019, SQL Server 2017 (WinCC) setup may abruptly abort with the message 'The following program could not be installed: SQL server 2017 - (Wincc) Setup cannot complete the installation'. In certain official installation media packages and localized image downloads, this failure is triggered by a corrupted setup filename in 'SQL2017std\setup\x64' where the library is misnamed 'microsoft.sqlserver.configuration.extensibility_configextens.dll' instead of 'microsoft.sqlserver.configuration.extensibility_configextension.dll'. Renaming this file to restore the missing 'ion' characters in the filename allows the SQL Server 2017 installation bootstrap engine to load the extensibility configuration module and complete the setup without errors.

Executive Summary

Installing SIMATIC PCS 7 V9.1 introduces Microsoft SQL Server 2017 Standard Edition (64-bit) as the core real-time relational database engine for WinCC V7.5 SP2. In numerous deployment environments—even those operating on fully compatible, freshly patched Windows 10 Enterprise LTSC 2019 systems—the automated setup sequence abruptly fails during the SQL Server 2017 installation phase. The installation halts, requiring multiple restarts, and ultimately displays a fatal error stating that SQL Server 2017 (WinCC) Setup cannot complete. Diagnostic investigation reveals that certain PCS 7 V9.1 installation distribution media contained an unpatched packaging defect where a critical Microsoft SQL Server setup extensibility binary had its filename truncated during ISO compression. This article documents the root cause, exact directory path, and corrective renaming procedure required to ensure successful deployment.

Architecture and Fundamental Mechanics

SQL Server 2017 Bootstrap Media Packaging, Extensibility Modules, and Dynamic Dependency Resolution:

SQL Server 2017 Setup Bootstrap Architecture:
The PCS 7 master installer (Setup.exe) orchestrates silent, chained child installations of system components, initiating SQL Server 2017 via SQL2017std\Setup.exe with preconfigured unattended command-line parameters.
During initialization, the SQL Server setup engine executes discovery rules and unpacks dynamic link libraries responsible for rule validation, feature extraction, and SQL configuration extension handling.
Root Cause of the Truncated Filename Defect:
In specific PCS 7 V9.1 ISO distribution images (including regional and multi-language download bundles), an archiving error caused the filename of the SQL extensibility assembly in SQL2017std\setup\x64 to be truncated by three characters.
Defective File Name: microsoft.sqlserver.configuration.extensibility_configextens.dll
Expected File Name: microsoft.sqlserver.configuration.extensibility_configextension.dll
When the SQL setup bootstrap engine attempts to bind the configuration extensibility assembly dynamically via reflection, the Windows loader fails to find the required DLL. The installer catches this failure as an unhandled configuration rule exception (0x84B10001 or missing file dependency), halts execution, and flags the WinCC database installation as failed.
Secondary Environmental Drivers:
When setup aborts, Windows Installer creates reboot entries in Session Manager\PendingFileRenameOperations. Rerunning setup without fixing the filename results in an endless reboot loop.

Step-by-Step Implementation Procedure

Locate and Extract the PCS 7 V9.1 Installation Package:
* If installing from an ISO image, copy the contents of the ISO to a local drive directory with a short path (e.g. C:\PCS7_V91_Setup\). Do not attempt to modify read-only optical discs or mounted ISO virtual drives directly.
Navigate to the SQL Server 2017 Setup Subdirectory:
* Open Windows File Explorer and navigate to:
C:\PCS7_V91_Setup\SQL2017std\setup\x64
Identify and Rename the Truncated DLL File:
* Scroll down to locate the file named:
microsoft.sqlserver.configuration.extensibility_configextens.dll
* Notice that the suffix extension was truncated to extens.
* Right-click the file, select Rename, and change the filename to:
microsoft.sqlserver.configuration.extensibility_configextension.dll
* Confirm that the file extension remains .dll.
Clear Lingering Windows Restart Flags:
* Open regedit.exe as Administrator.
* Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
* If present, delete the PendingFileRenameOperations multi-string value to clear pending reboot blocks.
Relaunch the PCS 7 V9.1 Installation:
* Return to the root folder C:\PCS7_V91_Setup\.
* Right-click Setup.exe and select Run as administrator.
* Proceed through the setup wizard. The SQL Server 2017 (WinCC) installation now discovers the properly named extensibility library and completes without errors.

Verification

Monitor the PCS 7 setup progress bar; verify that the step 'Microsoft SQL Server 2017 (WinCC)' proceeds through file copy, database instance configuration, and finishes with a green checkmark.
Review the SQL Server setup summary log in C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\Summary.txt; confirm that all installation rules and extension packages reported 'Passed'.
Open the Windows Services console (services.msc) and verify that the SQL Server (WINCC) service is present, configured for Automatic startup, and currently in the 'Running' state.

Limitations and Operational Precautions

Renaming the configuration DLL resolves setup failures originating from corrupted or truncated installation media, but does not circumvent underlying operating system incompatibilities. PCS 7 V9.1 remains strictly incompatible with non-LTSC Windows 10 editions (such as Windows 10 Pro or Home). Additionally, ensure that Microsoft .NET Framework 3.5 SP1 is installed before running setup.

Engineer FAQ

Why does SQL Server 2017 setup crash even on compatible Windows 10 Enterprise LTSC systems?

In specific PCS 7 V9.1 media packages, the SQL configuration DLL in 'SQL2017std\setup\x64' was packaged with a truncated filename ending in 'extens.dll' instead of 'extension.dll'.

What is the exact name of the file that needs to be renamed?

Rename 'microsoft.sqlserver.configuration.extensibility_configextens.dll' to 'microsoft.sqlserver.configuration.extensibility_configextension.dll'.

Can I rename the file on the original installation DVD or mounted ISO?

No, optical discs and mounted ISO images are read-only. Copy the setup folder to a local hard drive before renaming.

Why does the setup keep asking to restart the computer after the failure?

The aborted SQL installation leaves a 'PendingFileRenameOperations' registry key in Windows Session Manager, prompting a persistent reboot request.

Does this defect affect PCS 7 V9.0 or earlier releases?

No. PCS 7 V9.0 installs Microsoft SQL Server 2016 SP2, which uses a completely different setup package and directory structure.

Technical References

PendingFileRenameOperations

20 respuestas

Resolving SQL Server 2017 Setup Crash in PCS 7 V9.1 Caused by Truncated Configuration DLL in Installation Media