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

Resolving Disabled WinCC Tag Logging and Alarm Logging Archive Configuration in PCS 7

Resolving Disabled WinCC Tag Logging and Alarm Logging Archive Configuration in PCS 7

In SIMATIC PCS 7 WinCC Explorer, when the Archive Configuration options for Tag Logging and Alarm Logging are grayed out or disabled with the message 'Keine Archivkonfiguration möglich' (No archive configuration possible), the issue is caused by a computer name mismatch in the WinCC project properties. WinCC binds archive configuration privileges exclusively to the computer designated as the project host. If a project was retrieved from an archive or copied from another machine, the project retains the original computer name, treating the local Engineering Station or OS as a remote client. To resolve this: 1) In WinCC Explorer, right-click Computer and open Properties; 2) Change the Computer Name to match the exact local Windows computer name (or click 'Use Local Computer Name'); 3) Close WinCC Explorer and delete the project's .dcf database file; and 4) Reopen WinCC Explorer.

Table of Contents

Executive Summary

During plant upgrades, project migrations, or off-site engineering testing on laptops, automation engineers frequently retrieve SIMATIC PCS 7 multi-projects from archives. Upon opening the WinCC OS in WinCC Explorer, they discover that attempting to configure archive segmentation, retention durations, or backup paths in Tag Logging or Alarm Logging is completely blocked, displaying grayed-out menus or the notification 'Keine Archivkonfiguration möglich'. While runtime monitoring and basic graphics editing may appear operational, archive administration is locked. This technical guide explains the computer name binding architecture in WinCC, outlines the role of the project Database Configuration File (.dcf), and details the step-by-step recovery process.

Architecture and Fundamental Mechanics

WinCC Computer Name Binding and Archive Administration

+-------------------------------------------------------------------------+
|                         Engineering Station (ES)                        |
|   Actual Windows Computer Name: 'ES_LAPTOP_01'                          |
+-----------------------------------|-------------------------------------+
                                    |
                                    v Opens WinCC Project
+-------------------------------------------------------------------------+
|                    WinCC Project Database (Project.mcp)                 |
|                                                                         |
|   Registered Host Computer Name: 'SRV_PROD_01'  <-- [MISMATCH DETECTED] |
|                                                                         |
|   WinCC Security & Component Evaluation:                                |
|   - Is local machine ('ES_LAPTOP_01') the registered host server?       |
|   - NO! Local machine is treated as a secondary / read-only client!     |
|                                                                         |
|   CONSEQUENCES:                                                         |
|   - Tag Logging Archive Configuration:   DISABLED (Grayed Out)          |
|   - Alarm Logging Archive Configuration: DISABLED (Grayed Out)          |
|   - Status: 'Keine Archivkonfiguration möglich'                         |
+-----------------------------------|-------------------------------------+
                                    |
                                    v Resolution Workflow
+-------------------------------------------------------------------------+
|   1. Set Computer Name in WinCC Properties to 'ES_LAPTOP_01'            |
|   2. Delete Project.dcf (Forces SQL Schema Alignment)                   |
|   3. Reopen WinCC Explorer -> FULL ARCHIVE CONFIGURATION RESTORED!      |
+-------------------------------------------------------------------------+

The Role of the Project Configuration File (.dcf)

  1. The .dcf Cache: WinCC maintains a relational database configuration file with extension .dcf alongside the .mcp project file. This file caches component identities, server-client role assignments, and archive manager endpoints.
  2. Computer Name Desynchronization: If the project was copied or renamed, the .dcf file continues to point to the legacy computer name. Even if the operator modifies the computer name in the GUI, residual entries in the .dcf file can prevent WinCC Archive Manager from initializing.
  3. CCArchiveManager.exe Reset: When database pointers are heavily desynchronized, running a global reset via CCArchiveManager.exe -reset all restores default segment parameters.

Step-by-Step Implementation Procedure

Step 1: Verify Windows Computer Name

  1. On the PC where WinCC is running, press Win + Pause/Break (or open System Properties).
  2. Note the exact Computer name (e.g., ES_ENG_01).
  3. Note: Ensure the computer name conforms to Siemens naming conventions (maximum 15 uppercase characters, no underscores or special characters if possible).

