Alarm logging wincc stop saving the data in SQL server 2008R2

Hi all,

we have Wincc Runtime V7.2 + upd1 with CPU 319F.

we are using SQL Server 2008R2 in production PC and we have configure the alaramlogging so that all the error is logged in Database. we have also our own scripts which runs every 10 minutes and saved the information in User Defined table.

the problem we are facing from the beginning of the plant (Since 3 Year) that the alarm logging is stopped saving the Information in Database (internal Database which wincc use) and when we restart the wincc runtime  that data start writing again in the database.

Below is the setting of alarm logging which we have 

alarm logging setting   (image link)

i have also screenshot of database where you can see that after 12.12.2020 16.21 there is no any data and after restarting the wincc the data is appearing with the date 16.12.2020 08.25

Database image      (image link)

can someone guide me where is the real problem. should i have to change the setting in Alarmlogging or something else.

thanks in advance for your support.

 @bg2492

so that's the only reason that the alaramlogging save the data in database for some days and than stop writing it?

or it can be other things also

what else can effect this kind of scenario.

we have 15 PLC and in each PLC its the same. 

Regads,

tar

bg2492

Hello Tar89,

you have set in the Archivekonfiguration for Alarmlogging
the Timeperiod for Single Segment to 1 week, and the
the Timeperiod for of all segments to 2 weeks.
That means, you have always only two segments.
This does not work, you should have at least 3 segments,
that means the Timeperiod for of all segments should set
to 3 weeks or more.
The Max. size of all Segments is only the double of the
Max. Size of single segments.
This need to be set at least to 3x Max. Size of single segments.
Usually it is set to the available space of the harddrive/3,
if you use Alarmlogging and Taglogging.

Regards

Georg Berghof

 Hi Georg,

so after long time i am reply to this post again.

we still had a same problem even after changing the segment configuration.

what i have analyse in this time is that the Wincc visuale the error which is coming from the plant but it is not adding to the database table.

when i open the database file in SQL server 2008 and open the View 'dbo.AlgViewDEU' i don't see the new error messages.

we had a last message from 09.01.2021 and that there is no new messages.

I have closed the runtime of wincc and start it again and than it works. now i can the new messages in database. 

So my question why Wincc stop writing in to the database? how can i find the root cause? currently it looks likes that wincc is responsible somehow it stop writing in to the database.

can you please guide how can i resolve this issue.

Regads,

Tarun

bg2492

Hello Tar89,

if you have only 2 segments, you can get a problem during
the segment-change.
The responsible process for archiving the Alarmlogging-Events
is "CCWriteArchiveServer.exe". There are runing three instances
of it, if you use Alarmlogging and Taglogging.
(one for Alarmlogging, one for Taglogging Fast and one for Taglogging Slow).
There maybe other reasons to that the process crahs.
You can check the evenlogs (application) of the Windows-OS,
if you can find some crashes.

Regards

Georg Berghof

Hello Georg,

thanks for the Reply.

Yes we have tried this and its also works but the thing is it works for 2 or 3 Days and again stop writing in to the database.

stopping the runtime and deleting the file works but this cannot be a solution if you have this problem every week . we have 15 different station and stopping the runtime to solve this problem is not a solution. This happen every week. 

any suggestion on that?

Regads,

Tarun

bg2492

Hello Tar89,

the messages are stored in the runtimedatabase-sgments in the table "dbo.MsArcLong".
This table and one of the CSData-table is linked to the view, which content
is displayed in the Alarm-Control
i.e. "dbo.MsArcLong" + "dbo.AlgCSDataDEU" = "dbo.AlgViewDEU" for german language.

You should check at first the table "dbo.MsArcLong", if you have the messages there.
If you have the messages there, but not in the "dbo.AlgViewDEU", you should
stop the runtime, and delete the template segment for Alarmlogging (files <projectname>Alg.ldf
and <projectname>Alg.ldf) in the WinCC-projectfolder.
Then start the runtime again. The template segment for Alarmlogging will be generatet new.

Regards

Georg Berghof

 Hi Georg,

Thank you very much for your support.

I will update the post if we have find some solution to this. I really appreciate your time and effort.

Regards,

Tarun Patel

bg2492

Hello Tar89,

such a case needs a closer investigation.

You should use the SIMATIC Assessment Suite - Data Collector (SAS-DC)
- formerly known as SIMATIC Diagnostics Tool (SDT) - to collect
diagnostics and system information from the Computers.

https://support.industry.siemens.com/cs/ww/en/view/65976201

Then create a Servicerequest and send the data to the
Technical Support of Siemens.

Regards

Georg Berghof