Skip to main content

NAV 2013 R2 - The Object table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the SQL Server data type.

Hi all,

Let's discuss a issue resolution which most of us are facing after applying Rollup 5 for NAV 2013 R2 with Build  36281.

The Error Message that i faced is -

The Object table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the SQL Server data type.
Field : Version List
Type: Text 248
SQL type : VARCHAR(80)




Reason for Error Message (My Understanding) -

You tried to Open the Database created with a build earlier than 36281 in Build 32681 and didn't upgraded.

You clicked cancel when system asked to upgrade the database.

Here is what i Meant -

1. I have a database with old Build (say 35473) as shown below.



2. By Mistake i tried to open the database with Build 36281 and clicked cancel as shown below.



3. when i tired to open database again with old build (say 35473) it gives me error as shown below.


Resolution -

You need to upgrade the database to Build 36281 or Higher.

I hope you will be able to resolve the issue with the suggestion above.

These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

Regards,
Saurav Dhyani
saurav-nav.blogspot.com
Labels:
Location: Sector 62, Noida, Uttar Pradesh, India

Comments

Post a Comment

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.
28 comments
Read Complete Article »

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.
21 comments
Read Complete Article »

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.
Post a Comment
Read Complete Article »