WCCOAvalarch (6),, IMPL, SEVERE, 54, Unexpected state, DPE not present (ErrNum=4),

[cofelyhoogland]

We are using WinCC_OA 3.13 patch 8

We changed on 24.05.2017 the archive config from ValueArchive_0006 Tab Time of activiity:
- Archive file change never->monthly next automatic execution : 01.07.2017 02:00
-Files remain on hard disk 10->12.


There has been an archive file change at 01-06-2017.
Im am not sure the changes where made when the archive 006 was offline.

We get the folling errors in the log Viewer:
WCCOAvalarch (6), 2017.06.01 13:16:33.146, IMPL, SEVERE, 54, Unexpected state, DPE not present (ErrNum=4), ErrorDP: DpId = 15961, elementId = 5820, Archive::processWrite - Specified element not present in set belonging to specified time , [D:\\workspaces\\3.13\\workspace\\Exe\\DataNew\\ValueArchive\\Archive.cpp:2540]
WCCOAvalarch (6), 2017.06.01 13:16:33.146, IMPL, SEVERE, 54, Unexpected state, DPE not present (ErrNum=4), ErrorDP: DpId = 15961, elementId = 5820, Archive::processWrite - DPE does not exist in this SetFile, trying to add it, [D:\\workspaces\\3.13\\workspace\\Exe\\DataNew\\ValueArchive\\Archive.cpp:2554]

WCCOAvalarch (6), 2017.06.01 15:13:28.502, IMPL, SEVERE, 54, Unexpected state, DPE not present (ErrNum=4), ErrorDP: DpId = 15961, elementId = 5772, Archive::processWrite - Specified element not present in set belonging to specified time , [D:\\workspaces\\3.13\\workspace\\Exe\\DataNew\\ValueArchive\\Archive.cpp:2540]
WCCOAvalarch (6), 2017.06.01 15:13:28.502, IMPL, SEVERE, 54, Unexpected state, DPE not present (ErrNum=4), ErrorDP: DpId = 15961, elementId = 5772, Archive::processWrite - DPE does not exist in this SetFile, trying to add it, [D:\\workspaces\\3.13\\workspace\\Exe\\DataNew\\ValueArchive\\Archive.cpp:2554]

There are about 40 Errors in 6 days, they all have an unique elementId (f.i 5820 or 5772)

I can not see which DPE are giving the errors, but it looks like the archive is working normaly.

How can i solve this error?
And what is the problem?

[leoknipp]

With the CTRL function dpGetName() you can get the name for the DPE-ID given at the log message.
Maybe with the information which dp elements are affected you can get more useful information.

When the settings for the fileswitch are changed normally the log messages should not occur.
Maybe the _archive configuration at the dp elements was changed to save values in a different archive.

Best Regards
Leopold Knipp
Senior Support Specialist

[RudiKreiner]

Please be aware that if you delete a datapoint with an archive config, then recreate it with the same name and add the archive config, then it will get a different dpId and elementId.
This means that you cannot access the archived data for the datapoint at times before the deletion.
If you did this, that may have something to do with the error messages.
If the function dpGetName() does not return a name for the mentioned Ids that will pretty much confirm that something like this happened.

[cofelyhoogland]

When I use the function dpGetname() I can get the name of the DPE-ID.
I noticed that the first entry of a Dpe in the archive gives the error, the Dpe is logged in the archive
If the value of the Dpe is changed again, the error don't come, and the dpe is still logged correctly.

See also the topic: https://portal.etm.at/index.php?option= ... 15&id=4224

There has been a file change already
I think I have to restart archive_006 to solve the problems

Is that correctly?

[leoknipp]

In the last post you have written that the log message occurs only once for a dp element if a value is written for the first time.
In that case you have not to do anything as all values are saved in the archive and the message will not occur again if all dp elements have been set once or several times.

At my tests I could not find a situation where this log message occurs, even if values for the past are written.

Best Regards
Leopold Knipp
Senior Support Specialist