6 thoughts on “NAV 2013 R2 | The Object Metadata table cannot be changed because it is locked by another user

  1. waldo

    Well, in earlier builds, you would be in for a treat .. . When the object metadata and the snapshot is out of sync .. it’s darn difficult to get it back into sync. Definitely when you want to preserve data…


  2. Pingback: ArcherPoint Microsoft Dynamics NAV Developer Digest - vol 12 - Microsoft Dynamics NAV Community

  3. Jens Glathe

    You almost sound like me now 😉 One of my other favourites is when you copy from a blocked object (a report, for example),, do your changes, want to save it under a new name and it’s telling you “Locked by must by empty in somethingorother”… End result is you can cancel the new, unsaved object, unlock the source object, and try again.

    Liked by 1 person

    1. markbrummel Post author

      Jens, a lot of people complained about this. Microsoft listened and changed the behaviour in NAV2015.

      Don’t know about your blocked object. I’ll test it and report it if true, it sounds annoying.



      1. Sergio Carbajo

        Hi Mark,

        Cumulative Update 9, during data upgrade step 2 I get the same error!

        I am trying to compile everything and run schema syncronization with no luck. What would you do in this case?


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.