Skip to main content

MSDYN365BC 2019 Wave 2 - Something Went Wrong During Personalization.

Hi Readers,

We recently did an upgrade from NAV 2009 to Business Central Wave 2 (#MSDyn365BC).

I was super excited during migration and it was interesting to do that migration to the future latest and greatest version of the product.

Everything went well during Upgrades.



I always believe that customers from any version of NAV/Business Central can be upgraded to Business Central with all their data and customs.

As a best practice, I always install all Microsoft Base Extensions which are part of DVD for the customer.

So What is the Issue?

When a user started Personalizing Pages in Business Central 2019 Wave 2, they ended with below error message.
"Sorry, something went wrong and personalization could not be started. Please try again later, or contact your system administrator." 
What I did?
  • Checked Legacy user personalization and deleted them.
    • We have seen those in past, Legacy user personalization will block you to personalize pages.
    • Legacy personalization - User Personalization that was done by users in Pre-BC Versions of Product.
    • What's New Personalization -  Personalization in the Business Central world is an extension and no metadata as in previous versions.
  • Checked Extensions which may cause an issue.
    • A published Extension can generate this error message.

What I Found?

I switched license from customer to Partner License and it started working.

That led me to?

Event Viewer, to check issues.

What I Found in the Event Log? 

It's a Permission issue. But that does not mean that customer license had Issue.
Here is the error message from Event Viewer.


What was the Issue?

The issue was due to Test Runner Extension which is a part of Application (Extension) in the Product DVD.

Test Runner Extension is an extension that has all Test Suites. As we all know that with customer license you cannot run Test cases.

How to Fix It?

Just uninstall the Extension (Test Runner) and you will be good to go.


Hope you find it useful.

Let me know your views as a comment on this article.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

  1. Dear Saurav,

    I would highly recommend not to install all extensions from DVD. Reasons why are:
    Some extensions may not be compatible with others
    They can affect the way the system is running
    We (Microsoft) ship system modules, test extensions (like test runner) and others that may not be compatible with every license

    Best regards,
    Nikola

    So before shipping, publish only extensions that you know you want to use

    ReplyDelete
  2. hot to get resolve this issue Sorry, the page could not be found.

    ReplyDelete
    Replies
    1. Check in event log for the actual error message.

      Delete

Post a Comment

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.