Although it seems this question is specific to AP Check Printing, I believe it is some type of technical issue or overlooked setting:

One user, using Windows Remote Desktop Connection , experiences a crash when doing an AP check run.  It does not provide an error message or I would be able to troubleshoot, as we sometimes have experienced with Paperless/Crystal issues, etc.  Once it crashes, we, of course, get the bank code in use error, which we clear.  There are three other Sage users on that workstation, none of which print checks.  However, they are successful in printing other forms, like invoices.  There is never an issue printing reports nor does the affected user have issues printing anything else to her local printer from the remote connection.

We are able to successfully print the same checks from another user's workstation, all of whom are connected locally to the network.  This same user has been able to go back into check printing at a different time of day, when she was interrupted, and the checks printed fine.  Last week it happened again and I had all remote connections log out,  had everyone log out of Sage and rebooted that workstation and the checks were printed successfully.

I have worked with Sage for a long time and have never experienced this issue and feel comfortable it is not the software, but something we are missing.  Wish I knew what it doesn't like that causes it to crash.  We are running Sage 2014 Update 4, have not third party products, Windows 2012 server for Sage server and also for remote workstation.  Thank you, in advance, for any thoughts or advice about what to look for.