Troubleshooting
Why WinCC Runtime Reports Project Is Locked and How to Recover
Short answer
"Project is locked" in WinCC Runtime is an ownership conflict, not a license fault: a live session, or a stale ProjectOpened.lck left behind by a crash or power loss, still claims the project. Close every session that could own it, back it up, then clear the lock with reset_wincc.vbs or by removing ProjectOpened.lck; on a client, open the project by its UNC path.
On this page
WinCC Runtime reports "Project is locked" when the project you selected is already recorded as open by a WinCC session — including a session that died without cleaning up after itself. The lock is a small file, ProjectOpened.lck, written into the project directory when a project opens and removed at orderly shutdown. The fix, in order: if a client selects the project from a server share, open it by the UNC path; otherwise close every session that could own the project, confirm that none does, back the project up, then clear the stale lock with the documented reset script reset_wincc.vbs or by deleting ProjectOpened.lck, and reopen. The message is not a license error and not proof of an integrator lockout; those are separate faults.
What the lock is, and what it is not #
A project lock is an ownership marker. WinCC creates it when a project opens and removes it at orderly shutdown, so that two sessions never write into one project at the same time. "Project is locked" at selection therefore means one of two things: a live session owns the project, or the record of a dead session was never cleaned up. Classify before you act:
- Lock message at project selection: an ownership conflict. Find and close the owning session.
- A
.lckfile in the project directory: a lock artifact is present. Its existence alone does not tell you whether the owner is alive. - A license error at runtime activation: an entitlement fault. It has its own diagnostic path and stops the runtime outright.
- A login or authorization prompt: user administration. Solve it through user rights, not files.
The two documented cases #
Both documented cases come from WinCC Runtime Professional:
- A client selecting a project over a share. The message appears on the WinCC client at project selection, and the documented remedy is to open the project by entering its UNC path — the full
\\server\share\projectform — rather than a mapped drive letter. The working rule that follows: every station that opens the project uses the same path spelling. - A lock left behind by an abnormal end. When WinCC closes unexpectedly — a crash, an abrupt power loss — the cleanup that would remove the lock never runs.
ProjectOpened.lckstays in the project directory, and the next attempt to open the project is refused as locked even though nobody owns it.
Prove that no session still owns the project #
Deleting an active lock does not stop its owner. The other session keeps writing, and you get two writers in one project — the exact condition the lock exists to prevent. Establish zero owners before changing anything:
- On the local PC, close WinCC, then check Task Manager for remaining WinCC processes, and check other signed-in Windows sessions.
- On shared storage, ask every workstation that reaches the project folder, and have the server administrator check open-file handles on the share.
- If any process or handle shows, close it normally and let its shutdown finish before going further.
One safety note belongs here: schedule the recovery inside an approved interruption. While Runtime is down the machine runs blind — the controller keeps executing its logic, but the operator loses visualization and supervisory control.
Recovery, step by step #
- Record the exact project path shown in the message and confirm it is the project you intend — not a backup copy or an alternate location.
- If this station is a client reaching a server share, select the project by UNC path first. If it opens, you are done.
- Close every WinCC session on every station with access to the project. Confirm zero WinCC processes and zero open handles.
- Back up the complete project directory, structure included, and verify the copy before changing anything — the same discipline as when an HMI project fails to open and needs recovery and backup. File count and total size must match the source.
- Run the documented reset: open the Windows Run dialog, enter
reset_wincc.vbs, and restart the computer. - If the message still appears, delete the single file
ProjectOpened.lckfrom the project directory with all sessions still closed. For a closer look at that step, this walk-through of clearing a WinCC project lock by removing the .lck file goes through it in detail. - Reopen the project in Runtime from the recorded path. It should load without the lock message.
Worked example: power loss at 06:18 #
Illustrative example with realistic values; your timestamps and file counts will differ.
A site power event kills the Runtime PC at 06:18. At 06:31 the operator re-selects the project and gets "Project is locked".
- Windows event log: unexpected shutdown at 06:18.
ProjectOpened.lckmodified time: 06:18 — the same minute as the shutdown, and 06:31 - 06:18 = 13 minutes before your check, with nothing started in that window.- Task Manager: 0 WinCC processes. Open-file handles on the share for the project path: 0.
A lock timestamp equal to the shutdown minute, plus zero processes and zero handles, adds up to a stale lock. Back up: the project folder holds 2.1 GB in 14,362 files; the verified copy reports 2.1 GB and 14,362 files — a difference of 0 files and 0.0 GB. Run reset_wincc.vbs, restart, reopen: the project loads. Had any of the three checks shown a live owner, the correct move would have been to close that session, not to delete the file.
When it is not only the lock message #
A lock message is not evidence of a licensing problem. Licensing faults announce themselves when the runtime activates and stop the runtime; that path is its own investigation, as in why WinCC 8.0 runtime deactivates after a V7.5 migration. If the installation came from an unverified download, the legitimate route is authorized media and entitlement through Siemens or an authorized distributor; a lock-file edit has no effect on licensing.
Nor is the message proof that an integrator locked you out. It is a file-level ownership artifact, not a permission setting. If you need change rights on a commissioned system, request them from the project owner.
When the lock keeps coming back #
- It returns on a client: standardize the path. Every station opens the project by the same UNC path; mixing mapped-drive and UNC selection is the documented client-side trigger.
- It returns after every crash or power loss: the marker is behaving as designed. Fix the abnormal-shutdown cause — power quality, failing hardware, operating-system crashes — and the stale locks stop.
- Two engineering stations edit one shared project folder: keep one editor at a time. The lock exists precisely to stop concurrent editing.
Verify the recovery #
Open the project, close it normally, then open it again. A second open that needs no manual lock removal proves the create-and-remove cycle works again. Spot-check representative screens and configured connections against the backup. If screens load but values are stale or flagged bad, that is a connection fault, not a lock — diagnose the communications separately.
Questions asked
Does "Project is locked" mean my WinCC license is missing?
No. Licensing faults appear when the runtime activates, carry their own messages, and stop the runtime outright rather than refusing one selected project. The lock message appears at project selection and points at ownership. If you also see a license error, resolve it through authorized licensing channels; lock files have no effect on entitlement.
Can I delete the .lck file as soon as I see the error?
Not straight away, and not while any session might still own the project. Deleting an active lock does not stop its owner, so a second writer can begin conflicting writes into project data. If you cannot fully rule out an owner, rename or move ProjectOpened.lck to a temporary folder instead of deleting it, so the file can be restored if the behavior changes.
What does reset_wincc.vbs do?
It is the reset script supplied for WinCC: it clears the state an abnormal end leaves behind so the next start begins clean. Run it with WinCC closed, from the Windows Run dialog, and restart the computer afterward, as the documented procedure specifies.
Did our integrator lock us out of the project?
Not on the strength of this message alone. The lock is a file-level ownership artifact, not a permission setting; restrictions on what you may change come from user administration and show up as authorization prompts instead.