Scheduled Reports haven't worked since we upgraded to 2022 years ago. I think I've figured out why, or at least a major clue.
Before I get the canned response with the instructions on how to setup Scheduled Reports, just know I've done it all over the last few years. My latest try last week I setup a brand new computer, I didn't install a firewall, I totally disabled UAC, I did it all and the errors I found were the same. I even created a new DB from scratch and everything.
Basically when it was time for the scheduled report to fire, the exe would silently fail and the time would increment 1 hour to try again. It repeats this ad nauseam.
I've called support about this multiple times over the years with NO solution, and they usually just blame me or my network environment for the issue. After I found my clues in the post below I called back again to show them my findings and they told me they have no direct line to the dev team and gave me a canned response.
This functionality has been broken for 3 years. 3 *YEARS*. This bug has survived at least 2 major version changes, 5 different PCs, 4 different databases. The issue isn't me or our environment.
So, first I learned that with edition 2022, Quickbooks Desktop dropped support for 32-bit machines. This is the same edition our Schedules Reports stopped working.
After lots of digging and looking at logs and procmon and god know what else, I'm 99% sure that 'ScheduledReports.Scheduler.ex'` is trying to load 'QBWRPT32.DLL', which is a 64-bit DLL used by Quickbooks Desktop as well. This explains why it is shipped as a 64-bit library now.
Unfortunately, ScheduledReports.Scheduler.exe is a 32-bit app and cannot load this DLL, so it throws an exception and commits seppuku.
This explains why our Scheduled Reports stopped working after we upgraded to 2022 years ago. We have since upgraded 2 more times hoping it would be fixed with no luck.
I tried to call support again to tell them what I have found and they told me they don't have any direct ties to the dev team and cannot pass anything along.
This seems like a pretty straightforward fix and can be tested in a matter of minutes. There are tons of posts here asking about this broken functionality but no one does anything about it.
I really need to have a direct ticket with the dev side and not support side, we can actually track this and get it fixed. We used this functionality very heavily before it was broken.