PVSS00valarch - IMPL/SEVERE - Can't write value, maxCount reached

Enclosed you'll find the explanation for a log-message which can occur during runtime. The log-messages are written to the PVSS_II.log-file.

PVSS00valarch(0), 2013.01.12 09:25:27.911, IMPL, SEVERE, 54, Unexpected state, Can't write value, maxCount reached (ErrNum=8), ErrorDP: DpId = 1135, elementId = 916, ArchivSet::writeObject - Maximal values already written, have no place to write new one , [ArchivSet.cpp:3903]

Log-messages with symbolic names:

PVSS00valarch(0), <TIMESTAMP>, IMPL, SEVERE, 54, Unexpected state, Can't write value, maxCount reached (ErrNum=8), ErrorDP: <DP-element-ID>, ArchivSet::writeObject - Maximal values already written, have no place to write new one , [ArchivSet.cpp:3903]


This log-message describes that some values for the given DP-element-ID could not be saved in the current archive file. Converting the DP-element-ID into to a dp-element name is possible with the CTRL-function dpGetName().

If the threshold for the fill grade is reached a new archive file is created. In this case the values are written very fast and therefore the limit was reached before the new file was created.

When the values can be saved again the following log-message is written:
PVSS00valarch(0), <TIMESTAMP>, IMPL, SEVERE, 54, Unexpected state, can write again!, [ArchivSet.cpp:4011]

You can make a historical query for the given dp-element to see which values have been saved in the database.
Maybe with this information you can find the cause for the fast update rate of the dp-element and make modifications in your project to avoid the log-entries and loss of data the next time.