Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Upgrade from v14 to v25 error

(1) ShareShare
ReportReport
Posted on by 17
I'm currently trying to upgrade one of our older databases from v14 to v25 using the MS cookbook and I ended up with following error in Task 17 during the upgrade of Microsoft Base Application v25:
  Could not upgrade the extension 'Base Application' by 'Microsoft' from version '14.0.0.0' to '25.0.23364.25445' for tenant 'default' and company 'Southern Cross Pet Insurance' due to the following error: 'Cannot create the specified RecordId of length 448 for table 808482864 because it is invalid.' and AL stack trace: 
  "Upgrade - BaseApp"(CodeUnit 104000).UpgradeBankAccountsMobilePhoneNo line 9 - Base Application by Microsoft
  "Upgrade - BaseApp"(CodeUnit 104000).UpgradeContactMobilePhoneNo line 10 - Base Application by Microsoft
  "Upgrade - BaseApp"(CodeUnit 104000).OnUpgradePerCompany line 33 - Base Application by Microsoft
  "Upgrade Triggers"(CodeUnit 2000000008).OnUpgradePerCompany(Event) line 2
The event log also says this:
A record's keys, in table: 808482864, could not be deserialized into NavRecordId because the field type 12336 is not a valid NavType.The primary key value that caused an invalid NavType: <redacted>, startIndex: 0, and length: -1.
First, we thought the Change Log could cause this, but it apparently remains even after I had switched it off.
Has anyone ever faced an issue like this? I'm running out of ideas about what the cause may be.
  • Verified answer
    davhrb Profile Picture
    17 on at
    Upgrade from v14 to v25 error
    I figured this out. In my case it was caused by the corrupted data in the Bank Account table's field "Bank Stmt. Service Record ID", so the upgrade function UpgradeBankAccountsMobilePhoneNo was not able to loop through the records (which is kinda weird, I probably saw such thing for the first time; the error message is not very helpful either). I've set up a clear value (0x) to this field in all the records via SSMS and now the upgrade went through without further errors. 
  • davhrb Profile Picture
    17 on at
    Upgrade from v14 to v25 error
    Thanks for your reactions. That is the problem: no table with ID 808482864 exists, anywhere. It's definitely not a table from our application, I also cannot locate it in the MS System, Business Foundation and Base applications. I tried to google this error and the only mention of the issue like this is on some German forum, where the resolution is not mentioned and the site seems not working anymore (I tried to register and ask but the administrators haven't approved my post yet).
    So, I'm not able to check nor delete the table.
  • Suggested answer
    YUN ZHU Profile Picture
    84,278 Super User 2025 Season 1 on at
    Upgrade from v14 to v25 error
    It seems that table 808482864 was added directly in the base application?
    After backing up the database, delete this table to see if the problem still exists.
     
    Thanks
    ZHU
  • Vahid Ghafarpour Profile Picture
    11,742 Super User 2025 Season 1 on at
    Upgrade from v14 to v25 error
    Verify the configuration of the table with ID 808482864. Ensure that the primary key field is correctly set up and that there are no inconsistencies in the field types.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard >

Featured topics

Product updates

Dynamics 365 release plans