Recovering Disappeared OS Stations and Resolving Suspect SQL Server Databases in SIMATIC PCS 7

When an Operator Station (OS) disappears completely from the SIMATIC Manager project tree or becomes unopenable in PCS 7 V7.1, the root cause is a corrupted, locked, or 'Suspect' WinCC database attached to the Microsoft SQL Server instance. This state frequently occurs when third-party backup utilities (such as VersionDog) or aborted engineering sessions leave an orphaned copy of the project database attached to the SQL Server with corrupted file headers. SIMATIC Manager detects the conflicting database GUID and hides the OS station to prevent project corruption. To restore the OS station, open SQL Server Management Studio (SSMS), locate and delete the detached or 'Suspect' database from the WinCC SQL instance, restart SIMATIC Manager, and reopen the project.

Executive Summary

In SIMATIC PCS 7 V7.1 engineering environments, automation engineers occasionally encounter a sudden and alarming disappearance: upon launching SIMATIC Manager and opening a known healthy Multiproject, the WinCC Operator Station (OS) container—previously visible under the Component View and Plant View—is completely gone. The project appears reduced to only automation stations (AS) and libraries. Attempts to browse for the OS station or open WinCC Explorer directly fail, and standard diagnostic logs provide no clear error messages. Desperate engineering teams sometimes resort to reinstalling the entire operating system and PCS 7 suite. However, this failure is caused by a specific protective locking mechanism within Microsoft SQL Server. This technical article explains why the OS station vanishes and provides the definitive recovery workflow.

The STEP 7 and WinCC SQL Server Integration Model

SIMATIC PCS 7 links relational engineering data across two software layers:

STEP 7 Database Container: Coordinates hardware configurations, CFC charts, networks, and station pointers in proprietary files.
Microsoft SQL Server (WINCC Instance): Every WinCC project maintains a master configuration database (<ProjectName>.mdf) and runtime database (<ProjectName>R.mdf) attached to the local SQL Server instance named WINCC.
GUID Synchronization: When SIMATIC Manager opens an OS station, it queries the WINCC SQL instance to verify that the project's unique database identifier (GUID) is cleanly mounted and accessible.

Why OS Stations Disappear from SIMATIC Manager: The Protective Hiding Mechanism

The disappearance of the OS station is an intentional protective reaction by SIMATIC Manager:

Database Conflict or Corruption: If SQL Server reports that the WinCC database is in a 'Suspect' mode (e.g. transaction logs desynchronized or file system handles corrupted), or if a duplicate database with identical internal identifiers is attached, the SQL engine flags the database as unavailable.
Defensive Station Hiding: Rather than crashing or allowing an engineer to write corrupt data into a damaged database, SIMATIC Manager silently suppresses the OS PC Station object from the project tree.
Zero Error Notifications: Because the failure occurs at the initial database binding query before project editors open, no warning dialog is presented to the user.

How Third-Party Backup Software (VersionDog) Triggers 'Suspect' Database Locks

A classic engineering scenario triggering this fault involves automated version control software:

Automated Backup Routines: Automated version control systems (such as AUVESY VersionDog or custom backup scripts) attach a temporary copy of the WinCC database to SQL Server to verify archives or create delta snapshots.
Aborted Cleanup: If the backup routine is interrupted, experiences a network timeout, or terminates unexpectedly, it fails to execute the database detach command.
Orphaned Database Remains Attached: An orphaned database copy remains mounted inside SQL Server, often with a gray database icon labeled (Suspect) in SQL Server Management Studio. This lock confuses SIMATIC Manager when it subsequently tries to open the real OS.

Locating and Evaluating Database Status in SQL Server Management Studio (SSMS)

To inspect the SQL Server database state:

In PCS 7 V6.x, the utility was known as SQL Enterprise Manager.
In PCS 7 V7.1 and newer, the tool is SQL Server Management Studio (SSMS).
Connect to server name: .\WINCC (or <ComputerName>\WINCC) using Windows Authentication.
Expand the Databases tree. Healthy WinCC databases display a yellow/orange cylinder icon.
Corrupted or orphaned databases display a gray icon and append text such as (Suspect), (Recovery Pending), or have names appended with temporary backup prefixes.

Step-by-Step Procedure to Safely Purge Suspect Databases and Restore the OS Station

