Resolving SQL Server 2014 Installation Package Errors During SIMATIC PCS 7 Setup

The error 'This installation package could not be opened. Verify that the package exists and that you can access it' during Microsoft SQL Server 2014 installation in SIMATIC PCS 7 setup is caused by path length limits, Windows 'Mark of the Web' zone protection, or insufficient administrator privileges. To resolve this, extract the PCS 7 installation media to a short local directory path without spaces or special characters (e.g., 'C:/PCS7_Setup/'), right-click the setup media and unblock archive security attributes in Windows Properties, ensure the local Windows user belongs to the local 'Administrators' group, and launch 'Setup.exe' using 'Run as administrator'.

Executive Summary

During the deployment of SIMATIC PCS 7 V9.0 SP3 on industrial servers or engineering workstations, the automated installation wizard installs Microsoft SQL Server 2014 SP2 to support WinCC runtime databases and Tag Logging archives. If the setup process halts unexpectedly with the Windows Installer error: 'This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor', the problem typically stems from environmental file access limitations rather than corrupt media. This guide details the technical mechanisms behind MSI package access failures, outlines remediation steps, and provides verification routines for a successful installation.

Architectural and System Mechanics

Microsoft Windows Installer (MSI) and PCS 7 setup dependencies:

Path Length Constraints (MAX_PATH): The standard Windows API and Windows Installer engine enforce a 260-character path limit. Nested directory structures on extracted ISOs (e.g., C:/Users/.../Downloads/SIMATIC_PCS7_V903/DVD_1/SQL2014/x64/...) frequently exceed this limit, causing MSIexec to report that the package cannot be found.
Windows Attachment Execution Service (Zone.Identifier): Archives downloaded over corporate networks or browsers are tagged with an NTFS Alternate Data Stream marking them as untrusted. Windows blocks embedded MSI and CAB execution silently.
Local Account Privileges and UAC: SQL Server installation configures low-level Windows service accounts (NT SERVICE/MSSQLSERVER) and modifies DCOM security. If User Account Control (UAC) token elevation is incomplete, MSIexec cannot access system directories.
Network Share Execution: Launching setup from a UNC path (\\server\share) causes authentication handoff failures when the sub-installer spawns in the local system context.

Step-by-Step Engineering and Implementation Procedure

Step 1: Copy and Extract Media to a Short Root Directory

Do not install from a network share or deeply nested desktop folder.
Copy the PCS 7 installation ISO or archive directly to a local root folder (e.g., C:/Setup/PCS7/).
Extract the files using an archive utility such as 7-Zip.

Step 2: Unblock Downloaded Files in Windows Properties

Right-click the downloaded ISO or ZIP file and select 'Properties'.
In the 'General' tab, locate the security warning: 'This file came from another computer and might be blocked...'.
Check the 'Unblock' box and click 'Apply'.
If already extracted, execute the following PowerShell command to unblock all nested files recursively:

Get-ChildItem -Path 'C:/Setup/PCS7' -Recurse | Unblock-File

Step 3: Verify User Group Memberships and Permissions

Ensure the logged-in Windows user is an explicit member of the local Administrators group.
Temporarily disable third-party antivirus software or endpoint security agents (e.g., McAfee, CrowdStrike, Carbon Black) that block MSI execution from temp folders.
Confirm that the Windows Installer service is enabled and running (services.msc -> 'Windows Installer').

Step 4: Run PCS 7 Setup as Administrator

Navigate to C:/Setup/PCS7/.
Right-click Setup.exe and select 'Run as administrator'.
Proceed with package selection; the SQL Server 2014 installer executes and registers all database instances smoothly.

Verification

To verify successful SQL Server 2014 installation:
1. Open Windows Services (services.msc); verify that SQL Server (WINCC) reports status 'Running' with startup type 'Automatic'.
2. Open Windows Programs and Features; confirm that 'Microsoft SQL Server 2014' and 'SQL Server 2014 Native Client' appear in the installed programs list.
3. Launch WinCC Explorer; create a test project and confirm that the project database activates without SQL connection errors.

Limitations and Operational Precautions

Operational precautions:
- Never attempt to install a generic commercial edition of SQL Server from Microsoft directly; SIMATIC PCS 7 requires the customized Siemens-packaged SQL Server edition containing required collation and instance settings.
- Do not alter the SQL instance name WINCC; PCS 7 internal runtime components hardcode dependencies to this instance.
- Always reboot the operating system when prompted by the installer before proceeding with subsequent software packages.

Engineer FAQ

Q: Why does the error state 'package could not be opened' when the file exists?

A: Windows Installer throws this error when the file path exceeds 260 characters or when file access is blocked by Windows security zone identifiers.

Q: Can I run the SQL installer manually from the DVD?

A: Yes, you can navigate to the SQL2014 directory on the media and execute Setup.exe directly as administrator if the master installer stalls.

Q: What collation does WinCC SQL Server 2014 require?

A: WinCC requires the collation SQL_Latin1_General_CP1_CI_AS.

Q: Does PCS 7 support SQL Server 2016 or 2019 on PCS 7 V9.0?

A: No. Each PCS 7 version is certified for a specific SQL Server release; PCS 7 V9.0 SP3 strictly requires SQL Server 2014 SP2.

Q: Why is installing from a network share discouraged?

A: Because the Windows Installer service running under the LocalSystem account cannot access network shares without delegated Kerberos credentials.

Technical References

Related Tags

SQL Server 2014, PCS 7 Setup, Installation Error, Windows Installer, SIMATIC WinCC

20 respuestas

Resolving SQL Server 2014 Installation Package Errors During SIMATIC PCS 7 Setup