Resolving pniopcac.exe Line 580 Warning During STEP 7 V5.5 SP4

Problem Summary

Engineers performing a clean install of SIMATIC STEP 7 V5.5 SP4 on Windows workstations commonly encounter a recurring pniopcac.exe - line 580 assertion warning during the Component Configuration phase of the setup. When the installer is interrupted (or aborted) and the workstation subsequently boots without the original external media mapped to the original drive letter, the warning reappears on every logon and a secondary "E:\ drive not valid" error aborts any repair attempt.

The root cause is almost always an orphaned absolute path left behind by a previous installation that was performed from an external USB or removable HDD (typical example: E:\Siemens\Automation\...). Because SIMATIC installers use the installer's launch drive letter to populate shell-folder and HKLM\SOFTWARE\Siemens\... registry values, removing the source drive without first uninstalling the product produces dangling references that the PN IO OPC subsystem cannot resolve.

Affected Software Stack

Understanding pniopcac.exe and the PN IO OPC Layer

pniopcac.exe is the PROFINET IO OPC Common Architecture Component shipped inside SIMATIC NET. It acts as the bridge between the PROFINET IO base driver (PNIO) and the classic OPC DA 2.0 / 3.0 server (OPC.SimaticNET). The executable is registered as a Windows service and writes its working directories, logging path, and security configuration to the registry under:

The assertion at line 580 is triggered by the Siemens.Automation.ObjectFrame.Proxy.ACFactory when it tries to bind to a COM proxy whose module path no longer exists. The wrapper then pops a debug-style assertion dialog because the path validation routine cannot LoadLibrary() the dependent Siemens.Simatic.S7Comm.dll.

Root Cause Analysis

The chain of events that produces this failure is well documented:

1. STEP 7 V5.5 SP4 is launched from E:\Install\Step7\Setup.exe on a removable drive.
2. The MSI captures E:\ as the installer's source media path in the registry and in %APPDATA%\Siemens\S7WSInfo.xml.
3. CCleaner (or manual Add/Remove Programs cleanup) removes the visible programs but leaves the SIMATIC-specific COM registrations, file-type associations (.s7p, .s7l), and OPC class IDs behind.
4. The user reconnects the external drive later with a different letter or removes it permanently.
5. The PNIO OPC service tries to resolve its module path on boot and finds nothing at E:\Siemens\Automation\PNIO\..., throwing the assertion.

Siemens Support entry ID 189025 — "How do you uninstall STEP 7 completely including all the software packages?" describes the official removal procedure that prevents exactly this scenario. Any deviation from that procedure will leave residual references in:

• HKLM\SOFTWARE\Siemens (and the 32-bit mirror under Wow6432Node)
• HKCR\CLSID\{...OPC.SimaticNET...}
• %ProgramFiles%\Siemens\Automation
• %CommonProgramFiles(x86)%\Siemens\Shared

Pre-Remediation: Complete Uninstall per Siemens ID 189025

Before reinstalling or repairing, run the documented uninstallation in the exact order shown. Skipping the order is what produces the original failure mode.

1. Insert the STEP 7 DVD (or mount the ISO) and keep its drive letter constant (do not eject until step 7).
2. Open Control Panel → Programs and Features and uninstall, in this order:
   1. SIMATIC NET
   2. STEP 7 V5.5
   3. S7-PCT (if present)
   4. SINAMICS Starter
   5. TIA Portal V13 (use the TIA removal tool Siemens_TIA_Portal_V13_Uninstall.exe from the DVD)
   6. Automation License Manager
   7. Remaining Siemens-named entries
3. Delete residual folders: rmdir /s /q "%ProgramFiles%\Siemens" rmdir /s /q "%ProgramFiles(x86)%\Siemens" rmdir /s /q "%CommonProgramFiles%\Siemens" rmdir /s /q "%CommonProgramFiles(x86)%\Siemens" rmdir /s /q "%APPDATA%\Siemens" rmdir /s /q "%PROGRAMDATA%\Siemens"
4. Open regedit as Administrator and remove: HKLM\SOFTWARE\Siemens (and Wow6432Node) HKCU\SOFTWARE\Siemens HKCR\Siemens.* file-type associations
5. Reboot and confirm that Task Manager → Startup no longer lists any pniopcac.exe or s7oiehsx.exe entry.

STEP 7 V5.5 SP4 Installation Prerequisites

Step-by-Step Resolution Procedure

