.jpg)
We are getting an error "A StartDocPrinter call was not issued" when running reports at one of our customers. I want to believe this is a printer/os issue and not a Telerik reporting issue, as we have not seen this at other customers.
TIA for any input.
1 Answer, 1 is accepted
Hi Mark,
We have had cases with this error in the past and they were always related to OS updates. The most "recent" case was with the Windows 10 update KB50000802 update but that was back in 2021.
Back then, several users reported issues with the blue screen (Windows fatal error screen) after installing the above update. As a result, Windows has pulled this update, as WinCentral reports in the article Microsoft acknowledges Windows 10 update KB5000802 BSOD issue *update*. This update affected the printing, and people were reporting that their systems would crash into blue-screen and restart when trying to print.
The solution should be to have the user update his Windows version, preferably to the latest. If that doesn't resolve the problem, please attach a trace listener to the application to try and log the exception - How to: Create and Initialize Trace Listeners - .NET Framework | Microsoft Learn. The Event Viewer could also have logged the problem - Event Viewer – How to Access the Windows 10 Activity Log (freecodecamp.org).
I hope that the issue will be resolved after the system is updated, please let me know if you need further assistance.
Regards,
Dimitar
Progress Telerik