Hello ! We have a Navision 2.01b server running. While one off our Developers runs a simple Dataport, and a second Developer trys to import a new(and different object) then second one receives the message: (translated from german) The object table is loked from User XXX I can remeber that this happend once again, and we deleted the zup file and exportet and reimported it again. Then the problem was solved. But this time it is impossible to solve the problem, and i don’t know what to do further. Maybe someone her has a solution for us.
Typically you get this error when : User A import a FOB file User B try to save an object (ie: Dataport) User B will get the message (“The Object Table is locked by User A”) Now in your case if you’re just RUNNING a Dataport I’m guessing that this dataport is trying to do some modifications in the Object Table (ie : update of Version List, Objet Date and Time ?) But I might be guessing wrongly…
Hello Tarek! In our case the user A runs a simple dataport, wich only imports data into a Table 123(sample) and user B trys to import a ne report, wich has nothing to do with any object that user A uses (totaly different). As i wrote we had that some time before, it looks that either the zup file or the object has a damage (let say a bit is not set correctly) As this happend before, we where able to solve the problem by deleting the zup file and deleting the object and imported it from an backup again. But in the actual case deleting the zup file and deleting the dataport solved not the problem. So what to do further ?? When user A runs a simple dataport wich ONLY imports data into table 123 (without any further code in the dataport) there is no need, that the WHOLE object table is locked. Maybe you have a solution.
Hi, it’s only a thought but perhaps the system wants to check the rights from user A and locks the object table during checking. bye Andre
Hello Andre Don’t think that it is a permission check Problem, cause it only happens with this special dataport, and user A has admin rights. This mostly happens, if for example User A receives during the development (in this case a dataport)a GPF.
I once had the same problem and reported it to navision. The answer is quite simple. While you import data into an empty table the DBMS creates a TableData record in the object table where the real data is stored in the blob field. During this import the object table therefore is locked. The solution is before you start the dataport insert into the table one dummy record so the tabledata record is created and run after this process the dataport. the object table will not be locked again ! Greetings
Hello Kurt ! What you wrote sounds plausible, cause in our case user A was importing Data into an empty table. Thanks for that information, (good to know) now the situation is clear. I will try that again with an empty test table.