Report generation failed for a broader date range because the linked server's datetime used a Month/Day/Year 12-hour format, which caused timestamp parsing errors.
The issue has been addressed and the behaviour is now as expected.
To benefit from this fix: