Resolving s7tdpcox.dll Conflict Between PCS 7 and WinCC Flexible

1. Problem Overview

Engineers building PCS 7 v7.x projects frequently inherit a developer workstation that already has SIMATIC WinCC flexible 2008 (or WinCC flexible 2008 SPx) installed for separate HMI panel commissioning. When the same PC station is then promoted to a PCS 7 OS engineering role, opening the multiproject triggers a warning dialog that points at s7tdpcox.dll, typically followed by broken WinCC explorer views, missing OS pictures, and runtime alarms about "configuration inconsistent."

The visible failure is the WinCC dialog reporting a damaged or unregistered s7tdpcox.dll, but the underlying cause is a fundamental incompatibility between the two Siemens software stacks. PCS 7 v7.x ships with and pins to SIMATIC NET v6.4, while WinCC flexible 2008 was released against an older SIMATIC NET release and is not compatible with SIMATIC NET v6.4. The coexistence constraint is published in the Siemens "Which SIMATIC software components are released for SIMATIC WinCC flexible 2008?" entry and in the PCS 7 v7.x readme.

2. Affected Software Versions

3. Root Cause Analysis

3.1 What is s7tdpcox.dll?

s7tdpcox.dll is the SIMATIC NET COM/DCOM wrapper that exposes the S7 DP / S7-DOS channel to higher-level WinCC graphics, OPC servers, and WinCC flexible runtime components. It implements:

• S7DP protocol engine (PROFIBUS DP master class 1 / class 2 services).
• Channel DLL for the WinCC "S7-DOS" channel.
• Component Object Model (COM) registration for Siemens.SimaticNET.S7 and related prog IDs.
• Callback handling for diagnostic events, station failure, and time-stamping.

Each major SIMATIC NET release re-compiles this binary. Interface GUIDs and method signatures change subtly between v6.3 and v6.4. When PCS 7 v7.x installs SIMATIC NET v6.4, it overwrites the older s7tdpcox.dll in the Windows System32 (or SysWOW64) directory and rewrites the COM registry. The previous copy expected by WinCC flexible 2008 is now gone, and the next WinCC flexible project open triggers the dialog.

3.2 Why the Coexistence Constraint Exists

The constraint is documented because PCS 7 needs a deterministic DP stack for redundant OS servers, time-stamped alarms, and SFC/SFB hot-restart handling. SIMATIC NET v6.4 is the only release validated against PCS 7 v7.x. WinCC flexible 2008, by contrast, was qualified on SIMATIC NET v6.2 / v6.3 with the panel transfer and ProSave tool chains that ship with TIA predecessors. Installing WinCC flexible 2008 on top of a SIMATIC NET v6.4 PC station rolls back certain registry keys and breaks the WinCC OS graphics runtime.

4. Symptoms and Error Messages

5. Diagnostic Procedure

1. Capture the dialog text exactly. Open the OS project once and copy the full warning. Most often it references s7tdpcox.dll, the WinCC version, and the OS server name.
2. Inspect the SIMATIC NET version. Open "SIMATIC NET - Commissioning" → Installed software, or check HKLM\SOFTWARE\Siemens\SIMATIC NET for the Version value. Confirm v6.4 (build 6.4.x.x).
3. Inspect WinCC flexible installation. Use Start → SIMATIC → WinCC flexible 2008 → Information or check HKLM\SOFTWARE\Siemens\Automation\WinCC flexible\2008\Version.
4. Verify s7tdpcox.dll location. Search %SystemRoot%\System32 and %SystemRoot%\SysWOW64. Compare file version (right-click → Properties → Details). PCS 7 v7.x installs v6.4 builds (e.g., 6.4.0.0 or higher); the WinCC flexible 2008 release notes reference earlier builds.
5. Check COM registration. Run regedit and search for s7tdpcox.dll under HKCR\CLSID. The InprocServer32 path should point to the SIMATIC NET v6.4 directory (typically C:\Program Files\Siemens\Automation\SIMATIC_NET\...). If it points to the WinCC flexible directory or is missing, registration is broken.
6. Run regsvr32 probe. Open an elevated command prompt: regsvr32 /u "%ProgramFiles%\Siemens\Automation\SIMATIC_NET\...\s7tdpcox.dll" then regsvr32 again to re-register. Watch for exit code 0 (success) versus 0x3 or 0x5 (load library / access denied).
7. Check the Event Viewer. Application and System logs frequently contain a SideBySide error or a load-library failure that pinpoints the conflict.
8. Compare release lists. Cross-reference the "Which SIMATIC software components are released for SIMATIC WinCC flexible 2008?" FAQ in the Siemens Support knowledge base. The answer explicitly excludes SIMATIC NET v6.4.

