Resolving PDM Server Access Error in PCS 7 v7.1 SP1 Maintenance Clients

Field engineers running SIMATIC PCS 7 V7.1 SP1 with SIMATIC PDM V6.0 SP5 HF3 frequently encounter a fault where the Maintenance Client faceplate does not render the PDM button, and selecting parameter or diagnostic options raises an error message indicating the client has no access to the PDM Server. Although the official "PDM Server" concept was first released with PCS 7 V7.1 SP2 and PDM V7.0, the root cause observed on SP1 stations is not the absence of the PDM Server role itself; it is a missing PDM Application entry inside the PC station hardware configuration (HW Config / KoKo) of the Engineering Station. This article documents the underlying mechanism, the exact configuration fix, and the verification procedure so that field technicians can clear the fault without escalating to a full V7.1 SP2 / PDM V7.0 upgrade.

1. Symptom Description and Field Observation

The error presents itself in three reproducible layers:

1. Faceplate layer: The PCS 7 Maintenance Client faceplate (WinCC runtime) opens normally and shows process values, but the toolbar that normally contains the PDM icon (the lifebuoy or wrench icon, depending on the OS skin) is missing.
2. Option dialog layer: If the operator navigates to Parameter / Diagnostics / Asset within the Maintenance area, the faceplate returns an inline message of the form "No connection to the PDM Server" or "This client cannot access the PDM Server."
3. Engineering layer: On the Engineering Station (ES), the asset tree in SIMATIC Manager compiles successfully, the Maintenance OS downloads without warnings, and the diagnostic screens regenerate. PDM itself can still open the HART device tree on the ES directly through the HW Config or the Devices & Networks editor.

2. Affected Versions and Component Matrix

The following matrix summarizes the PCS 7 / PDM combinations where this symptom class has been confirmed in field installations and the recommended remediation path for each.

The official help documentation for the modern PDM Server role is published in the SIMATIC PCS 7 Help for SIMATIC PDM V9.3 SP1, which describes the SIMATIC PDM Server Configurator, SIMATIC PDM Portal, and Logging on procedures. The historical release notes for the first PDM Server–enabled version are available at SIMATIC PDM Version 7.0 Update 1 available.

3. PDM Server Architecture in PCS 7

SIMATIC PCS 7 separates the engineering view of field devices from the runtime view of field devices. The components involved in the faceplate-to-PDM jump are:

• ES (Engineering Station): Holds the PCS 7 project, HW Config, the HART device tree, and PDM itself. It is also where the PC station (KoKo / "Komponenten Konfiguration") is defined.
• Maintenance Client: A WinCC runtime that displays the Maintenance area of the operator interface. It may be the OS itself, a separate OS client, or a WinCC client on a separate node.
• Maintenance Server: The OS server that compiles and stores the Maintenance OS pictures.
• PDM Server role: A logical role inside the PC station of the ES that exposes the PDM device tree to other clients. From PCS 7 V7.1 SP2 / PDM V7.0 onward this is a distinct service; in pre-SP2 setups it is emulated by the PDM Application entry in the PC station configuration.
• KoKo (PC station hardware configuration): The HW Config view of the SIMATIC PC station. It contains slots such as WinCC Application, OPC Server, S7RT, PDM Application, and IE General. The presence and correct slot order of PDM Application determines whether the Maintenance Client can resolve the PDM jump.

3.1 Why the Faceplate Asks for a "Server"

When the operator opens a faceplate and the Maintenance Client WinCC runtime resolves the HART device identifier, it queries the ES PC station for a COM/DCOM endpoint that hosts PDM. The endpoint is registered by the PDM runtime service. If the PC station configuration does not contain a PDM Application object, the endpoint does not exist, and the faceplate reports a missing PDM Server. This is true regardless of whether the project technically uses PCS 7 V7.1 SP1 or V7.1 SP2; the engineering-time configuration must declare the role explicitly.

