Skip to main content

How to find the the root cause of Business Central not being accessible and resolving it - Part 1


In this blog, I will be discussing the approach of handling the Business Central downtime from an End User's perspective.
I will be addressing how to debug and understand what could be a possible source of error which is could be causing the downtime of Business Central Production & Sandbox.
Business Central not accessible


1. Microsoft Dynamics Business Central
2. Access to Business Central Admin Center
3. Access to Office 365 Admin


1. Check if you have a license assigned to your user: If you get the licensing error like the below, you need to confirm if you're getting logged in with the correct user and your license is correct.

Missing License or Invalid User

You can go to to verify the user logged in.
Dynamics Home -   

To be sure if this is not a license issue, kindly contact your Administrator or a friend who has access.
In Tell Me key in 'Users' > Select the User
License is not present in Business Central

At this point, if your Administrator says that there is a License assigned to you in Office then you need to ask them to refresh the User Group Permissions by Navigating to  Actions > Refresh User Group and Action > Update User info from Office 365
Refresh User & Update User info from Office 365

In the end, it all comes to if you actually have the license. This only the Admin can verify in Office 365, Admin.
Go to Admin in Office 365 > User > Active Users > Select the User > License  and Apps

Office 365 Admin > User  License

After providing the License to the User, the Admin should 'Refresh User Group' in Business Central.

2. Check if your app/add-on/extension is installed:
Every time a Sandbox is upgraded, the Add-on / Extension is removed. This means all the role centers, profiles, etc. will be reset to the default one.

3. Check if the session is causing any issues:
I have observed a couple of times that the sessions are not expired. This means that whenever you refresh your Business Central, you may log in to the same session.
In order to make this sure, you can simply login into INCOGNITO mode or PRIVATE mode in your browser and login from and then select your environment.

Also, if you see multiple sessions in Business Central Admin Center, you can cancel the session as well.
Go to Environments > Select your Environment > Manage Sessions > Select your session > Cancel Sessions

Manage Sessions in Admin Center and Cancel previously Logged In sessions

4. Check if your environment is on Upgrade:

It may happen that your Business Central environment in on Upgrade and you may login at the same time.

Unable to Access Business Central during Upgrade

In order to confirm if your environment is on Upgrade, you can head over to Business Central Admin Center.

Business Central is Updating


These activities might be pretty obvious for someone working in Business Central for more than 6 months but most of the end-users don't know what to do or how to work things out.
I hope this helps in some way or another.


Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

Business Central Environment Blinking after update to v20

Introduction: Business Central Updates after updating to version 20.x, there is a common problem which is observed. The Business Central environment starts blinking as per the video below - Pre- requisites : Business Central Online  v20 Demonstration: 1. Restart the Business Central Environment: Go to Business Central Admin Center > Select the Environment >Sessions > Restart Environment. 2. Ensure that your URL contains Tenant ID: When you login into the Business Central Environment, make sure that your links are in the following formats Sandbox :<SandboxEnvironmentName>/?sandbox=true Production :<ProductionEnvironmentName>/ If you URL like or any other format without Tenant ID, chances are that you will end up with the issue. Also, you can login through Admin Center URL -  Connect from URL in BC Admin Center 3. Check the status if the insta