Skip to main content

Resolving Error - 'Invoke-NAVApplicationDatabaseConversion: An unexpected error occurred after a database command was cancelled.'

Introduction:

While doing Data Migrations from BC14 to BC22, there was an error 'Invoke-NAV ApplicationDatabaseConversion: An unexpected error occurred after a database command was cancelled.' in Business Central in the Database Conversion.
I confirmed the DB connectivity is working fine and failed only at Invoke-NAVApplicationDatabaseConversion.

Pre-requisites:

1. Understanding of BC Data Migrations
2. Basic understanding of SQL versions

Demonstration:

As you know that while upgrading NAV / Business Central, you are requested to run the Application Database Conversion.
In this case, I was directly trying to convert from BC14 to BC22 and I ended up with this error.

To confirm this I checked the Upgrade compatibility matrix https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-v14-v15-compatibility and then there was an unexpected error.

I tried to do the steps again and seem to receive the error again.



After checking the Event Viewer it was clear to some extent that the property is not present in the SQL version of BC14.


The resolution was to upgrade the DB version from SQL Server version 14 to SQL Server version 15.
After this, I restored the DB to the new version of SQL Server and then was able to proceed.

Conclusion:

Ideally, your SQL server version should be compatible with the latest installed but if you are doing an upgrade and the difference in version is huge then it is recommended to restore your DB to SQL Server which is directly on the target SQL Server version. 



Labels

Labels:

Comments

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta...
Post a Comment
Read more

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Ed...
Post a Comment
Read more

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 1

Introduction: The launch of the Microsoft Dynamics Business Central gave way to upgrades from Microsoft Dynamics NAV to Microsoft Dynamics Business Central. This blog is about sharing my experiences with Business Central Upgrade from NAV 2017. However, for different versions of NAV, a set of steps are to be followed to get to NAV 2017 and then upgrade to Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations#online https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths https://www.sauravdhyani.com/2018/10/msdyn365bc-data-upgrade-to-microsoft.html Demonstration: Microsoft Dynamics NAV to Microsoft Dynam...
Post a Comment
Read more