This question has arisen for earlier versions many times, and as many times it has been answered as well. In the old times it was easy enough, just delete contents of some tables and voilá, you are in. After three-tier architecture things got a tad bit more difficult. My answer has been for a long time to use a T-SQL script to add my AD account to all relevant NAV tables so I can just start the RTC client and start using the new database conveniently. The original script is stolen from Anonymous commenter in Waldo's blog , and during the years I have added all the new fields that have been…

I installed a new development server and a brand new MS SQL 2017 server. After installing all the NAV components to the NAV development server, I restored the demo database, run the script to add my AD user to NAV tables, started the service and tried to log in. Not so suprisingly, I received an error, but this time I had never seen it before. The error message is in the title and attached screenshot. After brief examination, I found out that this table is indeed missing from the NAV installation disk database backup. Luckily it is very easy to create: * Open the database with Development…

I was doing some changes to NAV 2018 tables and run into this error after import + compile a table as a text file. The error is very confusing, since in this special case I do not have any kind of tenancy, it is just old plain familiar all-in-one solution with normal SQL, normal virtual machine as NAV Server and local development environment. I tried re-compiling, and the error went even wackier: "Unable to process table changes because the Microsoft Dynamics NAV Development Environment cannot connect to the specified Microsoft Dynamics NAV Server instance: <snip> Microsoft Dynamics NAV…