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?
- John Murphy
- PowerBuilder
- Tuesday, 16 March 2021 04:04 AM UTC
- Page :
- 1
There are no replies made for this question yet.
However, you are not allowed to reply to this question.
However, you are not allowed to reply to this question.
This looks like the dw.Print() command is called and executing, but there's no printer selected.