Since updating a Project from 3.12 to 3.13 I got following 2 effects:
1) Log message(s)
WCCILdata (0), 2015.03.17 18:25:59.294, IMPL, SEVERE, 54, Unexpected state, AlertHistory, commitUpdate, Tote Meldung lebt wieder !
System1:_MemoryCheck.FreeKB:_alert_hdl.3._state (Type: 11 Sys: 1 Dp: 89 El: 6 : _alert_hdl.3._state)
TIME_VAR 196608 Fri Mar 13 19:37:39 2015 563
Deleting Alerthistory has no effect, I even get more of those errors.
2) Special characters
The project was configurated in german (de_AT.iso88591), after the update datapoint characters ä, ö, ü are displayed wrong (rhomb with question mark) in para, I did not notice any functionaly error, Ascii out results in correct characters. Same (para) effect creating a new Dp manually or e.g. paneltopologies sumalert dp's.
Grateful for any suggestion
Project update 3.12 -> 3.13
- Gertjan van Schijndel
- Posts:634
- Joined: Mon Aug 02, 2010 10:37 am
Re: Project update 3.12 -> 3.13
Perhaps the last stored value is causing an alert and this error.
You could check if the 'Last value' is enabled in the para. If not you could enable it and check if this error is gone. When the error is gone you can disable the last value storage again.
You could check if the 'Last value' is enabled in the para. If not you could enable it and check if this error is gone. When the error is gone you can disable the last value storage again.
- peka
- Posts:19
- Joined: Wed May 15, 2013 4:46 pm
Re: Project update 3.12 -> 3.13
Thanks Gertjan, fixed the alerthistory error.
Just remains the 2nd para effect.
Just remains the 2nd para effect.
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Project update 3.12 -> 3.13
Hello,
the problem is that umlauts are normally not an allowed character for a datapoint name in projects using iso-languages.
The valid characters are A...Z, a...z, 1-9, _
At the moment we are discussing with our developers how the functions to check if a dp-name is valid need to be changed to work in iso- and UTF8-projects.
Best Regards
Leopold Knipp
Senior Support Specialist
the problem is that umlauts are normally not an allowed character for a datapoint name in projects using iso-languages.
The valid characters are A...Z, a...z, 1-9, _
At the moment we are discussing with our developers how the functions to check if a dp-name is valid need to be changed to work in iso- and UTF8-projects.
Best Regards
Leopold Knipp
Senior Support Specialist