1. John Murphy
  2. PowerBuilder
  3. Tuesday, 16 March 2021 04:04 AM UTC

We just moved a bunch of scheduled tasks from Win Server 2013 to 2016 and now scheduled tasks cannot print.  It leaves an instance of splwow64.exe in task manager for each print failure. Using 2019 R2. Any Ideas?

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 16 March 2021 20:00 PM UTC
  2. PowerBuilder
  3. # 1

Hi John;
  What technique(s) are these Apps using to print?
   Also, are these Apps run as a Window's "Service"?
Regards ... Chris

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 17 March 2021 21:09 PM UTC
Good question Miguel ... I would assume the "default" printer of the account that the batch EXE is run under.
  1. Helpful
  1. Miguel Leeuwe
  2. Wednesday, 17 March 2021 21:24 PM UTC
Hence my question :)

John, I was thinking, maybe there's no "default" assigned printer for that account?
  1. Helpful
  1. John Murphy
  2. Thursday, 18 March 2021 08:58 AM UTC
There is a default printer.
  1. Helpful
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Tuesday, 16 March 2021 07:32 AM UTC
  2. PowerBuilder
  3. # 2
Comment
  1. John Murphy
  2. Tuesday, 16 March 2021 16:42 PM UTC
The PB app does close and everything ran fine. It is just that the dw.Print() does not work and in task manager details there is an instance of splwow64.exe for every time a PB app tried to print.
  1. Helpful
  1. Olan Knight
  2. Wednesday, 17 March 2021 19:50 PM UTC
Are you sure that you have a printer selected?

This looks like the dw.Print() command is called and executing, but there's no printer selected.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.