6/26/2009 7:53 PM | |
Joined: 10/18/2007 Last visit: 9/12/2024 Posts: 66 Rating: (3) |
Hi guys! I have ran into somewhat of a problem with our engineering station, and will need your expert assitance in resolving the issue. We are experiancing issues with our engineering station freezing WinCC runtime and disconnectingfrom the network. When I say freezing, I mean that none of the pushbuttons, faceplates, animations, display valueswork, but you can still click on pushbuttons andfaceplates and they even depress;it appears like the script behind them is not executing. By the way, there is no custom script onour systems.When this happens, the only way I can exit runtimeis to press thepower buttonon the PC. This will initiate aWindows shutdown sequence and will terminate the WinCC runtimeprocess. OnceWinCC is terminated I can use Windows with no issues. The engineering stationis running Simatic Logon, and Simatic Lifebeat Monitoring.Due to it running these applications, it causesalarm messages when it starts to experiance connection problems. The alarm messages will come in and leave within a second, indicating that the system faulted connection and then quickly recovered the connection. This process will continue for hours, until eventually the system disconnects for good. There areerror messages in the logs which are OPC error, "GetStatus - Error 80010108".The engineering station will also prevent any Simatic Logon authorizations from occuringagainst its user list. This means that no clientsat the plant are able to authorize against the engineering station while this problem is happening. We have about a dozen PCS7 computers setup in our environment; that includes 2 servers, 1 engineering station (also functions as a client),1 web server, and 8 clients. All the systems are running the same project on them, and most of the system are running on Siemens supplied IL PC computers. The systems are all networked view a single switch, using ethernet cable. I have also confirmed that there is nothing wrong with the network by being able to ping and connect and transfer files to and from the engineering station while its locked in WinCC runtime. This proves that something is going on in the WinCC layer, notWindows or hardware.The engineering station is the only computer that experiances these problems. The other stations have never had a connection/freezing issues like the engineering station. This problem started to happen on June 13, 2009 at 22:49, and continued till June 15, 2009 9:42, at which point I restarted the system. I have used a Siemens tool called PCS7Tools to obtain full diagnostic logs from both the engineering station (EWS), and the server (serv1a). I have looked through all the log files that were date stamped June 13-June15, and have found multiple errors. I have also looked through the windows event logs. Below are the errors I have found, but I am not sure how to go around resolving these errors. I have researched these forums, and the FAQs that are usually posted for these errors, but they did not help me to resolve the problem. Error 1: "ActionOverflow: more than 5000 actions at work".As stated, there is no custom script, as it appears this error is usually caused by a programming mistake. I have read the FAQ posting on ActionOverflow, but they did not help me with troubleshooting the issue. Error 2: I ran APDIAG to try to locate a possible scripting problem. I set APDIAG to the highest level, so that it would log everything. I located the following error "EndAct Timeout", which also had .cpp filesand line numbers mentioned. I don't know how to address this error, and would appreciate any assistance. By the way, this error is generated in a continuous cycle, with no user input. The error will reiterate over and over again ever few hundered milliseconds, and could be causing the ActionOverflow issue. Error 3: I am receiving Access_Violation errors. I can see the pdlrt.exe process has generated an access violation error and generated a stack dump within the log file. Can this information be used to troubleshoot the issue, or does Siemens development need an entire process memory dump generated by Windows userdump? As you can see, there are many issues that are being caused from whatever conflict I have. Basically the scripting stops, I start to experiance network connection problems, and my clients are unable to authenticate against the engineering station. I have attached a zip file containing all logs that I have obtained from the troubleshooting upto this point. Thanks for any help, Vadrad AttachmentTroubleshoot.zip (104 Downloads) |
Follow us on