Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Error when converting a database from 2013 to 2017
AitorEG
Member Posts: 342
Hi everyone,
I am having a problem when I try to open a database from NAV 2013 in the development environment of NAV 2017.
The database only has the tables, and a few CodeUnits from a partner AddIn, needed in the conversion process (I see this issue when converting from 2009 to 2013).
When the conversion process starts, I see this error:
Why can this happen?
This step is paret of the process of upgrading from 2009 to 2017.
Thank you very much.
I am having a problem when I try to open a database from NAV 2013 in the development environment of NAV 2017.
The database only has the tables, and a few CodeUnits from a partner AddIn, needed in the conversion process (I see this issue when converting from 2009 to 2013).
When the conversion process starts, I see this error:
"Codeunit 1 does not exist"
Why can this happen?
This step is paret of the process of upgrading from 2009 to 2017.
Thank you very much.
0
Answers
As I've said before, this is part of a migration between NAV2009 to 2017. The migration to the 2013 version is correct, and I make the process of transfering data with the page 104002, for all the companies.
But after this, instead of uninstalling the NAV2013 and installing NAV2017, I create a SQL backup, and I restore it intio a different machine, which has NAV2017 installed. And when I rty to open in this new machine the databse in the develepoment environment, is where I see the error.
May be I should compile all the objects in NAV2013 before making the backup?
I'm quite lost with this issue, and I don't know what else to try.
I will really appreciate any hint.
Thank you all