IMDTouchKnowledge BaseShop main store

Troubleshooting

Checking WinCC OPC registrations after a 7.0 setup

HMI and touchscreens Published 5 min read

Short answer

After a WinCC 7.0 setup, the file C:\Documents and Settings\All Users\Documents\Siemens\SimaticSecurityControl#tmpRules.xml records the installed components and their executable paths, including the three OPC servers and OpcEnum.exe. A missing entry there is the first thing to check when OPC communication fails; the fix is a setup repair, never a hand edit.

On this page
  1. Where does WinCC 7.0 record what setup installed?
  2. How do you read the file without changing it?
  3. Which ten components should the record list?
  4. Which executable entries does OPC communication depend on?
  5. What does a missing entry mean, and what is the fix?
  6. Does a recorded path prove the server actually works?
  7. Questions asked

After a WinCC 7.0 installation, setup leaves a written record of everything it registered: C:\Documents and Settings\All Users\Documents\Siemens\SimaticSecurityControl#tmpRules.xml. The file names the installed components and the executable paths recorded for them, including the three WinCC OPC servers and OpcEnum.exe. When OPC communication fails on a fresh install, read this file before touching DCOM settings or the project: one missing entry tells you the fault is in setup, not configuration. Below is what belongs in the record, how to read it without changing it, and the decision for each missing piece.

Where does WinCC 7.0 record what setup installed? #

Setup writes the record to C:\Documents and Settings\All Users\Documents\Siemens\SimaticSecurityControl#tmpRules.xml, a file kept by SIMATIC Security Control, which is itself one of the ten components the install registers on the station.

The file is XML. It holds the product names setup registered and the executable paths it recorded for them, so it works as the installation's own self-report: what setup believes it installed, and where it believes the programs live. The Documents and Settings\All Users\Documents segment is the Windows XP shared-documents location, which dates the station this record comes from; on later Windows versions, search the shared documents tree for the file name instead of typing the XP path.

How do you read the file without changing it? #

Open it read-only in a text editor or XML editor, search for the names below, and never save it back — this is a security rules record, and hand-editing it is unsupported.

If you want to annotate anything, copy the file to a new name and mark up the copy. The one safety note in this whole procedure belongs here: SIMATIC Security Control owns this file, and a corrupted rules file can strip the protection it configures on the station. Treat the original as evidence, nothing else.

Which ten components should the record list? #

The record names ten components, every one of which should appear in the file on a full install; the one that decides OPC behavior is SIMATIC WinCC OPC.

  • SQL Server 2005
  • SIMATIC WinCC
  • SIMATIC WinCC User Archive
  • SIMATIC WinCC OPC
  • SIMATIC WinCC WebNavigator
  • SIMATIC HMI DataMonitor Server
  • SIMATIC NET PC-Software
  • SIMATIC Communication Services
  • Automation License Manager
  • SIMATIC Security Control

SQL Server 2005 appears because WinCC keeps its runtime data there, and its two executables, C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe and C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe, sit among the recorded paths. Licensing is a separate matter handled by Automation License Manager, not by this file. A name that does not appear is a finding about setup, not noise: that component was not registered when the station was built.

Which executable entries does OPC communication depend on? #

Four of the sixteen recorded paths matter for OPC: the three WinCC OPC servers — Data Access, Alarm and Events, Historical Data Access — plus the enumerator OpcEnum.exe.

OPC function Recorded executable
Data Access — live tag reads and writes C:\Program Files\Siemens\WinCC\OPC\dataaccess\bin\sopcsrvrwincc.exe
Alarm and Events — alarm data C:\Program Files\Siemens\WinCC\OPC\AlarmEvent\bin\sopcaesrvrwincc.exe
Historical Data Access — archived values C:\Program Files\Siemens\WinCC\OPC\HistDataAccess\bin\sopchdasrvrwincc.exe
Enumerating local servers for browsing clients %windir%\system32\OpcEnum.exe

Check the executable that matches the function you are troubleshooting: a client reading live tags depends on the Data Access server, a client pulling archived values on Historical Data Access. The other twelve recorded paths cover the rest of the install — C:\Program Files\Siemens\WinCC\bin\CCProjectMgr.exe, C:\Program Files\Siemens\WinCC\bin\CCRtsLoader.exe, C:\Program Files\Siemens\SIMATIC.NET\simnetcom\pniopcac.exe and the SQL pair among them — so the same file answers completeness questions well beyond OPC.

