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

How to Resolve WinCC OS Client Download Error 'An Error Occurred While Changing the Computer Name'

How to Resolve WinCC OS Client Download Error 'An Error Occurred While Changing the Computer Name'

To resolve the SIMATIC PCS 7 OS Client download error 'An error occurred while changing the computer name in project [ClientName]', engineers must correct Windows security permissions, release file locks on the client SQL database, and verify network station naming. This fault occurs when the Engineering Station (ES) successfully transfers the WinCC client project files over the network share but fails to modify the target computer name inside the project database (.mdf/.ldf) via remote DCOM/SQL calls. The resolution requires running CCCleaner.exe on the client to terminate hung WinCC processes, ensuring the logging-in Windows user belongs to the SIMATIC HMI and local Administrators groups on both machines, setting network share permissions to 'Full Control', and verifying that the computer name in PCS 7 matches the target workstation name exactly.

Table of Contents

Root Cause Analysis: Why Target Computer Renaming Fails

When downloading an OS Client project from the Engineering Station (ES) via SIMATIC Manager (PLC -> Download -> Target System), the process executes two distinct phases:

  1. File Transfer Phase: The ES copies the project directory structure, graphic files (.pdl), scripts, and base project files across the Windows network share (<Shared_Folder>) to the target OS client.
  2. Project Initialization Phase: The ES invokes remote SQL Server and WinCC components (CCProjectMgr.exe) on the target client to mount the local database and update the internal project table CC_ConfigStudio to reflect the physical Windows computer name of the OS client.

If the file transfer completes but the renaming step fails with the error 'An error occurred while changing the computer name in project', it indicates that:
* The remote ES process was denied SQL administrative privileges on the OS client database instance.
* Existing WinCC processes on the client (CCProjectMgr.exe, CCClientRT.exe, sqlservr.exe) hold an exclusive lock on the project file.
* Network NetBIOS name resolution or Windows firewall settings blocked the remote database management call.
* The station name defined in SIMATIC Manager does not match the actual physical Windows computer name of the client.

Prerequisite Checklist: Windows User Groups and Share Permissions

Before performing an OS Client download, verify that the following system prerequisites are met:

1. User Account Consistency

  • The engineering user logged into the ES must exist on the OS Client with the exact same username and password (or belong to the same Active Directory domain).
  • The user account must be an explicit member of the following local groups on both ES and OS Client:
  • Administrators
  • SIMATIC HMI
  • SIMATIC NET

2. Network Share Configuration

  • The target project directory on the OS Client (e.g., D:\WinCC_Projects) must be shared.
  • In Windows Explorer, right-click the shared folder -> Properties -> Sharing -> Advanced Sharing -> Permissions:
  • Grant Full Control to Everyone or the SIMATIC HMI group.
  • On the Security tab (NTFS permissions):
  • Grant Full Control to the SIMATIC HMI group and SYSTEM.

Step-by-Step Resolution: Terminating Locks and Re-executing Download

Follow this procedure to recover the client and complete the download:

Step 1: Clean Up Hung Processes on the OS Client

  1. On the OS Client, close WinCC Explorer if open.
  2. Open an administrative Command Prompt and execute:
    cmd "C:\Program Files (x86)\Siemens\WinCCin\CCCleaner.exe"
  3. Wait for CCCleaner to terminate all background WinCC processes (CCProjectMgr.exe, CCDataServer.exe, CCRTSys.exe).
  4. Restart the OS Client workstation if file locks persist.

Step 2: Verify Station Naming in SIMATIC Manager

  1. In SIMATIC Manager on the ES, select the OS Client object.
  2. Right-click the OS Client -> Object Properties.
  3. Verify the Computer name field: It must match the Windows computer name of the target client character-for-character (case-insensitive, max 15 alphanumeric characters, no spaces or underscores).
  4. Verify the Target OS path: It must point to the valid UNC network share (e.g., \OSCLIENT01\WinCC_Projects\Client.mcp).

