Resolving WinCC Runtime Hanging at 'Initializing Archive Management' After Computer Rename

In SIMATIC PCS 7 and WinCC, changing the Windows computer name after software installation corrupts Microsoft SQL Server instance metadata and Windows security group bindings, causing WinCC Runtime to hang indefinitely at 'Initializing Archive Management' (CCArchiveManager.exe). Resolve this by restoring the original computer name, or by re-aligning SQL Server server names via Transact-SQL, rebuilding security groups using Siemens Security Controller, and updating the WinCC computer name.

Root Cause Analysis: Why Renaming Windows Breaks WinCC

In industrial IT maintenance, an engineer operating a combined Engineering Station (ES) and Operator Station (OS) in SIMATIC PCS 7 V8.0 SP2 may attempt to re-purpose the machine as a dedicated redundant server by modifying the Windows computer name (for example, renaming the PC from ES to SERVER1 in Windows System Properties).

Upon restarting Windows and activating WinCC Runtime, the startup sequence freezes:
* The WinCC startup progress dialog displays: Initializing Archive Management....
* The progress bar halts permanently.
* In Windows Task Manager, the process CCArchiveManager.exe consumes 0% to 5% CPU in a persistent deadlock state.
* If an engineer manually terminates CCArchiveManager.exe via Task Manager, WinCC Runtime abruptly resumes and opens graphics, but historical tag logging and alarm archiving fail to function.
* Reinstalling PCS 7 over the existing operating system does not resolve the freeze.

This failure occurs because renaming a Windows PC after installing SIMATIC PCS 7 breaks Microsoft SQL Server and Windows Security Group architectures:
1. SQL Server Instance Name Discrepancy: During setup, Microsoft SQL Server creates instances linked to the initial machine name (OLD_NAME\WINCC). Renaming Windows changes the OS name, but SQL Server internal system catalog tables (sys.servers) retain the old name.
2. Windows Security Identifiers (SIDs): Siemens creates local Windows security groups containing the old computer name (e.g. SQLServer2008MSSQLUser$OLD_NAME$WINCC, SIMATIC HMI). CCArchiveManager.exe attempts to connect to SQL archive segments using these security contexts and deadlocks upon authentication denial.

Diagnostic Symptoms of the CCArchiveManager Deadlock

When CCArchiveManager.exe hangs, several diagnostic indicators confirm SQL metadata corruption:

SQL Server Name Query Mismatch: Opening SQL Server Management Studio (SSMS) and querying SELECT @@SERVERNAME returns the old computer name (OLD_NAME\WINCC), whereas querying SELECT SERVERPROPERTY('MachineName') returns the new computer name (SERVER1).
WinCC Project Configuration Mismatch: In WinCC Explorer, the computer object listed under Computer still references the old name or displays red mismatch crosses.
Corrupted Database Context File (.dcf): The WinCC project directory contains cached configuration files (ProjectName.dcf) that cache old computer names and security tokens, preventing database connection strings from resolving.

Step-by-Step Remediation Workflow Without Reinstalling Windows

Method 1: Reverting to the Original Computer Name (Fastest & Safest)

In Windows, open Control Panel > System > Advanced system settings.
Click Computer Name > Change....
Re-enter the exact original computer name (e.g. ES).
Restart the computer.
WinCC Runtime and CCArchiveManager.exe will initialize cleanly.

Method 2: Comprehensive System Re-Alignment to the New Computer Name

If the new computer name must be retained, execute the following technical recovery procedure:

Step 2.1: Re-align SQL Server Internal System Names

Open SQL Server Management Studio (SSMS) as Administrator, connecting to instance .\WINCC.
Open a New Query window and execute the following Transact-SQL commands:
sql -- Drop the old internal server reference EXEC sp_dropserver 'OLD_NAME\WINCC'; GO -- Add the new internal server reference matching the new computer name EXEC sp_addserver 'NEW_NAME\WINCC', local; GO
Open Windows Services (services.msc), locate SQL Server (WINCC), and restart the service.
Verify by running SELECT @@SERVERNAME; - it must now match NEW_NAME\WINCC.

Step 2.2: Rebuild Windows Security Rights via Security Controller

Open the Windows Start menu, navigate to Siemens Automation > Security Controller.
Right-click Security Controller and select Run as Administrator.
Click Repeat Settings; ensure all checkboxes (Registry, Windows Firewall, User Rights, DCOM) are selected.
Click Apply Recommendations. This updates all internal Windows user groups with the new computer name.

Step 2.3: Update WinCC Project Computer Name and Purge Caches

Open the WinCC project in WinCC Explorer.
In the navigation tree, click Computer.
In the right pane, select the old computer name, right-click, and select Properties.
Click the button Use Local Computer Name. Confirm the name updates to NEW_NAME.
Close WinCC Explorer.
Open Windows Explorer, navigate to the WinCC project directory, and delete the cached file:
<ProjectName>.dcf
Re-open WinCC Explorer and activate Runtime.

Computer Name Dependency Matrix in SIMATIC PCS 7

Component / LayerWhere Computer Name Is StoredImpact if Name Is ChangedRemediation ProcedureMicrosoft SQL Serversys.servers catalog tableConnection authentication deadlockTransact-SQL sp_dropserver / sp_addserverWindows Security GroupsLocal Users and Groups (SIMATIC HMI)Access Denied on archive directoriesRun Siemens Security Controller (SimaticRights.exe)WinCC Project (.mcp)Project properties databaseProject opens in read-only / demo modeClick 'Use Local Computer Name' in WinCC ExplorerWinCC Cache (.dcf)Binary cache in project rootHolds stale network socket referencesDelete <ProjectName>.dcf file with WinCC closedSimatic ShellNetwork adapter bindingCommunication loss with partner stationsSelect network adapter in Simatic Shell settings

Verification

Open SQL Server Management Studio; confirm SELECT @@SERVERNAME returns NEW_NAME\WINCC.
Open WinCC Explorer; confirm the Computer properties display NEW_NAME.
Click Activate to launch WinCC Runtime.
Monitor the startup dialog: verify the step Initializing Archive Management... completes successfully within 10 to 15 seconds without freezing.
In Windows Task Manager, verify CCArchiveManager.exe is running normally with status 'Running'.
Open the Alarm and Tag Logging trend screens; confirm historical process tags and alarms log continuously.

Limitations and Operational Precautions

Official Manufacturer Policy: Siemens officially documents that changing the computer name after PCS 7 installation is unsupported. In mission-critical pharmaceutical or nuclear installations, perform a clean reinstallation of Windows and PCS 7 to ensure validated compliance.
Redundant Server Pairs: If the renamed station is part of a redundant server pair, you must re-generate the OS Server Package and update the partner server's redundancy configuration in WinCC Redundancy.
Domain Controllers: Industrial PC stations running PCS 7 should never be configured as Windows Domain Controllers.

Engineer FAQ

Why did reinstalling PCS 7 over Windows fail to fix the problem?

Reinstalling PCS 7 without uninstalling and reinstalling Microsoft SQL Server preserves existing SQL registry entries and master database tables, retaining the corrupted computer name references.

What does CCArchiveManager.exe do in WinCC?

CCArchiveManager.exe is the master runtime process responsible for attaching, segmenting, swapping, and managing WinCC Tag Logging and Alarm Logging database archives.