Order Error

I think we've had that error before when a PC died mid-transaction, and the batch appeared open even though the PC was off. So we held the batch via the backend, replaced the PC with a another but named it the same thing, and had the same user log in to that new PC, open the order, close it, exit the batch, and then other people could access it. Not sure if all those steps were entirely necessary, but it worked.

I think we've had that error before when a PC died mid-transaction, and the batch appeared open even though the PC was off. So we held the batch via the backend, replaced the PC with a another but named it the same thing, and had the same user log in to that new PC, open the order, close it, exit the batch, and then other people could access it. Not sure if all those steps were entirely necessary, but it worked.

HI Matt,

Good day.

error message came from here:

in [TP_LOCK_TABLES_NB]

line 146-165:

------------------------------

Select @table = 't_order'

Select  @null_rows = count(*)
From  t_order (UPDLOCK)
Where order_no = @order_no and mir_lock = 0

If @null_rows = 0 GOTO OldOrderErrMsg1

GOTO StartLockingMirrorOld

OldOrderErrMsg1:

--If an error from above, give message, release locks and exit
SELECT @err_msg = 'Data in ' + @table + ' table is checked out by an another batch. Data could not be locked!'
print @err_msg
RAISERROR(@err_msg, 11, 2) WITH SETERROR
Rollback Tran OldOrderTran
return

---------------------------

So as you can see, in t_order table the order you want to open has mir_lock field not zero.

that is it.

it means this order is being opened by someone else.

or if not, you have to set mir_lock field to 0 from back end.

have fun

Ben