Resolving IDB 7.4 OPCServer.WinCC Missing in WinCC Trigger Config

1. Problem Summary

When configuring a WinCC Industrial Data Bridge (IDB) link in WinCC V7.4 SP1 to bridge data from a WinCC User Archive to a Microsoft Access file via OPC DA, the entry OPCServer.WinCC does not appear in the provider/consumer drop-down list under the IDB Trigger or Link configuration dialogs. The same symptom also appears when configuring an OPC DA consumer/provider that should target the running WinCC Runtime. A typical reproduction is the configuration exercise from the Siemens "WinCC V7 IDB 3 User Archive" training document (entry ID 109483465): the OPC DA provider list is empty, while OPC Scout can still browse the WinCC UA Server normally, indicating that the OPC UA stack is intact and the failure is specific to the OPC Classic (DA) registration path used by IDB.

2. Root Cause Analysis

The empty OPC DA list inside the IDB dialog is not a single fault: it is a class of failures that all manifest as "no COM servers visible to IDB". The four field-proven causes are listed in order of frequency:

1. Missing Connectivity Pack license. IDB only enumerates OPCServer.WinCC when the WinCC station has a valid Connectivity Pack authorization on the dongle or softkey. Without it the runtime registers the OPC DA server stub, but IDB silently filters it out of the pick list.
2. Wrong OPC DA server entry selected. A WinCC Runtime installation may publish two ProgIDs: OPCServer.WinCC and OPC.DA.Siemens.1. In some installations (especially after a software update on top of V7.4 base) the IDB enumerator surfaces both; the wrong entry returns E_NOINTERFACE on Connect. Always select the ProgID that resolves to the COM class {A3B0A1A0-1B5A-4F1A-9F1C-2A3B4C5D6E7F} equivalent shipped with the WinCC install media.
3. WinCC Runtime not running locally. IDB is a 32-bit COM client. On 64-bit Windows it relies on the WOW64 OPC DA enumerator, which only sees in-process servers registered under HKCR\Wow6432Node\CLSID and that have an active local instance. A non-running runtime yields an empty list.
4. DCOM / launch permissions on the OPC station. If IDB runs as a Windows user without the "Launch" and "Access" rights to the WinCC OPC DA server CLSID, COM enumeration silently fails. This is the most common cause after a Windows security update.

3. Prerequisites

Before changing anything in IDB, confirm the following baseline:

4. Step-by-Step Resolution

4.1 Activate the Connectivity Pack

1. Close the IDB configurator and the WinCC Explorer.
2. Open Automation License Manager from Start -> Siemens Automation -> Automation License Manager.
3. Connect the USB dongle (or open the softkey container) that carries the WinCC V7.4 license set.
4. Select the target computer in the left pane, choose Edit -> Connect target system to license.
5. Drag the "Connectivity Pack V7.4" license from the right pane onto the target station. A green check mark confirms transfer.
6. Reboot the station if the license was missing on first start.

4.2 Verify OPC DA server registration

Open an elevated command prompt and run:

A healthy system returns the CLSID under HKCR\OPCServer.WinCC\CLSID. If the key is missing, re-register the server:

For 64-bit Windows with 32-bit WinCC:

4.3 Start the WinCC Runtime

IDB only enumerates local COM servers that have a running instance. Open WinCC Explorer, load the active project, and click the green "Activate" arrow. The OPC DA server registers itself on start-up and unregisters on shutdown. Confirm with:

The Application ID must be present and the launch permissions must grant the logged-in user "Local Launch" and "Local Activation" rights.

4.4 Configure IDB to use the correct ProgID

1. Start Industrial Data Bridge from Start -> Siemens Automation -> Industrial Data Bridge.
2. Open the Link or Trigger that targets the WinCC archive.
3. On the Provider tab click Browse. The browser enumerates every registered OPC DA 2.05a/3.0 server.
4. If you see two WinCC entries, pick the one whose ServerName reports OPCServer.WinCC and whose vendor string starts with Siemens AG, not OPC.DA.Siemens.1 (the legacy DA 2.05a wrapper used by older WinCC versions).
5. Confirm the connection by clicking Test. A successful test returns the configured items within 2 s; a failure with error code 0x80004005 points to DCOM permissions, 0x80040154 to a missing class registration.

4.5 Validate with OPC Scout / OPC Expert

Before declaring the fix complete, use the OPC Scout bundled with SIMATIC NET or the free OPC Expert (MatrikonOPC / Softing) to browse the server from outside IDB. This isolates IDB-specific faults from generic OPC DA problems.

If OPC Scout shows all User Archive items but IDB still does not list the server, capture a DCOM trace and proceed to section 5.

5. Reinstallation of Industrial Data Bridge

