Hello Randolph.

I would advise taking a look at the documentation for the reporting service if you have not done so already: https://docs.thinkwisesoftware.com/docs/kb/report_service

Specifically the architecture section https://docs.thinkwisesoftware.com/docs/kb/report_service#architecture .

Basically, the service calls a couple of stored procedures to get information about which report records it must perform from the queue.

The first one of which is “rpt_get_reports” https://docs.thinkwisesoftware.com/docs/kb/report_service#rpt_get_reports .

The implementation of these stored procedures is usually left up to the developer so I cannot say how it has been implemented in your project.

Having more than one service use the same report queue records is not recommended since there is no locking mechanism between them. This can cause the same report being generated more than once.

However, the names of these procedures can be changed for a specific reporting service by modifying the configuration file: https://docs.thinkwisesoftware.com/docs/kb/report_service#configuration

So in theory you could create a “rpt_get_reports_srvprt02” procedure which only returns records from the queue that were entered with a specific printer name and have the reporting service on the second server query this procedure using the “GetReportQueue” setting.

It might also be a good idea to upgrade to version 5 of the service if you are still on version 3 or 4: https://docs.thinkwisesoftware.com/docs/kb/report_service#upgrading-from-v4-or-v3-to-v5 .

Doing so will allow you to use more than one service on the same server: https://docs.thinkwisesoftware.com/docs/kb/report_service#running-as-a-windows-service

I hope this is enough information to get you started on a solution to your problem.

Kind Regards,

Tim Waalewijn