Resolving Ghost Station Names ('OS_BOA') in WinCC Runtime Tag Logging and Archive Selection

The appearance of an unfamiliar station name such as 'OS_BOA' in the WinCC Runtime Selection of Archives/Tags on a Single Station system is caused by residual server data packages (.pck), obsolete computer names in the WinCC Computer Editor, or leftover metadata from a cloned project or previous multi-user engineering setup. In WinCC Explorer, open 'Server Data', delete any obsolete or orphaned server data packages, verify under the 'Computer' editor that only the local workstation name is defined as a server, and execute a full project save and reorganization to purge ghost station entries from the internal WinCC SQL database.

Why Ghost Stations Appear in WinCC Tag Logging Dialogs

In SIMATIC PCS 7 and WinCC, operators and engineers accessing archive trend controls, user archives, or report generators interact with the Selection of Archives/Tags dialog. This dialog populates its tree view by querying the internal WinCC configuration database for registered archive providers.

In a Single Station system where the project is named OS_RMS, an engineer may be startled to find a second server listed, such as OS_BOA, containing duplicate or empty archive structures. Even though OS_BOA does not physically exist on the plant network, WinCC treats it as an active archive source, confusing operators and cluttering runtime trend selection screens.

The Role of Server Packages and Project Cloning Residuals

This defect typically originates from one of three engineering workflows:

Cloned or Migrated Project Baseline: The current project was originally cloned from another facility, demo project, or older engineering multiproject where OS_BOA was a server node or client.
Orphaned Server Data Packages: In WinCC Explorer under Server Data, a server package (OS_BOA.pck) was loaded at some point in the past. Even if the remote PC is disconnected, WinCC retains the package definitions in the SQL Server tables CC_AlgServerData and CC_TagServerData.
Multi-Station Computer Editor Entries: If someone created a client or server computer object named OS_BOA under the WinCC Computer editor, the runtime window manager assumes a distributed system.

Auditing Computer Editor and Server Data in WinCC Explorer

To determine where the ghost station is registered:

Open WinCC Explorer directly on the OS station.
Expand the Computer icon in the tree. On a Single Station project, only one computer name should exist: the exact Windows hostname of the local machine. If OS_BOA is listed as a client or redundant partner, it must be removed.
Expand Server Data. If an entry named OS_BOA exists, WinCC is actively importing tag logging and alarm logging dictionaries from that fictitious server package.

Step-by-Step Procedure to Remove Ghost Archive Servers

Follow this sequence to cleanly remove the ghost server:

Deactivate WinCC Runtime: Completely exit runtime and close WinCC Explorer.
Launch WinCC Explorer: Open the project in configuration mode.
Delete Orphaned Server Packages: Expand Server Data. Right-click OS_BOA, select Delete, and confirm the deletion.
Clean Computer Editor: Expand Computer. If OS_BOA appears as an additional station, right-click and select Delete.
Clean Physical Packages Folder: In Windows File Explorer, browse to <ProjectPath>\<OS_Directory>\Packages\. Delete any physical files named OS_BOA.pck or OS_BOA.dcf.
Reset Project Type if Necessary: If the project was erroneously configured as a 'Multi-User Project', right-click the project root in WinCC Explorer, select Properties, and ensure the project type is set to Single-User Project.
Recompile OS: In SIMATIC Manager, perform an OS Compile (Changes only) to update the runtime database.

WinCC Station Registration and Metadata Comparison

The following table compares where station names reside in WinCC and how they impact archive selection:

Configuration LocationDatabase Table / FileNormal Single-Station SettingSymptom if Ghost Entry PresentWinCC Server Data<Project>\Packages\*.pckEmpty / No external packagesExternal server appears in archive tag treesComputer EditorCC_Config_...\MCACHEPATHLocal hostname onlyStation treated as multi-user client/serverProject TypeWinCC Project PropertiesSingle-User ProjectMulti-User options enabled; network locks enforcedSimatic ShellTerminal Bus Network CacheLocal station + ESRemote station discovery packets broadcast

Verification

Verify that the ghost server has been eradicated through the following steps:

Activate WinCC Runtime on the OS station.
Open a graphic picture containing the WinCC Online Trend Control.
Open the trend properties dialog, select Tag / Archive Selection, and expand the archive tree.
Verify that only the true project server OS_RMS is listed and that OS_BOA has vanished completely.
Confirm that archive tags log and display data normally without communication errors in WinCC Channel Diagnosis.

Limitations and Operational Precautions

Consider these operational rules when managing WinCC project metadata:

Never Edit SQL Server Tables Directly: Do not attempt to delete rows manually from SQL Server database tables via SQL Server Management Studio; always use the WinCC Explorer interface to ensure relational integrity.
Multi-Client Warning: If the system is actually a multi-client OS station that queries multiple real OS Servers, ensure you do not delete legitimate server packages required for plant operations.
Backup Before Deletion: Create a project backup using the WinCC Project Duplicator or SIMATIC Manager Archive before removing computer and package objects.