Skip to main content

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 : https://businesscentral.dynamics.com/<SandboxEnvironmentName>/?sandbox=true
Production: https://businesscentral.dynamics.com/<ProductionEnvironmentName>/

If you URL like

https://businesscentral.dynamics.com/SandboxName 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 installed or dependent apps are updated:

Go to Admin Center > Select Environment > Apps

    
If any app is in Install Update or Updating then ensure that they are Up to Date. 

4. Login into Environment through https://portal.office.com:

I have observed that sometimes irrespective of all these steps being followed or not, the issue still does not resolve it self.
Hence, you can go to portal.office.com  > Select Chocolate Button on Top Left > Select the Environment you want to login


5. Login through Incognito Mode:

If nothing works, its possibly the browser cache. A best way to avoid browser cache is use Incognito Mode.
Use Incognito Mode > Login with your Office 365 Account > Open Business Central from Office 365

If the environment is still blinking after trying to login through all the above methods, try to login after 30mins

Note: If you are having this issue in Production and is not resolved after the steps provided, I recommend raising a Production Down [RED FLAG].

Conclusion:

This issue has probably effected multiple Customers. I had few customers unable to login into Business Central, and with almost all of them the issue was resolved with above steps.
Let me know if you have any other resolution if you have found so we can share it together.

Hope this helps!!

Feel free to either drop comments or email me on olisterr@outlook.com for any suggestions.



Comments

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: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant 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 resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe