Okay, I got mine resolved (figured out a workaround, which helped give me an understanding of what was happening) and I will share:

1. The issue happened in relation to the Syracuse server being on a different subnet from the Mongo server (I think firewall, but I wasn't able to get them to open it up between those servers, which lead to my workaround)

2. I installed a second instance of Syracuse (I called it the internal one) on the Mongo server (anything on the same subnet should be fine)

3. Noting that both Syracuse servers would not both show OK as the status in the hosts function

4. From this second installation of Syracuse it was discovered that each has its own batch server

5. I stopped the batch server on the external Syracuse server, and started it on the internal one

6. At this point I am able to get the accounting tasks to start and process

P.S. I hope this helps since it cost our team over 6hrs of work to uncover!

Okay, I got mine resolved (figured out a workaround, which helped give me an understanding of what was happening) and I will share:

1. The issue happened in relation to the Syracuse server being on a different subnet from the Mongo server (I think firewall, but I wasn't able to get them to open it up between those servers, which lead to my workaround)

2. I installed a second instance of Syracuse (I called it the internal one) on the Mongo server (anything on the same subnet should be fine)

3. Noting that both Syracuse servers would not both show OK as the status in the hosts function

4. From this second installation of Syracuse it was discovered that each has its own batch server

5. I stopped the batch server on the external Syracuse server, and started it on the internal one

6. At this point I am able to get the accounting tasks to start and process

P.S. I hope this helps since it cost our team over 6hrs of work to uncover!

in my case the syrcause  and mongo on the same server.

Thanx