Resolving 'Updating DCF File' Freezes During WinCC OS Download in SIMATIC PCS 7

When downloading a WinCC Operator Station from the Engineering Station (ES) and the progress bar freezes indefinitely at 'Updating DCF file' after project files have copied, the primary root cause is a mismatch between the configured computer name in WinCC Explorer and the physical target station's Windows hostname, or a corrupted Distributed Configuration File (.dcf). During the DCF update phase, the ES executes remote DCOM/RPC calls to configure multi-station distributed pointers. To resolve the freeze, verify that the computer name in WinCC matches the target Windows hostname exactly, ensure the target network share has full write permissions, close WinCC on the target, delete the local .dcf file, and re-attempt the download.

Executive Summary

Loading target Operator Stations (PLC > Download) from the Engineering Station is a routine engineering task across the lifecycle of SIMATIC PCS 7. However, automation engineers frequently encounter an abrupt halt during the final phase of the download process: the project files copy over the network successfully, but the download dialog hangs indefinitely at the status message 'Updating DCF file'. The progress bar stops advancing, task managers show zero network throughput, and after 15 to 30 minutes, the wizard aborts with a communication timeout. Because the .dcf file establishes distributed communication routing between OS Servers and Clients, resolving this stall requires verifying computer naming conventions, DCOM permissions, and database lock releases.

The Role of the DCF File in WinCC Distributed Systems

The .dcf file (Distributed Configuration File, e.g. <ProjectName>.dcf) resides in the root directory of every WinCC project:

It acts as a compact, relational configuration cache for the WinCC communication kernel (CCProjectMgr.exe).
Stores multi-station server package mappings, computer hostnames, redundancy partner assignments, and security IDs.
During an OS download, the Engineering Station opens this file remotely to update station properties to reflect the physical target environment.

Why the OS Download Wizard Freezes at 'Updating DCF File'

The freeze occurs during remote execution of DCOM / RPC commands:

Computer Name Discrepancy: If the computer name defined in SIMATIC Manager / WinCC Explorer (e.g. OS_SRV01) does not match the actual Windows hostname of the physical PC (e.g. OS-SRV01 or mismatched capitalization), the remote procedure call waits indefinitely for a response from the non-existent identity.
Corrupted Local DCF Cache: If the .dcf file on the ES or target OS became corrupted during an abnormal process termination, the serialization parser deadlocks.
Exclusive Database Lock: If WinCC Explorer or a background service (CCExp.exe) is active on the target OS, the .dcf file is locked against write access.

Computer Name Resolution, DCOM, and Network Share Handshakes

Successful DCF updates depend on three prerequisites:

Exact Hostname Alignment: Windows computer name, Simatic Shell name, and WinCC Computer Properties name must be identical.
Administrative Network Share Access: The ES must have full read/write/modify access to the target project directory.
DCOM Security Hardening: DCOM default access and launch permissions must permit remote activation by the logged-on user.

OS Download Failure Symptom and Resolution Matrix

The following table compares download stall symptoms and their technical resolutions:

| Error Symptom | Phase of Failure | Underlying Root Cause | Corrective Engineering Action |
|---|---|---|---|---|
| Freeze at 'Updating DCF file' | 95% Completion | Mismatched computer name in WinCC | Align WinCC computer name with Windows hostname. |
| Freeze at 'Updating DCF file' | 95% Completion | Locked or corrupted .dcf file | Delete .dcf file; re-run OS compile on ES. |
| 'Target computer not reachable' | 0% Initialization | Simatic Shell / Multicast failure | Configure Multicast Proxy in Simatic Shell. |
| 'Access denied' during copy | File Copy Phase | Windows share permissions restricted | Grant 'Full Control' to SIMATIC HMI user group. |
| 'Cannot deactivate project' | Download Start | WinCC Runtime active on target | Deactivate Runtime and close WinCC on target OS. |

Step-by-Step Procedure to Resolve DCF Update Freezes

Method 1: Aligning Computer Hostnames

On the target OS Server/Client PC, open Windows System Properties (sysdm.cpl).
Note the exact Full computer name (e.g. OSSERVER01).
On the Engineering Station, open the project in SIMATIC Manager.
Right-click the OS object and select Open Object (opens WinCC Explorer).
In WinCC Explorer, right-click the computer node in the navigation tree and select Properties.
Verify the Computer name field. Ensure it matches the target Windows hostname character-for-character.
If mismatched, enter the correct computer name and click OK.

Method 2: Regenerating the Corrupted DCF File

Close WinCC Explorer and SIMATIC Manager on the Engineering Station.
Navigate to the project directory on the ES hard drive: <ProjectPath>\wincproj\<OS_Name>\.
Locate the file <OS_Name>.dcf.
Delete this file (or rename it to .dcf.bak).
On the target OS computer, close all WinCC applications and delete the corresponding .dcf file in the target project folder.
Re-open SIMATIC Manager on the ES.
Right-click the OS project and select Compile > Tags and messages.
SIMATIC Manager generates a fresh, clean .dcf file automatically.
Right-click the OS project and execute PLC > Download. Confirm that download completes cleanly without stalling.

Verification

To verify that OS download functionality is restored:

Complete Download Execution: Execute PLC > Download > Entire Project. Confirm that the progress dialog transitions smoothly through 'Updating DCF file' in less than 5 seconds.
Target Project Verification: On the target OS computer, open the project in WinCC Explorer. Confirm that the project opens with zero database connection errors.
Runtime Activation: Activate WinCC Runtime on the target station. Confirm that process graphics, alarms, and communication channels initialize normally.

Limitations and Operational Precautions

Do Not Delete DCF While Runtime Is Active: Deleting the .dcf file while WinCC Runtime is executing can crash the communication manager.
Case Sensitivity: Although Windows networking is generally case-insensitive, internal WinCC SQL scripts can exhibit sensitivity to hostname case mismatches; maintain uniform uppercase naming across all stations.
Domain vs Workgroup: If operating in a domain environment, verify that Domain Name System (DNS) reverse lookup zones resolve the target hostname accurately to its Terminal Bus IP address.

Engineer FAQ

Is it safe to delete the .dcf file?

Yes. The .dcf file is a temporary configuration cache that WinCC automatically regenerates from the project database upon opening or compilation.

Why does the OS download require DCOM permissions?

The Engineering Station uses DCOM to remotely trigger database registration, project activation, and file update services on the target station.

Can delta downloads freeze at 'Updating DCF file' as well?

Yes, delta downloads execute the same DCF consistency check; if station pointers are mismatched, delta downloads stall identically.

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=os-download
https://industrialautomation.net/search?query=wincc
https://industrialautomation.net/search?query=troubleshooting

6 respuestas

Resolving 'Updating DCF File' Freezes During WinCC OS Download in SIMATIC PCS 7