Resolving PCS 7 V9.0 SP1 SQL Prerequisite Errors Guide

PCS 7 V9.0 SP1 installation can proceed after the setup source, Windows release, station role, and SQL prerequisite all match the same Siemens release baseline. A request for SQL Server 2016 SP2 during a V9.0 SP1 installation is a mismatch: the released database level for PCS 7 V9.0 SP1 is SQL Server 2014 SP2.

SQL release baseline

The prerequisite checker reads the selected PCS 7 packages and compares their dependencies with the software detected on the computer. The term release baseline here means the exact combination of PCS 7 version, update level, operating system, station role, and SQL Server release approved to operate together.

PCS 7 release	Released SQL level	Installation implication
PCS 7 V9.0 SP1	SQL Server 2014 SP2	Use the V9.0 SP1 media and its matching prerequisites. Do not satisfy a request for SQL Server 2016 SP2.
PCS 7 V9.0 SP2 UC01 and later baseline stated here	SQL Server 2014 SP3	SP3 is released and recommended from this level. Obtain the SP3 package from Microsoft when the selected PCS 7 media requires it.
PCS 7 V9.0 SP1 setup requesting SQL Server 2016 SP2	Contradictory combination	Stop and identify the setup source or package producing the requirement.

Installing SQL Server 2016 SP2 merely to clear the displayed requirement creates an unapproved combination and can leave PCS 7 services dependent on a database level outside the V9.0 SP1 release matrix.

Check 1: Expect the compatibility selection and installation media to associate PCS 7 V9.0 SP1 with SQL Server 2014 SP2, not SQL Server 2016 SP2.

Windows edition and station role

Record the full Windows identity before changing SQL components. Windows 10 Enterprise LTSB 2015 is a specific servicing release; LTSB was subsequently renamed LTSC. The name change does not make different Windows releases interchangeable.

A compatibility result from another PCS 7 generation cannot qualify V9.0 SP1. For example, the PCS 7 V8.2 SP1 information lists Windows 10 Enterprise LTSC 2015 (64-Bit) only for OS Single Station, OS Client, Web Server, Web Client, Information Server, SIMATIC BATCH Client, SIMATIC Route Control Client, OpenPCS 7 Standalone, OpenPCS 7 with OS Client, and OpenPCS 7 OS Single Station. That V8.2 SP1 role list does not establish approval for a V9.0 SP1 Engineering Station, server, or any other V9 role.

1. Read the Windows edition, servicing release, architecture, and installed updates from the operating system.
2. Define the intended PCS 7 station role before selecting packages.
3. In the Siemens compatibility tool, select PCS 7 V9.0 SP1, the recorded Windows release, and that station role as one combination.
4. If the combination is not released, change the operating-system or PCS 7 baseline before continuing. Do not use an entry for V8.2 SP1 as a substitute.

Check 2: Expect one compatibility result that names V9.0 SP1, the installed Windows release and architecture, and the intended station role without borrowing qualifications from another PCS 7 version.

Installation media integrity

The integrated PCS 7 setup can install bundled prerequisites only when it can read the correct package set. A wrong disc, mixed media set, incomplete copy, or inaccessible package can make the prerequisite page disagree with the product release. The displayed SQL Server 2016 SP2 requirement is therefore a reason to validate the setup source before modifying Windows.

1. Confirm that the setup launcher belongs to the complete PCS 7 V9.0 SP1 distribution.
2. Keep all media folders together in their original structure; do not combine files from different PCS 7 service-pack levels.
3. If installation from the internal DVD path produces the mismatch, copy the complete DVD to a USB drive or use an external USB DVD drive.
4. Launch setup again from the root of that source and select the packages required for the verified station role.
5. Review the prerequisite page before starting installation.

Changing the media path does not change product compatibility. It tests whether the installer can consistently reach the prerequisite payload and metadata supplied with the release.

Check 3: Expect the copied or externally mounted media to show the same V9.0 SP1 identity and a prerequisite list aligned with SQL Server 2014 SP2.

Prerequisite correction procedure

Treat the SQL warning as a baseline fault, not as permission to install the requested database version. The correct action depends on what the preceding checks show.

Finding	Action	Expected result
Media is not V9.0 SP1	Replace it with the complete V9.0 SP1 distribution.	The checker evaluates the V9.0 SP1 prerequisite set.
Windows or station role is not released for V9.0 SP1	Select a released operating-system and role combination.	The compatibility decision contains no cross-version assumptions.
DVD access is unreliable or the package list changes	Use a complete USB copy or an external USB DVD drive.	Repeated setup runs enumerate the same packages and requirements.
V9.0 SP1 still requests SQL Server 2016 SP2 from verified media	Stop installation and preserve the setup diagnostics for Siemens support.	No unsupported SQL version is added to the computer.
The selected baseline is V9.0 SP2 UC01 rather than V9.0 SP1	Apply the SQL Server 2014 SP3 requirement for that baseline and obtain SP3 from Microsoft.	PCS 7 and SQL belong to the same released combination.

An operating-system reinstall reportedly cleared a similar installation problem on Windows 10 LTSB 2016, but rebuilding Windows is a last isolation step. First eliminate incorrect media, mixed package levels, and an unsupported Windows-role combination. If a rebuild becomes necessary, install the verified Windows baseline and run PCS 7 setup before adding unrelated software.

Check 4: Expect the prerequisite page either to recognize the bundled SQL Server 2014 SP2 path for V9.0 SP1 or to produce diagnostics suitable for escalation; it must not be bypassed with SQL Server 2016 SP2.

Windows networking pitfall

Installation success does not prove that the terminal-bus configuration will remain reachable. A documented Windows 10 case uses two network adapters, one configured with a default gateway and one without. After repeated failures to reach an unavailable communication partner, the adapter without a gateway can stop establishing the IP connection until its ARP cache is cleared.

For the Windows 10 configuration described with PCS 7 V8.2 SP1, operating the PC with one network adapter is recommended. Redundant or high-availability terminal-bus designs require their applicable Siemens compatibility guidance rather than this single-adapter recommendation; the referenced entry identifier is 109739786.

1. List every enabled network adapter and record which adapter has a default gateway.
2. Compare the adapter arrangement with the compatibility guidance for the actual V9.0 SP1 role and terminal-bus design.
3. Before blaming PCS 7 services, test IP reachability to each required partner and inspect the ARP state if communication remains unavailable after the partner returns.

Check 5: Expect the approved adapter topology, stable IP reachability, and renewed communication after an unavailable partner returns; a connection that recovers only after clearing ARP identifies the Windows networking condition rather than a SQL installation fault.

End-to-end installation verification

1. Check 6.1 — Product identity: Expect setup to identify PCS 7 V9.0 SP1 on every selected package screen.
2. Check 6.2 — Platform match: Expect the Windows edition, servicing release, architecture, and station role to match one V9.0 SP1 compatibility result.
3. Check 6.3 — Database level: Expect the installed or offered database prerequisite to be SQL Server 2014 SP2. A request for SQL Server 2016 SP2 fails this check.
4. Check 6.4 — Repeatable media reading: Expect two launches from the verified USB copy or external DVD to enumerate the same packages and prerequisites.
5. Check 6.5 — Setup completion: Expect all selected PCS 7 components and their prerequisites to finish without an unresolved requirement.
6. Check 6.6 — Communications: Expect each required PCS 7 communication partner to remain reachable across the approved network-adapter arrangement.

Frequently asked questions