Troubleshooting SIMATIC PCS 7 V8.1 Setup Hangs at Microsoft SQL Server 2008 R2 SP2 Installation

Troubleshooting SIMATIC PCS 7 V8.1 Setup Hangs at Microsoft SQL Server 2008 R2 SP2 Installation

During the installation of SIMATIC PCS 7 V8.1 (or V8.1 SP1) on an Engineering Station or OS Server, setup hangs indefinitely during the Microsoft SQL Server 2008 R2 SP2 (WinCC) phase typically because the Microsoft Windows .NET Framework 3.5 SP1 feature is missing, incomplete, or blocked by Windows Update, or because a pending system reboot flag remains locked in the Windows Registry. Resolving the hang requires terminating the stuck setup process, enabling .NET 3.5 via Windows Features or offline DISM source media, clearing the 'PendingFileRenameOperations' registry key, and executing the SQL Server prerequisite installation independently from the PCS 7 DVD media.

Table of Contents

Root Causes of Setup Freezes During SQL Server Installation

When executing Setup.exe from the SIMATIC PCS 7 V8.1 DVD, the master installer systematically deploys system prerequisites, Automation License Manager, Microsoft SQL Server 2008 R2 SP2 (under instance name WINCC), WinCC V7.3, and STEP 7 V5.5 SP4. A complete stall during the SQL Server stage is caused by:
1. Unresolved .NET Framework 3.5 Dependency:
- SQL Server 2008 R2 requires Microsoft .NET Framework 3.5 (which includes .NET 2.0 and 3.0).
- On Windows 7 SP1, Windows Server 2008 R2, or Windows Server 2012 R2, if .NET 3.5 is not pre-installed, SQL setup silently triggers a background Windows Update query to download packages.
- If the engineering workstation is on an isolated plant network without direct internet access, the download stalls indefinitely without displaying an error prompt.
2. Pending File Rename Operations in Windows Registry:
- Previous driver updates or software installations set registry restart flags that prevent the Microsoft SQL Server installer from launching sub-services.
3. Active Antivirus / Endpoint Security Blocking:
- Antivirus software (such as Windows Defender, Symantec, or McAfee) blocks SQL Server registry modifications, service account creations (NT SERVICE\MSSQL$WINCC), or disk volume permission changes.

Windows .NET Framework 3.5 and OS Prerequisite Configuration

Before initiating the PCS 7 V8.1 installer on an offline machine, enable .NET Framework 3.5 using local installation media:

  1. Insert Windows OS Installation DVD / Mount ISO:
    - Insert the original Windows installation media (e.g. drive D:).

  2. Deploy .NET 3.5 via DISM (Offline Command):
    - Open Command Prompt as Administrator.
    - Execute the Deployment Image Servicing and Management (DISM) command:
    cmd dism /online /enable-feature /featurename:NetFX3 /all /Source:D:\sources\sxs /LimitAccess
    - Wait for the operation to complete: The operation completed successfully.

  3. Verify Windows Components:
    - Open Control Panel > Programs and Features > Turn Windows features on or off.
    - Verify that Microsoft .NET Framework 3.5.1 displays a solid checkmark.

Clearing Pending Registry Locks and Standalone SQL Setup

If setup is already stalled, recover the system using the following steps:

  1. Terminate Stuck Installer Processes:
    - Open Windows Task Manager.
    - End processes: Setup.exe, SetupBootstrap.exe, and any running msiexec.exe instances.

  2. Remove Pending Reboot Registry Keys:
    - Press Win + R, type regedit, and press Enter.
    - Navigate to:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
    - Locate the value named PendingFileRenameOperations.
    - Right-click and delete PendingFileRenameOperations (or rename it to PendingFileRenameOperations_OLD).
    - Reboot the computer.

  3. Install SQL Server 2008 R2 SP2 Manually from DVD:
    - Open the PCS 7 V8.1 installation DVD in Windows Explorer.
    - Navigate to the prerequisites subfolder:
    <DVD_Root>\Support\SQL2008R2SP2\ (or Setup_SQL\).
    - Right-click Setup.exe and select Run as Administrator.
    - Verify that the installer installs the WINCC instance without errors.
    - Once the SQL instance is successfully created, re-launch the master PCS 7 Setup.exe and select Package Installation. The master setup detects the pre-installed SQL instance and proceeds directly to WinCC and STEP 7.

