web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

'A Record was Locked' Error when Running Inventory Checklinks

(0) ShareShare
ReportReport
Posted on by

Good Evening everyone, 

When running checklinks within Inventory we are getting the following error: 

'A get/change next operation on table "IV_Item_MSTR" failed. A records was already locked.'

We cleared the Activity, SY00800, SY00801, temdp..dex_session and tempdb..dex_lock tables and have run reconcile on Inventory without error. 

Does anyone have any ideas on why we continue to get this error when trying to run Checklinks? 

Thank you in advance! 

Stephanie 

*This post is locked for comments

  • Community Member Profile Picture
    on at

    Stephanie, did you ever get an answer?  I am having the same issue where check links thinks there are locks, however, activity/sy00800/801/dex lock/session are clear???!!

  • Suggested answer
    Raghu Anipeddi Profile Picture
    35 on at

    Hi,

      I have tried the steps available in the link "http://cowmasterscorner.blogspot.in/2017/03/dynamics-gp-when-running-item-check.html"  and  "https://www.gpug.com/communities/community-home/digestviewer/viewthread?GroupId=247&MID=30191&tab=digestviewer&CommunityKey=4754a624-39c5-4458-8105-02b65a7e929e".

    As per the article:

    The IV00101.Purchase_Tax_Options field for those records is 0.
    Valid values are

    1 – Taxable

    2 – Nontaxable
    3 – Base on customer / vendor


    Update all affected items and item classes accordingly to resolve the error message.


    --Alternatively, you can also run this script to set all items without a purchase tax schedule to non-taxable.

    update iv00101 set Purchase_Tax_Options = 2 where Purchase_Tax_options = 0

    --Also run this to update the item classes to prevent new items from starting with 0

    update iv40400 set Purchase_Tax_Options = 2 where Purchase_Tax_options = 0

     

    Let me know if this works for you.

    Thanks,

    Raghunath. 

  • Raghu Anipeddi Profile Picture
    35 on at

    Hi,

     I have tried the steps available in the link "cowmasterscorner.blogspot.in/.../dynamics-gp-when-running-item-check.html"  and  "www.gpug.com/.../viewthread;MID=30191&tab=digestviewer&CommunityKey=4754a624-39c5-4458-8105-02b65a7e929e".

    As per the article:

    The IV00101.Purchase_Tax_Options field for those records is 0.

    Valid values are

    1 – Taxable

    2 – Nontaxable

    3 – Base on customer / vendor

    Update all affected items and item classes accordingly to resolve the error message.

    --Alternatively, you can also run this script to set all items without a purchase tax schedule to non-taxable.

    update iv00101 set Purchase_Tax_Options = 2 where Purchase_Tax_options = 0

    --Also run this to update the item classes to prevent new items from starting with 0

    update iv40400 set Purchase_Tax_Options = 2 where Purchase_Tax_options = 0

    Let me know if this works for you.

    Thanks,

    Raghunath.

  • Community Member Profile Picture
    on at

    I tried the solution of changing the tax options to 2 when it's 0 but I still got the same error.  It didn't work for me.  Any ideas?

  • GMA Profile Picture
    1,074 on at

    Probably next best bet is to turn on dex logging and/or setup a SQL trace to see what is actually going on and possibly which table is causing the error.

    As you may know, checklinks checks that several tables all have the correct "ID" records and so it may be a table that is not referenced during reconcile that is causing the problem.

  • Community Member Profile Picture
    on at

    I had this issue and noticed that it stopped on every record that had the column MSTRCDTY  = 0 in the IV00101 table.

    I took a back up of the IV00101 table and then changed those records so the column MSTRCDTY  = 1. Check links then continued without locking.  

  • Community Member Profile Picture
    on at

    Thanks Alex but that's not my case.  All records in IV00101 already had MSTRCDTY=1

  • Community Member Profile Picture
    on at

    Hi Edward,

    All I can suggest is look at the Checklinks progress and identify which records it is stopping at, compared to the ones that it is skipping. Then check the contents on the IV00101 table and examine what is different between the records that it thinks are locked compared to those that are not.

    Alec

  • Richard Wheeler Profile Picture
    75,854 Moderator on at

    I would first check for any SQL locks and if there are any you can simply reboot the server or stop and start SQL. This will clear any SQL locks. Do the usual select * from dex_session and select * from dex_lock and the SY00800 and SY00801 tables. Report back after this and we will move onto plan B.

  • Suggested answer
    Community Member Profile Picture
    on at

    Thanks Alec.  I found that the problematic records have these 3 fields being 0, PRICMTHD, VCTNMTHD,TAXOPTNS.  They are not supposed to be 0 according to the column definition.  So I changed PRICMTHD and VCTNMTHD to 1 and TAXOPTNS=2 then checklinks started to run without errors.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans