Has anyone ever experienced a batch in GP that's stuck showing "Printing" status on Batch Status? The transactions in the batch were still un-posted but the user was able to continue with their other work (which, to them at least, meant that it was completed). Once we had the user log out and log back, that action seemed to enable the batch to complete processing (and then the transactions showed as posted). Root Cause? Someone said it might have been a "connection loss" during the process? Or some other form of "process contention within GP" that caused this? Anyone have any other theories? Thanks in advance for your input.
*This post is locked for comments