To resolve the fault and restore the disappeared OS station:

Close SIMATIC Manager: Close SIMATIC Manager and all engineering tools completely.
Open SQL Server Management Studio:
* Navigate to Start -> Microsoft SQL Server -> SQL Server Management Studio.
* Connect to Server: .\WINCC, Authentication: Windows Authentication.
Identify and Delete Orphaned / Suspect Databases:
* In Object Explorer, expand Databases.
* Locate the database displaying a gray icon or labeled (Suspect).
* Verify that this is an orphaned backup copy (e.g. created by VersionDog or an aborted backup session).
* Right-click the suspect database and select Delete.
* In the delete dialog, check the box Close existing connections and click OK.
Restart SQL Server Service:
* In Windows Services (services.msc), restart SQL Server (WINCC).
Reopen SIMATIC Manager:
* Launch SIMATIC Manager and open the Multiproject.
* The OS PC Station will immediately reappear in the project tree in full working order.

SQL Server Database Status and OS Recovery Matrix

The following table provides diagnosis and recovery actions for WinCC SQL database states:

Database State in SSMSVisual Icon AppearanceImpact on SIMATIC ManagerVerified Recovery WorkflowNormal / OnlineYellow / Orange CylinderOS Station visible and functionalNo action required(Suspect)Gray Cylinder with warningOS Station completely disappearsDelete suspect database in SSMS; restart SIMATIC Manager(Recovery Pending)Gray CylinderOS Station fails to open (Error dialog)Restart SQL Server (WINCC) service; run reset_wincc.vbsOrphaned Backup DatabaseDuplicate project nameOS Station locked / Read-OnlyDetach/Delete duplicate backup database in SSMSDatabase Missing CompletelyNo database under WINCCOS Station displays broken iconAttach project MDF via WinCC Explorer -> Open Project

Verification

Confirm that the OS station and project database are fully recovered:

Project Tree Visibility Check: In SIMATIC Manager, confirm that the OS PC Station, WinCC Application, and OS project container are visible under Component View and Plant View.
Open WinCC Explorer: Double-click the OS project icon in SIMATIC Manager. Confirm that WinCC Explorer opens cleanly without database connection warnings.
Graphics Designer Access: Open a process graphic (*.pdl). Confirm that all tags, block icons, and dynamic scripts load properly from the active database.
OS Compile Check: Execute Compile OS -> Changes only. Confirm compilation succeeds with 0 database errors.

Preventive Backup and Version Control Guidelines for PCS 7 Projects

To prevent database locking during automated version management:

Configure VersionDog for Native PCS 7 Integration: Ensure third-party backup tools use official Siemens certified integration interfaces rather than brute-force database copying.
Never Copy MDF Files While SQL Server Is Running: Always close SIMATIC Manager and WinCC before executing manual file copies.
Use Standard SIMATIC Archiving: Use File -> Archive... in SIMATIC Manager as the primary backup mechanism, which safely detaches database handles during ZIP compression.

Limitations and Operational Precautions

Never delete the active project database (<ProjectName>.mdf) if it is the only existing copy of your project. If the active database itself enters Suspect mode due to physical hard drive damage, restore the project from the most recent valid SIMATIC archive backup.

Always verify that a valid backup of the project folder is stored on secondary storage before manipulating SQL Server tables directly.

Engineer FAQ

Why does SIMATIC Manager hide the OS instead of displaying an error?

SIMATIC Manager treats a corrupted database as unreadable and hides the container defensively to prevent overwriting or exacerbating database corruption.

Will deleting the suspect database in SSMS delete my project files?

Deleting an orphaned database in SSMS removes the registration pointer inside SQL Server; it does not delete your physical project directory files unless explicitly configured.

Where do I find SQL Server Management Studio in PCS 7 V7.1?

In Windows Start -> All Programs -> Microsoft SQL Server 2005 (or 2008) -> SQL Server Management Studio.

Does this problem occur in newer versions like PCS 7 V9?

Yes, this issue can occur in any PCS 7 release (V7.x, V8.x, V9.x) whenever third-party software leaves an unhandled database lock in SQL Server.

Recovering Disappeared OS Stations and Resolving Suspect SQL Server Databases in SIMATIC PCS 7