Hi Experts!

We've been running for about 2months now. I'm using WinCC Advanced Runtime V14 SP1 installed/running on a Desktop PC Windows 10. Lately we've found out that there no Log for June 27 to July 8 2018(which originally implemented from May 2018 until now). We are using Excel to extract the data from the database[Microsoft SQL Server 2014]. some of the data's are more on OEE variables and time accounts.

In order to correct the issue, what I'm doing is Close the runtime and run again from the PC. There's no error showing in the alarm list for what is the cause of not logging even the system is up 24/7 a week.

Hope some of you have an idea what is the cause and I'm grateful to your ideas/comments.

Many Thanks!

marky

Hi Murof

This what cause the stoppage of the wincc advanced database logging which I have found early morning. Do you have any idea why this occur?

In order to run properly the system again, i shutdown the runtime and load again.

>>configuration in TIA

Thanks

Marky

Hi Marky,

It may be because of high load on the SQL server in combination of the netwrk card/operating system used.

Try to have a look at this KB942861 and see if this can help.

Hi marky_spicer,

From your post, and others, and my own experience, WinCC Advanced SQL logging does not appear to auto-recover after failing to log a tag.

I have not implemented this myself, but I think a work-around would be to do the following:

1. Regularly query the logging tables from WinCC, using scripting (See FAQ 61883659).

2. If the data is stale, restart logging, or even restart the entire runtime.

The criteria for checking if the data is stale could be to record the latest timestamp value for one of the tables.  If this doesn't change for X minutes, trigger the restart.