Hi all,
Does anybody know what causes this error: Shaded orders can not be locked and were not printed
We're getting it while batch printing and I'm almost positive none of the orders that should be printing are already locked.
There is a TASK solution (#15234) which talks about entries that need to be made in t_defaults if this is happening due to Tessitura freezing during the print job, but I'm not sure if that is the issue you are having.
Thanks. I did notice that one, but that seemed to deal with not being able to get into the orders after the job froze. We didn't have a previous attempt freeze, the set just stopped because of the error, but the orders aren't locked...or if some are, I can't figure out which. I did try the solution in there anyway but it didn't affect any rows.
We had this happen a couple years ago and I think it might have been because a local procedure that was not written correctly was running at the time and locking those orders, or at least doing something to cause the error.That might be a good thing to check on.