Why Manual File Copying of WinCC Projects from ES to OS Fails in PCS 7

Manually copying a WinCC OS project folder from the Engineering Station (ES) to an Operator Station (OS) instead of using the standard SIMATIC Manager download function is strictly unsupported and causes immediate runtime failures. A copied project retains the original computer name and internal SQL Server database paths embedded in the project definition files (.mcp, .mdf), triggering 'Database context does not exist or is invalid' errors upon startup. Furthermore, manual copying fails to register Process Object (PO) runtime licensing, causing WinCC to default to missing tag-based licenses. Always execute a formal ES-OS download via PLC -> Download to Target Station after properly configuring Simatic Shell and network sharing.

Architectural Difference Between WinCC Standalone and PCS 7 OS

In standard factory automation with standalone WinCC, copying project folders between PCs and updating the computer name in WinCC Explorer is a common engineering technique. However, SIMATIC PCS 7 operates on a fundamentally different DCS architecture where the Engineering Station acts as the single source of truth for the entire multiproject.

In PCS 7, Operator Stations (OS Single Stations, OS Servers, and OS Clients) are managed as configured PC Stations in STEP 7 HW Config and NetPro. When you compile an OS, SIMATIC Manager generates database records, message structures, and technological Process Object (PO) metadata specifically keyed to the target station. Deploying an OS project requires the integrated PLC -> Download mechanism, which manages Microsoft SQL Server database attachment, computer name translation, and network share security automatically.

Why Manual File Copying Causes Database Context Errors

When an engineer manually copies an OS folder (e.g., from C:\...\wincproj\OS1) across the network to a target OS machine, several severe configuration discrepancies occur:

Embedded Computer Name Mismatch: The WinCC project file (<ProjectName>.mcp) and SQL Server database files (*.mdf / *.ldf) retain references to the ES computer name. When WinCC Explorer opens on the OS, the local SQL Server instance cannot reconcile the project context, triggering the fatal error: 'The project could not be opened. Database context does not exist or is invalid.'
License Invalidation (PO vs Tag Licensing): In PCS 7, runtime licensing is governed by booked Process Objects (PO). A manually copied project bypasses the PCS 7 licensing handshake, causing the WinCC runtime to fall back to classic tag-based licensing mode, resulting in license demo mode popups or missing tag license faults.
Broken Inter-Station Redundancy and DCOM Security: Manual file copying fails to establish SIMATIC Shell multicast associations, preventing redundant server synchronization and OS client interconnection.

Comparison of ES-OS Deployment Methods

The table below contrasts manual folder copying against the standard PCS 7 ES-OS download mechanism.

Deployment CriterionManual Folder Copy & PasteStandard PCS 7 ES-OS Download (PLC -> Download)Database RegistrationFails; database context remains tied to ES machineAutomated; SQL Server attaches databases to local instanceComputer Name AdaptationRetains ES name; requires manual and error-prone editsAutomated; Project Editor adapts station name dynamicallyRuntime Licensing ModelDefaults to WinCC RC/RT tag licensing (Demo mode)Correctly registers PCS 7 Process Object (PO) runtime licensesRedundancy & Simatic ShellInternal GUIDs break; redundancy pairing failsEstablishes authenticated Simatic Shell communicationSiemens Support StatusStrictly Unsupported; invalidates project integrityOfficial Standard Practice; fully certified and supported

Resolving Database Context and Network Download Failures

When the standard ES-OS download fails with database errors or transfer aborts, resolve the underlying communication issues rather than resorting to manual copying:

Configure Simatic Shell Settings:
- On both ES and OS stations, open Windows Explorer, right-click Simatic Shell, and select Settings.
- Verify that the network adapter assigned to the Terminal Bus is selected on all nodes.
- Ensure that Multicast settings (TTL and IP range) match across all stations.
Configure Network Folder Sharing and Permissions:
- On the target OS computer, share the destination folder (e.g., D:\WinCC_Project) on the network.
- Grant full read and write permissions to the Windows user group SIMATIC HMI.
Verify Windows User Accounts and LMHOSTS:
- Ensure that identical Windows user accounts and passwords exist on ES and OS nodes, and belong to Administrators and SIMATIC HMI.
- Add IP addresses and computer names to C:\Windows\System32\drivers\etc\lmhosts on all stations to guarantee instant name resolution.
Reset SQL Server (WinCC) Service:
- If the OS database is locked, open Windows Services (services.msc), stop SQL Server (WINCC), delete orphaned *.ldf lock files if advised, and restart the service.

Verification

Verify correct OS deployment through the following steps:
1. In SIMATIC Manager on the ES, right-click the OS object and select PLC -> Download: verify that the download progress bar completes with status 'Download completed successfully'.
2. On the OS station, open WinCC Explorer: confirm that the title bar displays the local computer name rather than the ES name.
3. Start WinCC Runtime: verify that the runtime activates without 'Database context invalid' or 'Missing tag license' warnings.
4. Open Automation License Manager on the OS: verify that booked AS/OS Process Objects are recognized correctly.

Limitations and Operational Precautions

Never execute a full OS download while the target OS Server is actively controlling plant processes, as a full download stops WinCC Runtime. In redundant server pairs, execute OS downloads sequentially: download changes to the standby partner first, activate runtime, verify synchronization via @RM_MASTER, and then download to the partner server.

Engineer FAQ

Can I use WinCC Project Duplicator instead of ES download?

Project Duplicator is designed for standalone WinCC redundant partner creation, not for PCS 7 multiprojects. In PCS 7, always configure redundant servers in SIMATIC Manager and download via the ES.

Why does WinCC ask for RC tag licenses after copying an OS project?

PCS 7 uses Process Object (PO) licensing. When an OS is copied manually, the project metadata that links WinCC to the PCS 7 PO license pool is bypassed, forcing WinCC to look for classic tag licenses.

What should I do if Simatic Shell does not show the target OS?

Check the Terminal Bus network card binding in Simatic Shell Settings. If encrypted communication is enabled in PCS 7 V9.0, ensure that the security keys match across all nodes.