What does a missing entry mean, and what is the fix? #

A missing component name means that piece was never registered by setup, and a missing executable path while the component is listed means registration did not finish — the fix in both cases is to run setup again, never to edit the file.

Worked example, a station where OPC reads fail right after installation:

  • Search the file for sopcsrvrwincc: 0 hits.
  • Search for CCProjectMgr: 1 hit, C:\Program Files\Siemens\WinCC\bin\CCProjectMgr.exe.
  • Search the component names for SIMATIC WinCC OPC: 0 hits.

Reading: the base WinCC installation recorded normally, the OPC option did not register, so 0 of the 4 OPC-critical entries exist. Decision: rerun WinCC setup with the OPC option selected. If instead the component is listed but an executable path is missing, run a repair of the existing installation. If all four OPC entries are present, registration is done and the fault lies further out.

Does a recorded path prove the server actually works? #

No — a matching entry proves only that setup recorded the executable, not that it launches, runs, or accepts clients; once all four OPC entries are present, move on to runtime checks.

Watch whether the server executable starts when a client connects, and confirm OpcEnum.exe is running. OPC DA traffic rides on DCOM, so machine-level DCOM security and the firewall decide whether a registered server ever receives the connection; SIMATIC Security Control is the component that manages rules for these executables, and its Windows Firewall rules show up under group names beginning with SIMATIC. If the connection direction itself is the doubt, settle which end is the OPC server and which is the client before blaming either side — the question that settles OPC UA links settles this one too. When registration and direction both check out, trace the path from the S7 PLC to the runtime instead of re-checking the install.

Questions asked

Is OpcEnum.exe a Siemens program?

No. OpcEnum.exe is the OPC server enumerator that arrives with the OPC Core Components, not with WinCC alone. Clients that browse for local OPC servers go through it, which is why WinCC setup records its path, %windir%\system32\OpcEnum.exe, next to the three WinCC OPC servers. If browsing finds nothing but direct connections work, check that this enumerator is running.

Can I add a missing OPC entry by editing the XML file myself?

No. The file is a record that SIMATIC Security Control writes, and nothing documents it as editable. Adding a path by hand does not register the COM server, does not create the firewall rule, and risks corrupting the security rules on the station. Run WinCC setup again with the OPC option selected, or run a repair of the existing installation.

My station runs a newer Windows version. Where is the file?

The documented path sits under Documents and Settings, the Windows XP shared-documents location. Later Windows versions changed that folder layout, so search the shared documents tree for the file name SimaticSecurityControl#tmpRules.xml instead of typing the XP path literally. The names to check inside the file stay the same.

All entries are present but the client still connects to nothing. What next?

Registration is then not the fault. OPC DA runs over DCOM, so verify that DCOM launch and access permissions on the server machine allow the client account, that the firewall permits the connection, and that the server executable actually starts when a client calls it. Only after those pass should you move on to tags, addresses, and the project itself.

Keep reading

  • How-to

    Connecting an Omron CV1000 PLC to WinCC over an OPC server

    Classic WinCC has no Omron CV-series channel, so the working route is an OPC server that speaks Host Link to the CV1000 and OPC DA to WinCC. Configure the server against the PLC first, prove one read, then build WinCC tags from the server's item addresses. Use the documented CV1000-CPU01-EV1 Host Link reference values: ASCII, 7 data bits, even parity, 2 stop bits, unit 00, 9600 or 19200 bps.

    HMI and touchscreens

  • How-to

    How to Address S7 PLC Outputs in a WinCC Flexible Tag

    A WinCC flexible tag must carry the address of the real PLC operand: Bool tags on Q0.1, Q0.2 and Q0.3 for the line, delta and star outputs. DB1.DBX0.0 is bit 0 of byte 0 in data block 1 and follows an output only if the PLC program copies it there — and the S7-200 CPU family has no data blocks at all.

    HMI and touchscreens

  • How-to

    How to Configure a Two-State Auto/Manual Switch in WinCC Flexible

    Pair the functions on each switch event: the Manual event runs SetBit on M10.0 and ResetBit on M10.1, and the Auto event runs SetBit on M10.1 and ResetBit on M10.0. After every transition exactly one mode bit is high, which is the state the PLC mode logic expects.

    HMI and touchscreens