We have multiple web apps running on our server farm and have Sharepointboost AD Sync deployed on all of them. The Timer Job shows as being scheduled for all web apps, on all servers, we have 2 WFE and 1 App server. The timer job shows "Success" on all web apps, but no results are returned for any job run on Server 3, which happens to be our App Server. Web apps that have the job run on Server 2, one of the WFE servers, work as expected. I have confirmed that App Pools have the same access, web.config files show no Sharepointboost differences, even the GAC looks the same. The solution is deployed to all the web apps, showing deployment to all the servers as well. In the Timer Job Scheduling I can see the job scheduled for each web app on all 3 servers, but it only appears to run on 1 server per web app. The one that works shows server 2 in Job History, the one that does not shows server 3 in Job History.
Is there a way for me to tell if the process that the Timer Job is supposed to start, the Synchronization Profile, is actually being called? Looking in the ULS logs I can not see any differences between the one that is working and the one that isn't. Is there any way for me to force the jobs that are currently running on server 3 to run on server 2 as a test? Any other steps I can take that anyone can think of to debug this, I am in discussion with the folks at Sharepointboost as well.
As we did not develop this, we have no access to the code or assembly directly.