4. Root Cause Analysis

From the field evidence in the symptom matrix, three causes are observed in order of frequency:

1. Missing PDM Application object in ES HW Config (KoKo). The PC station of the ES contains only the WinCC Application, OPC Server, S7RT, and IE General slots. The PDM slot is absent, so no PDM runtime endpoint is registered. This is the dominant cause in V7.1 SP1 installations.
2. Stale Maintenance OS / Diagnostic screens. The Maintenance OS picture and the asset / diagnostic screens were generated before the PDM Application was added. The faceplate therefore references a non-existent PDM jump target. The fix here is to re-run Create / Update Diagnostic Screens on every project in the multiproject, then recompile and download the Maintenance OS.
3. Project editor settings. The Maintenance project on the OS has not been designated as the Maintenance Station inside PDM settings. Without this designation the asset management integration is not wired.

5. Preconditions for the Fix

Before opening HW Config, confirm that the following conditions are met on the ES:

6. Step-by-Step Resolution Procedure

Perform the following steps in order. Steps 1–4 register the PDM endpoint in the PC station; steps 5–7 regenerate the runtime artifacts that reference it.

6.1 Open the PC Station HW Config of the ES

1. In SIMATIC Manager, select the ES station in the project tree.
2. Double-click Configuration (or right-click > Open Object) to launch HW Config / KoKo.
3. Confirm that the station is a SIMATIC PC station with the typical slots (WinCC Application, OPC Server, S7RT, IE General) visible in the upper rack.

6.2 Insert the PDM Application Object

1. In HW Config, open the hardware catalog (View > Catalog).
2. Navigate to SIMATIC PC Station > HMI > PDM Application (catalog path varies slightly between versions; in V7.1 SP1 it appears under SIMATIC PC Station > User Application > PDM Application).
3. Drag the PDM Application object into the PC station rack at the next free slot index. Typical placement is after WinCC Application and before IE General.
4. Close the catalog.

6.3 Configure the PDM Application Slot

1. Double-click the inserted PDM Application object.
2. In the Properties dialog, accept default values. The application name should read PDM.
3. Confirm the slot index. The PDM runtime uses this index as the COM/DCOM endpoint identifier for the faceplate jump.

6.4 Compile and Download the PC Station

1. In HW Config, choose Station > Save and Compile.
2. Choose PLC > Download to PC Station. Target is the local PC.
3. When prompted, allow the Station Configuration Editor to be updated. The Set PC Station dialog will register the new endpoint.
4. Wait for the download to complete and for the Station Configuration Editor to indicate RUN on the PDM Application component.

6.5 Designate the Maintenance Project in PDM Settings

1. In SIMATIC Manager, choose Options > SIMATIC PDM > Settings.
2. Navigate to the Maintenance Station tab.
3. Check Set current multiproject as maintenance station and confirm.

6.6 Regenerate Diagnostic Screens

1. In SIMATIC Manager, select the project root.
2. Choose Options > Plant View > Create / Update Diagnostic Screens.
3. Repeat for every project in the multiproject (AS, OS, ES, libraries).
4. Wait for completion. This regenerates the asset and diagnostic picture elements that the faceplate uses to jump to PDM.

6.7 Recompile and Download the Maintenance OS

1. Open the Maintenance OS in WinCC Explorer.
2. Choose File > Compile / Check.
3. Choose File > Download on the Maintenance Server.
4. Restart the WinCC runtime on the Maintenance Client to clear the cached faceplate picture set.

7. Verification Checklist

After completing the procedure, run the following checks. Each check has an expected, deterministic outcome.

8. Common Pitfalls and Field-Proven Caveats

8.1 PDM Application Inserted but Slot Index Wrong

If the slot index collides with another component, the Station Configuration Editor will refuse to start the component. Verify with the component status column; the affected component shows STOP with a configuration error.

8.2 DCOM Permissions

