Pmon wants to write to progs file

[RudiKreiner]

When we start our WINCC OA V3.14 projects, we always get this message in the log viewer:

WCCILpmon1:WCCILpmon (1), 2016.06.20 08:15:44.588, SYS, SEVERE, 126, PmonTable: could not open the progs-file for writing. Error 13: Permission denied

That makes sense insofar as we have write protected our progs file because we have it in our SVN repository and need to check it out before modifiying it.

What I don't understand is what does the pmon want to write into the progs file anyway, and why?

Can anyone enlighten me on this, please?

[mkoller]

AFAIR this stems from the time where pmon was introduced, where the start of pmon could detect an old progs file (or on windoze read the old registry settings), where then the new format of the progs file was created and Pmon had to write it back to disc afterwards.

[RudiKreiner]

Does that me we can safely ignore this message?

Does it also mean that the message could be removed from the pmon manager because it doesn't try to write at all?

[mkoller]

You can ignore it.
We can not remove the writing code, since it can still convert an old file (we sometimes have customers with very old projects ...)

[RudiKreiner]

Wouldn't it be possible to issue the error message only if the progs file needs to be updated and rewritten to the disc?

Error messages that can be ignored shouldn't appear at all, because they make it difficult for users to distinguish them from those that should definitely not be ignored.

[mkoller]

There're always ways to solve issues ... most problem is available time ...

[RudiKreiner]

I understand that resources are limited.
This is not a real bug, but classifies as a "nice to have"