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

How to Restore Disappeared WinCC OS Applications in SIMATIC Manager Due to SQL Suspect Databases

How to Restore Disappeared WinCC OS Applications in SIMATIC Manager Due to SQL Suspect Databases

In SIMATIC PCS 7 (including legacy versions such as V6.0 SP1 up to modern releases), the sudden disappearance of all WinCC OS applications from the SIMATIC Manager project tree occurs when Microsoft SQL Server flags an attached project database as 'Suspect'. This corruption is commonly triggered by third-party automated backup utilities (such as VersionDoc), antivirus file locking, or unexpected power losses that leave temporary database files (.mdf/.ldf) detached or locked. To restore the vanished OS stations, stop the SQL Server instance, delete orphaned or suspect temporary databases using SQL Server Management Studio or system commands, and restart SIMATIC Manager.

Table of Contents

SIMATIC Manager Integration with Microsoft SQL Server

In SIMATIC PCS 7 architectures, SIMATIC Manager acts as an engineering umbrella that integrates controller logic (Step 7) and supervisory visualization (WinCC).

When an engineer expands an Engineering Station or OS Server object in the Component View or Plant View, SIMATIC Manager does not simply parse flat text files; it dynamically communicates with the local Microsoft SQL Server instance (e.g., MSDE 2000 in PCS 7 V6.x, SQL Server 2005 in V7.x, SQL Server 2008/2014 in V8.x/V9.x).

SQL Server attaches the project database files:
* Master Project Configuration Database: <ProjectName>.mdf and <ProjectName>.ldf
* Project Catalog and Tag Management Tables
* Cross-Reference and Alarm Logging Databases

If SQL Server can successfully attach and validate these databases, SIMATIC Manager renders the WinCC OS application icon and its associated Graphics, Tag Management, and Alarm Logging objects in the project tree.

Root Cause Analysis for Disappearing OS Applications

Engineers occasionally open SIMATIC Manager only to find that all WinCC OS stations have completely vanished from the project tree. The Step 7 hardware configurations and CFC charts remain visible, but every WinCC object is absent.

The 'Suspect' Database Mechanism

When Microsoft SQL Server encounters an I/O failure, an ungraceful system crash during an active database write, or file locking from an external process, it marks the affected database state as 'SUSPECT'.

Common catalysts for this failure include:
1. Automated Backup Utilities (e.g., VersionDoc): Version control and daily backup software often create transient shadow databases in SQL Server. If the backup tool terminates unexpectedly without detaching its temporary database, the orphaned database enters Suspect mode.
2. Antivirus File Locking: Non-whitelisted antivirus software scanning .mdf or .ldf files locks write access during project saves.
3. Defensive Safe Mode in SIMATIC Manager: If SIMATIC Manager queries the SQL Server instance and detects any attached database flagged as 'Suspect'—even an orphaned temporary database completely unrelated to the active project—it enters a defensive fallback mode and suppresses the display of all WinCC applications to prevent cascading corruption.

Step-by-Step Recovery Procedure for Suspect Databases

To resolve the SQL corruption and restore the missing OS applications, follow this recovery procedure:

Step 1: Terminate SIMATIC Manager and WinCC Processes

  1. Close SIMATIC Manager.
  2. In Windows Task Manager, ensure that CCProjectMgr.exe, s7tgtopx.exe, and WinCC background editors are terminated.

Step 2: Open SQL Server Management Utility

Depending on the PCS 7 version:
* In modern PCS 7 (V7.x, V8.x, V9.x): Open SQL Server Management Studio (SSMS) and connect to the local instance (e.g., .\WINCC).
* In legacy PCS 7 V6.x (Windows 2000 / XP): Use SQL Server Enterprise Manager or launch command prompt to use osql / sqlcmd.

Step 3: Identify and Delete the Suspect Database

  1. In SSMS or Enterprise Manager, expand the Databases tree.
  2. Look for any database marked with a grey icon or bearing the status label (Suspect).
  3. If an orphaned temporary database (e.g., created by VersionDoc or an old aborted copy) is marked Suspect:
    * Right-click the suspect database and select Delete.
    * Check 'Close existing connections' and click OK.
  4. If a command line interface is required:
    sql EXEC sp_detach_db 'Suspect_Database_Name';

