I have been getting repeated messages that a scheduled upgrade has failed and when I go to the details, it is as shown above. This has happened on both sandbox and production environments. I have googled the error and see a number of references to others having the issue but no solutions to be found.
Does anyone know what this error is about, and can I do anything or do I need to wait for Microsoft to do something on their end? (Cloud version Business Central).
Thanks.
I’m in same boat, not sure whether we’re just waiting or we need to reach out to partner to get it resolved.
This post on the D365 Community forums details the current state of this as a known issue alot of us are experiencing.
Looks like all we can do at the moment is keep watching Microsoft support for updates & a resolution.
We have the same issue and a support case open with Microsoft. It’s been going on since end of April with no success. They tell us it will be fixed by the next automated update…and we’ve had 3 so far and still have the problem.
Sorry I don’t have a resolution for you, but you’re not alone!
Gina
Thanks for the replies. At least we have company. I guess nothing to do but wait until Msoft gets their stuff together.
We were experiencing the same error and had to get our partner involved to fix the issue.
I would definitely suggest reaching out to your partner. They may have some insights into why your environment is failing, or would be able to assist you with escalating a ticket with Microsoft.
We have been able to get past this error for several customers, it just requires some time and careful attention.
Thank you for the suggestion Tonya.
However, one thing I try to avoid at all costs is opening a ticket that involves the partner and Microsoft trying to sort things out between them. It is like throwing money down a bottomless pit. I think I’ll just wait it out.
Jeff - Does the error look like this:
If yes, this scenario happened to my customer and Microsoft did help. Below was the result that Microsoft cleaned up the table for them.
"Customer has over 100m records in change log entry and this is causing the issue even with the upgraded db.
{COMPANY NAME}$Change Log Entry$437d[TENANT]
{COMPANYNAME}GL4262021$Change Log Entry$437[TENANT]
My recommendation is that I truncate the change log table, it means all records in the Change Log Entry table will be deleted.
We’re having issues with change log entry table growing tremendously and retention policy is unable to clean it or as in this case, customers running into upgrade issues.
Do you want to clean this up yourself or do I have the approval to ask Microsoft to truncate and update? You can config package export the table but it will take time. Doing it in small ranges will work faster, but still will take time. Please advise how to proceed.
I would have your Partner enter a support ticket for you to resolve.
Thanks,
Steve
1 Like
We have seen this error related to a specific ISV, and some records being in a table that is changing to temporary.
I would hope that your partner would have a few ideas for your specific tenant, and why you might be getting the error.
I would hope you could reach out, and just ask if they have any insights for you. Your partner should be your trusted advisor and here to help you!
Tonya
1 Like
