Error when converting a database from 2013 to 2017

AitorEG
AitorEG Member Posts: 342
in NAV Three Tier
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:
"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.

Answers

  • AitorEG
    AitorEG Member Posts: 342
    A bit more information:

    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

Categories