TaskAgent Failure 8.03.409C

Yahoo Archive
1
If the customer switched from a single server to a dual server, make sure the OpenEdge processes are not starting on the SQL server. My direct experience with v8 running in a dual setup is limited, but I have heard plenty of situations where the same problems were happening and for this reason we recommended customers beef up the hardware and use solid state drives wherever possible.

If these are two brand new servers, what is the OS of each, OpenEdge and SQL versions as well? What OS version did you come from?

Version 8.03.4xx is only supported to run on Windows 2003/SQL 2005. Although, many customer run this successfully on Windows 2008 R2, Epicor will treat this as an unsupported setup and will probably offer limited support.

Hope this helps.

Jason Claggett
Vice President of Technology
2W Technologies, Inc.
Epicor Gold Partner
312.533.4033 x8039
jason@...<mailto:jason@...>
[Description: bus_prtnr_2C_vert_sm]


[Non-text portions of this message have been removed]
2
TaskAgent Failure 8.03.409C

Just wondering if anyone had discovered common themes to the TaskAgent failing and not being able to be restarted without a complete reboot of the server.


Have a customer who’s system is just stopping processing anything through the SystemTaskAgent.

This wasn’t a problem until a couple weeks ago when they switched from a single server to a dual server one SQL and one App. There is nothing in any of the logs that is pointing to a cause, and they are all set to verbose and append so we don’t lose anything upon a restart.

I don’t think it is related to time outs of any kind, like a network card or hardware, since there is too much activity to cause a time out. They are also not doing any kind of snapshot or VEEAM backups on the system at all either.

Any other ideas what could be causing these stoppages?

Also as a side note, just stopping and restarting the Task and Process Servers doesn’t fix the problem, requires a full reboot only.

3

I’ve experienced something similar in the past and it was related to report .  The user was choosing  too big of a date range and for some reason his report killed the task agent.  Take a look at reports that were being ran around the same time it dies and maybe you’ll find something. Also way way  back when  also we had an issue with our Antivirus program. It was trying to scan the reports data folder which also caused the task agent to die.

 

Good luck!

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Monday, January 5, 2015 12:53 PM
To: vantage@yahoogroups.com
Subject: [Vantage] TaskAgent Failure 8.03.409C

 

 

Just wondering if anyone had discovered common themes to the TaskAgent failing and not being able to be restarted without a complete reboot of the server.


Have a customer who’s system is just stopping processing anything through the SystemTaskAgent.

This wasn’t a problem until a couple weeks ago when they switched from a single server to a dual server one SQL and one App. There is nothing in any of the logs that is pointing to a cause, and they are all set to verbose and append so we don’t lose anything upon a restart.

I don’t think it is related to time outs of any kind, like a network card or hardware, since there is too much activity to cause a time out. They are also not doing any kind of snapshot or VEEAM backups on the system at all either.

Any other ideas what could be causing these stoppages?

Also as a side note, just stopping and restarting the Task and Process Servers doesn’t fix the problem, requires a full reboot only.