This keeps happening to us as well. We were told Epicor is working on a solution that will allow SaaS customers to restart the Task Agent. No timeline was given.
I was told they already monitor the task agent continuously and are aware when it fails. Doesn’t add up though if people are still having to notify support for it to get fixed.
In any case we have a solution to notify ourselves when our task agent is down but I bet it could be adapted to work for cloud customers. We run a scheduled task to run a ps script that looks for: SELECT COUNT(*) FROM Kinetic.ice.SysAgentSched WHERE SchedType=‘Immed’ And DATEDIFF(SS,NextRunOn,GetDATE())>20"
In other words, immediate run requests sitting in scheduled. And then email if there are any. I bet you could write an Epicor function that checks that table and sends an email, and put it on a schedule to run every 10 minutes or whatever.
This is what they call observability - looking at the system from the outside to determine its health. There is a DevOps Idea for those with votes available.
Exception has been thrown by the target of an invocation.
Cannot open Service Control Manager on computer '.'.
This operation might require other privileges.
Today from 7:11am to 8:11 Central we were not able to print.
The error was:
“Program Ice.Services.Lib.RunTask when executing task 1079930 raised an unexpected exception with the following message: RunTask:
System.Net.WebException: The remote server returned an error: (503) Server Too Busy.”
I just checked with the attached BAQ. We had 58 cases today, most in the morning, but also right after lunch.