Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

ActionOverflow : more than 5000 Actions to work

Created by: gpfl at: 11/13/2006 5:53 PM (34 Replies)

Rating (1)

Thanks 0

Result pages:: |; 1 | 2 | 3 | 4; |

35 Entries

Entries per page: 10 | 20 | all

11/13/2006 5:53 PM	Rate (0)
gpfl Advanced Member Joined: 3/8/2006 Last visit: 7/9/2024 Posts: 15 Rating: (4)	Hello, Every 2147483647 ms (2^31-1)after theWinCC start the scripts freeze and the "ActionOverflow:more than 5000 Actions to work" message is logged in the WinCC_Sys_xx.log file. Has somebody an idea about the source of this trouble. Thanks. Regards,

Suggestion To thank Quote Answer

11/13/2006 6:57 PM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Looks to me that you have more then 5000 actions running at the same time. Could this be possible? with regards, Ikkezelf
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

11/13/2006 7:26 PM	Rate (0)
gpfl Advanced Member Joined: 3/8/2006 Last visit: 7/9/2024 Posts: 15 Rating: (4)	Normally, at max 200 scripts shouldrunningat the same time. But the strange thing is that the "ActionOverflow:more than 5000 Actions to work" message appears allways 2147483647 ms after a WinCC start. No script have this time period. When I look the number of script in the queue during 2 days, it doesn't increase. Best regards,

Suggestion To thank Quote Answer

11/14/2006 9:48 AM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	2147483647 ms, = approx 24 days, that's a long time. Is there anything in the log files that can tell us more? Try to post them here please. with regards, ikkezelf
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

11/14/2006 10:20 AM	Rate (1)
Nemo Posts: 3149 Rating: (171)	Hi perhaps this FAQ can help as well http://support.automation.siemens.com/WW/view/en/2357302 nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

11/14/2006 11:47 AM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Thanks Nemo, I have a day off I think, forgot even to look in the faq myself... with regards, Ikkezelf
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

11/14/2006 12:05 PM	Rate (0)
gpfl Advanced Member Joined: 3/8/2006 Last visit: 7/9/2024 Posts: 15 Rating: (4)	Sorry I didn't take the log file, but as I can see, there was no special message in it. If you really need them, I can ask my customer to send them to me. I don't know if it could help, but in the WinCC application there is an action with notrigger. Normally this action should not be activated, but does the system always used it ? To answer Nemo,the FAQ "http://support.automation.siemens.com/WW/view/en/2357302"seem not to be helpful. All my scripts or actions are at least used onceper day. And none of them generated an error. Whatever the moment of starting, the script blocks after exactly 2147483647 ms. Best regards,

Suggestion To thank Quote Answer

11/14/2006 12:27 PM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	Hi gpfl So after one day you see this message in the log file and all your scripts freeze. Is this correct ? This error is often caused by another script hanging, thus causing all other scripts to queue up. However the exact timing of the error is a little confusing as you cannot determine how many scripts will run (think of all the button and picture scripts ! ). I would recommend you activate runtime, start APDIAG.EXE and periodically (e.g. every hour) go to Info -> First Action and hit Save. If this ever generates a file then it will show what script is hanging. If not then it's possibleasudden influx of scripts are executed 24 hours after start up [:o] Can you try the APDIAG suggestion and also let us know what version of WinCC / Windows you are running. Salma We dance in a circle and suppose,while the secret sits in the middle and knows

Suggestion To thank Quote Answer

11/14/2006 12:48 PM	Rate (0)
gpfl Advanced Member Joined: 3/8/2006 Last visit: 7/9/2024 Posts: 15 Rating: (4)	No, the message appears only 24 days after the application's starting and not after 24 hours. I already start the Appdiag and I activated the update ofscript's tags and also the script gradient and scanrate. No script is hanging after 24 hours. For information, this trouble appears only on the WinCC server and never on the 2 WinCC clients. Noboby uses the graphic runtime on this server, so there are no script's queue increase due to the operator. Best regards,

Suggestion To thank Quote Answer

11/14/2006 12:54 PM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	My mistake, I meant 24 day [:xxx:]. However my suggestion still stands. Also, does WinCC scripting actually freeze at this point ?? Salma We dance in a circle and suppose,while the secret sits in the middle and knows

Suggestion To thank Quote Answer

Result pages:: |; 1 | 2 | 3 | 4; |

35 Entries

Entries per page: 10 | 20 | all

|

Share this page:

Share this page on...

Follow us on