I was on a project which was manually applying the October 2020 Wave 2 update and after saying this never go wrong, what happens, yep, it goes wrong.
The question is what do you when this happens. In reality you can only raise a Microsoft support ticket.
I raise a P1 with premier support and Microsoft do not reply for 2 and half hours, clearly their idea of a P1 is different to mine.
So I was poking round the system, which is not straight forward because with PowerApps portal there are at least 3 ways to do everything.
So I got to Environments →Dynamics 365 apps
I can see I have two apps with an update available. Of course pressing this button looks like it kicks of an install but nothing seemed to happen.
So I look at solution history record in advanced find to see if any solution imports fail. and I find that one of the solution patches from Microsoft has been failing since 15/08/2020. Doesn’t Microsoft check?
The error is
Mobile Offline Profiles import: FAILURE: Mobile Offline Profiles import: FAILURE
I found the same error somewhere else
The mobile offline profile is if you have a canvas app and you enable it to go offline, which means it can work without internet by downloading data onto the device, e.g.a salesman using a tablet and having the app work offline.
In this case weren’t using offline functionality and the only canvas with offline enabled and the profile was Microsoft’s Field Service app.
I have had problems with the mobile offline profile before
Dynamics 365 — mobile offline profile error
It would surprise me if this is the problem but I didn’t really have any method to investigate.The way the patches are applied I can’t see the import logs to identify where the errors are.
What’s surprising is Microsoft best practices is not to use patches and yet they use them. They are pushing regular update of patches and some of them aren’t working and no one is informed or does anything about it!
I will wait to see what the resolution is to the problem but it was frustrating because I couldn’t do much to investigate or fix it. The problem is with Microsoft updates and they will have to investigate.