On multi-node installations where the Maintenance Client is on a separate Windows host, DCOM must permit anonymous or explicit access to the PDM runtime. If the client is a dedicated WinCC client, verify that the PDM endpoint is reachable via the configured account. Refer to the SIMATIC PCS 7 Help for SIMATIC PDM V9.3 SP1 for the modern equivalent configuration; the principle (DCOM endpoint registered via PDM Application) is the same.

8.3 Multiproject vs Single Project

The Maintenance project may sit inside one project of a multiproject while the ES in another. Create / Update Diagnostic Screens must be executed on every project; missing one project breaks the jump for all HART blocks inside that project.

8.4 HART Secondary Variable Mapping

Devices that publish secondary variables but are not assigned a proper HART tag in PDM still trigger the faceplate error even after the PDM Application is loaded. Verify the HART device tag with PDM > Device > Properties > Communication.

8.5 Operating System Compatibility

Windows Server 2008 R2 is the typical OS for PCS 7 V7.1 SP1. Windows Server 2012 / 2016 require a later PDM hotfix. Always confirm the PDM hotfix supports the deployed OS before applying the fix above.

9. Workarounds When PDM Server Has Not Been Released

For installations where the official PDM Server role is not yet released (pre-SP2), the workaround is the PC station PDM Application described in this article. The faceplate code path that queries "is PDM available?" returns true as soon as the runtime endpoint is registered, independent of the PDM Server marketing concept. Document this as a configuration workaround, not as a PDM Server installation.

9.1 Alternative: Direct PDM Jump from the ES Only

If the operator's Maintenance Client cannot be reconfigured quickly, restrict the PDM jump to the ES only. In SIMATIC Manager, choose Options > SIMATIC PDM > Settings > Maintenance Station and uncheck the option to expose PDM on other clients. Operators can then view parameters only on the ES itself; the faceplate on remote clients no longer raises the missing-PDM error.

9.2 Alternative: Upgrade to V7.1 SP2 / PDM V7.0

For long-term stability, plan a migration to PCS 7 V7.1 SP2 with SIMATIC PDM V7.0. The release announcement and component matrix are documented at SIMATIC PDM Version 7.0 Update 1 available. After upgrade the PDM Server role is officially supported and can be configured through the dedicated wizard.

10. Troubleshooting Matrix

11. Commissioning and Long-Term Preventive Measures

To prevent recurrence after the fix is applied, integrate the following items into the project's change-control procedure:

• Add the PDM Application slot as a mandatory checklist item in every new PCS 7 ES commissioning procedure.
• Include "HW Config / KoKo verification of PDM Application" in the standard project backup script. A simple diff between project ZIPs can catch accidental removal.
• After every SIMATIC Manager / PCS 7 service pack upgrade, re-run Create / Update Diagnostic Screens and recompile the Maintenance OS as a preventive step.
• Document the location of the PDM Application slot index in the project's commissioning report so that future engineers can locate it without trial-and-error.
• When migrating to PCS 7 V8.x / V9.x with PDM V8.x / V9.x, use the SIMATIC PCS 7 Help for SIMATIC PDM V9.3 SP1 as the canonical reference; the PDM Application slot remains, but a dedicated PDM Server Configurator becomes available.

12. Summary

The PCS 7 V7.1 SP1 Maintenance Client "no access to PDM Server" symptom is, in the majority of field cases, not caused by the absence of the PDM Server concept itself but by a missing PDM Application object in the PC station hardware configuration of the Engineering Station. Inserting the object, saving and compiling HW Config, downloading to the PC station, designating the Maintenance project in PDM settings, regenerating diagnostic screens, and recompiling the Maintenance OS restores the faceplate-to-PDM jump without requiring a PCS 7 / PDM upgrade. For installations that require the official PDM Server role, plan a migration to PCS 7 V7.1 SP2 with PDM V7.0 or later, using the manufacturer documentation linked above as the primary reference.