Troubleshooting
Plant SCADA Connector shows connected but historian tags are NULL
Short answer
Connected status on both Connector ends proves the connections, not the reads: with Citect error 29, Bad User Parameters, the driver subsystem rejects the read before any value exists to store. Check the I/O Device special options and the variable tag data types first and leave the historian destination alone.
On this page
- Why does the Connector show Connected while every historian tag is NULL?
- Where are the Connector trace logs and how do you read them?
- What does Citect error 29 mean?
- Which I/O Device settings cause error 29?
- How can a variable tag data type leave a tag NULL?
- How do you tell a source-side fault from a destination fault?
- How do you verify the correction end to end?
- Questions asked
Both ends of the Plant SCADA Connector read Connected, every tag in the historian sits at NULL, and the management console repeats "failed to update tag value". The connections are healthy; the reads are failing. Open the Connector's trace logs and the failing read reports Citect error 29, which the Plant SCADA error help calls "Bad User Parameters" — a rejection raised in the driver subsystem, below the I/O Server, before any value exists to store. The two places that produce bad parameters are the I/O Device's special options and the variable tags' data types. Work them in that order and leave the historian destination alone.
Why does the Connector show Connected while every historian tag is NULL? #
Connected proves the Connector established its source and destination sessions and nothing else: with Citect error 29 the driver subsystem rejects the read's parameters before a value exists, so the historian stores NULL for every affected tag.
The status indicators cover the connection stage of the path only. A NULL value is the symptom at the end of the path, and on its own it cannot tell you which earlier stage failed. The console warning narrows the fault to the tag's update path, and error 29 narrows it further, to the Citect driver and I/O side rather than to the historian.
| What you see | What it establishes | What to check next |
|---|---|---|
| Source and Destination show Connected | Both Connector sessions are up | Tag-read errors in the trace logs |
| "failed to update tag value" in the console | One tag's update did not complete | Whether the variable read failed in the trace |
CitectErrorCode='29' in the trace |
The driver rejected the request's parameters | I/O Device special options, then the tag's data type |
Where are the Connector trace logs and how do you read them? #
The trace files sit in the folder C:\ProgramData\Wonderware\Citect SCADA Connector\Log, and the failing read shows up as two lines: a Citect client exception raised with error code 29, then a variable-reader line carrying CitectErrorCode='29'.
SchneiderElectric.Data.CitectClient.CitectException has been raised an error code:29CitectVariableReader, The connection returns a citect error. CitectErrorCode='29'
Open the trace before changing any configuration, and match the timestamp of the console warning to the trace lines around it. If the trace instead shows the source session itself dropping rather than a rejected read, you are in the case where the Citect connector to historian shows disconnected, and its checks replace these.
Illustrative example of the correlation: the console logs "failed to update tag value" at 09:14:07, and the trace holds both error lines stamped 09:14:07 — a difference of 09:14:07 minus 09:14:07 = 0 s. No historian write for that tag appears in the seconds after, because the read never produced a value. That pairing — warning and error line in the same second, with no write following — is what convicts the read stage.
What does Citect error 29 mean? #
Error 29 is the Plant SCADA documented code for "Bad User Parameters": the driver subsystem, the protocol-generic layer below the I/O Server, rejected the parameters of the request and passed the rejection up to the Connector's CtAPI client.
"Parameters" here are the values that shape each read the Connector asks for: the options configured on the I/O Device and the definition of the variable tag both feed them. The consequence is simple — no value was read, so nothing was forwarded, and the historian stored nothing for the tag. The code says nothing about the destination, so it is not evidence of a historian fault. The meaning is the one documented in the Plant SCADA online help error table, scoped to that product's driver stack.
Which I/O Device settings cause error 29? #
Check the failing I/O Device's special options first, because those options are the parameters the driver validates on every request, and an edited or mismatched option is the most direct way to raise error 29.
- Record the device name and the exact special options currently configured.
- Compare them against a known-good backup, a working device of the same type, or the device's documented settings.
- Correct one confirmed mismatch only, using the documented value.
- Repeat the read and re-read the trace before touching anything else.
Change one thing at a time so the next trace result can confirm or reject the suspected cause. And because the same I/O Server serves the plant-facing driver, make device-option changes under your site's change control, not as a live experiment.
How can a variable tag data type leave a tag NULL? #
A variable tag whose configured data type no longer matches the source variable fails the same parameter check — the driver cannot shape the value the Connector asked for, the read is rejected, and the tag stays NULL while its neighbors update.
Compare the failing tag's identity and configured data type against the source variable's definition and against a similar tag on the same device that still reads. Look for recent edits first: a type changed during a project update explains a tag that read yesterday and reads NULL today. The correct type comes from the source definition, not from trial.
| Configuration to check | Where it lives | What the trace shows after the fix |
|---|---|---|
| I/O Device special options | Plant SCADA I/O Device configuration | The read completes with no CitectErrorCode='29' |
| Variable tag identity and data type | Plant SCADA variable tag configuration | The value returns and the console warning stops |
How do you tell a source-side fault from a destination fault? #
Follow the trace stage, not the status lights: error 29 is logged by CitectVariableReader during the read, before any historian write is attempted, so this code places the fault on the source side until a write-stage error says otherwise.
Destination faults announce themselves at the write stage with different messages — a failed login, a schema or provisioning error, a rejected write. The historian database creation failing on a named instance is that family of fault, and its checks replace these when the trace fails at the database rather than at the driver. With error 29 on the read and both connections green, the destination is healthy on the evidence you hold.
How do you verify the correction end to end? #
Fix one confirmed mismatch, then prove the whole path: error 29 absent from a fresh trace, the console warning gone, and the historian value populated and moving with the source.
- Capture the tag, its current configuration, the warning time and the matching trace lines before changing anything.
- Correct the single confirmed mismatch — the special option value or the tag's data type.
- Let the tag read again on its normal cycle.
- Open the new trace at that timestamp and confirm no
CitectErrorCode='29'. - Confirm the historian holds the value and that it tracks the source across several cycles.
Illustrative check with numbers: a tag on a 5 s update cycle produces 60 ÷ 5 = 12 read attempts in a 60 s capture. Before the fix, that window holds 12 attempts, 12 error-29 lines and NULL at the historian; after the fix it should show 12 clean reads and 12 populated updates. If even one of the 12 still logs error 29, the mismatch is not fully corrected. The stage-by-stage discipline is the same one used when tracing a PLC tag from controller to historian display.
Decision: with both ends Connected and error 29 in the trace, work the I/O Device special options and then the variable tag data types, and leave historian connectivity alone. If both verify correct against known-good configuration and the error persists, capture the trace excerpt and the device configuration and take that package to your vendor support channel — the fault is then outside configuration.
Questions asked
Will restarting the Plant SCADA Connector clear error 29?
A restart rebuilds the two sessions the status page already shows as healthy, and it changes neither the I/O Device special options nor any variable tag's data type. If one of those is the rejected parameter, the same error returns on the next read of that tag. Copy the trace lines first, then restart only to force a fresh read, not as the fix.
Where do Plant SCADA's own logs live besides the Connector trace folder?
Plant SCADA writes its log files under the Windows ProgramData directory. Its alarm and trend logs follow the YYYYMMDD.TXT naming format inside the Citect SCADA DATA directory, so a day's file pairs easily with the Connector trace taken the same day. Error 29 itself only appears in the Connector trace, which records the CtAPI reads.
How do you turn on Connector trace logging when the folder is empty?
In the management console, go to Manage > Runtime Management, open Settings & Configuration, click Properties, then the Advanced tab, and enable Connector Trace Logging. Reproduce the failed tag update, read the new lines in the trace folder, and match them to the warning's timestamp. Drop the setting back once you have captured the evidence.
Does error 29 hit every tag on the plant or only some?
Only the tags whose request parameters are rejected. If every tag on one I/O Device is NULL while other devices still update, that device's special options lead the list. If a single tag is NULL while its device neighbors update, that tag's identity or data type leads. The scope of the NULLs points at the layer to fix.