C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Diagnosing OS Project Download Errors and Verifying SQL Server Service Dependencies in PCS 7

Diagnosing OS Project Download Errors and Verifying SQL Server Service Dependencies in PCS 7

When downloading an OS project to a target OS Server fails with database connection or transfer errors in SIMATIC PCS 7 V9.0 SP3, the root cause is typically inactive Microsoft SQL Server services on the target station. The transfer engine strictly requires that the 'SQL Server (WINCC)' instance and 'SQL Server Browser' services are active and running on the OS Server. To resolve this: open Windows Services (services.msc) on the OS Server, ensure both SQL services are set to Automatic and started, verify local write permissions on the shared project directory, restart both stations, and re-attempt the download.

Table of Contents

Executive Summary

In SIMATIC PCS 7 (V8.0 through V9.1), deploying an operator station project from the Engineering Station (ES) to target OS Servers requires multi-tiered client-server communication over the Terminal Bus. When an engineer initiates 'Target OS -> Download' in SIMATIC Manager, the process does not execute a simple file transfer; it connects to the target machine's database engine to mount and register project database files. If target SQL Server services are stopped or unconfigured, the download engine fails immediately with cryptic transfer errors. This article details the database service architecture required on OS Servers and outlines the step-by-step diagnostic procedure to ensure successful project deployment.

Architecture and Fundamental Mechanics

Target OS Database Services and Download Mechanics across the Terminal Bus:

  • Multi-Tier Database Deployment Protocol:
  • When SIMATIC Manager executes an OS download, the ES connects to the target OS Server using Microsoft DCOM and RPC services.
  • The target station must host an active, responsive Microsoft SQL Server instance designated specifically as MSSQL$WINCC.
  • The WinCC Project Manager daemon (CCProjectMgr.exe) on the target machine accepts the incoming project database files (.mdf/.ldf) and instructs the SQL Server instance to attach them.

  • If the SQL Server (WINCC) service is stopped, disabled, or hanging in a zombie state, the attachment request times out, causing SIMATIC Manager to report fatal transfer errors.

  • The Role of the SQL Server Browser Service:

  • Named instances of SQL Server (such as WINCC) do not listen exclusively on standard TCP Port 1433; they use dynamic ports assigned at startup.
  • The SQL Server Browser service (listening on UDP Port 1434) resolves dynamic port assignments for incoming remote connection requests from the Engineering Station.

  • If SQL Server Browser is stopped, remote tools cannot locate the WINCC instance, causing project downloading and database attachment to fail.

  • Windows File Sharing and UNC Staging:

  • The destination folder on the OS Server must be configured as a standard Windows network share with write access granted to the local SIMATIC HMI group.
  • Stale database lock files (.lck) from previous aborted downloads will prevent SQL Server from mounting the new project.

Step-by-Step Implementation Procedure

Step-by-Step Procedure to Diagnose and Start Required SQL Services:

  1. Inspect and Start Target SQL Server Services:
    - Log on to the target OS Server with administrator privileges.
    - Press Win + R -> type services.msc -> press Enter.
    - Scroll down to locate SQL Server (WINCC).
    - Verify that 'Status' indicates Running and 'Startup Type' is set to Automatic.
    - Locate SQL Server Browser: Confirm status is Running and startup type is Automatic.
    - If either service is stopped, right-click and select Start.
  2. Verify SQL Server Instance Configuration in SQL Configuration Manager:
    - Open SQL Server Configuration Manager on the OS Server.
    - Navigate to SQL Server Network Configuration -> Protocols for WINCC.
    - Ensure that TCP/IP and Named Pipes are both set to Enabled.
  3. Verify Local Share Write Permissions:
    - Open Windows File Explorer on the OS Server; locate the target project directory.
    - Right-click the folder -> select Properties -> Sharing.
    - Verify the folder is shared with Full Control permissions granted to the SIMATIC HMI group.
    - Delete any temporary .lck or .tmp files lingering in the project directory.
  4. Run Siemens Security Controller on Both Stations:
    - On both ES and OS Server, open Start -> Siemens Automation -> Security Controller.
    - Click Repeat Settings to ensure firewall ports (UDP 1434, TCP 135, TCP 445) and DCOM security rights are applied.
  5. Re-attempt Project Download from SIMATIC Manager:
    - Restart both ES and OS Server if services were previously hanging.
    - In SIMATIC Manager Component View, right-click the OS project -> select PLC -> Download.
    - Execute download and monitor progress to completion.

Verification

Verification Procedure:
1. Service Health Check: Open Windows Task Manager on the OS Server; verify that sqlservr.exe is running with normal background CPU utilization (< 2%).
2. Download Progress Audit: Observe the transfer progress dialog in SIMATIC Manager. Confirm that the progress bar advances smoothly through file copy, database initialization, and concludes with 'Download completed successfully'.
3. Project Attachment Verification: Open WinCC Explorer on the OS Server; confirm that the downloaded .mcp project file opens cleanly without SQL connection error popups.

Limitations and Operational Precautions

Operational Precautions and SQL Maintenance Rules:
- Never Manually Edit SQL Tables: Direct editing or modifying of WinCC SQL Server tables via SQL Management Studio is unsupported and will void system support.
- Whitelist Exclusions: Ensure SQL Server database directories (C:\Program Files\Microsoft SQL Server\MSSQL*\Data\) are strictly excluded from antivirus on-access scanning to prevent file-locking during project download.
- Dedicated Account Rights: The active Windows user account performing the download must be a member of the local SIMATIC HMI group on both stations.

Engineer FAQ

Why does OS downloading fail even when network ping works perfectly?

Ping only verifies basic ICMP network reachability. OS project downloading requires the active Microsoft SQL Server instance (MSSQL$WINCC) and the SQL Server Browser service to be running on the target station.

What port does the SQL Server Browser service use?

The SQL Server Browser service listens on UDP Port 1434 to resolve dynamic port numbers for named SQL instances.

What should I do if the SQL Server (WINCC) service fails to start?

Check the Windows Event Viewer under System and Application logs; common causes include corrupt master database files, insufficient disk space, or account permission changes.

Can I download an OS project while WinCC Runtime is active on the server?

Only if performing an Online Delta Download (Download Changes). A full OS download requires WinCC Runtime and WinCC Explorer to be closed on the target server.

Where are download failure details logged in SIMATIC Manager?

Details are displayed in the SIMATIC Manager compilation and transfer output window at the bottom of the screen.

Technical References

Related Articles

Related Tags

  • SQL Server
  • OS Download
  • WinCC Services
  • Terminal Bus
  • SIMATIC Manager
20 respuestas