how to fix Ignition OPC-UA Bad_ConnectionRejected refused on Kepware endpoint

By Sai Kiran Pandrala · Last verified: 2026-06-01 · Source: in-controller diagnostic help, controls-community forums (r/PLC, r/Robotics, r/CNC, r/Fanuc, r/KUKA, r/Cognex, r/labview), OEM service bulletins and changelogs, OEM service manuals

I was called out at 2am because Line 4 had a CNC throwing a how to fix Ignition OPC-UA Bad_ConnectionRejected refused on Kepware endpoint alarm on Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 and the swing-shift operator could not clear it - below is the route most field service techs walk in 2026 when this exact alarm hits during a production run. My muscle-memory shortcut is to stop, photograph the alarm history screen, capture the controller hour-meter, and work the fault in the order below rather than chasing the symptom. None of these steps require pinging the OEM hotline first unless the cell is under active warranty.

What how to fix ignition opc-ua bad_connectionrejected refused on kepware endpoint actually involves on Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026

On Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 the first three tools that earn their keep are Rockwell FactoryTalk Diagnostics Viewer (FTDiag), Wireshark for OPC-UA/OPC-DA packet capture, GE Proficy iFIX SCU diagnostic. Each of these surfaces a different layer of the fault - keep at least the first one in your fault-history notebook so the next time this happens you do not start cold.

For verification on Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026, the methods that survive contact with a real second-shift production workload are delete RDMDATA cache and .CAC tag file then restart FT View SE to rebuild tag db and export Ignition gateway logs via Status > Diagnostics > Logs > Download. Anything less than that and you are shipping on vibes.

Authoritative sources for Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 that I cross-reference before committing to a fix: aveva.com/support, docs.inductiveautomation.com, ge.com/digital/documentation. OEM marketing brochures and trade-press writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the cabinet.

Diagnose first, fix second

Seventh: run the dedicated diagnostic option for whichever subsystem the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 alarm points at. Drive suspected? Force a servo discharge and re-energize from the drive panel, then check the drive status LEDs for the green ready signal and the last-fault timestamp. Encoder suspected? Power down fully (lockout-tagout), check the encoder battery voltage at the back of the controller, re-home the axis on power-up. Cable suspected? Pin-check the encoder cable continuity end-to-end with a meter (EtherCAT or Profinet drop = use a cable tester, look for an LED link light at both ends). Each of these surfaces config that the controller silently inherits from a previous session, and 90 percent of "this used to work yesterday" reports trace to a stale parameter or a vibrated-loose connector. Capture the result of each step in your notes alongside the timestamp so you do not redo the discovery the next time.

Start by capturing the exact failure signal in writing before you change a single thing on your Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 setup. On the controller HMI that is the alarm code, the alarm message text, the timestamp, the controller hour-meter, and the part-count when the alarm hit. On the OEM diagnostic interface that is the fault-history dump (Fanuc alarm history, KUKA KSS log, Cognex In-Sight event log) plus the running program block number at the moment of fault. Photograph the HMI screen with the alarm panel open. Do not paraphrase. Most OEM service workflows will not even route the warranty case without the controller serial number, the alarm history dump, and the fault timestamp - the field service engineer pastes the alarm code straight into the OEM diagnostic tool and the first response is "we see the fault, here is what the controller logged."

Third pass: read the alarm code and the alarm message like an x-ray of your Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 cell. Servo faults (SRVO-023 servo overcurrent, SRVO-068 overheat, SRVO-014 motor overload) point at the drive, the cable, or the motor itself - 023 = instantaneous overcurrent during accel, 014 = sustained thermal overload during a heavy duty cycle, 068 = ambient or coolant fault on the drive heatsink. Axis or motion faults (4078 absolute position lost, OT001 over-travel, EX1043 spindle alarm) point at encoder battery, hardstops, or the spindle drive. Vision faults (Cognex In-Sight 5403 timeout, 5404 illumination, 5410 acquisition) point at trigger, lighting, or the GigE link. Cross-reference the alarm code against the OEM fault-code list - SCPI instruments will return the same hex code via SYST:ERR? that the front panel shows. If the same alarm cycles between SRVO-023 and SRVO-068 over a tight loop, the duty cycle is exceeding the drive thermal envelope - back off the feedrate or add a duty-cycle dwell.