Step 2: Update Computer Properties in WinCC Explorer

  1. In WinCC Explorer, navigate to the project navigation tree.
  2. Click on Computer.
  3. In the right pane, right-click the listed computer name and select Properties.
  4. In the Computer Properties dialog, inspect the Computer Name field.
  5. Click the button Use Local Computer Name (or manually type the exact Windows computer name recorded in Step 1).
  6. Click OK to save the modification.
  7. Close WinCC Explorer completely.

Step 3: Delete the Project .dcf File

  1. Open Windows Explorer and navigate to the folder containing the WinCC project ([ProjectName].mcp).
  2. Locate the file named [ProjectName].dcf (Database Configuration File).
  3. Delete [ProjectName].dcf (or rename it to [ProjectName].dcf.bak).
  4. Do not delete any other files in the project folder.

Step 4: Reopen WinCC Explorer and Verify Archive Configuration

  1. In SIMATIC Manager, reopen the OS project in WinCC Explorer.
  2. Upon launching, WinCC detects the missing .dcf file, queries the local Microsoft SQL Server instance, and regenerates a fresh .dcf file perfectly synchronized with the local computer name.
  3. In the WinCC Explorer tree, expand Tag Logging and Alarm Logging.
  4. Right-click Archive Configuration > TagLogging Fast and select Properties.
  5. Confirm that the configuration dialog opens with all segment sizes, time parameters, and backup paths fully accessible and editable.

Step 5: Execute Archive Manager Reset (If Grayed-Out State Persists)

  1. If archive options remain locked:
  2. Ensure WinCC Runtime is completely deactivated.
  3. Press Win + R, type the following command, and press Enter:
    cmd CCArchiveManager.exe -reset all
  4. This resets the internal archive tracking tables and restores default 1-day/1-week archive segments, clearing any legacy lock conditions.

Verification

  1. GUI Property Access Check: Open Tag Logging in WinCC Configuration Studio. Navigate to Archive Configuration for both Fast and Slow archives. Confirm that input fields for maximum total size and segment duration are active and saveable.
  2. Alarm Logging Check: Open Alarm Logging. Confirm that message archive configuration settings can be adjusted and applied without permission warnings.
  3. Test Runtime Activation: Activate WinCC Runtime locally. Confirm that the SQL Server creates the active archive segment databases ([Project]_TLG_F_*.mdf) in the project directory without error.

Limitations and Operational Precautions

  1. Single Station vs Server Projects: If the project is configured as a redundant OS Server pair, the master server project must reference Server 1's computer name and the standby must reference Server 2's computer name; setting both to the ES name will break redundancy synchronization.
  2. Archive Data Loss on Reset: Executing CCArchiveManager.exe -reset all purges active runtime archive segments; never execute this command on an operating production OS Server holding live historical data without first making a full database backup.

Engineer FAQ

Why is Archive Configuration disabled in WinCC?

The computer name configured in the WinCC project does not match the actual local Windows computer name, causing WinCC to treat the station as an unauthorized client.

What does 'Keine Archivkonfiguration möglich' mean?

It translates to 'No archive configuration possible', indicating that the local station lacks host server rights to configure archive segments.

Where is the computer name updated in WinCC?

In WinCC Explorer, click on Computer in the tree, right-click the computer object in the right pane, and select Properties.

What is the function of the .dcf file?

The .dcf file (Database Configuration File) caches component configurations and computer bindings; WinCC automatically regenerates it if deleted.

Will deleting the .dcf file delete my process tags?

No. Tags, screens, scripts, and alarms are stored in the project SQL database (.mdf/.ldf) and are not affected by deleting the .dcf cache.

What does CCArchiveManager.exe -reset all do?

It resets all Tag Logging and Alarm Logging archive configurations to factory defaults (1 day / 1 week) and clears runtime tracking tables.

Can I edit archive settings while WinCC Runtime is running?

Certain basic settings can be viewed, but structural archive segment size modifications should be performed while Runtime is deactivated.

Does this issue occur on Engineering Stations?

Yes, very frequently when an OS Server project is retrieved on an ES whose computer name differs from the production server.

What naming rules apply to computer names in PCS 7?

Maximum 15 uppercase characters, containing only letters, numbers, and hyphens; avoid underscores and special symbols.

Why did Tag Logging work while Archive Configuration was locked?

Tag logging queries and graphics can function across clients, but administrative schema modifications are restricted strictly to the designated host server.

Technical References

Related Articles

Related Tags

  • Archive Configuration
  • Computer Name
  • WinCC Tag Logging
  • Alarm Logging
  • .dcf File
  • CCArchiveManager
  • WinCC V7.5
20 respuestas