Changing Companies Kills Task Agaent

Has anyone else experienced a case where changing companies stops the task agent from working properly?

We have multiple companies here, some of which are operational that everyone uses everyday and some others that are more holding company-like. If a user switches from an operating company to a non-operating company and run any report it will not generate. In the System Monitor it will show as complete in the History tab but on the reports it is not there. Relaunching Epicor has the report pop up like I would expect if the System Monitor crashed. However once they have relaunched Epicor from a non-operating company, if they move back to an operating one they have to go through the same process.

Moving between operating companies does not have this effect. We have a single task agent that the entire instance uses as well.

Does your Task Agent user account have access to both operating and non-operating companies? How about the App Server username/pass in System Agent Maint - does that account have access to all companies?

It’s not that the task agent has stopped working. It’s that they made the reports tab company-context specific. Its obnoxious. You can put the system monitor in your menu and then launch it after changing companies to get the reports back.

Yes, as far as I can tell all the access is available and it does work if you restart epicor but I don’t see this when switching between our normal companies so it is very weird and annoying for the few people in accounting that have to do this.

That doesn’t explain why company switching works fine amongst all of our companies except for a few select ones. For the amount they do in these companies it is easier to have them restart epicor than to train them to restart the system monitor as well.

I think you will find the behavior is the same in all companies if you test the exact same steps. Open Epicor. Open the system monitor. Confirm the current company context of the system monitor matches your current company context. Run a report. See it appear in the reports tab. Now switch to another company. CLOSE EPICOR. Reopen Epicor. Open the system monitor. Confirm the system monitor is now in the company context of the company you had switched to. Note you can’t see the report anymore.

It can be confusing because once you launch the system monitor, then even when you change companies in Epicor, it doesn’t change the company in the system monitor. Unless you put it in menu maintenance and launch it from within the new company context.

Yes I tell users to just restart Epicor after switching companies if their report doesn’t popup. Definitely simpler than trying to explain this ridiculousness to them.

I agree with what you are saying except for the fact that in the other companies the reports pop up as expected. If I change to one of these companies it does not until I reload, then if I go back to one where it will normally work it does not come up again until I restart it. This isn’t just that the report does not show in system monitor, it shows as having run successfully in the history but never actually launches the PDF until it is restarted. and then that holds gaing back to a ‘normal’ company.

Yep, I see the same thing every day. It’s very frustrating.

So every time your users switch between any company they have to relaunch epicor? That’s the part that doesn’t make sense to me with the scenario you are describing, in my case most of them work, it is only this handful that don’t, if it was any company switch I could understand it being a task agent/system monitor issue like you describe, but only on these ‘special’ ones?

In my case, the issue appears at random. In other words, it not that it has to be done every time when switching from company a to company b. It’s just sometimes (with no apparent pattern) reports stop popping up after switching companies and then a restart is required. If you are seeing any kind of pattern PLEASE tell support. They won’t accept a bug because I can’t reproduce the issue.

I’ve had similar situations in the past and in those cases it was resolved by clearing out the Epicor AppData/ProgramData/etc folders and reinstalling epicor on that particular machine because the System Monitor would actually crash on that machine but this is different and I am not sure how that would look with cloud vs on-prem prior to the browser first deal.

I have hesitated to open a ticket on this issue since we are moving to 2024 shortly and I have told them to test it in that version to see what the result is, if it still fails then I will open a ticket but otherwise support won’t do much for the version I am on so I am just wondering if anyone else has seen this type of behavior before.

Problem still exists in 2024.1.8

I just had them run some tests of switching between companies and running random reports and the issue does not appear to be there so I think you are dealing with a different issue than the one I am.

Like I said its random.