Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

PCS7 6.0 WinCC Server Crash

Created by: aussie at: 8/21/2006 8:31 AM (11 Replies)

Rating (0)

Thanks 0

Result pages:: |; 1 | 2; |

12 Entries

Entries per page: 10 | all

8/21/2006 8:31 AM	Rate (0)
aussie Posts: 12 Rating: (0)	Hi, We have 2 x WinCC Redundant Servers (PCS7 V6.0 SP1 HotFix1) installed on Windows 2000 Server SP4. The WinCC is WinCC V6.0 SP2; V6.0 SP2 + Hotfix2. Whenever we look for a historical trend for a longer period (more than two months), the system crashes showing a PCS7 message to reboot the system. It happens on either servers into which the client is connected to. The clients are WinCC true clients with WinCC V6.0 SP2 Hotfix2 installed on Windows 2000 Professional Service Pack 4. I have checked with technical support but they say it could be a problem with PCS7 V6.0. Are there anyone experienced such a problem with WinCC V6.0 SP2 ? Are there any hotfix or service pack to fix this problem ? Appreciate your response. John
aussie Posts: 12 Rating: (0)
Suggestion To thank Quote Answer

8/21/2006 9:20 AM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi are you using PCS7 or WinCC??? If you are using PCS7, please always install PCS7 OS for your Server/Clients from the PCS7 /DVD/CD - never from a WinCC-CD. Please post your WinCC server/client logfiles in the Forum nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

8/21/2006 9:33 AM	Rate (0)
aussie Posts: 12 Rating: (0)	Hi Nemo, Thanks for the response. We used PCS7 for Server and Client installation. I mentioned WinCC versions to get some feed back from WinCC V6.0 users. Attached are the log files (zip format) including Windows events and some screen shots of the error messages. Thanks, John Attachment Server1b.zip (121 Downloads)
aussie Posts: 12 Rating: (0)
Suggestion To thank Quote Answer

8/21/2006 10:15 AM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi, in your logfiles I´ve seemlot of entries like this: 255,10.08.2006,13:51:30:406,1007001,4,,SERVER1B,SCRIPT,ExecuteError in Action @b 255,10.08.2006,14:09:36:714,1012253,4,,SERVER1B,ArchiveManager,Backup:Not enough diskspace on path \\Server1a\Archive1A\ ! 255,10.08.2006,14:09:36:714,1012252,4,,SERVER1B,ArchiveManager,Backup:invalid path ! => so check the pathes/available diskspacefor your redundancy-project and try to get rid of the ExcecuteErrors: http://support.automation.siemens.com/WW/view/en/8385493 http://support.automation.siemens.com/WW/view/en/22198106 nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

8/22/2006 12:53 AM	Rate (0)
aussie Posts: 12 Rating: (0)	Hi Nemo, Thanks for ur response. ---------------- 255,10.08.2006,13:51:30:406,1007001,4,,SERVER1B,SCRIPT,ExecuteError in Action @b I am not sure about the meaning of this error as I could not identifythe action script @b -------------- 255,10.08.2006,14:09:36:714,1012253,4,,SERVER1B,ArchiveManager,Backup:Not enough diskspace on path \\Server1a\Archive1A\ ! 255,10.08.2006,14:09:36:714,1012252,4,,SERVER1B,ArchiveManager,Backup:invalid path ! The log files related to archive backup are correct as sometimes the backup drive reach the maximum limit or gets full. These are optical disks and mapped on to Server1a. If the Server1a crashes or shutdown, then Server1b shows a log like invalid path. The Servers work perfect all other times. There may be some other script errors as well which are basically coming from either the Power Solutions library orother WinCC add-on like ArchiveManager tool from I&S ITPS. The system crashes only when we request for a longer trend spanning two months or more. Regards, Roy
aussie Posts: 12 Rating: (0)
Suggestion To thank Quote Answer

8/22/2006 8:01 AM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi, as mentioned in http://support.automation.siemens.com/WW/view/en/8385493 I´d try to catch this error in using GSC-Runtime / APDIAG: http://support.automation.siemens.com/WW/view/en/22196773 If you are displaying lots of trends for e.g. 2 months you should check as well how much resources (CPU, memory,...) on your server are available....I could imagine, that you are running in a "lack of memory/available resources". nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

8/22/2006 9:24 AM	Rate (0)
aussie Posts: 12 Rating: (0)	Hi Nemo, Thanks for your response. The servers are having 1GB RAM each and 60GB HDD. There is plenty of harddisk space free. And it is basically a Siemens Rack PC designed for PCS7 OS Server with Windows 2000 Server. I will take a closer look at the script diagnostics based on those links mentioned in your message. Thanks, John
aussie Posts: 12 Rating: (0)
Suggestion To thank Quote Answer

8/22/2006 9:35 AM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi, in my experience you cannot have enough RAM for any Microsoft compatible application => I would use more RAM [:D] nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

8/25/2006 9:52 AM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (150)	I remember similar problems with V6 SP1 but I think SP2fixed these. However I could be wrong and it was SP3 that fixed the trend display issues. If it were me I would check PC resources in Task Manager / Performance Monitor before, during and after the error message to see if anything is spiking. Also check the files in the <project directory> \ ArchiveManager folder to see if any files have a file size < 1Mb. This is a sure sign of a corrupt database which I have seen cause problems. Finally as Nemo says, it's best to clear all errors from the log files. Sometimes this can stop other problems (such as this trend crash) as it could be a symptom and not the cause.

Suggestion To thank Quote Answer

8/25/2006 10:46 AM	Rate (0)
aussie Posts: 12 Rating: (0)	Hi Salma, We did all the monitoring several times but could not locate the exact cause. It is easy to re-produce the error, just look for a two months trend. The main issue is the customer see this as a deffect rather than a performance issue. So we can't really propose a full upgrade to PCS7 V6.1 as it involves a lot of licenses and major changes in the project libraries. I have seen somewhere in this forum about a problem with the harddisk array supplied with some of the Simatic Rack PCs.There was also somedocumentation on how to update the hitachi harddiskfirmware.I have noted some disk problems (device timeout)with both the PCs in the Windows event log. Will there be any connection between the harddisk problems and the trending? I would be able to update the harddisk firmware or even replace the disk during our next maintenance as I can't confirm this could be the reason behind PCS7 crash. Regards, Roy
aussie Posts: 12 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on