I've got this error and I'm really confused. I don't think it is caused by a deadlock...
I'm using a NAS to do some processing.
The NAS is running all day on an endless loop, looking for records to process. After processing every record, I do a COMMIT to unlock tables used by the NAS.
I do also do some kind of error control, so that if a record throws an error, the NAS can move to the next record and forget about the first one.
Here is the code for the endless loop and the error control:
WHILE TRUE DO
BEGIN
Table1.RESET;
Table1.SETRANGE("Error Field",FALSE);
IF Table1.FIND('-') THEN
REPEAT
CLEAR(Codeunit1);
Codeunit1.FunctionToSetRecordToProcessAsGlovalVarOnCodeunit(Table1);
IF NOT Codeunit1.RUN THEN
BEGIN
FunctionToInsertErrorMessageAsCommentOnRecord(Table1,GETLASTERRORTEXT);
CLEARLASTERROR;
Table1."Error Field" := TRUE;
Table1.MODIFY;
END;
COMMIT;
UNTIL Table1.NEXT = 0;
END;
And here the code on the OnRun trigger
Table1Lines.SETRANGE("Document No.",Table1GlobalVar."Document No.");
//*****
// Here the processing code for both header (the global var that the previous function passed to the codeunit) and its lines
//*****
Table2.INIT;
Table2.TRANSFERFIELDS(Table1GlobalVar);
Table2.INSERT;
IF Table1Lines.FINDSET THEN
REPEAT
Table2Lines.INIT;
Table2Lines.TRANSFERFIELDS(Table1Lines);
Table2Lines.INSERT;
UNTIL Table1Lines.NEXT = 0;
Table1GlobalVar.DELETE;
Table1Lines.DELETEALL;
Table2Lines.INSERT gives an error because the line already exists.
Ok, this can happen. But... the error control on the function that does codeunit.RUN should catch it...
It is catching many other errors (the blocked error when trying to insert item on a transfer line and the item is blocked, error saying that Quantity cannot be less than shipped quantity if the process tries to reduce quantity on a partially posted transfer line, etc. etc.).
I've even seen the error that is poping now about line already existing on Table2Lines on my error control table...
I've also seen on my error control table a record that could not be processed because of locking.
But now... instead of catching the error and moving on... I do see the error message on the server's Event Viewer, and right after the error, there is another event on the Event Viewer that says: Internal error 1247 in module 19.
It cannot be a deadlock, as the NAS starts (and has got the error) at midnight and there are no users at that time...
It could have locks on some other times, as the NAS is running all day long and at some point, of course, there are users on the database... but this particular one, at midnight, it is impossible!
Any help will be really appreciated
Login
Register
RSS Feed
Rules
FAQ
Search the forum
)
