The Sales Line table cannot be changed because it is locked

LovelyLady

I am calling custom made webservice to create headers and lines inside the Nav database. I get inturrupted in between by this error message. Can anyone please suggest how I can avoid conflicts between 2 calls to update the Sales Line table.

"The Sales Line table cannot be changed because it is locked by another user. Wait until the user is finished and then try again."

kine

The NAV side is based on NAV 2009 webservices or some older solution? How you are calling the webservices? Synchronously? Asynchronously?

LovelyLady

The webservice call is made and waits to recieve the header number , that means the call is asynchronous.
then the lines are sent along with the header number recieved and wait to recieve a success message.
The insertion of the lines is the stage when I recieve the table locked error message.

kine

Is this problem only on live system? Is it working when there is only one active user on the system?

LovelyLady

A couple of users are synching with the same Nav database simultaneously. It is highly likely that they coincide while synch process.
that means- more than one users are making web service calls to add Sales line.
It works fine in the Developement environment where I am the single user.

kine

Ok, than you need to look to the performance or make the timeout longer in NAV. It looks like the line creation is taking more than the timeout...

stryk

This might help you to identify the cause of that blocking issue, and maybe to solve it:
http://dynamicsuser.net/blogs/stryk/archive/tags/Locking/default.aspx

Cheers,
Jörg

LovelyLady

annot access the link, "Service Unavailable" is the message I recieve.

stryk

Hmmm ... should work ...

You could also go to my BLOG http://dynamicsuser.net/blogs/stryk/ then click on the tag "Locking".

LovelyLady

Cannot find anything good about it ...........

knolvsky

hii..

i have the same problem with my NAV 5...and then i got my problem solve \:D/ \:D/

i kick the other user that use my ID login..(file-->database-->information--->sessions--->and lookup)

and then wooss...there is no problem again..

REASON :

maybe the other person user my ID and we edit the same thing..