This procedure restores a healthy STEP 7 V5.5 SP4 + PNIO OPC environment without a full reformat. It is the validated recovery path used when only the pniopcac.exe line 580 warning is reported.

1. Copy the install media to a fixed disk. Create C:\Install\Step7V55SP4\ and copy the entire DVD image (or extract the ISO with 7-Zip) into it. Confirm the folder contains Setup.exe, S7SETUP.MSI, and the CD_1...CD_N directories.
2. Map the source to a stable drive letter. Use subst E: "C:\Install\Step7V55SP4" so the installer sees the same letter it expects. Important: do not run this from cmd.exe launched as a different user; the mapping is per-logon-session.
3. Repair the existing installation first. Launch E:\Setup.exe, choose "Repair existing installation", and accept the default component selection. The repair re-registers pniopcac.exe, restores the OPC.SimaticNET class ID, and rewrites the registry path to point at the local %ProgramFiles(x86)%\Siemens\Automation tree. This step alone closes the bug in the majority of cases and is the resolution documented in the original incident.
4. If repair fails (missing source), perform a clean install with the same fixed-disk folder from step 1. The installer will detect the orphaned PNIO OPC entries and prompt to overwrite them.
5. Reboot before connecting to a PLC. After the setup completes, do not skip the reboot; the PNIO OPC service writes its DCOM launch permission set during shutdown.
6. Reinstall TIA Portal V13 and Starter 4.4 after STEP 7 V5.5 SP4 is healthy. TIA V13 detects the existing SIMATIC NET and shares the OPC proxy.

Verification

Run the following checks in sequence. Each step must pass before the next.

1. Service status. Open services.msc and confirm SIMATIC NET OPC Server is set to Automatic and state is Running. sc query "S7OpcService" | find "STATE" should report RUNNING.
2. No assertion on next logon. Log off, log on. The pniopcac.exe dialog must not appear. Verify in Event Viewer → Application that source = pniopcac.exe entries are absent or informational only.
3. Module load test. where pniopcac.exe must return C:\Program Files (x86)\Siemens\Automation\PNIO\bin\pniopcac.exe. reg query "HKLM\SOFTWARE\Siemens\Automation\InstalledComponents\PNIO_OPC" /v InstallPath must return a path on C:\, never on E:\ or another removable letter.
4. OPC connectivity test. Launch the OPC Scout V10 (installed with SIMATIC NET). Add a server OPC.SimaticNET. Browse tags and confirm a live S7 connection is reachable (e.g., S7:[S7 connection_1]DB1,BYTE0).
5. STEP 7 online test. Open SIMATIC Manager, create an Accessible Nodes search via PLC → Accessible Nodes. The CP must appear without a yellow triangle.
6. Repro check on the original drive. If the original error referenced E:\, confirm that no HKLM or HKCU value still contains the literal string E:\Siemens: reg query HKLM /s /f "E:\\Siemens" 2>nul reg query HKCU /s /f "E:\\Siemens" 2>nul Both must return zero matches.

Alternative Recovery Methods

Field-Proven Diagnostics Matrix

Preventing Recurrence

• Always perform the STEP 7 V5.5 SP4 installation from a fixed disk. If only a USB installer is available, copy it to C:\Install\... first and run from there.
• Use the documented uninstall sequence in Siemens Support entry 189025 whenever retiring a workstation. Do not rely on third-party registry cleaners (CCleaner, Revo, etc.) for SIMATIC products; their heuristics do not understand the OPC class-ID tree.
• Pin the source-drive letter by setting a persistent subst mapping via a one-time scheduled task at logon: schtasks /create /tn "MapStep7Media" /tr "subst E: C:\Install\Step7V55SP4" /sc onlogon /rl highest.
• Disable the Siemens AutoStart entry on developer VMs that never need live PLC connectivity; the OPC service can be started manually from SIMATIC Manager when required.
• For TIA Portal projects that also depend on STEP 7 V5.5, keep both installations in Repair mode awareness — patching one without the other is the leading cause of cross-version registry drift.

Standards and Reference Material

• Siemens Support entry 189025 — Complete uninstallation of STEP 7.
• Siemens Industry Online Support root: support.industry.siemens.com.
• SIMATIC NET V8.2 SP1 documentation: search the Siemens Support portal for ID 50229241 (PN IO OPC manual).
• PROFINET Installation Guide (PNO document 8.062): profinet.com — reference for OPC DA/UA integration over PNIO.

FAQ