Troubleshooting Database Errors and Download Failures on WinCC Reference Stations in PCS 7

When downloading a project to a WinCC Application Reference ('WinCC Appl. (ref)') station fails with the error 'The project could not be opened. Database context does not exist or is invalid', the failure occurs because the Base OS was never compiled or downloaded prior to the reference download, or because stale SQL database attachments exist in the target directory on the reference PC. To resolve the failure, execute an Entire OS compilation and download on the Base OS first, detach any lingering database registrations on the reference machine using CCDataDetacher, verify that the reference PC Station name in HW Config matches the target computer name identically, and re-download the Reference OS.

Executive Summary

Deploying secondary operator stations using WinCC Application Reference (WinCC Appl. (ref)) streamlines DCS engineering by allowing multiple PCs to inherit a unified Base OS project. However, following project migrations (such as upgrading from CPU 416 to CPU 410-5H or migrating from PCS 7 V7.1 to V8.1/V9.0), engineers frequently encounter an abrupt download failure on the referenced station: The project could not be opened. Database context does not exist or is invalid. This error halts commissioning, leaving the secondary station unconfigured even when the primary Base OS operates normally. This article details the database replication mechanics during reference downloads, explains the prerequisite sequence, and provides a verified troubleshooting procedure.

Architecture and Fundamental Mechanics

Reference OS Deployment Mechanics, Database Context Generation, and Computer Name Adaptation:

Architecture of the Reference OS Download Sequence:
Unlike an independent OS, a Reference OS (WinCC Appl. (ref)) has no standalone compilation process; it relies completely on the compiled artifacts of its assigned Base OS.
When PLC > Download is initiated for a Reference PC Station:
1. The Engineering Station accesses the compiled project directory of the Base OS.
2. It transfers the project files across the Terminal Bus into the shared destination folder on the Reference PC.
3. A specialized deployment script invokes the SQL database engine on the destination station, executes a computer name substitution inside the internal project tables, and attaches the databases (<Project>.mdf/.ldf) to the local SQL Server instance (WINCC).
Root Causes of the 'Database Context' Failure on Reference Stations:
Base OS Never Compiled or Downloaded: If the project was migrated, the Base OS must be compiled and deployed first. If the Base OS binaries do not exist or have invalid internal GUIDs, the Reference OS deployment script fails to resolve the source.
Stale SQL Database File Attachments on the Reference PC: If the Reference PC already hosted an earlier project iteration, SQL Server may still hold an active registration for the project name. The newly copied .mdf file cannot be attached due to an SQL context collision.
Station Configuration Editor Name Mismatch: The PC Station name in HW Config must match the physical Windows Computer Name of the Reference station exactly. A character mismatch causes DCOM security rejection during database registration.

Step-by-Step Implementation Procedure

Verify and Compile the Base OS Station First:
* In SIMATIC Manager Component View, locate the primary PC Station hosting the WinCC Application (Base OS).
* Right-click the Base OS and select Compile.
* Perform an Entire OS compile; verify that compilation completes with zero errors.
* Download the Base OS to its physical machine (PLC > Download) to confirm baseline operational integrity.
Clear Stale Database Registrations on the Reference Machine:
* Log onto the physical Reference PC station as Administrator.
* Close WinCC Explorer and all Siemens applications.
* Open C:\Program Files (x86)\Siemens\WinCC\bin\CCDataDetacher.exe as Administrator.
* Select any attached project databases matching your project name and click Detach.
* Delete all existing files inside the shared target project directory (e.g. D:\WinCC_Projects\Ref_Station\).
Verify Reference PC Station Properties in SIMATIC Manager:
* In SIMATIC Manager, check the PC Station name of the Reference station: it MUST match the Windows Computer Name of the Reference PC.
* Right-click the Reference OS object and select Object Properties.
* Under Target OS and Standby OS Computer, confirm that the assigned Base OS is correctly selected.
* Verify the UNC destination path (e.g. \\REF_PC01\WinCC_Project).
Verify SIMATIC Shell on Reference Machine:
* Open Windows File Explorer on the Reference PC; right-click SIMATIC Shell and select Settings.
* Verify that the network adapter connected to the Terminal Bus is selected.
* Confirm that both the ES and Base OS are visible in the SIMATIC Shell tree.
Execute Entire Download to Reference OS:
* On the ES, select the Reference OS object.
* Select menu PLC > Download, select Entire OS, and click OK.
* Confirm that files copy and SQL Server attaches the database cleanly without context errors.

Verification

Confirm that the SIMATIC Manager download dialog completes with 'Download completed successfully'.
On the Reference PC station, launch WinCC Explorer; confirm that the project opens immediately.
Verify that the computer name displayed in WinCC Explorer reflects the Reference PC's local hostname.
Start WinCC Runtime; verify that all graphic screens, faceplates, and alarm logs function identically to the Base OS.

Limitations and Operational Precautions

Never attempt to compile the Reference OS directly; compilation must always occur on the Base OS. If logic or graphics are modified, compile the Base OS, download the Base OS, and then download the Reference OS.

Engineer FAQ

Why did the Reference OS download fail with 'Database context does not exist'?

The Base OS was not compiled/downloaded first, or stale SQL database files locked the project on the reference machine.

What must be done before downloading to a WinCC Appl. (ref)?

You must compile and download the Base OS project first to generate the required database templates.

How do I clear locked databases on the Reference station?

Run CCDataDetacher.exe from the WinCC bin directory as Administrator and detach the conflicting project database.

Does the Reference PC station name have to match Windows?

Yes, the PC Station name in HW Config must match the physical Windows computer name exactly.

Can I download changes to a Reference OS?

Yes, once the initial Entire Download establishes the project baseline, Changes download is supported.

Technical References

WinCC Appl Ref

Reference OS

Database Context Invalid

20 respuestas

Troubleshooting Database Errors and Download Failures on WinCC Reference Stations in PCS 7