Dynamics NAV 2018 "The tenant 'default' is not accessible" when compiling a table

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 Development Environment will detect a running server automatically.

Check that:
1. The Microsogt Dynamics NAV Server is running
2. The Management service is configured
3. The firewall is open for the management port if remote
4. The server is running with only one tenant
5. Microsoft Dynamics NAV Development Environment is running as Administrator, or
6. UAC is turned off.

After restarting the NAV service, compile went nicely, and I continued working. Next table import+compile -> same errors again.

It appeared that I was missing pos. 5 of the list above...

 

Comment List
Anonymous
  • I got the error again and ended up here again. And this time I both solved it and thought I would share my solution.

    In your case , the solution clearly was that you didn't start the C/Side client with admin rights. Because of that any objects that you imported did not import/compile correctly. 

    If you had done this in a different way, then importing them put your database tenant (default) in a state of 'OperationalWithSyncPending'. Iif importing them again is not an option, ie. via DevOps CI, then the state can be corrected to 'Operational' via the Sync-NavTenant Powershell cmdlet.

    Just for the reference, Microsoft made a page on this problem. :

    And one on how to fix it:

  • Same problem, but with NAV in Docker, accessing external SQL database....

  • Hi... the point 5 is annoying me. I don't know why I have to run Dynamics NAV development as Admin, really??? what the hell is going on???!!!

    By the way, after think about it and making some more testing, we are a team programming in our computers and DB and NAV service is installed on a Server... if I run Dynamics NAV development as admin, doesn't work, I get the same error... the solution is to make my user (and all the other programmers) admin in server (where NAV service is running). That way we can make changes in tables with no erros like that. I don't like this solution, but it's the only way to do our work properly by now.

  • I  had the same problem when peforming upgrade steps from 2017CU4 to 2018CU1 and when starting the Windows Client form within the Development Env.

    After changing the following value in the Service CustomSettings.config the error did not appear anymore.

     <add key="DeveloperServicesEnabled" value="true" />

    But some other services still had the value set to "true" and did experience the error...

  • I had a similar issue after importing some objects (a mix of tables, pages, reports). The solution that worked for me was to sync-navtenant from the NAV 2018 Administration Shell.

  • I have the same issue, but resolved by clearing  <C:\Users\...\AppData\Local\Temp\>

Related
Recommended