Locking versus rollback

RoelofRoelof Member Posts: 377
Hi,
I have a question about locking of a table. What happens if a user 2 get's a warning that a table is locked and needs to wait until user 1 is finished and then to try again. Does User 2 still sits in the piece of code where it stopped because of the table locking or has it already left all the code and is back to a screen entry for example.
I'm asking because we have this issue with one of our customers. We have currently installed E-Ship from Lanham to one of our customers. That works great except sometimes we have a locking problem. There is no proper rollback when that happens. At one hand Navision is creating a Shipment and on the other hand Navision is NOT updating the Saleslines, so that the Qty to ship field is not updated.

Please advise.

Thanks,
Roelof de Jong.
Roelof de Jonghttp://www.wye.com

Comments

  • 2tje2tje Member Posts: 80
    As far as I know. Navision should do a rollback, unless a COMMIT is programmed. I don't know E-Ship, but you could check the code for this.

    BTW, there should not be a difference between a C/Side and SQL db, but what are you using?
  • kinekine Member Posts: 12,562
    For 2tje:
    There is difference - MS SQL server option have no such a message about locking (only for deadlocks...) I assume that Roelof is using Native DB...

    For roelof:
    You can use client monitor for checking, if there is (and where is) the commit statement... run client monitor, run the action which leads to the locking, after the message stop client mon and check the lines. You can use the extended client monitor objects (see download) which give you much better picture of what happend...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • DenSterDenSter Member Posts: 8,307
    When Navision errors out, it rolls back to the latest COMMIT, regardless of whether you are on C/SIDE or SQL. If there is a transaction with a commit in the middle, and it errors out after that statement, it will not roll back to the original starting point of the transaction, but to the latest COMMIT.

    There are many COMMIT statements in E-ship. It is possible that if your E-ship has been modified that there is a COMMIT in there somewhere that commits a partially posted transaction.

    Get in touch with Lanham support and have them address this issue.
  • RoelofRoelof Member Posts: 377
    Hi Daniel,

    Yes, that's what I thought.
    I will contact Lanham and see if they can help me further.
    Thanks for your help.

    Roelof de Jong.
    Roelof de Jonghttp://www.wye.com
  • PerPer Member Posts: 46
    This document describe some of the problems that has been seen with installing E-Ship in large installations. It also mention many of the changes that occur when using a more direct and real-time approx. This causes extra load on the system and could require upgrade of hardware to handle the extra load.

    http://www.lanhamassoc.com/faq/FAQ_00048_WEB.htm
Sign In or Register to comment.