NAV2015 upgrade error - metatdata table 89 not found

davmac1
Member Posts: 1,283
Doing an upgrade from NAV2009 to NAV2015, I received an error:
The metadata object Table 89 was not found.
This is really strange for 2 reasons:
1) Table 89 is the BOM Journal Line which is deleted in NAV2009 at the end of step 1
2) I had converted earlier versions of the database without any problems.
I received this error at the end of the tools -> data upgrade in NAV2015.
There is no table 89, and there should be no table 89.
Does this mean the metadata got messed up in NAV2009?
NAV2015 - some of the upgrade looks like it is handled at the executable level and is not fixable by code.
The metadata object Table 89 was not found.
This is really strange for 2 reasons:
1) Table 89 is the BOM Journal Line which is deleted in NAV2009 at the end of step 1
2) I had converted earlier versions of the database without any problems.
I received this error at the end of the tools -> data upgrade in NAV2015.
There is no table 89, and there should be no table 89.
Does this mean the metadata got messed up in NAV2009?
NAV2015 - some of the upgrade looks like it is handled at the executable level and is not fixable by code.
David Machanick
http://mibuso.com/blogs/davidmachanick/
http://mibuso.com/blogs/davidmachanick/
0
Answers
-
Hey,
Just run Table Journal Line Dimension and filter for Table ID 89 and i hope you find some records.
If there are any delete them and try again the data migration process.
Hope this helps.
Thanks & Regards,
Saurav Dhyani
Do you Know this About NAV?
Connect - Twitter | Facebook | Google + | YouTube
Follow - Blog | Facebook Page | Google + Page0 -
Thanks.
I have been deleting the BOM Journal Lines in the past. This time the user did it and I have no lines but 2 dimension entries.
Do you know of a safe way to make the resume work? It always starts too early for this problem and fails.
I have though of code to bypass all the conversion routines except the dimensions.
Have you experimented with this before?David Machanick
http://mibuso.com/blogs/davidmachanick/0 -
To get around the last problem, I bypassed the code to update the data, and only updated the dimensions. Since it deleted the old dimensions after it processes them, the current upgrade logic was able to complete updating dimensions.David Machanick
http://mibuso.com/blogs/davidmachanick/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