Troubleshoot the WinCC “Computer Is in the Client List” Project Error

The message “The project could not be opened, this computer is in the client list project. Please Open the project on the server first” indicates a WinCC project/server-client relationship that must be checked before changing files. Confirm which computer and project are involved, and whether the client-list entry is intentional. The discussion does not verify that deleting the entry or recreating the project folder fixes the problem; its later database-context error needs separate diagnosis.

Interpret the client-list message before changing files

The message “The project could not be opened, this computer is in the client list project. Please Open the project on the server first” points to a WinCC project/client relationship: the computer being used is associated with a project as a client, so the project operation expects its server-side project to be opened on the server. It does not establish that the transferred project folder is corrupt. In a PCS 7 engineering workflow, a server project may also maintain a client computer list for remote access or configuration, so first identify the exact project object and computer named in the message.

The ticket reports that the project files are present on the OS server and can be opened there, but it does not include the screenshot, WinCC project computer list, the server/client topology, or the exact download dialog. A forum reply suggests deleting an entry, after which a different database-context error appeared. That sequence does not prove deletion was the correct fix.

Check the project role and computer list

Preserve a complete backup of the PCS 7 multiproject and the WinCC projects on the ES and both OS servers. Do not delete or recreate the target project directory as a first diagnostic step.
Record the exact computer name in the error and identify which project is open on that computer. In WinCC, distinguish the project server from client computers registered in its computer list.
Check whether the target OS computer is intentionally configured as a WinCC client for remote configuration, or whether the project is being opened on a workstation that is listed as a client. The WinCC configuration manual describes registering clients in the server project's computer list for remote access/configuration.
On the server, open the correct server project as required by the documented server/client workflow, then perform the intended PCS 7 ES-to-OS download from the Engineering Station. Avoid opening or editing the same project concurrently from multiple computers.
If the computer-list entry is demonstrably stale or incorrect, change it only using the matching WinCC version's documented procedure and after confirming the target's role. Recompile or transfer the project using the PCS 7 workflow and review the OS load log.
If the error changes to “Database context does not exist or is invalid,” treat it as a separate diagnostic. Capture the full message and inspect the WinCC/PCS 7 load log and project/database association; the ticket does not show that deleting folders or creating a new share resolves it.

Use the right procedure for remote client configuration

WinCC distinguishes configuring the project on its server from client access. The WinCC 2017 configuration manual states that a client intended to access or remotely configure a server project must be registered in the server's computer list. That registration is not by itself proof of a fault; deleting a legitimate client can remove an intended access relationship.

The cited manual covers WinCC client/server project configuration, while PCS 7 V9.1 has its own ES-to-OS engineering and download process. Follow the release-matched PCS 7 Operator Station/Engineering System procedure for the download, and use WinCC computer-list instructions only to verify that the server and remote clients have the intended roles. Do not conflate server packages for PCS 7 OS clients with WinCC's remote-configuration client list.

Verification

After correcting a confirmed role or computer-list mismatch, reopen the intended server project and repeat the download through the documented ES-to-OS workflow. Confirm the target OS, project path, and load-log status. Verify that both redundant OS servers retain the intended project and that their client/remote-access entries remain correct. If the separate database-context error persists, preserve it with its full logs and investigate the project/database context rather than assuming the first error was solved.

Limitations and Operational Precautions

The source omits the screenshot, exact PCS 7 and WinCC update levels, project computer list, target and client names, download mode, and full load log. The underlying cause cannot be established. The reported follow-on database-context message and the suggested folder deletion/recreation are not documented as a verified solution in this evidence.

Deleting a project folder, changing shares, or removing a computer entry can disrupt project access, database associations, or redundant OS configuration. Back up before changes, confirm which project is authoritative, and coordinate any OS download or configuration change with operations.

Engineer FAQ

What does “this computer is in the client list project” mean? It indicates that the computer is associated with a WinCC project as a client, but the ticket lacks the project list and screenshot needed to identify which computer or project relationship triggered it.

Should I delete the computer from the client list? Only if you verify that the entry is stale or incorrect for the intended topology and follow the matching WinCC procedure. A legitimate client registration may be required for remote access.

Does seeing the project files on the server prove the project is correctly associated? No. File presence does not confirm that the intended server project is open or that the project/database context and target path are correct.

Does the next database-context error prove folder deletion was required? No. The thread does not establish a causal relationship or a verified fix for that second error.

What logs help distinguish the problem? Capture the full ES-to-OS load log, the complete message, project/server/client computer names, and the WinCC/PCS 7 versions and update levels.

Technical References

Siemens, WinCC: Configurations, System Manual, 02/2017, section 1.6.3, “How to Register Clients in the Computer List.” It describes registering client computers in a server project's computer list and the project server/client configuration: PDF.
Siemens, WinCC: Configurations and Communication, System Manual, 09/2018, section 1.6. It states that server projects are configured before associated clients and that remote-configuration clients are registered in the server's computer list: PDF.
Siemens, SIMATIC PCS 7 Operator Station V9.1 SP1 Configuration Manual, sections 6.1 and 6.4, for OS project types and OS configuration: PDF.

Troubleshoot the WinCC “Computer Is in the Client List” Project Error