Sage 100

Very finicky for sure.

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924650093753

It has to be a print queue on the server that does not prompt for file name, set as the default printer for the Windows login used for the task.  We've asked Sage to stop the nonsense status page that prints to the printer, but no luck so far.

It can be a Generic / Text Only printer (paused), but it must be local to the server (not redirected).

Thanks for confirming my thoughts.  So does the Microsoft xps document writer qualify or do I ask for an actual network printer?

Very finicky for sure.

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924650093753

It has to be a print queue on the server that does not prompt for file name, set as the default printer for the Windows login used for the task.  We've asked Sage to stop the nonsense status page that prints to the printer, but no luck so far.

It can be a Generic / Text Only printer (paused), but it must be local to the server (not redirected).

XPS doesn't work since it prompts for file name.  You'll end up with a locked process.

You can use a real printer if you want.  Now I'm in the habit of using a dummy print object like this (pointed to File or NUL), to avoid the waste of paper.

Thanks for confirming my thoughts.  So does the Microsoft xps document writer qualify or do I ask for an actual network printer?

Very finicky for sure.

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924650093753

It has to be a print queue on the server that does not prompt for file name, set as the default printer for the Windows login used for the task.  We've asked Sage to stop the nonsense status page that prints to the printer, but no luck so far.

It can be a Generic / Text Only printer (paused), but it must be local to the server (not redirected).

Please forgive my tech skills (or lack thereof), but this is what I have so far.  I set up the generic printer.but do not see any tab where I can point it to a file or null.  My test cleared Sage and the output is sitting in queue.  Is there another step?

XPS doesn't work since it prompts for file name.  You'll end up with a locked process.

You can use a real printer if you want.  Now I'm in the habit of using a dummy print object like this (pointed to File or NUL), to avoid the waste of paper.

Thanks for confirming my thoughts.  So does the Microsoft xps document writer qualify or do I ask for an actual network printer?

Very finicky for sure.

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924650093753

It has to be a print queue on the server that does not prompt for file name, set as the default printer for the Windows login used for the task.  We've asked Sage to stop the nonsense status page that prints to the printer, but no luck so far.

It can be a Generic / Text Only printer (paused), but it must be local to the server (not redirected).

The printer is just to handle the Sage Task Scheduler's need to print something... you don't need the queue to do anything other than not cause problems for your task.

Please forgive my tech skills (or lack thereof), but this is what I have so far.  I set up the generic printer.but do not see any tab where I can point it to a file or null.  My test cleared Sage and the output is sitting in queue.  Is there another step?

XPS doesn't work since it prompts for file name.  You'll end up with a locked process.

You can use a real printer if you want.  Now I'm in the habit of using a dummy print object like this (pointed to File or NUL), to avoid the waste of paper.

Thanks for confirming my thoughts.  So does the Microsoft xps document writer qualify or do I ask for an actual network printer?

Very finicky for sure.

https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=225924650093753

It has to be a print queue on the server that does not prompt for file name, set as the default printer for the Windows login used for the task.  We've asked Sage to stop the nonsense status page that prints to the printer, but no luck so far.

It can be a Generic / Text Only printer (paused), but it must be local to the server (not redirected).