Step 3: Execute Target Download

  1. In SIMATIC Manager, right-click the OS Client -> PLC -> Download.
  2. Select Entire OS (or changes only if previously synchronized).
  3. The download process will complete file copying and successfully adjust the project computer name without errors.

Manual Project Configuration Fallback Procedure

If an urgent operational deadline prevents immediate resolution of remote network DCOM permissions, use this verified manual fallback:

  1. Copy Project Directory: Using Windows Explorer, navigate to the ES project directory where the client project is stored (<PCS7_Project>\wincproj\<Client_OS>).
  2. Copy the entire client project folder to an external drive or directly over the network to the target OS client storage directory (e.g., D:\WinCC_Projects\Client_OS).
  3. Open Locally: On the OS Client, launch WinCC Explorer as Administrator and open Client_OS.mcp.
  4. Update Computer Name:
    * In the WinCC Explorer navigation tree, right-click the top-level project name -> Properties.
    * Under the General tab, click Change Computer Name to Local.
    * When prompted: 'The computer name will be changed. WinCC must be closed', click OK.
  5. Reopen and Verify: Reopen WinCC Explorer on the client. Verify that the computer name is updated to the local workstation name and activate Runtime.

Diagnostic and Configuration Troubleshooting Matrix

The following table outlines the diagnostic failure points and corrective actions for OS Client downloads:

Error Symptom / Failure StageRoot CauseDiagnostic LocationCorrective Action'Error changing computer name'DCOM / SQL permission denied; file lockWinCC_Sys_01.log on clientRun CCCleaner.exe; verify SIMATIC HMI group'Network share not accessible'Missing share or firewall blocking SMBWindows Explorer \Client\ShareShare folder with Full Control to SIMATIC HMI'Computer name mismatch'Station name in ES != Windows hostnameWinCC Project PropertiesCorrect hostname in SIMATIC Manager Object Properties'SQL database attach error'Locked .mdf/.ldf database filesEvent Viewer -> Application logStop SQL Server instance; delete orphaned .ldf'DCOM Security Exception'Restrictive Windows DCOM policiesdcomcnfg security logConfigure SIMATIC DCOM security via Security Controller

Maintaining synchronized Windows credentials prevents recurring download initialization errors.

Verification

To verify that the OS Client download succeeded:
1. Verify that the SIMATIC Manager download progress dialog completes with 100% and closes without error popups.
2. On the OS Client, open WinCC Explorer and check the project title bar: It must display the local workstation name.
3. Activate WinCC Runtime on the client.
4. Verify that server data packages are loaded, process pictures from all OS Servers are accessible, and alarms populate the alarm banner.

Limitations and Operational Precautions

  • The manual copy fallback should only be used as a temporary emergency measure; long-term plant management requires establishing clean network downloads from the ES.
  • Computer names must never exceed 15 characters, must not start with a digit, and must not contain special characters or underscores (_).
  • Never use the WinCC Project Duplicator tool to transfer OS Client projects; OS Clients must be managed via SIMATIC Manager download.
  • Always ensure all Windows updates and security policies conform to the officially released PCS 7 compatibility tool specifications.

Engineer FAQ

Can I rename the OS Client computer name directly in the Windows System Properties?

Renaming a Windows computer after WinCC is installed requires running the WinCC project preparation tool or updating SQL instances. It is best to assign the final hostname before installing WinCC.

Why does CCCleaner need to be run when download fails?

CCCleaner forcibly closes residual WinCC background services and releases file locks on the .mdf and .ldf database files, allowing the download process to overwrite them cleanly.

Does the OS Client require its own process object licenses?

No. OS Clients require an OS Client Runtime license (e.g., SIMATIC WinCC RT Client), but process objects (POs) are hosted and counted exclusively on the OS Servers.

Technical References

Related Articles

Related Tags

  • OS Client Download
  • WinCC Error Changing Computer Name
  • CCCleaner
  • SIMATIC HMI Group
  • Network Permissions
6 respuestas