We are using CR 13.0.4 within a .NET service running on Windows server 2008 to print to several printers, this all goes well for the majority of the time but every now and then the printing stops without an error. The only thing that needs to be done to get the printing going is to log on to the server where the service is running. The printing continues where it stopped so we are not missing any printouts. But since the printouts are used in a production line we can not have this delay. Furthermore since this problem is bound to happen during out of office times, we won't always be able to respond without losing precious production time.
We pinpointed the problem to the PrintToPrinter call, which simply waits for no apparent reason, until someone logs on to the server.
Does anyone ever seen this or similar behaviour and/or have a solution for this issue?