Resolving Greyed Out OS Server Assignment in SIMATIC Manager OS Clients

In SIMATIC PCS 7 multiprojects, the checkbox to assign an OS Server to an OS Client being greyed out or unselectable in SIMATIC Manager (under 'Assign OS Server...') occurs when the target OS Server has not generated its Server Data package (*.pck) or when project path relocation invalidated package pointers. OS Clients require server data packages to resolve remote tags, alarms, and picture trees. To resolve this issue, right-click the OS Server's WinCC Application in Component View, select 'Generate server data' (or recompile the OS with server data generation enabled), return to the OS Client, and assign the now-selectable server package.

Client-Server Architecture and Server Data Packages (*.pck)

In a SIMATIC PCS 7 distributed architecture, Operator Stations operate in a multi-client client-server relationship. Dedicated OS Servers interface directly with automation controllers (AS) to acquire process tags, manage alarms, and log trends. OS Clients (WinCC Appl. Client) do not communicate directly with PLCs; they display graphics, trends, and faceplates by querying data through their assigned OS Servers.

To establish this connection, the OS Client requires a Server Data Package (<Project_Name>.pck). The package is an exported database descriptor containing server network names, database IDs, available archive tags, and message class definitions. Without a valid server data package, an OS Client cannot bind to an OS Server.

Root Causes of Greyed-Out Server Assignment Checkboxes

When an engineer right-clicks an OS Client in SIMATIC Manager and selects Assign OS Server..., the dialog displays all available server packages across the multiproject. If the checkbox for the target server is greyed out or missing:

Uncompiled Server Data: The OS Server has never generated its server data, or the existing .pck file was deleted during project maintenance.
Project Path Relocation: If the multiproject was moved to a new drive letter or renamed without regenerating server data, the internal path pointer in SIMATIC Manager points to an invalid directory, forcing the UI to disable the checkbox.
Uncompiled OS Server: If the OS Server project contains uncompiled changes (indicated by an orange station icon), the system disallows assigning uncompiled packages to clients.

Client-Server Engineering Workflow and Package Status Matrix

The table below contrasts OS Server data states, file extensions, and client assignment behaviors in SIMATIC Manager:

Component / OperationGenerated FileFile LocationAssignment Status in Client DialogServer Data Generated<Server_Name>.pck<OS_Server_Path>\packages\Active / Selectable: Checkbox enabled; can be checked.Server Data MissingNoneDirectory emptyMissing / Greyed Out: Server not listed or disabled.Path RelocatedObsolete .pckOld project pathGreyed Out / Invalid: Path cannot be verified by SIMATIC Manager.OS Client ApplicationWinCC Appl. ClientPC Station SlotTarget application that receives and loads .pck packages.Implicit UpdateAS-OS CompilationAutomaticRecompiling OS Server automatically updates client packages.

Step-by-Step Procedure to Generate Server Data and Assign Clients

Generate Server Data on OS Server:
- In SIMATIC Manager, switch to Component View.
- Locate the target OS Server PC Station -> expand to the WinCC Application object.
- Right-click the OS Server object -> select Generate server data.
- Confirm execution: SIMATIC Manager compiles server definitions and generates the .pck file in the OS project folder.
Verify Server Package Creation:
- Open Windows Explorer: navigate to <Multiproject>\<OS_Server_Folder>\packages.
- Confirm the presence of <Server_Project_Name>.pck with the current system timestamp.
Assign Server Package to OS Client:
- In SIMATIC Manager Component View, navigate to the OS Client PC Station.
- Right-click the OS Client object -> select Assign OS Server....
- In the Assignment dialog, the checkbox for the target OS Server is now fully enabled.
- Check the checkbox next to the target OS Server and click OK.
Configure Standard Server (If Multi-Server Project):
- Open WinCC Explorer on the OS Client.
- In the tree, right-click Server Data -> Standard Server....
- Define standard server defaults for Alarms and Split Screen Wizard if multiple OS Servers exist.
Download OS Client: Execute PLC -> Download from SIMATIC Manager to transfer the updated client configuration.

Verification

Verify client-server integration through the following steps:
1. In SIMATIC Manager, reopen Assign OS Server... on the OS Client: confirm that the target OS Server displays a solid green checkmark.
2. Open WinCC Explorer on the OS Client: expand Server Data: confirm that the OS Server package is loaded.
3. Activate WinCC Runtime on the OS Client: verify that process screens open seamlessly, displaying live tags and alarms streamed from the OS Server without server connection errors.

Limitations and Operational Precautions

Whenever an OS Server undergoes an AS-OS compilation that adds new process tags or modifies alarm classes, server data is regenerated. In redundant OS Server architectures, ensure that server data generation reflects both redundant partners (Master and Standby). Crucially, downloading updated server data packages to an OS Client does not require restarting the active OS Servers, ensuring continuous plant visibility during client updates.