Hi all,
I've recently begun experiencing the error below on starting WinCC OA. I've checked the datapoint configuration but can't find anything wrong with it. Does anyone know what this means, and how to fix it?
WCCILdata (0), 2018.03.13 17:03:31.855, IMPL, SEVERE, 54, Unexpected state, AlertHistory, commitUpdate, Alert not in datasets nor in living DB
System1:PLCXYZ_Comms.ConnState:_alert_hdl.3._state (Type: 348 Sys: 1 Dp: 1234 El: 2 : _alert_hdl.3._state)
Kind regards,
Angus Heyworth
Severe Error 54 on Starting - Unexpected State
- AngusETM
- Posts:37
- Joined: Tue Apr 25, 2017 4:48 pm
Severe Error 54 on Starting - Unexpected State
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Severe Error 54 on Starting - Unexpected State
Please check if there is an alert pending for this dp element and which time stamp it has. Maybe the time stamp is quite old.
Which type of alert archiving is used in this project?
Which WinCC OA version + patch level is installed?
Best Regards
Leopold Knipp
Senior Support Specialist
Which type of alert archiving is used in this project?
Which WinCC OA version + patch level is installed?
Best Regards
Leopold Knipp
Senior Support Specialist
- AngusETM
- Posts:37
- Joined: Tue Apr 25, 2017 4:48 pm
Re: Severe Error 54 on Starting - Unexpected State
Hi Leopold,
Yes, the error only occurs when an unacknowledged alert exists for the value. When it's acknowledged and WinCC OA is restarted, the error does not occur.
We have several other instances of the same datapoint which do not have the same problem. The difference is that the problematic datapoint has some differences in its configuration
The normal datapoints all have #AlertValue configs with Manager/User "ASC", however the problematic datapoint has four additional lines with Manager/User "UI".
We're using an Oracle database via the RDB manager.
WinCC OA 3.11-SP1
Yes, the error only occurs when an unacknowledged alert exists for the value. When it's acknowledged and WinCC OA is restarted, the error does not occur.
We have several other instances of the same datapoint which do not have the same problem. The difference is that the problematic datapoint has some differences in its configuration
The normal datapoints all have #AlertValue configs with Manager/User "ASC", however the problematic datapoint has four additional lines with Manager/User "UI".
We're using an Oracle database via the RDB manager.
WinCC OA 3.11-SP1
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Severe Error 54 on Starting - Unexpected State
The information which process/user has modified the configuration for the _alert_hdl config does not have an effect on how the config works.
If you see additional lines for the same config you have probably used the option "H" at the ASCII export. Then also the configuration history for the _alert_hdl config is also exported.
The line with the newest timestamp (seconds since 01.01.1970) for a dp-element/config are those with the current configuration.
Best Regards
Leopold Knipp
Senior Support Specialist
If you see additional lines for the same config you have probably used the option "H" at the ASCII export. Then also the configuration history for the _alert_hdl config is also exported.
The line with the newest timestamp (seconds since 01.01.1970) for a dp-element/config are those with the current configuration.
Best Regards
Leopold Knipp
Senior Support Specialist
- AngusETM
- Posts:37
- Joined: Tue Apr 25, 2017 4:48 pm
Re: Severe Error 54 on Starting - Unexpected State
Ah ok, thanks Leopold. I've been using the "regular export" format in the ASCII Manager.
We managed to fix the problem by deleting the datapoint, then then recreating it with the same ID Number using an export from a datapoint of the same type as a template.
Still not sure exactly what the problem was but happy it's fixed
We managed to fix the problem by deleting the datapoint, then then recreating it with the same ID Number using an export from a datapoint of the same type as a template.
Still not sure exactly what the problem was but happy it's fixed