Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

WinCC v6.0/SP4 crash

Created by: stplanken at: 3/14/2006 4:48 PM (6 Replies)

Rating (2)

Thanks 0

7 Entries

3/14/2006 4:48 PM	Rate (0)
stplanken Silver Member Joined: 3/4/2006 Last visit: 12/6/2024 Posts: 73 Rating: (3)	This morning the WinCC server (v6.0/SP4) crashed with the following popup on the screen: --------------------------- C:\Siemens\WinCC\bin\CCDmRtServer.DLL --------------------------- Unhandled exception was raised. Look WinCC Diagnose directory for details. --------------------------- OK --------------------------- (This is the literal text.) There was only one message logged on the server in ccrtsloader.log (the other logs had only entries showing the last project startup): //==================================================================== // WinCC reported exception with code: C0000005 ACCESS_VIOLATION // Date: 14.3.2006 - Time: 12.44.7 // Caused at logical address 10001604 01:00000604 I assume the time is UTC since it happened around 6am MT. On the eight client workstations it appeared that the grahics runtime was OK, i.e. the I/O fields were not greyed-out but data was not updated.Five of the eight clients had only tagtimeout messages with a time stamp minutes after the fault so I assume thiswas caused by the server error; there were no other errors logged on the clients.On the server, I dropped the runtime, executed the reset script and restarted the project and everything seems OK again for now. Does anyone know what this could indicate? If it was caused by a script somewhow, can I still find out which one (does the address point to anything relevant)?The error messages do not seem to offer much. The Windows event logs did not log anything unusual either. This is a project that has been running for some time now without any problems. It was originally migrated from 5.1 to 6.0/SP2 more than a year ago, then upgraded to v6.0/SP3, and now v6.0/SP4. Thanks, Stephan Planken

Suggestion To thank Quote Answer

3/14/2006 5:13 PM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi, in this forum there has already been a discussion about tools for diagnosing WinCC scripts: /tf/WW/en/Posts/2548 You should check the entries in your WinCC log files on your Server and Clients as well: ..\siemens\wincc\diagnose\... How much diskspace is available? How much RAM is available => task manager? Do you e.g. use option "storage" (and try to export large amounts of data at this time)? Are any other applications running on your Server - except WinCC? Which other software is installed on your server? Did you a lot of C-scripting? nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

3/14/2006 5:50 PM	Rate (0)
stplanken Silver Member Joined: 3/4/2006 Last visit: 12/6/2024 Posts: 73 Rating: (3)	I am familiar with the diagnostics tools, but it was too late to start a diagnostics after the fact. This server is an older PowerEdge 2300 with single 700Mhz CPU and 512MB, of which typically 121MB is available. It is dedicated to WinCC only. After the WinCC conversion from v5 to v6 more than a year,I converted many of the C scripts to VBS, but there are still several smaller C scripts running, mainly for bit manipulation in mouse events. The global actions are all converted to VBS. It could be that one of theC scriptsis the culprit, but those have been running since 1999 under WinCC v4.x. The only failure msg on the server was in CCRtsLoader.LOG, the one I posted. The clients had timeout messages, but all with a time stamp after the server error. Here is an example of one of the clients: 255,14.03.2006,05:59:41:536,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC6_DB10_DBB016 timeout 255,14.03.2006,06:00:41:485,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC5_DB09_DBB008 timeout 255,14.03.2006,06:00:51:490,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC5_DB09_DBB008 timeout 255,14.03.2006,06:01:01:525,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC4_DB11_DBB009 timeout 255,14.03.2006,06:01:11:520,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC4_DB11_DBB009 timeout 255,14.03.2006,06:02:01:544,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC4_DB11_DBB009 timeout 255,14.03.2006,06:02:11:539,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC4_DB11_DBB009 timeout 255,14.03.2006,06:03:01:543,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC3_DB09_DBB007 timeout 255,14.03.2006,06:04:01:553,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC4_DB09_DBB000 timeout 255,14.03.2006,06:04:11:558,1007006,4,,MC1,SCRIPT,Variable XXXXXXX_SRVWINCC::PLC4_DB09_DBB000 timeout 255,14.03.2006,06:04:21:562,1007006,4,,MC1,SCRIPT,10 errors occurs, no more errors will be reported I altered the server prefix since this is also the company name. Four other clients logged similar messages, with different tags in different PLCs, probably depending on the active display at that time. One thing I forgot to mention is that before I restarted the project, I disabled the alarms logging just in case it is a hard drive/space issue. I will run the diagnostics tools on several of the client machines today to see if this will yield anything useful. Thanks for your response. Stephan Planken

Suggestion To thank Quote Answer

3/15/2006 4:40 PM	Rate (0)
stplanken Silver Member Joined: 3/4/2006 Last visit: 12/6/2024 Posts: 73 Rating: (3)	Update: After having used apdiag on several machines yesterday I could not find anything out of the ordinary. No exceptionally long script execution times, no errors in the server or client log files at all, everything seems to run fine. The plant has now been running for more than 27 hours since the crash.I am still struggling with the meaning of the error: --------------------------- C:\Siemens\WinCC\bin\CCDmRtServer.DLL --------------------------- Unhandled exception was raised. Look WinCC Diagnose directory for details. and whether this could have been a script at fault or whether this was an internal problem in WinCC (the Windows properties screen shows this as being the data manager runtime). I disabled the only C global action since it was not critical anyway, the other 5 or 6 or so global actions are done in VBS. I'll take this up with Tech Support.

Suggestion To thank Quote Answer

3/20/2006 11:23 AM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	Just one thing, the Data Manager handles communications in WinCC. Any problems with the Data Manager usually indicate a problem with comms to your PLCs, tag configuration, etc. I am sure Tech Support will be able to cast more light on the situation.

Suggestion To thank Quote Answer

3/21/2006 7:20 AM	Rate (1)
stplanken Silver Member Joined: 3/4/2006 Last visit: 12/6/2024 Posts: 73 Rating: (3)	Not sure of this is directly related tolast week'scrash but over the weekend I made two changes. First, I found an error in one of the 5 or 6 VBS global actions. It was calling another function with an SQL query but that function had one parameter added, while the global action was never updated to reflect this. Second, I reduced the amount of data retained in the alarms logging due to the fact that hard drive space is becoming a precious commodity on that server. The global action problem I only discovered by temporarily running the graphics runtime on the server. The server is the only machine with the global script runtime active so on none of the workstations can you monitor any error msg related to the global actions (other than using some local tags with debug values). So far no errors in any log file on any workstation/server.

Suggestion To thank Quote Answer

3/21/2006 9:05 AM	Rate (1)
Ikkezelf Posts: 1084 Rating: (72)	Thanks for sharing!
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on