During a batch printing session, the system lost its connection. The entire batch was locked and we ran through the knowledgebase solution and it did not fix the issue. The problem now is someone has posted the batch. My question is if I go through the knowledgebase solution again will it revert back to the original setting?
Maria,
We have had an issue where the batch printing froze during the print process and it would place the batch in a locked status. I would have to place the batch in a held status until they could go in a try to reprint the batch again. What we ended up doing is updating the firmware for the printers and changing some printer configurations. This has cleared up all the printing problems all together. Perhaps I am not understanding your particular problem but I hope this helps.
Naomi
Our problem is the client lost connection to the server during the batch printing. So, when it came back up the batch had a status of open but is was locked and it showed that all the tickets had printed but they really didn't. Our DBA found the knowledgebase solution regarding this issue but it did not fix the problem but now someone has posted that batch and we don't know what to do now.
Hi Maria,
Are the tickets still locked?
Typically I think the solution is to place the batch on hold (this is probably what the knowledge base solution was) so that it can be posted and therefore release the locked seats.Since you already posted the batch you should be able to go back and reprint the batch.