13 Sep’17

Dynamics NAVConverting a Database from NAV 2016 to NAV 2017 in Microsoft Dynamics NAV


To upgrade the database to NAV 2017,  following main steps must be completed.

  • Convert the database
  • Upgrade the Application code
  • Upgrade the Data

This blog gives a steps wise procedure to covert the database from NAV 2016 to NAV 2017


  • Microsoft Dynamics NAV 2016
  • Microsoft Dynamics NAV 2017
  • Microsoft SQL Server Management Studio(SSMS)


  1. Backup NAV 2016 Database   
    1. Open SSMS and connect to the SQL server.
    2. Expand the Database to NAV 2016 Database i.e ‘Demo Database (9-0)’.
    3. Navigate to Task > Back up.
    4. Click on Add then Navigate the path where you want to store the back up(.bak) file by clicking on the Assit edit button.
    5. Specify the file name then click on OK.
    6. A pop up displays after the back up of NAV 2016 database is taken.
    7. Clear all Microsoft Dynamics NAV Server instance records from the dbo.ServerInstance table in the database on SQL Server.You can do this by using SQL Server Management Studio to open and clear the table.
  2. Upload 2017 Licence file in NAV 2016 Database ‘Demo Database (9-0)’
    1. Navigate to File > Database > Alter.
    2. In the Integration tab, Enable Save licence file and select the licence file of NAV 2017 then click on OK.
    3. Alternatively, Select the Tools menu > Licence Information then Upload.
    4. Restart the NAV Server Instance in the Microsoft Dynamics NAV admin.
  3. Uninstall NAV 2016 and Install NAV 2017.
  4. Convert the NAV 2016 Database to NAV 2017.
    1. Open Microsoft Dynamics NAV 2017 Development Environment, select the NAV 2016 database i.e ‘Demo Database (9-0) and click on OK.
    2. Till will prompt to convert the database dialogue box.
    3. Click on OK. A confirmation dialogue box pops up.
    4. Click on OK. This will take few minutes. A message pops up once the database is converted.
  5. Connect the Server Instance to the converted database
    1. Open Microsoft Dynamics NAV Administration, Click on Add Instance.
    2. Specify a Server name and unique port numbers then click on OK.
    3. An instance is created, open the instance, click on edit, expand the Database tab.
    4. In the Database Name specify the converted database name then Restart the instance. In the below screenshot NAV90 is the server instance name for the converted database.
    5. Open the converted database in the NAV 2017 Development Environment. Navigate to the Tools menu > Options.
    6. Specify the Server Instance name, Server Port and the Management port.
    7. Click on OK.
    8. Make sure the user login has access to the Converted database.
      • Open SSMS, expand Logins and select the user.
      • Under the ‘Select a page’ tab, Select User Mapping, enable map for the converted database and master database and enable db_owner then click on OK

    9. Under master database, expand the Tables, select the Dbo.$ndo$srvproperty then properties.
    10. elect the Permissions then select the user and grant Select permission to the user.
    11. Restart the Server instance after applying the above permissions.
  6. Run the schema synchronization to initialize the database.
    1. Open the Microsoft Dynamics NAV 2017 Development Environment, navigate to Tools menu then click on Sync. Schema For All Tables > With Validation.
    2. This will pop up a dialogue box, click on Yes.
    3. After synchronizations, navigate to Tools menu > Build Server Application Objects.
      Building the application makes sure that the database is also synchronized in the SQL server and compiled.
    4. Building the application may lead to compilation errors which needs to be fixed.
      Follow the below link to fix .NET variable errors refer this link
    5. Build the Application again until the Build is successful.


The database is successfully converted to NAV 2017. The next step is Upgrade the Application code for which you can refer this link

Written by

Chris D'Silva

Software Developer

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Dynamics 365 Client Diagnostics

    15 March’ 2018

    Main cause of Performance Issues: Bandwidth and latency are the primary characteristics which affects the performance o...

    Read more
  • Closing Blind Shift in MPOS and CPOS in Dynamics 365 for Retail

    15 March’ 2018

    Manual For closing Blind shift in POS: Blind shifts terminate the currently ongoing shift and when logged in a new shif...

    Read more
  • Persistent Filters in the Power BI Service

    13 March’ 2018

    Introduction: The feature is finally release, and it is power BI has announced general availability of persistent filt...

    Read more
  • Cause and Solution for Scribe MSMQ not receiving Message from AX

    10 March’ 2018

    Issue: Microsoft Message Queuing (MSMQ) service running on Server might be unable to receive messages. Therefore, messa...

    Read more
  • User Privileges on SharePoint – D365 Document Integration

    10 March’ 2018

    Overview: Often, we wonder what could be wrong where we see a generic error on Documents in Dynamics 365. Something lik...

    Read more