7/25/2016 11:24 AM | |
Joined: 11/26/2009 Last visit: 1/11/2025 Posts: 223 Rating: (1) |
i am using TIA advanced v13sp1 and databse engine is SQL server 2008 r2. |
6/16/2018 10:08 AM | |
Joined: 2/11/2018 Last visit: 11/18/2024 Posts: 18 Rating: (0) |
Hello Pratik Did you find resolution of the problem? I am also facing same issue. Can anybody help? |
6/22/2018 1:48 PM | |
Joined: 7/25/2017 Last visit: 1/13/2025 Posts: 338 Rating: (54) |
Hi pratik7332, I have also had DB logging die, but in my case it was because I was using SQL Server Management Studio to modify the logging table in the database. RT Advanced doesn't seem to like the table being edited in some ways (e.g. I have killed logging by adding a trigger to the table). But I guess yours is stopping for no reason. A few things I can think of to find the problem: 1. Create an alarm view with the attached settings. It will record information about the logging system. You might find out the problem from reviewing entries in this alarm view. If you don't find any information, perhaps check Windows Event Viewer (eventvwr.msc) for errors in WinCC Runtime. 2. Is your ODBC link breaking somehow? When the logging stops, can you still access the DB through the ODBC connection from another program? 3. Just checking - could it be due to the logging settings? E.g. if you had a non-circular log, it could run out of space. 4. This is not ideal, but a work-around could be to automatically force a restart of logging (system functions ) or of the WinCC runtime when logging stops. You can do this by using a VBscript to check the timestamp of the latest logged value in the database. With a little work, you could adapt the examples from here to find the age of the newest entry in the log table: https://support.industry.siemens.com/cs/ww/en/view/61883659 I can send you a more specific example if you want - reply yes and I'll dig it up :) |
Last edited by: Jen_Moderator at: 6/25/2018 10:03:36 AMOptimized link. |
|
7/2/2018 12:19 PM | |
Joined: 7/25/2017 Last visit: 1/13/2025 Posts: 338 Rating: (54) |
Hi pramodva, It's hard to tell what could be causing your logging to stop. But let me share what I am doing, which seems to be stable:
i would suggest trying to avoid the possibility of errors in your insert trigger (or handling them), and also avoid modifying the wincc logging table in any way (UPDATE, DELETE, etc). Just let WinCC modify that. But in any case, I think it wise (and I should do it too!) to implement a monitoring script in WinCC, which restarts the logging in the event of failure. This can be done by using SQL queries (e.g. https://support.industry.siemens.com/cs/ww/en/view/61883659) to check the latest value. if it is not changing, use logging functions (CloseAllLogs?, StopLogging? StartLogging?) to restart logging. It may be necessary to restart the whole runtime to restore logging, I'm not sure. |
Follow us on