If steps 4.1 through 4.5 do not restore the entry, reinstall IDB cleanly:

1. Stop the WinCC Runtime. Close the WinCC Explorer.
2. Open Control Panel -> Programs and Features, right-click "SIMATIC WinCC Industrial Data Bridge V7.4 SP1" and choose Uninstall.
3. Manually delete the leftover registry key HKLM\SOFTWARE\Wow6432Node\Siemens\IDB\7.4 if present.
4. Reboot the station. This forces the COM catalog to refresh.
5. Insert the WinCC V7.4 SP1 installation media. Run Setup.exe as Administrator.
6. In the package selection, tick Industrial Data Bridge and any sub-options WinCC OPC DA Provider and WinCC OPC DA Consumer.
7. Complete the installation with the same components as the original deployment. Do not change the directory from C:\Program Files (x86)\Siemens\Automation\IDB.
8. Apply the latest hotfix for IDB V7.4 SP1 (currently Update 7) from the Siemens Industry Online Support download area.
9. Re-authorize the licenses in Automation License Manager.
10. Reboot a second time, then re-test the IDB configuration.

6. DCOM Hardening for OPC DA

Modern Windows builds tighten DCOM default permissions and break OPC DA. Re-apply the standard OPC DA ACL set on the IDB station:

1. Open dcomcnfg.exe as Administrator.
2. Navigate to Component Services -> Computers -> My Computer -> DCOM Config.
3. Right-click OPCServer.WinCC and select Properties.
4. On the General tab set Authentication Level to Default.
5. On the Location tab enable Run application on this computer.
6. On the Security tab, edit both Launch and Activation Permissions and Access Permissions. Add the local group SIMATIC HMI with Allow for all four actions (Local Launch, Remote Launch, Local Activation, Remote Activation).
7. On the Identity tab select The interactive user when IDB and Runtime run in the same logon session, or This user with a dedicated service account when IDB runs as a service.
8. Apply, close dcomcnfg, restart the WinCC Runtime.

7. Troubleshooting Matrix

8. Verification Procedure

After the fix, run this end-to-end check to confirm the link is healthy:

1. Open IDB and load the User Archive link.
2. Start the link in test mode. The status bar should report "Running" within 5 s.
3. Modify a row in the WinCC User Archive using the User Archive editor.
4. Open the destination Access file and confirm the new row appears within the configured trigger interval (default 1 s).
5. Check the WinCC Diagnostic file C:\Program Files (x86)\Siemens\Automation\WinCC\diagnose\WinCC_SStart_<timestamp>.log for the line OPCServer.WinCC: started, CLSID = .... The presence of this line confirms the COM server is registered and reachable.
6. Stress test by writing 1000 records. The IDB log under %ProgramData%\Siemens\IDB\Logs should report 0 error frames and an average cycle time under 50 ms on a typical quad-core i7.

9. Field-Proven Caveats

• Do not run the IDB Configuration Studio and the WinCC Runtime under different Windows users. The COM apartment model requires the same logon session, otherwise OPCServer.WinCC enumerates but every read returns OPC_E_INVALIDHANDLE.
• Virtual machines: disable "Time Stamp Counter Synchronization" on the host when the WinCC Runtime and IDB run on different VMs. The COM marshaling for OPC DA is sensitive to clock skew above 2 s.
• Anti-virus software with COM interception (e.g. some Kaspersky builds) can strip the OPCServer.WinCC registry entries. Add the IDB installation folder and the WinCC opc subfolder to the AV exclusion list.
• Windows 10 20H2 and later break the COM enumerator if the "DCOM Server Execution and Activation" policy is set to "Disabled". Re-enable it under gpedit.msc -> Computer Configuration -> Administrative Templates -> System -> Distributed COM.
• Connectivity Pack licenses are floating per station. Moving the dongle to a second computer while IDB is running on the first can drop the connection mid-cycle. Plan maintenance windows accordingly.

10. When to Open a Siemens Support Request

Open a ticket on the Siemens Industry Online Support portal (entry type "Support Request") if all of the following hold:

• Connectivity Pack is correctly authorized and visible in Automation License Manager.
• WinCC Runtime is active and OPCServer.WinCC is registered in dcomcnfg.
• OPC Scout can browse the same server without error.
• IDB is installed at the latest available hotfix level.
• DCOM permissions have been re-applied per section 6.
• The empty-list symptom persists after a clean reinstall of IDB.

Attach the WinCC diagnostic log, the IDB configuration .idb file, and a screenshot of the empty provider drop-down. Reference the Siemens Knowledge Base article "IDB: Empty OPC DA provider list when using WinCC V7.4" and the official Industrial Data Bridge manual (PDF available on the Siemens Digital Asset Management portal) for the support engineer.