Skip to main content

Resolving The tenant 'default' is not accessible error or Regenerating new symbols for Business Central On-Premise for customised Database

Problem Statement:

This blog is only applicable for Business Central On-Premise Version. If you are stuck in the same issue, try this at your own risk. 

I had installed Business Central v14 (Spring 2019) On-Premise with LS Retail. In this, Business Central comes with a ready made setup to connect with VS Code. As I restored the DB given by LS Retail, I could no longer connect to VS Code. This could be a potential case of Running C/SIDE and AL Side-by-side or customising on top of LS Retail.

Despite all the configurations being correct in project's app.json and launch.json, I could no longer connect to Business Central, I couldn't download any Symbols and I couldn't publish any Extension to Business Central. 
App.json and Launch.json

I checked all BC Administration setup for Development and it seemed to be perfectly fine. I had Enabled Development Endpoint,  Development Endpoint Port was 7049Target was set to Internal, Enable Debugging was Enabled.
Development Endpoint - BC Administration
I checked my Permissions were set to SUPER, I had setup the WebServiceKey.
User Card
I had also checked my Developer License but still had the same thing 

This is where I noticed that, even after reverting back to the standard Demo BC(14-0) Database no longer helped. The only error I got was "The tenant 'default' is not accessible error".

I tried changing the AL Language Extension for VS Code guessing this could be a potential issue that BC v16 AL Language might not be able connect to BC v14.

Also, to ensure I created a new Server Instance and Web Server Instance, and tried connecting the same error "The tenant 'default' is not accessible error"
AL Project : The tenant 'default' is not accessible
I even tried a fresh install of BC but I simply couldn't figure out!!


  • Microsoft Dynamics Business Central On-Premise DVD
  • AL Language Extension
  • VS Code
  • Basic Understanding of PowerShell

Books & References:


When it comes to a new Database, the Symbols for the DB used are not pre-generated.
AL Extension requires this symbol to be installed for symbols to be downloaded in the project for compilation process.
When these new symbols for different Database are generated, it also checks if the Data version is as per the latest version prior to publishing these new Symbols to the Database.

Importing the NAV-Admin module in PowerShell.
Import-Module NAV-Admin
Refresh the Command in Command Add-On in PowerShell

1. Checking if the Symbols are present for newly restored Database using Get-NAVAppInfo command:
Get-NAVAppInfo -ServerInstance <SERVERINSTANCENAME> -SymbolOnly
If you notice, you will see that the Application.App NAV-App is not installed.

2. You need to Generate the Application Symbol App:
i. From C/SIDE Development Environment, export all the objects into a single .txt file excluding the Codeunits >= 2000000001.

ii. Move this .txt file into a folder making sure that the folder has only this .txt exported of the objects

iii. Running the SymbolReferenceGenerator <Source Folder> <Output Package File Name> <Package Name> <Package Version> [<GenerateDevelopmentPackage>] command

Generate Symbols

3. Publish the NAV-App as Symbols Only:
This command will Publish as Application symbols so that it can be downloaded inside AL Project.

4. Check if  NAV-App is installed:
This step will make sure that your NAVApp in compiled with the latest symbols and installed in BC.
Get-NAVAppInfo with

5. Check if AL Extension in VS Code can connect to Business Central:
After Restarting the Business Central Instance, I tried to connect to AL Project with Business Central Server.
AL Project: Symbols have been downloaded
Finally, I got it running and now I can deploy the Extension App to Business Central.


Thus in this blog we saw how to enable customising using AL Extensions for a database that has already been customised by a 3rd Party.
I would like to share the acknowledgement of this blog to Mr. Manoj from Microsoft Support Bangalore for sharing his research and content and helping me in this issue.
I hope this helps!


Unknown said…
I didn’t know about the SymbolReferenceGenerator tool.
Another option could be to download the symbols extension from a W1 database and install that extension in your database.
After that you should be able to connect and run finsql.exe with generatesymbolreference command parameter and there’s no need to export the objects text file.
Yes your method is right and would serve perfectly for standard BC. But I had installed LS Retail Objects in C/SIDE because of which I had to export the Text files to generate a BC + LS Symbol Reference.

Thanks for your comment as things got more clear!
Unknown said…
Yes. My method is just to let you bypass the “tenant is not accessible” error and connect to Business Central.
Even in your database, with LS Retail, if you install the standard symbols extension, you should be able to connect VSCode to BC.
But yes, after that you’ll have to run finsql with the generatesymbolreferences command parameter to update the symbols to include LS Retail objects. But no need to export files.

But many thanks for your article. I didn’t know about the SymbolReferenceGenerator application.
That makes sense..
Actually the export is necessary for SumbolReferenceGenerator.exe
I couldn't run the finsql generatesymbolreference as it would give me limit upto 47 character other wise it would throw an error.
Thanks for your response I will consider it the next time.

Popular posts from this blog

Understanding and How to use APIs Business Central - 2

Introduction: In my last blog post ( Business Central API -1 ) on Creating API in Business Central, we discussed all the commonly used properties of the page, query, and controls like field and data-item. In today's blog, we will be diving deeply into the validation of the data passed through the API endpoint, how it enters into the source tables and is manipulated to be inserted/modified into single or multiple tables. Also, I will be demonstrating how APIs are to be used. Pre-requisites: Microsoft Dynamics Business Central (SaaS) VS Code( ) AL Language Extension( ) API V1 from Business Central On-Premise DVD Books & References: API V1 from Business Central On-Premise DVD API(V1.0) for Business Central ( Click Here ) API(Beta) for Business Central ( Click Here ) Theory: Understanding API in Business Central 1. BINDSUBSCRIPTIONS: Use to trigger IntegrationEvent for the Codeunit stated

Enum Object in Business Central - How to create and how to extend!

Introduction: Since the dawn of Business Central Era (2nd April 2018 - Today), there are many new data types introduced by Microsoft. One such data type is Enum(Enumeration). Essentially, what enumeration is having a single select value with multiple options at a given time! Well, I know what your thinking what about the 'Option' data type. Anyways, enough of talking let's just dive in! Disclaimer:   The knowledge in this blog is true and complete to the best of authors and publishers knowledge. The author and publisher disclaim any liability in connection with the use of this information. Pre-requisites: Microsoft Dynamics Business Central (SaaS or On-Premise) VS code with AL Language extension Code: 1. Enum as an Object: Just like Tables and Pages, Enum behaves like an Object. Enum Object Note that Extensible means that the Enum Object can be extended in another module. By default, this property is set to TRUE. Enums created in a module(App), ca

Creating APIs in Business Central - 1

Introduction: While writing a blog on Automated Testing in Business Central, I was going through sample apps provided by Microsoft and realized that the complexity is nowhere close to what examples Microsoft has provided on In this blog, I will try to explain how APIs work and how to be creative with the implementation. Also, an API which were in beta are finally out with version V1.0 in the April 2019 release let's see some important key things from development aspects. This blog is going to be theoretical one kindly bear with me. Pre-requisites: Microsoft Dynamics Business Central (SaaS) VS Code( ) AL Language Extension( ) API V1 from Business Central On-Premise DVD Books & References: API V1 from Business Central On-Premise DVD API(V1.0) for Business Central ( Click Here ) API(Beta) for Business Central ( Click Here ) Solution: Key Requirements: API source table