Skip to main content

Metadata for object of type Table with id 20000000xx is in a failed state. This is caused by a previous exception: Object of type Table with id 20000000xx could not be found.

Hi all,

Sometime we face the error while trying to connect or change company in Role Center Client.

Metadata for object of type Table with id 20000000xx is in a failed state. This is caused by a previous exception: Object of type Table with id 20000000xx could not be found. 

xx Can Be - 01,07,09,10,20,22,24,26,28,29,37,38,39,40,41,42,43,44,45,46,47,48,49,50,52,53,55,56,58,59,63,70.

These are the System Hidden Tables in Navision. For the list of hidden tables refer this post.

Where is Metadata Stored?
Metadata is stored in Table 2000000071 Object Metadata for all navision objects ( visible / hidden).

Why this error?
This error occured if there in no metadata for any object in the table.

When Metadata is Created?
This has been created while we restore the database,if you remeber there is a new process in RTC Versions "PROCESSING OBJECTS" after creating keys.

How to create Metadata?
For Visible objects you can compile the object and the metadata will be created.
For Hidden tables, you need to work around.

1) Go to File, Alter Database. Select Option Tab.
2) Check Single user & Uncheck Enable for Microsoft Dynamics NAV Server, as shown in image below.

3) Click Ok, after that you will receive message as shown below hit ok.

4) After process get completed, Check Enable for Microsoft Dynamics NAV Server as shown in image below.

5) Click ok on the message that appear. It will process all objects (visible & hidden) as shown below.

6) Once process get completed, goto alter database and uncheck the single user.

Now stop and start the NAV Server service and Run the Role tailored client. It will start working without any issues.

Thanks & Regards,
Saurav Dhyani


  1. Thank you! This really help me! I've got some problems with metadata of Windows Language Table and doing these steps, now it is solved.

  2. Many thanks for this. It helped me to quickly resolve the problem.


    1. Hi,

      You are always welcome :)

      Thanks & Regards,
      Saurav Dhyani

    2. Thx, This really helps !!

  3. When I try to step 4, I get the following message: Table 200000009 has no name.

    Please advice.

    1. Hi,

      The table you are referring is a hidden Table Named Session.

      I am not sure about the error, but can u just check creating a list form based on this table and tell me the results.

    2. I have also the same error and I am not able to create list form for it

      Warm Regards,
      Uday Mer


Post a Comment

Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.