Field notes from real Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 callouts

In Manufacturing work the cost of guessing is measured in scrap and downtime, so I read the Manufacturing release notes before I touch a setpoint, every time, no exceptions. My standing rule on any Manufacturing ticket is to baseline with Wireshark for OPC-UA/OPC-DA packet capture before touching a single wire, half the "failed" parts I have replaced over the years were not actually failed. My fastest sanity check after touching Manufacturing firmware is `open Ignition Gateway > Status > Connections > OPC and confirm endpoint state`; if that comes back inside spec, I close the ticket and head to the next bay.

Tools I actually reach for

For most Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 faults I start with Rockwell FactoryTalk Diagnostics Viewer (FTDiag), fall back to AVEVA Log Viewer (formerly Wonderware Log Viewer), GE Proficy iFIX SCU diagnostic, Wireshark for OPC-UA/OPC-DA packet capture when Rockwell FactoryTalk Diagnostics Viewer (FTDiag) cannot surface the answer, and keep GE Historian Administrator service status panel handy for the cases where neither answers. That ordering is not academic - it matches the layers of the fault as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the alarm screen is still open, not after I have already cycled controller power.

Verification I run before I call it fixed

Before I mark a Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 fault resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

tail GE Historian Administrator status to confirm collector heartbeat

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

verify WinCC OA S7Plus driver state via PARA > _Driver internal datapoint

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

check FactoryTalk View SE event log for 'TCP/IP port may be in use' message

Only when every line above runs clean do I close the loop and update my fault-history notebook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 detail, the disambiguation order I lean on is stable. I usually check forum.inductiveautomation.com for the ground-truth view on this part of Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026. I usually check aveva.com/support for the ground-truth view on this part of Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026. I usually check ge.com/digital/documentation for the ground-truth view on this part of Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026. OEM marketing brochures and trade-press writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

If the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 symptom started after an overnight firmware update, a drive swap, or a parameter edit, treat firmware and parameter set as the prime suspect. Roll the controller back to the previous firmware if the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 OEM supports rollback (most do via the maintenance bootloader). Restore the saved parameter set from your last known good backup (Fanuc all-parameter PUNCH OUT, KUKA archive, Cognex In-Sight job export) and rerun the program. If both rolled-back firmware and restored parameter set still fault with the same alarm and the same drive, you have a hardware-level or wiring issue. Decision point: if the rolled-back firmware still faults and the cell is under an OEM service contract, open the OEM hotline with the alarm history dump; on an out-of-warranty cell the path is the OEM forum or r/manufacturing with a minimal reproduction. Save the working firmware revision to your notes so the next rollback is a one-line "pin to firmware X."

Before any destructive step on a Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 cell, slow down and stage rollback. Snapshot the current firmware revision, the current parameter set (PARAM PUNCH OUT, KUKA archive, Cognex job export), the current ladder and HMI screens, the current I/O mapping, and the current member-roster of teach pendants registered to the cell to a notes entry first. Capture the failing photo, the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 alarm history dump, and the timestamp window. Photograph the cell from two angles: the controller HMI showing the alarm, and the cabinet showing the drive status LEDs. Then do the destructive step (clear a parameter, swap a drive, remove a teach pendant, restore a backup) inside a maintenance mode or a sister cell first, never the production cell directly. Capture the firmware revision, the safety-PLC permissions, the connected-pendant list, the cell operator roster, and the relevant fieldbus log snapshot to your notes before the destructive step. Decision point: if the cell is under an OEM service contract, the cheapest correct path is almost always to open the OEM hotline in parallel with the rollback - the OEM service engineer can confirm whether an OEM-side firmware push is responsible while you are still staging the change, which avoids a needless parameter edit if the fix is in the next firmware revision.

For Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 cells where duty-cycle limits or thermal envelopes are suspect, read the in-controller hints honestly. "Servo overcurrent" usually means you hit the peak current envelope of the drive during accel. "Motor overload" is the sustained-thermal signal on the motor winding. "Drive overheat" is the heatsink thermistor signal. Each is telling you the exact same thing in a Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026-specific dialect. Apply duty-cycle dwell for repeated-cycle programs (insert a 500ms dwell between high-load moves), reduce the rapid feedrate, and chunk a long cycle into smaller passes. Decision point: if you are hitting the thermal limit sustained rather than in bursts, the cell is undersized for the workpiece - upgrade the drive amperage rating or request a thermal margin review from the OEM with a written duty-cycle analysis; without it, dial back the throughput at the cell. Replay the failing program against a fresh test workpiece at half the feedrate to confirm the new safe envelope before pushing to the production cell.

Automate this fix so you do not do it twice

Multi-cell rate-limit + retry policy via shared client wrapper

When the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 integration runs across multiple cells or controller types, every consumer needs the same backoff, jitter, and idempotency behavior or one noisy cell will starve the rest of the MES poller. Wrap the OEM SDK or fetch call in a thin client that reads the rate-limit headers (X-RateLimit-Remaining, Retry-After, x-ratelimit-reset), applies full jitter (base 200ms, cap 30s, max 5 retries), and de-dupes writes by a stable key (the controller cycle id, the fieldbus drop external id, the destination MES record id). Emit simple log lines tagged with the cell id so a fieldbus burst on one cell shows up in the same log as the downstream cascade.

# Python - manufacturing controller API wrapper with full-jitter retry
from tenacity import retry, wait_random_exponential, stop_after_attempt, retry_if_exception_type
import requests class RateLimited(Exception): pass @retry( wait=wait_random_exponential(multiplier=0.2, max=30), stop=stop_after_attempt(5), retry=retry_if_exception_type(RateLimited),
)
def call_manufacturing(method, path, token, payload=None): r = requests.request(method, f"https://controller.plant.local{path}", headers={"Authorization": f"Bearer {token}"}, json=payload, timeout=10) if r.status_code == 429: raise RateLimited(r.headers.get("Retry-After")) r.raise_for_status() return r.json()

Monitor + alert via Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 OEM diagnostic reports, alarm history, and plant dashboard ingestion

For the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026, the most useful long-running telemetry is the OEM diagnostic reports + alarm history shipped to a plant dashboard (Grafana with a CSV source, Ignition with a tag history, the fab MES OEE per SEMI E10, a Notion database via the API) and graphed on a single view. Pair that with synthetic monitoring (a small script that triggers the failing cycle or runs the failing test sequence every 5 minutes from at least two cells) so a fleet-level regression lights up before teammates report it. Subscribe the on-call inbox or a private Teams channel to the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 OEM service bulletin (Atom/RSS or vendor portal webhook) plus the OEM service-status handle so an open bulletin self-correlates with the synthetic failures.

# Tiny synthetic monitor - hit the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 controller health endpoint every 5 minutes
while true; do curl -s -o /dev/null -w "%{http_code} %{time_total} $(date -Iseconds)\n" \ -H "Authorization: Bearer $TOKEN" \ https://controller.plant.local/api/v1/me \ >> /var/log/manufacturing-synth.log sleep 300
done

Automate Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 parameter + I/O mapping snapshots via OEM utility or API

On the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026, regular parameter and I/O snapshots catch silent parameter drift, recipe edits, and stale safety-PLC permissions well before the cell starts faulting in prod. Pair OEM health checks (the OEM diagnostic SDK, the controller users API, the fieldbus device listing) with a license-validity check so both OEM-side and cell-side issues land in one folder. Run the scheduled task on a control-plane logger PC (a hardened IPC at the cell, a GitHub Actions runner against the cell-controller VPN, a small Linux box at the line) under a tightly scoped service account that mirrors the maintenance role.

