![]() ![]() We are wondering if there is any way to be proactive here and identify the issue before it causes jobs to fail, maybe even have the agent service recycled automatically. ![]() This allowed the jobs to be run fine after being resubmitted. To fix the issue I simply stopped and restarted the agent service. The job ended up failing with a 255 instead. I passed a return code of 0 for a simple test of the agent. I even ran the SetExitC.exe that comes with the agent install. This seemed to be causing jobs to simply fail for no reason. However, in looking at the application logs from the agent server, we found the below error. It was not marked inactive, the manager server was able to communicate fine to the agent. We had one of our Windows agents (11.3.4 version) causing jobs to fail all of a sudden. Just wondering if anyone has come across a similiar issue. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |