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

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to update your Business Central to Latest CU

Introduction:  There are times when Microsoft releases the latest major version upgrade for Business Central Upgrade and you face many issues with it. As soon as the bugs are reported to Microsoft, they start to fix them and ask you to upgrade to a certain Cumulative Update. In this blog, I will be sharing my experience with Business Central v21 CU0 upgrade to Business Central v21 CU2. Pre-requisites:  Business Central DVD for Latest CU Basic Understanding of Business Central CU Updates Books & References:  List of Update Packages How to Update CU version Demonstration:  1. Check the current state of BC: As part of knowing the current state of your Business Central environment, I'm assuming that your Business Central Environment will have some data in the standard Base App also there will be customization with extended tables and newly created tables. Customization - TableExtension on Customer Table  Customization - Custom Table created Make a note of the data that is present i