Resolving Error - 'Invoke-NAVApplicationDatabaseConversion: An unexpected error occurred after a database command was cancelled.'
Olister Rumao
3,957
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 Migrations2. Basic understanding of SQL versions
After checking the Event Viewer it was clear to some extent that the property is not present in the SQL version of BC14.
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.
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.
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.
After this, I restored the DB to the new version of SQL Server and then was able to proceed.
Conclusion:
This was originally posted here.
*This post is locked for comments