PCS 7 V8.1 Installation Prerequisites and Troubleshooting Table

The following table details common installation failure modes during PCS 7 V8.1 setup:

Setup StageObserved Failure SymptomUnderlying System BottleneckVerified Corrective ActionSQL Server 2008 R2Progress bar freezes at 50% indefinitely.NET 3.5 attempting internet downloadEnable .NET 3.5 offline via DISM using Windows mediaSystem Check'Please restart computer before setup' loopLocked PendingFileRenameOperations keyDelete PendingFileRenameOperations in Windows RegistryWinCC ComponentError 1603 during database creationInsufficient admin rights or antivirus lockDisable antivirus, run setup as Local AdministratorAutomation License ManagerALM service fails to registerCorrupted Microsoft Visual C++ redistributableInstall VC++ 2008/2010 redistributables manually from DVDMessage Queuing (MSMQ)Setup stops reporting missing MSMQWindows Message Queuing feature disabledEnable MSMQ in Windows Features prior to setup

Verification

To confirm that the SQL Server and PCS 7 installations have completed successfully:
1. Open Windows Services (services.msc) and verify that the following services are running with startup type Automatic:
- SQL Server (WINCC)
- SQL Server Integration Services 10.0
- Automation License Manager Service
2. Open SQL Server Configuration Manager:
- Navigate to SQL Server Network Configuration > Protocols for WINCC.
- Verify that Shared Memory, Named Pipes, and TCP/IP are all Enabled.
3. Launch SIMATIC Manager. Create a test multiproject, insert a PC Station with a WinCC OS, and open WinCC Explorer. Verify that WinCC opens and connects to the local SQL database without errors.

Limitations and Operational Precautions

When installing SIMATIC PCS 7:
1. Never Install on Unsupported Windows Builds: PCS 7 V8.1 is certified strictly for Windows 7 SP1 (64-bit) and Windows Server 2008 R2 SP1. Installing on Windows 10 or Windows Server 2016/2019 will cause unpredictable SQL and driver failures.
2. Never Rename the PC After Installation: Changing the Windows Computer Name after Microsoft SQL Server and WinCC are installed breaks SQL database instance bindings. If a PC rename is mandatory, complete it before running PCS 7 setup.
3. Local Administrator Rights: Always execute setup from a local administrator account. Running setup under a domain account restricted by Group Policy Objects (GPOs) frequently blocks necessary DCOM security permission assignments.

Engineer FAQ

Why does SQL Server setup try to connect to the internet during an offline install?

Microsoft designed the .NET 3.5 feature installer in newer Windows versions to query Windows Update servers for payload files by default unless an offline DISM source path is explicitly provided.

Can I install standard retail Microsoft SQL Server instead of the Siemens version?

No. Siemens WinCC requires a customized SQL Server instance containing specific collation settings (Latin1_General_BIN), custom service accounts, and embedded database templates provided exclusively on the PCS 7 DVD.

What should I do if the installation still hangs after deleting the registry key?

Check the detailed SQL setup log file located at: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt. This file reveals the exact error code or missing system DLL blocking setup.

Does PCS 7 V8.1 support SQL Server 2012 or 2014?

No. PCS 7 V8.1 and V8.1 SP1 are certified exclusively with Microsoft SQL Server 2008 R2 SP2 (32-bit instance). Upgrading SQL Server independently breaks WinCC runtime database engines.

Technical References

Related Articles

Related Tags

  • PCS7_V8_1
  • Installation_Troubleshooting
  • SQL_Server_2008R2
  • DotNet_35
  • DISM
  • PendingFileRenameOperations
  • Engineering_Station
6 respuestas