09-16-2022 10:11 PM
I created a new print queue for an existing process, and I am unable to map it to a network printer, and because of that, I'm unable to add it to a print server. However, this is only happening in our Production environment. I have no problems doing this in Test.
Long story short - we have a workflow process that prints documents to network printers on our Production server. Each branch has their own print queue, which is mapped to a specific printer at that location only. We have Thick client running as a service for this process using the -PS switch.
This is not something new --- we've had it in place for 7 or 8 years. This new print queue is for a new location that is being converted this weekend (9/16-9/18/2022).
We upgraded from v16 to v18 in October of 2020, and obviously hadn't added to this process since before that, because this is the first time we've had this problem.
Is there possibly a registry key on the Production server that could cause this?
Any help you could provide would be greatly appreciated --- thank you in advance!
09-20-2022 12:46 PM
Hi
Check out this TKB article and the System Administration MRG for information on What's required to print a document to a network printer from the Workflow 'Print Document' action?
What components etc are required to print a document to a network printer from a Workflow timer using the print document action?
I hope this helps!
Thanks,
~Alan
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.