I saw this in another post from 2015 which ended as not to worry from the System. However, this is an annoying error message which comes back even after re-importing the customization. It doesn’t give one confidence that Epicor is running the complete customization or not.
Has anyone an idea of what causes this error to occur and how to resolve it?
I haven’t seen that one in many years. It’s usually something wrong with the customization XML itself. Felt those pains coming from 9.05 to 10 then 10.1 to 2. but not since then. What happens if you try to debug in Visual Studio?
Haven’t tried that. Luckily, we had exported the customizations out once completed to add them to AzureDevOps source control. Re-importing them corrected the issues.