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

Adapting WinCC Computer Name After Project Retrieval on New SIMATIC IPC Stations in PCS 7

Adapting WinCC Computer Name After Project Retrieval on New SIMATIC IPC Stations in PCS 7

When a SIMATIC PCS 7 project is retrieved from an engineering backup onto a newly commissioned SIMATIC IPC with a different Windows computer name, WinCC Explorer will fail to activate and trigger the error 'The configured server is not available' because the project remains bound to the original computer name. To adapt the retrieved project to the new IPC: 1. Open WinCC Explorer on the IPC; 2. In the navigation tree, click 'Computer', right-click the old computer name in the right pane, and select 'Properties'; 3. In the Computer Properties dialog, click 'Use Local Computer Name'; 4. Click OK, close WinCC Explorer, and restart the IPC. In SIMATIC Manager on the ES, also update the target computer name in the PC Station properties.

Table of Contents

Executive Summary

Migrating or deploying a SIMATIC PCS 7 operator station project from a development laptop or staging environment to the final production hardware—typically a Siemens SIMATIC IPC running Windows 10 Enterprise or Windows Server—is a standard step in plant commissioning. However, because production IPCs almost always possess distinct hostnames (e.g. OS_SRV_01 vs DEV_LAPTOP), opening the retrieved WinCC project on the target machine produces immediate startup errors: 'The configured server is not available' or a persistent prompt attempting to establish remote connections to the missing development PC. This article provides the exact procedure to adapt the WinCC project header to the local computer name, synchronize station names in SIMATIC Manager, and align the Station Configuration Editor.

Architecture and Fundamental Mechanics

WinCC Project Architecture, Computer Name Binding, and Station Configuration Editor Mechanics:

  • Internal Computer Name Resolution in WinCC:
  • Inside a WinCC project database (<Project>.mcp and SQL database CC_..._M), the project stores the unique NetBIOS computer name of the station authorized to host and activate the runtime database.
  • When WinCC Explorer initializes, it queries the local Windows operating system for its computer name (%COMPUTERNAME%) and compares it against the registered hostname in the project properties table.

  • If the two names do not match, WinCC assumes the user is running an OS Multi-Client or remote engineering console attempting to access a distributed server. It attempts to connect to the remote development computer across the network, generating the familiar alarm: 'The configured server is not available'.

  • The Role of 'Use Local Computer Name':

  • Within the WinCC Computer Properties dialog, clicking the button 'Use Local Computer Name' updates the internal SQL project record, replacing the legacy development hostname with the active Windows hostname of the physical IPC.

  • This change reconfigures internal local DCOM bindings, SQL connection strings, and runtime startup processes (CCProjectMgr.exe).

  • Architectural Distinction: Renaming a Windows PC vs Adapting Project Settings:

  • Renaming an already-installed PCS 7 computer in Windows is a complex procedure requiring software reinstallation or re-registration of Microsoft SQL Server and WinCC system components.

  • In contrast, adapting a retrieved project to match an already-named IPC is a standard, lightweight operation taking under two minutes.

  • Alignment with SIMATIC Manager and Station Configuration Editor:

  • For distributed engineering integrity, the PC Station object name in SIMATIC Manager on the ES must also match the physical IPC name, and the Station Configuration Editor (SCE) on the IPC must host identical virtual component rack assignments.

Step-by-Step Implementation Procedure

  1. Adapt the Computer Name in WinCC Explorer:
    * On the target SIMATIC IPC, launch WinCC Explorer and open the retrieved project (.mcp file).
    * In the left navigation pane of WinCC Explorer, click on Computer.
    * In the right data window, observe the computer name listed (this will be the old development PC name).
    * Right-click the old computer name and select Properties (or double-click it).
    * In the Computer Properties dialog, click the button Use Local Computer Name.
    * Verify that the 'Computer Name' field immediately updates to match the local IPC's Windows hostname.
    * Click OK to commit the change.
    * A prompt appears stating that the project must be restarted; close WinCC Explorer completely.

  2. Restart WinCC Explorer and Verify Database Re-attachment:
    * Re-open WinCC Explorer on the IPC.
    * Confirm that the project opens immediately without the 'configured server is not available' prompt.

  3. Update the Target Computer Name in SIMATIC Manager (ES Alignment):
    * On the Engineering Station, open the project in SIMATIC Manager.
    * Switch to Component View.
    * Right-click the PC Station representing the IPC -> Properties.
    * Ensure the Name matches the physical IPC name, or set the Target Computer Name field to match the IPC hostname.
    * Recompile the OS and download the target station.

  4. Verify Station Configuration Editor on the IPC:
    * On the IPC, open the Station Configuration Editor (tray icon with station rack).
    * Ensure the Station Name displayed at the top matches the IPC Windows computer name.
    * Confirm that the WinCC Application and communication processors are assigned to their matching virtual slots.

Verification

  1. In WinCC Explorer on the IPC, verify that the Computer list shows only the active IPC hostname.
  2. Click the Activate icon in WinCC Explorer toolbar; verify that WinCC Runtime starts cleanly.
  3. Confirm that all graphics, alarms, and trend windows open without communication server warnings.
  4. Execute an OS Delta Download from the central ES to confirm bidirectional engineering synchronization.

Limitations and Operational Precautions

The 'Use Local Computer Name' function applies strictly to Single Station and OS Server master projects; on dedicated OS Client stations, the client project references server data packages (.pck) which must be regenerated on the server and reloaded on the client if server hostnames change. Never alter the Windows computer name while WinCC Runtime is active.

Engineer FAQ

Why does WinCC say 'The configured server is not available' after retrieving a project?

Because the project database still references the development computer's hostname instead of the new physical IPC hostname.

What does the 'Use Local Computer Name' button do in WinCC?

It updates the internal WinCC SQL database tables to bind the project to the current Windows hostname of the local computer.

Do I have to reinstall WinCC when moving a project to a new PC?

No. WinCC software is installed independently; moving a project only requires adapting the computer name within the project.

What must be done in SIMATIC Manager when the IPC name differs?

Update the PC Station properties so the 'Target Computer Name' matches the physical IPC name before downloading.

What is the Station Configuration Editor?

It is a Siemens utility running on IPCs that maps virtual slots to communication processors and WinCC runtime applications.

Technical References

Related Articles

Related Tags

  • Computer Name
  • WinCC Explorer
  • SIMATIC IPC
  • Use Local Computer Name
  • Project Retrieval
  • Station Configuration Editor
  • PCS 7 V9.0
20 respuestas