SCADA servers, historians and engineering workstations run on Windows, and their problems first appear as an error number or an event ID. Knowing that 10060 means 'no answer at all' while 10061 means 'answered but nothing listening', or that event 1129 at logon is a network-at-boot problem, points straight to the cause.
Standards followed
Microsoft Win32, HRESULT and Windows Sockets error codesWindows event IDs: Service Control Manager, Kernel-Power, disk, Time-Service, GroupPolicy, NETLOGON, DistributedCOM, Schannel, Security auditingKerberos (RFC 4120) error codes
What it can do
- 89 entries, each with the meaning, typical causes on a SCADA system and what to check.
- Search by number in decimal or hex (a Win32 code entered as 0x8007xxxx is found too), by symbolic name or by word.
- Filter by area: network, time, domain logon, services and crashes, disk, DCOM/OPC DA, TLS, security, hardware.
Example problem
An IEC 104 client in the control centre logs 'connect failed, error 10061' for one RTU, and 10060 for another.
- 10061 (connection refused): the RTU answered but nothing listens on TCP 2404 — service off, wrong port, or client limit reached.
- 10060 (timed out): the other RTU never answered — off, unreachable, or a firewall drops the packets.
Two different faults: check the IEC 104 server settings on the first RTU, and the path and firewall to the second.
The list covers the codes most often met on SCADA hosts; it is not the complete Microsoft list. The event text and Microsoft's documentation remain the reference.