Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

WinCC 5.1 Crash problem

Created by: recruta42 at: 9/5/2007 7:24 PM (3 Replies)

Rating (1)

Thanks 0

4 Entries

9/5/2007 7:24 PM	Rate (0)
recruta42 Posts: 10 Rating: (0)	Hi, my name is Angelo and I am new here on this board. I work at a great siderurgy and we have WinCC 5.1 running under windows NT on our production lines. Actually, the one that is giving us the greatest headaches in the one installed in our CCL line (Colour Couting Line). From times to times it simply crashes for no reason. The frequency of these crashes are increasing and since our line is continuous (24 hours a day...) sometimes it can stops the line since the operator loses controls of what is heppening on it during the process. The problem now is to track down what is causing this problem (WinCC Vs Windows NT) and how to fix it. I believe it is a sum of problems since from the comissioning of the lines we have script problems that were never solved and the quantity of changes since then only increased. I am starting to learn how to use Apdiag and the first thing to pop up on the screen was: WinCC-Runtime found: 0x000101EA :( Either way I will put our diagnose directory here to see if any of you can help us on some way... Thanks Attachment Diagnose.zip (110 Downloads)
recruta42 Posts: 10 Rating: (0)	Last edited by: recruta42 at: 05.09.2007 21:30
Suggestion To thank Quote Answer

9/5/2007 10:58 PM	Rate (1)
Danielle Posts: 1275 Rating: (123)	Boa tarde Angelo, I see you've already ran APDIAG and posted your diagnose! That made things faster... So... about your diagnose, here we go: // WinCC reported exception with code: C0000005 ACCESS_VIOLATION // Date: 24.8.2007 - Time: 20.11.37 // Caused at logical address 61662FAA 01:00091FAA ====================================OnErrorExecute==================================== szTagName: (ThreadId 548) "@Previous_Actual_Weight" szErrorTextTagName: (ThreadId 548) Tag deliver status szErrorText: (ThreadId 534) Tag unknown, timeout or conversion failed 255,03.09.2007,14:53:44:390,1003051,2,Administrator,C_HMI_SRV,Alarm Logging,Acknowledge tag(bit) already used 255,02.09.2007,10:16:13:515,1003055,2,Administrator,C_HMI_SRV,Alarm Logging,Message tag or tag type (only unsigned permitted) is invalid ! Dmc 2 : 3827.535483 msec K:\ohio_prj\AP\AP_CLIENT\apresult.cpp 144 : Anzahl Ergebnisse :11 Dmc 2 : 3828.425092 msec K:\ohio_prj\AP\AP_CLIENT\apresult.cpp 161 : Ergebnisse der GTI Funktion vor Aufruf der PDLRT Callback gscrt 0 : 3829.837296 msec K:\ohio_prj\AP\AP_CLIENT\apresult.cpp 144 : Anzahl Ergebnisse :1 gscrt 0 : 3830.522387 msec K:\ohio_prj\AP\AP_CLIENT\apresult.cpp 161 : Ergebnisse der GTI Funktion vor Aufruf der PDLRT Callback I don't speak german, so I have no idea what these two mean... FunctionName OnBtnScroll PathName \\C_HMI_SRV\SCRIPTFCT\Alarm\bscroll.fct =============================================================== szErrorTextInfo: (ThreadId 543) Action WinCC-Runtime found: 0x000101EA szErrorTextInfo: (ThreadId 543) Action szErrorTextInfo: (ThreadId 293) Action WinCC-Runtime found: 0x000101EA WinCC-Runtime found: 0x000101EA WinCC-Runtime found: 0x000101EA WinCC-Runtime found: 0x000101EA I couldn't find anything regarding this error... 255,03.09.2007,19:18:25:015,1003015,4,Administrator,C_HMI_SRV,Alarm Logging,AlarmLogging is being overloaded with 1903 messages / 10 min. Check out why you had this many messages... if you normally have too many messages, you may consider filtering the critical ones from the events... szErrorText: (ThreadId 543) Tag unknown, timeout or conversion failed szTagName: (ThreadId 543) "@Previous_Actual_Length" Well... you should check the "onerror" and "onprintf" logs for the tags which are not being found... also check the alarm messages and acknowledge bits... then you gotta make sure that whatever caused the access violation has been worked out too... Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

9/19/2007 6:24 PM	Rate (0)
recruta42 Posts: 10 Rating: (0)	Bom dia Danielle... You are really a sweet person..... Well...I managed to fix the easy "missing tag" script errors and now I am with themost complicated ones to solve. Can you give me a little more help ? Thanks Attachment Diagnose.zip (109 Downloads)
recruta42 Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

9/20/2007 10:32 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	Boa tarde Angelo, I've taken a look at your logs again.. This showed some time ago, but I didn't know if you had already taken a look at this function... FunctionName OnBtnScroll PathName \\C_HMI_SRV\SCRIPTFCT\Alarm\bscroll.fct =============================================================== szErrorTextInfo: (ThreadId 543) Action WinCC-Runtime found: 0x000101EA I've also found these: szErrorText: (ThreadId 813) Tag unknown, timeout or conversion failed szTagName: (ThreadId 813) "ActPict00" dwCycle: (ThreadId 813) 0 szErrorTextTagName: (ThreadId 813) Tag deliver status lpszPictureName: (ThreadId 813) @SCREEN.@WIN12:@1001.@DESK:RN UC 2 PDI lpszObjectName: (ThreadId 813) (NULL) dwParamSize: (ThreadId 813) 12 szErrortext: (ThreadId 813) Tag not found ====================================OnErrorExecute==================================== szErrorText: (ThreadId 813) Tag unknown, timeout or conversion failed szFunctionName: (ThreadId 813) @b31 szTagName: (ThreadId 813) "ActBox00" dwCycle: (ThreadId 813) 0 szErrorTextTagName: (ThreadId 813) Tag deliver status lpszPictureName: (ThreadId 813) @SCREEN.@WIN12:@1001.@DESK:RN UC 2 PDI lpszObjectName: (ThreadId 813) (NULL) lpszPropertyName: (ThreadId 813) (NULL) dwParamSize: (ThreadId 813) 12 szErrortext: (ThreadId 813) Tag not found ====================================OnErrorExecute==================================== szErrorText: (ThreadId 813) Tag unknown, timeout or conversion failed szFunctionName: (ThreadId 813) @ac5 szTagName: (ThreadId 813) "ActBox00" szErrorTextTagName: (ThreadId 813) Tag deliver status lpszPictureName: (ThreadId 813) @SCREEN.@WIN12:@1001.@DESK:G2A_ENTRY_S&R lpszObjectName: (ThreadId 813) (NULL) lpszPropertyName: (ThreadId 813) (NULL) dwParamSize: (ThreadId 813) 12 szErrortext: (ThreadId 813) Tag not found Once you've cleared the unknown tags, you should run the application under APDIAG. Make sure you execute all scripts possible (passing through all screen, pressing all buttons...), so you can catch as many errors as possible... You probably have a lot of work ahead of you... so... good luck with that! Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on