Step 4: Repairing an Active Project Database Marked Suspect

If the actual project database itself is marked Suspect:
1. Run emergency reset commands in SQL query window:
sql ALTER DATABASE [Project_DB_Name] SET EMERGENCY; ALTER DATABASE [Project_DB_Name] SET SINGLE_USER; DBCC CHECKDB ([Project_DB_Name], REPAIR_ALLOW_DATA_LOSS); ALTER DATABASE [Project_DB_Name] SET MULTI_USER;
2. Alternatively, if a clean recent project backup (.zip / .arj via SIMATIC Manager Archive) is available, restoring the project from archive is safer than forcing data loss repairs.

Step 5: Restart SQL Services and SIMATIC Manager

  1. In Windows Administrative Tools -> Services, restart the SQL Server (WINCC) service.
  2. Open Windows Explorer and navigate to the project directory; delete any orphaned <ProjectName>.dcf file.
  3. Relaunch SIMATIC Manager; the WinCC OS applications will reappear in the project tree.

SQL Server Health and Recovery Commands Reference

The following table outlines diagnostic states and corrective SQL commands used when troubleshooting PCS 7 WinCC database issues:

Database State in SQLVisual IndicatorMeaning / CauseRecommended Recovery ActionONLINEYellow / Normal iconDatabase healthy and accessibleNone (Normal operation)SUSPECTGrey icon / (Suspect)Corrupted transaction log or locked fileDetach orphaned DB or run emergency repairRECOVERY PENDINGGrey icon / Status labelSQL Server waiting for resources to openRestart SQL service; verify disk spaceOrphaned Backup DBNamed with timestampLeftover database from VersionDoc backupExecute sp_detach_db or delete in SSMSMissing .dcf fileNot applicableTransient project connection cacheHarmless; WinCC auto-regenerates on open

Maintaining a clean SQL instance prevents SIMATIC Manager from hiding supervisory components.

Verification

To verify that the WinCC OS applications have been successfully restored:
1. Launch SIMATIC Manager and open the multiproject.
2. In Component View, expand the Engineering Station and OS Server PC Stations.
3. Confirm that the WinCC Application and OS project icons appear with their normal yellow/blue graphics.
4. Right-click the OS project and select Open Object; verify that WinCC Explorer launches smoothly with all Tag Management, Graphics, and Alarm Logging editors populated.
5. In SQL Server Management Studio, expand Databases; confirm that all attached databases report (Online) with zero suspect markers.

Limitations and Operational Precautions

  • Never use DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS without first taking a physical copy of the .mdf and .ldf files.
  • Ensure automated backup tools (such as VersionDoc) are fully certified for the exact version of PCS 7 and SQL Server in use.
  • Configure antivirus exclusions strictly according to Siemens guidelines: exclude all .mdf, .ldf, .dcf, and project directories from real-time on-access scanning.
  • Do not manually rename .mdf or .ldf files while SQL Server services are running.

Engineer FAQ

Why did SIMATIC Manager hide all OS stations when only one database was suspect?

SIMATIC Manager performs an integrity check across the entire SQL instance on startup. If any database is flagged as corrupt or suspect, it enters a protective safe mode to prevent cross-project corruption, hiding all WinCC objects.

Can I reinstall SQL Server without reinstalling PCS 7?

Yes, but reinstalling SQL Server requires specific Siemens instance names (WINCC) and collation settings (Latin1_General_CI_AS). Running the WinCC installation setup in 'Repair' mode is the recommended method to rebuild SQL Server.

What is the role of VersionDoc in this failure?

VersionDoc creates daily automated archives by attaching project databases to SQL Server, creating a snapshot, and detaching them. If the workstation shuts down mid-backup, the detached snapshot is left in SQL Server in Suspect mode.

Technical References

Related Articles

Related Tags

  • SIMATIC_Manager
  • SQL_Server
  • Suspect_Database
  • WinCC_Disappeared
  • PCS7_V6_0
6 respuestas