![]() |
|
![]() |
AutoMate Discussion | ![]() |
Topic Title: Appcrash and kernel error Topic Summary: Created On: 12/05/2011 03:58 AM Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
||||||||||
The eventviewer is showing mulitiple error on the BPA 7.1.3 server. We are at the same time having problems with workflows henging. When to workflow trigger a task at the same time (seconds) both workflow are henging. It seems like the agent are loosing contact with the workflow. Memoryleak?? According to the timestamp in eventviewer and Execution Status windows the error is not necessarily at the same time.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Kaare,
What version of Windows are you running? The crash information refers to bpatask.exe and these processes close after every task is done with its execution. Does this occur over time or does the crash occur with every task?
------------------------- ![]() Leonard Amabile | Director, Cross Platform Support AutoMate | InterMapper | Skybot | Divisions of HelpSystems T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Leonard, We are running Windows 2008 SP2 x64 on all our servers. BPA and MSSQL (2008 SP2) server are on different servers. This is happening over time and not on every task.
|
||||||||||
|
||||||||||
![]() |
||||||||||
We are having problems with workflows not exiting and over time BPA stops responding. How fast BPA stops is depending on the amount of load, but normaly the server stops responing in 48-72 hours. The kernel error accour more frequently in the end of an 48-72 hours periode. At the time there are running 8 workflow with one matching task, but only 2 workflow/task are actual running. In TaskManager on BPA server there are running only 2 bpatask.exe. These to are matching the 2 running workflow/task.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Kaare,
Can you describe the workload as far as triggering is concerned? How many of each type and at what intervals?
------------------------- ![]() Leonard Amabile | Director, Cross Platform Support AutoMate | InterMapper | Skybot | Divisions of HelpSystems T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
At the time we are running 10 workflows that are scheduled on time. There are 5 workflow that are trigged by file, but those are not the main problem since they are fired so rarely. All 10 time scheduled workflows are scheduled on different time. Ex every 63 second, every 67 second and so on. This is to prevent workflows to "collide". The reason for different time scheduling is that almost always to different workflow trigged on the same time is hanging. All schedule trigging is fired between 60 and 300 seconds. All schedule are setup with a interval, no exclude, no end date and default rescheduling ("Immediately run..." and "Realtive to the original....")
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Kaare,
Would it be possible to setup a GoToAssist session so that we can take a closer look at this issue? If so please send an email to support@networkautomation.com with your availability. Note: Please include a link to this forum thread in your email.
------------------------- ![]() Ricardo Castaneda | Principal Support Analyst AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 |
||||||||||
|
FuseTalk Enterprise Edition v4.0 - © 1999-2021 FuseTalk Inc. All rights reserved.