How to Resolve 'The Configured Server Is Not Available' and OS Project Load Failures in SIMATIC PCS 7

In SIMATIC PCS 7 V7.1 SP3, the error 'The configured server is not available. Do you want to open the project using local computer as the server' occurs when an Operator Station (OS) project is downloaded from an Engineering Station (ES) but the WinCC project file retains the ES computer name or when network path mapping fails. This typically happens when the ES station lacks a local WinCC Application in HW Config, forcing improper target path synchronization, or when local Windows computer names do not match the assigned PC Station names in SIMATIC Manager. To resolve this, verify matching PC Station names, check the OS Target Path in SIMATIC Manager, and execute the WinCC Project Duplicator or reset project server assignment.

Architecture of PC Station Names and WinCC Computer Properties

In SIMATIC PCS 7, multi-station engineering relies on strict naming synchronization across three distinct layers:
1. Windows Computer Name: The host machine name configured in Windows System Properties (e.g., SERVER1, SERVER2, ES-PC).
2. SIMATIC Manager PC Station Name: The container object in the multi-project tree (e.g., SIMATIC PC Station (SERVER1)).
3. WinCC Computer Configuration: The internal node name recorded in the WinCC project database (<ProjectName>.mcp / CCProjectMgr.exe).

When an engineer opens or downloads an OS project, WinCC reads the computer name stored in the database. If this internal name does not match the local Windows hostname of the computer executing the runtime, WinCC warns that the configured server is unavailable and asks whether to convert the project to local server mode.

Root Causes of 'Configured Server Is Not Available'

Forensic investigation of PCS 7 V7.1 SP3 sugar plant and chemical installations identifies three root triggers:
* Opening Runtime Directly from ES Network Share: Engineers sometimes open the shared folder on Server 1 directly from the ES instead of executing a formal PLC > Download. WinCC detects that the host machine opening the .mcp file is ES-PC, not SERVER1.
* Missing WinCC Application on ES PC Station: If the ES PC Station in SIMATIC Manager is configured without a WinCC Appl. or WinCC Appl. (stby) reference, the AS-OS compiler cannot determine the server assignment correctly.
* Corrupted Project Configuration Cache: If Server 1 crashed or an OS download was aborted mid-stream, the internal database table CC_Computer retains a stale GUID or locked flag, causing WinCC to reject incoming runtime activation requests.

Configuring Target Directory Paths in SIMATIC Manager

To ensure proper file synchronization during OS download from the ES:

Configure Target OS Path in SIMATIC Manager:
* In the component view, right-click the OS Server object: select Object Properties.
* Open the Target OS and Standby OS Computer tab.
* Path to the target OS: Click Browse... and navigate across the network neighborhood to the shared project folder on the target server (e.g., \\SERVER1\WinCC_Project\).
* Standby OS Path: Navigate to the redundant partner share (e.g., \\SERVER2\WinCC_Project\).
Verify Network Share Permissions:
* On Server 1 and Server 2, ensure the destination directory is shared with full read/write permissions for the SIMATIC HMI user group and local Administrator account.
Perform OS Download:
* Right-click the OS object: PLC > Download.
* For the initial deployment, select Entire WinCC Project to overwrite stale configuration files.

Step-by-Step Server Assignment Repair and reset_wincc.vbs

If the project on Server 1 is stuck reporting the error, follow this repair sequence:

Terminate Active WinCC Processes:
* On Server 1, execute reset_wincc.vbs from Start > Run.
* Confirm in Task Manager that CCApp.exe, pdlrt.exe, and s7oemax.exe terminate.
Correct Computer Name Inside WinCC Explorer:
* Launch WinCC Explorer on Server 1.
* If prompted with 'The configured server is not available. Do you want to open the project using local computer as the server?', click Yes (or open the project).
* In the left project navigation tree, click Computer.
* In the right pane, select the computer name: right-click and choose Properties.
* Click the button: Use Local Computer Name.
* WinCC replaces the old hostname with the exact Windows computer name of Server 1.
Close and Reopen Project:
* Close WinCC Explorer. Wait 15 seconds.
* Relaunch WinCC Explorer: the project will open cleanly without any server availability warnings.

Comparison of Common OS Download Errors and Remedies

The table below outlines common OS download and startup failures in distributed PCS 7 systems.

Error Message / SymptomRoot CauseImmediate Diagnostic StepResolution Action'Configured server not available'Mismatched computer name in MCPCheck Computer > Properties in WinCCClick 'Use Local Computer Name''Database context does not exist'SQL database detached or lockedRun reset_wincc.vbsDetach DB via WinCC Project Scanner'Target path invalid'Windows share unreachable or offlinePing target server hostnameRe-enter UNC network share path'Cannot load changes - license error'Insufficient WinCC RT POs in ALMOpen ALM on target serverInstall required WinCC RT PO license'WinCC project locked by user'Orphaned .lck files after crashCheck project directoryDelete *.lck and *.tmp files

Verification

To confirm that the server assignment and OS download are fully operational:
1. On Server 1, open WinCC Explorer: verify that the title bar displays [SERVER1 - <ProjectName>] without any local conversion prompt.
2. Under Computer Properties, verify that the computer name matches SERVER1 and the startup list includes Graphics Runtime, Alarm Logging Runtime, and Tag Logging Runtime.
3. Activate WinCC Runtime on Server 1: confirm that runtime activates to 100% and displays the plant process overview graphics.
4. On the ES, make a minor test tag comment change in CFC, compile OS (Changes Only), and execute PLC > Download > Changes.
5. Confirm that the delta download applies to Server 1 seamlessly while runtime remains active.

Limitations and Operational Precautions

Never rename a Windows computer after PCS 7 and WinCC software packages have been installed; changing a computer name breaks SQL Server instance bindings and requires reinstalling Microsoft SQL Server.
Do not click 'Open using local computer as server' on a live production Standby server without re-synchronizing redundant project configurations, as this can sever redundant partner tracking.
Always ensure that all engineering and server nodes operate within the same workgroup or domain with identical user accounts and passwords.
Verify final hardware configurations, IPC industrial models, and software licenses against the applicable Siemens catalog and authorized distributor quotation.

Engineer FAQ

Why did this error appear after downloading a new motor block?

Adding the motor block required an OS compile and download. If the OS was downloaded with an incorrect target path or while a background process locked the MCP database, WinCC could not update the server assignment.

What does clicking 'Yes' to use local computer actually do?

It updates the internal WinCC database tables (CC_Computer), overwriting the recorded server name with the hostname of the computer where WinCC Explorer is currently running.