INDEX   SEARCH   <--BACK

NT Service isn't printing

KB ARTICLE: KB0019
KB DATE: 18/09/2005, revised 08/04/2006, 02/05/2008, revised 09/07/2011
REQUIRES VERSION: 2.00 or above
 

For a video demonstration on running as an NT Service see our video demos here

1. Make sure monitor mode is turned on.

2. Make sure the service is running.
check for "Batch And Print.exe" in the task manager, if not running check the BPPNTService.log file for errors.

3. Clear the log files if you're using log checking.

4. Check that the service login account has access to the files and printers.
NOTE: printers drivers are installed under a user profile so will not be available unless installed under the login account.  (LOCALSYSTEM has access to all)

5. On windows 2008r2 / 64bit systems, right mouse on "Batch And Print.exe" and select properties, set to "Run as Administrator"
NOTE: for pdf's on 64bit systems, we recommend you use the PDF to PS or PDF to PCL conversion options.

6. To see what the service is doing run with UserInterface = Yes in the BPPNTService.ini (edit with notepad)

7. If you are using mapped drives make sure they are available under that login, otherwise use UNC paths e.g. \\server1\testfolder

8. If you are getting can't print or association error printing PDF's try re-installing Adobe Reader under the account name you are going to use.

9. try printing .txt files first to see if it's a problem with the 3rd party application associated to print the files, if it is try re-installing the 3rd party application under the account name you are going to use.
otherwise we have optional internal printing addons available, see: http://www.traction-software.co.uk/batchprint/addons/index.html

10. Try first without running as a service.

11. if you get error: "A device attached to the system is not functioning. This could be due to an association error"
This could be because the 3rd party software e.g. Microsoft Word was installed under a different user profile to what the BPPNTService.ini is configured to use, most 3rd party applications don't complain but some do as the registry entries are under USER_LOCAL, the way around it is to change the BPPNTService.ini login / password to the same username as the user profile used to install the software.
AccountUsername = "LOCALSYSTEM"
AccountPassword = ""