The BarTender Print Scheduler Service is a Windows Service that manages BarTender print engines and intelligently assigns jobs to them while maximizing performance.
This article will provide an overview of the Print schedulers functionality and role within the BarTender environment.
BarTender 2019 and later
BarTender Print Scheduler Service uses a single pool of print engines so that resources are used efficiently. The Print Scheduler service ensures that jobs printing to a specific printer will always come out of that printer in the order the requests were received. When documents contain embedded data that can change, such as serialized counters, they will be bound to a single print engine to ensure that they print in the correct order.
The BarTender Print Scheduler has three main functions:
Manage the print engines, which includes:
- Starting/stopping the print engines dynamically
- Opening/closing documents automatically
- Handling the printing process
- Automates print jobs through the use of BTXML Script
- Runs BarTender designer as a service in the background without need for user input
Print Scheduler Process Using a BTXML Script
- Receive BTXML script
- Uses an open Print engine or opens a new print engine
Opens document and during print time will access:
- Linked resources such as images
- Processes data from BTXML
- Sends print job to the print queue
Configuring Print Scheduler Settings
Have a look at the following article for information on how to configure the Print Scheduler settings: How to Configure Print Scheduler Settings.
Common Print Scheduler Issues
Enabling visible window for print scheduler:
- Stop the integration
- Stop the Print scheduler service
- Go to main installed directory and open Pint Scheduler.Service.exe.instance.config
- Change the <Console EngineVisibility="None" />. to all instead
- Save the file
- Open command prompt and navigate to main install directory
- Run PrintScheduler.Service.exe /console
- Start the integration
- After testing revert the settings
BarTender Print Engine could not be started
- The issue had to do with the Print Scheduler being unable to inherit the necessary information from the Local System account in order to run correctly. In these small, uncommon instances, the resolution is to have the Print Scheduler use the same elevated credentials that the integration is using as well.