We recently split our AppServer off of the SQL server onto its own server and everything seemed to be going fine until we tried AP Check Printing. When we run the AP Process Payments process, it just hangs in the system monitor and the user’s Epicor client goes to “Not Responding” indefinitely. Restarting the Task Agent process on the new server clears the hung process from the System Monitor but the checks won’t print.
As a test, I reverted the one user that prints checks back to the old AppServer (which I left running on the SQL server temporarily) and they were able to print checks with no problems. All other reports and processes seem to be running fine on the new AppServer and Task server.
Are there any additional security settings or configurations that need to be configured on the AppServer specifically for the check printing process?
One additional piece of information that I just noticed. While the process is hung, it appears that it is creating a new instance of the process in the System Monitor every 15 minutes:
Hey, Jay. Interesting problem. Question for you. Have you reviewed System Agent Maintenance?
I suspect the AP Checks process may need to write/read to the server’s file system during the process due to its complexity. You may need to update the Server Data Directory to something accessible to your new application server. Let us know what you find!
Epicor advised that I should clear the Appserver URL field and set the processing delay to 3 (it was previously 0), but neither of those suggestions helped.
For context, we previously ran a single server that had DB, application, etc. all on it. I recently split that into a three server setup (DB on one, main application on another, and task agent and other automated processes on a third). I previously had the EpicorData folder shared only on the Task server but, after your suggestion, I shared that folder on the Application server, as well (just in case), but that didn’t seem to change anything.
Unfortunately, I didn’t get an answer from Epicor support but I did end up solving this issue. For future reference, in case anyone comes across this, it had to do with our printer setup. We use Server printing and when I switched over to the new application server, I hadn’t yet moved all of the printers to the new server.
The printers were setup as shared printers on the old server and every other report printed fine (printer maintenance in Epicor was setup with the \OLDSERVER\Printer name). The issue ONLY existed in processing AP payments, for whatever reason. Installing the printer on the new server and sharing it from there then changing Epicor’s printer maintenance to \NEWSERVER\Printer name solved the issue.
Thanks for sharing the final solution. Also, if you’re using it, don’t forget to update routing rules in the Report Style module. I’ve had to change networked printer settings in the Epicor printer module, but it doesn’t propagate those changes to my routing rules that auto-select a printer for certain tasks.
