noorulhaq
23rd November 2003, 07:43
Hi,

We are facing serious problem while we are running "Post Integration Trascations to Finance Transactions (tfgld4201m000)" session as it is not showing any process and gets hung.

Aslo gives error Message "Error 107 (Record is locked) on tfgld415111 (Max retries (10) exceeded)"

Please advise.

Thanks.

Norman
24th November 2003, 07:26
noorulhaq

In the past I have had a similar problem with Triton version 3.1.
The problem was due to the fact that we had integration turned on to real-time. The system could not cope with the backlog of integration transactions.

Our solution was to turn off the real-time mode and create 6 daily jobs run over a 24-hour period that ran the posting of integration session. This worked for us and the backlog was cleared in about 5 days.

This may help.

Regards

Norman

noorulhaq
24th November 2003, 08:04
Norman,

Thanks for your reply,

It is not real-time posting. The session is scheduled to run at Midnight as a Job. Still we are facing same problem.

Please advise.

lbencic
24th November 2003, 18:03
First thing to try is rebooting your system. This will clear any old locks. If the problem persists - the code could be causing the problem, or your environment. Check if any patches, etc. were applied before this started happening.

This Post (http://www.baanboard.com/baanboard/showthread.php?s=&threadid=119&highlight=Error+107) talks about a similar problem. It leads to an oracle discussion, but you can see that there are some settings in the Environment (db_resource) that can effect this error. You can also see from the post that it can be a serious problem, and Baan Support may be of use to you.

Please backup before letting anyone try anything. The reboot should be safe, but the 107 lock table errors in NT can be the signal of other problems. This type of thing can snowball, pls backup!

jlalgue
27th November 2003, 10:38
Hi,

I had the same problem in tfgld4201m000 (but in table tfgld418).
Probably there was a process locking this table.

I rebooted the server and it was solved.