6. Resolution Paths

6.1 Path A - Clean separation (recommended)

Install either PCS 7 or WinCC flexible 2008 on the affected engineering workstation, never both.

1. Back up the OS project (folder copy and SIMATIC Manager Archive).
2. Open Control Panel → Programs and Features and uninstall, in this order: WinCC flexible 2008 (all SPs), SIMATIC NET v6.4, STEP 7, then PCS 7.
3. Reboot. Manually delete any residual Siemens\Automation folders and the SIMATIC NET registry keys under HKLM\SOFTWARE\Siemens.
4. Reinstall the stack you intend to keep. For a PCS 7 OS engineering host, follow the official PCS 7 v7.x Setup guide (SIMATIC NET v6.4, WinCC v7.0, STEP 7 V5.4/V5.5, then PCS 7).
5. For a WinCC flexible engineering host, install only WinCC flexible 2008 with the SIMATIC NET release listed in its compatibility matrix (typically v6.2 / v6.3). Do not install SIMATIC NET v6.4.
6. Open the project and verify the dialog is gone.

6.2 Path B - Dual boot / virtual machine

If the same physical PC must support both environments, isolate them.

• Use a second internal disk or a separate boot partition. Each OS image carries its own SIMATIC NET version.
• Alternatively, run the WinCC flexible 2008 instance inside a virtual machine (VMWare Workstation / Hyper-V) with its own bridged network adapter and the original SIMATIC NET build. PCS 7 v7.x is not officially virtualized for production OS servers; the VM is acceptable only for engineering.
• Map COM ports and CP 5512 / CP 5611 / CP 5612 PROFIBUS adapters to one OS at a time to avoid hardware contention.

6.3 Path C - Migrate WinCC flexible project to TIA Portal / WinCC

Long term, eliminate WinCC flexible 2008 by migrating the panel project.

1. Use TIA Portal's "Migrate project" function to convert WinCC flexible 2008 SPx projects (.hmi) to WinCC (TIA Portal) Comfort / Professional panels.
2. Verify variables, alarms, and scripts. Manually review Connect MySQL-style VB scripts because some WinCC flexible 2008-specific functions are no longer supported.
3. Replace the panel hardware if the migration tool flags incompatibilities (e.g., older OP 170 to a Comfort Panel TP700).
4. For PC-based visualization previously running on a WinCC flexible runtime PC, move to WinCC Runtime Professional inside TIA Portal and consolidate on a single Siemens stack.

7. SIMATIC NET Version Compatibility Matrix

8. Verification Checklist

1. Open the PCS 7 OS project → WinCC Explorer loads without the warning dialog.
2. Tag Management → S7-DOS → Connection status is "OK (established)" with the assigned AS.
3. Channel Diagnostics shows the connection in green and reports the correct S7 station address.
4. Activate the OS runtime; alarm logging, time stamping, and SFC chart visualization all populate.
5. If WinCC flexible is required on a separate host, push a panel image via ProSave / Ethernet and confirm the transfer completes without a version conflict message.
6. Run regsvr32 /s "%ProgramFiles%\Siemens\Automation\SIMATIC_NET\opc\s7asymox.dll" as a sanity check for the broader OPC family; success indicates the SIMATIC NET install is healthy.

9. Troubleshooting Matrix

10. Preventive Configuration Recommendations

• Treat each engineering workstation as single-purpose: one stack (PCS 7 OS OR WinCC flexible) per physical OS image.
• Maintain a documented image baseline. Use a deployment tool (Acronis, Veeam, MDT) to capture a known-good state after stack installation.
• Disable Windows auto-update on Siemens engineering hosts to prevent driver or VC++ redistribution interference. Approved update levels are listed in the PCS 7 v7.x release notes.
• Keep a copy of the WinCC flexible 2008 SPx installation source and its matching SIMATIC NET release (v6.3) on a separate partition or USB drive.
• When commissioning a panel, prefer TIA Portal migration (Path C). It removes the need for a parallel WinCC flexible stack and aligns the engineering workstation with the long-term Siemens roadmap.

11. SVG Diagram - Decision Flow

12. FAQ