# List cell operator roster + safety-PLC roles
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/operators \ > manufacturing-operators.json
# List active fieldbus drops + their last-link-up timestamp
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/fieldbus_drops \ > manufacturing-fieldbus.json
# Validate the maintenance license token itself
curl -H "Authorization: Bearer $CONTROLLER_TOKEN" \ https://controller.plant.local/api/v1/me \ > manufacturing-me.json

Common pitfalls and what to watch for

Read-only validation before any write is the single step most Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 fixes skip, and it is the step that lets you roll back when a fix backfires. Photograph every existing parameter page (the axis parameters, the spindle parameters, the safety parameters, the I/O mapping, the recipe library), capture the failing photo in a notes entry, export the relevant log to CSV if the controller supports it (the OEM diagnostic tool fault-history export, the PMC log download), and photograph the HMI alarm history showing the failing window before any change. On Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 cells with multiple operating modes (manual jog, MDI, auto) record the firmware revision, the parameter state, and the I/O mapping in each before toggling anything, because a "fix" pushed only to manual mode is a known regression vector when auto mode has a different interlock set.

The mirror-image mistake is confusing a cell-level symptom with an OEM fault on Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026. A persistent SRVO-023 is often a workpiece-level change pushed by the production team rather than a Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 bug. A "program not loading" can be a renamed program rather than a deleted one. A "trigger not firing" is frequently a vibrated-loose sensor cable or a contaminated lens rather than an OEM-side regression.

Verify the fix worked

• Reproduce the original faulting cycle against Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 on the same cell AND a sister cell with the same recipe. If the alarm or fault code still surfaces on any cell, you have not fixed it.
• Watch for 24 to 48 hours via the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 controller alarm history + the fieldbus log + your fault-history notebook. Cached fault states and stale fieldbus link state mask slow-burn drift and intermittent fieldbus issues.
• Smoke-test under realistic load: replay the cycle against a test workpiece for at least 30 minutes at your normal production feedrate, log success / alarm and the timestamp per attempt to a notes file.
• Capture the new state in a fault-history notebook entry so the next time this happens you do not rediscover it. Note firmware revision + parameter set + I/O mapping + failing photo + verbatim alarm string + fix applied. Push to a plant-wide maintenance wiki if your plant uses one.
• If the fix involved a maintenance-token rotation or a parameter set change, commit the new token to your password manager and photograph the parameter dump for archival.

Safety, rollback, blast radius

• Test in a Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 maintenance mode or on a sister cell first before any change that touches the production cell. Snapshot the firmware revision, the parameter set, the I/O mapping, and the safety-PLC permissions before changing anything.
• Apply the principle of least surprise when granting teach-pendant access or safety-PLC permissions. Review the operator roster against the people who actually need access - extra teach pendants are extra blast radius.
• Use idempotent cycles where the Manufacturing, SCADA/MES Platform Error Codes (Rockwell FactoryTalk, AVEVA Wonderware, Inductive Automation Ignition, Siemens WinCC, GE Proficy), 2026 controller supports it (the OEM cycle-id de-dupe, external id keys on MES records) so a re-run cycle does not double-count parts or duplicate scrap records.
• Know your rollback path. Firmware rollback is a one-line OEM utility load; a maintenance-token rotation is reversible if you kept the old token in the password manager during cutover; a parameter set change is reversible only if you saved the previous archive.
• For cell-wide or plant-wide changes, line up a maintenance window with production scheduling before pushing through the OEM utility.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to recover Inductive Automation Ignition OPC-UA Bad_SecurityChecksFailed connection error
• how to clear Ignition gateway 'Failed to create subscription' faulted OPC-UA after upgrade
• how to recover Ignition tag provider 'Bad' write quality to AB Logix device
• how to fix Ignition 'Type com.inductiveautomation.OpcUaServerType is not a known server type' after 8.1 upgrade
• how to clear AVEVA System Platform GR node engine restart loop on cross-deploy
• how to clear FactoryTalk Linx subscription failed read-only mode after primary loss