Archive problems since updating to V3.13

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
5 posts • Page 1 of 1
funkey
Posts:85
Joined: Mon Dec 27, 2010 1:11 pm

Archive problems since updating to V3.13

Post by funkey »

Hello, since updating to new version V3.13 I had several server crashes (both servers on redundant system) that started with an archive error log message:

Code: Select all

 01:53:40.869[140290371921664](ArDPElwatch.cpp:134) Assertion '[start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet]' failed !! - start=4179, lifeIntervalArr_[i].startSet=3441, start=4179, lifeIntervalArr_[i].endSet=4180
ACE_ASSERT: time Sat Jun 27 22:29:08.870066 file /pvss_dev/workspaces/3.13/workspace/Exe/DataNew/ValueArchive/ArDPElwatch.cpp, line 134 assertion failed for 'start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet'.
 14:03:57.578[140392784566016](ArDPElwatch.cpp:134) Assertion '[start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet]' failed !! - start=4201, lifeIntervalArr_[i].startSet=3441, start=4201, lifeIntervalArr_[i].endSet=4202
ACE_ASSERT: time Thu Jul  9 00:57:01.585186 file /pvss_dev/workspaces/3.13/workspace/Exe/DataNew/ValueArchive/ArDPElwatch.cpp, line 134 assertion failed for 'start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet'.
 13:39:59.665[139990828861184](ArDPElwatch.cpp:134) Assertion '[start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet]' failed !! - start=4206, lifeIntervalArr_[i].startSet=3529, start=4206, lifeIntervalArr_[i].endSet=4207
ACE_ASSERT: time Sun Jul 12 15:50:23.665457 file /pvss_dev/workspaces/3.13/workspace/Exe/DataNew/ValueArchive/ArDPElwatch.cpp, line 134 assertion failed for 'start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet'.
 09:28:41.678[140160197142272](ArDPElwatch.cpp:134) Assertion '[start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet]' failed !! - start=4212, lifeIntervalArr_[i].startSet=3529, start=4212, lifeIntervalArr_[i].endSet=4213
ACE_ASSERT: time Thu Jul 16 16:22:49.678474 file /pvss_dev/workspaces/3.13/workspace/Exe/DataNew/ValueArchive/ArDPElwatch.cpp, line 134 assertion failed for 'start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet'.
 20:27:57.516[139786271696640](ArDPElwatch.cpp:134) Assertion '[start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet]' failed !! - start=4220, lifeIntervalArr_[i].startSet=4219, start=4220, lifeIntervalArr_[i].endSet=4221
ACE_ASSERT: time Wed Jul 22 00:57:01.516777 file /pvss_dev/workspaces/3.13/workspace/Exe/DataNew/ValueArchive/ArDPElwatch.cpp, line 134 assertion failed for 'start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet'.
 07:59:09.741[140365346064128](ArDPElwatch.cpp:134) Assertion '[start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet]' failed !! - start=4242, lifeIntervalArr_[i].startSet=4219, start=4242, lifeIntervalArr_[i].endSet=4243
ACE_ASSERT: time Sat Aug  8 00:57:01.764344 file /pvss_dev/workspaces/3.13/workspace/Exe/DataNew/ValueArchive/ArDPElwatch.cpp, line 134 assertion failed for 'start < lifeIntervalArr_[i].startSet || start > lifeIntervalArr_[i].endSet'.
We now have installed V3.13 Patch 4.
Never had this problem with previous versions. This is very severe, because of loosing a lot of data while both servers are restarting!

Hope you can help me!

Greetings
Christoph

funkey
Posts:85
Joined: Mon Dec 27, 2010 1:11 pm

Re: Archive problems since updating to V3.13

Post by funkey »

Still the same big problems, they even got worse! We use now V3.13 Patch 21.
:angry:

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Archive problems since updating to V3.13

Post by leoknipp »

A similar issue was found in newer version and was fixed with a patch.
Can you make an upgrade to a newer version?

Best Regards
Leopold Knipp
Senior Support Specialist

funkey
Posts:85
Joined: Mon Dec 27, 2010 1:11 pm

Re: Archive problems since updating to V3.13

Post by funkey »

Thanks for your answer,

but we can only upgrade version once a year and next time is in about 10 months. But we can always patch the version 3.13 until then.
It would be great, if we can patch this bug in current version.

Best regards
Christoph

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Archive problems since updating to V3.13

Post by leoknipp »

If the problem fixed in newer versions is the same in your project we cannot see without detailed information.
Please get in contact with your common WinCC OA support for further analysis.

Best Regards
Leopold Knipp
Senior Support Specialist

5 posts • Page 1 of 1