Skip to main content

NAV 2009 - Metadata for object of type Table with id 2000000073 is in a failed state.

Hi all,

With NAV 2009, while using web services we face a common issue related to Metadata of the Table with Id 2000000073.

Let's see the reasons behind it and how to resolve it.


Error Message -

<faultstring xml:lang="en-US">
Metadata for object of type Table with id 2000000073 is in a failed state. This is caused by a previous exception: Metadata for object of type Table with id 2000000071 is in a failed state. This is caused by a previous exception: There are errors in the text conversion because text no. 1971-27 does not exist in the .stx file. Internal error: 47-1
</faultstring>
<detail>
<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">
Metadata for object of type Table with id 2000000073 is in a failed state. This is caused by a previous exception: Metadata for object of type Table with id 2000000071 is in a failed state. This is caused by a previous exception: There are errors in the text conversion because text no. 1971-27 does not exist in the .stx file. Internal error: 47-1
</string>

Reason -

1. You might have an exe upgrade from Version 5/4/previous to NAV 2009.
2. Incorrect Hotfix Update.

Resolution -

1. Take a Navision backup of the Database.

2. Create a New Database in the Navision (say 2009/2009SP1/2009R2).

3. Restore the backup taken in step 1 into the database.

4. Stop Services (Web Service & RTC Service).

5. Configure the Service tier to point to New Database.

6. Start the Services (Web Service & RTC Service).

Hope this help as i am getting so many queries for the same.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype

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.