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

How to Resolve 'Action Not Possible: Project Opened on Another PC' During PCS 7 OS Compilation

How to Resolve 'Action Not Possible: Project Opened on Another PC' During PCS 7 OS Compilation

To resolve the SIMATIC PCS 7 error 'Action not possible as the project is opened on another PC' during OS compilation on the Engineering Station, engineers must clear residual Microsoft SQL Server database locks and reorganize the multi-project. In multi-user engineering environments, SIMATIC Manager places concurrency locks in the OS project's SQL Server instance. If a secondary workstation closes abnormally while viewing or editing the OS, the SQL lock table retains the remote computer's ownership flag. The resolution requires ensuring the remote workstation has closed the project, stopping and restarting the SQL Server (WINCC) service on both the client and Engineering Station, running CCCleaner.exe, and performing File -> Save As... with reorganization (slow) in SIMATIC Manager.

Table of Contents

Concurrency Architecture in Multi-User PCS 7 Engineering

In large SIMATIC PCS 7 implementations, multi-user engineering allows multiple automation engineers on separate workstations to access a centrally hosted multiproject across the engineering network.

To prevent concurrent write conflicts:
1. When an engineer opens an AS chart, SIMATIC Manager places an object lock on that specific chart folder.
2. When an engineer opens a WinCC OS project or browses WinCC Tag Management, the master Engineering Station mounts the OS project database (.mdf/.ldf) via the local Microsoft SQL Server instance (MSSQL$WINCC).
3. An internal ownership record containing the remote machine's NetBIOS name (e.g., AAEIN...) is registered in the project's lock tables.
4. Compiling the OS requires exclusive, unshared write access to the WinCC database. If any workstation holds an active or orphaned lock, the compiler halts immediately.

Root Causes Behind the 'Project Opened on Another PC' Lock

When SIMATIC Manager aborts OS compilation with 'Action not possible as the project is opened on another PC', the failure typically stems from:

  1. Abnormal Client Disconnection: A secondary engineering workstation had the OS project or a related CFC chart open when it suffered a network drop, Windows crash, or hard power shutdown without executing a clean project close.
  2. Lingering Background SQL Connections: The secondary workstation closed SIMATIC Manager, but background WinCC processes (CCProjectMgr.exe, CCClientRT.exe) remained active in memory, maintaining an active network socket to the SQL Server instance.
  3. Database Transaction Log Inconsistency: The project's SQL transaction log (.ldf) has uncommitted lock transactions that were not rolled back.
  4. PC Station Name Mismatch: The PC station in the project tree is misidentified or has conflicting network routing bindings.

Step-by-Step Recovery Procedure: Clearing SQL Locks and CCCleaner

Follow this comprehensive procedure to clear orphaned locks and re-enable OS compilation:

Step 1: Clean Up the Secondary Workstation (Reported in Error Dialog)

  1. Navigate to the specific computer identified in the error message (e.g., AAEIN...).
  2. Close all instances of SIMATIC Manager, STEP 7, and WinCC.
  3. Open an administrative Command Prompt and run CCCleaner.exe:
    cmd "C:\Program Files (x86)\Siemens\WinCCin\CCCleaner.exe"
  4. Open SQL Server Configuration Manager, select SQL Server Services, right-click SQL Server (WINCC), and select Restart.

Step 2: Clear Locks on the Master Engineering Station

  1. On the master Engineering Station hosting the multiproject, close SIMATIC Manager.
  2. Run CCCleaner.exe to terminate any residual WinCC background engines.
  3. In SQL Server Configuration Manager, restart the SQL Server (WINCC) service.
  4. If file locks persist, restart the Engineering Station workstation.

Database Reorganization via 'Save As... with Reorganization'

If clearing processes and restarting SQL Server does not clear the ownership lock, the project database contains orphaned registry pointers. Executing a reorganization purges these records:

  1. Open SIMATIC Manager as Administrator.
  2. Open the affected Multiproject.
  3. In the menu bar, navigate to File -> Save As....
  4. In the Save As dialog:
    * Select a new target folder or disk drive.
    * Check the box: 'With reorganization (slow)'.
  5. Click OK.
  6. SIMATIC Manager will perform a block-by-block database reorganization:
    * It deletes all fragmented gaps, temporary lock flags, and orphaned user registrations.
    * It rebuilds internal SQL Server indices and re-verifies cross-project references.
  7. Once reorganization finishes, open the newly saved project.
  8. Right-click the OS project -> Compile OS. Compilation will now proceed without encountering the concurrency error.

OS Compilation Lock Symptoms and Remediation Matrix

The following table outlines the compilation lock symptoms, diagnostic checkpoints, and verified fixes:

Failure SymptomResponsible ComponentDiagnostic ToolCorrective Action'Project opened on another PC'Orphaned remote SQL lockError dialog workstation IDRun CCCleaner.exe on remote PC; restart SQL'SQL Server database locked'Local process holding handleWindows Resource MonitorRestart SQL Server (WINCC) service on ESPersistent lock after PC rebootOrphaned record in project DBSIMATIC Manager File menuPerform 'Save As... with reorganization (slow)'Yellow arrow missing on PC StationNetwork computer name mismatchObject Properties in ManagerAlign PC station name with physical hostnameCompile aborts at Tag ManagementCorrupted <Project>.dcf fileOS project root directoryDelete <Project>.dcf and re-open OS project

Disciplined multi-user exit procedures prevent concurrency lockouts during critical engineering milestones.

Verification

To verify that the OS compilation lock is resolved:
1. In SIMATIC Manager on the Engineering Station, select the target OS project.
2. Right-click the OS -> Compile.
3. Select the target AS controllers, define network connections, and click Next -> Compile.
4. Verify that the compilation progress bar advances past the initial SQL connection phase without displaying concurrency error popups.
5. Confirm that the compile finishes with the status message: 'Compilation completed: 0 Errors, 0 Warnings'.

Limitations and Operational Precautions

  • Always coordinate with all engineering personnel before restarting SQL Server services or performing project reorganizations.
  • Never attempt to manually edit or delete SQL Server lock tables using third-party database tools.
  • 'Save As... with reorganization (slow)' can take between 15 and 45 minutes on large multiprojects; ensure uninterruptible power supply (UPS) during the operation.
  • When working in multi-user engineering, ensure all team members close their subprojects before major system-wide compilations.

Engineer FAQ

Why does the error report the project is open when the remote PC is shut down?

SIMATIC Manager writes the remote PC name into the project's SQL database lock table when opened. If the PC shuts down without a clean project exit, the database retains that lock record until explicitly reorganized or cleared.

What does 'Save As... with reorganization (slow)' actually do?

It copies the project file-by-file into a clean directory, discarding temporary edit logs, orphaned lock flags, and deleted block fragments while compacting SQL database structures.

Can multiple engineers compile different OS projects in the same multiproject simultaneously?

Yes, provided each OS project resides on a separate PC station object and does not share locked AS symbol tables during the compilation phase.

Technical References

Related Articles

Related Tags

  • OS Compilation
  • Multi-User Engineering
  • Project Locked
  • CCCleaner
  • Save As Reorganization
6 respuestas