Upgrade BC230 to BC240 (On Prem): Error when running Start-NavDataUpgrade on Base Application

greys
Member Posts: 29
hi there,
I'm currently upgrading an on-prem BC230 to on-prem BC240. When I run StartNavDataUpgrade, I get the following error:
"Could not upgrade the extension 'Base Application' by 'Microsoft' from version '23.0.12034.12841' to '24.0.16410.18056' for tenant 'default' and company '' due to the following error: 'You tried to invoke the Report object with the ID xxx from the object Upgrade - BaseApp. An object with that ID does not exist in the current application compiled with emit version 24034.'"
The objectID xxx refers to an object no. in our own addon solution. I have followed several upgrade paths in the past, but I never encountered such an error. Does anyone have a clue where this comes from?
Regards,
Josh
I'm currently upgrading an on-prem BC230 to on-prem BC240. When I run StartNavDataUpgrade, I get the following error:
"Could not upgrade the extension 'Base Application' by 'Microsoft' from version '23.0.12034.12841' to '24.0.16410.18056' for tenant 'default' and company '' due to the following error: 'You tried to invoke the Report object with the ID xxx from the object Upgrade - BaseApp. An object with that ID does not exist in the current application compiled with emit version 24034.'"
The objectID xxx refers to an object no. in our own addon solution. I have followed several upgrade paths in the past, but I never encountered such an error. Does anyone have a clue where this comes from?
Regards,
Josh
0
Answers
-
It appears to be one of our own reports that is present in the Custom Report Layout table (it has a word layout attached to it). Apparently, the upgrade code errors out in the MigrateCustomReportLayouts function in codeunit 5409. There it wants to move records from Custom Report Layout to Tenant Report Layout table. The object ID's refer to reports in our app (which is published yet not installed).
Has anyone ever encountered this?0 -
We ran into this exact same issue, and other upgrade paths did not throw this error.
Fortunately, we were dealing with a very small development dataset, so we re-installed BC240 from scratch, loaded our customizations and re-imported our dataset.
I am curious, were you able to get around this?
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions