The error message "Method not found: 'System.IServiceProvider Microsoft.Extensions.DependencyInjection.ServiceCollectionContainerBuilderExtensions.BuildServiceProvider(Microsoft.Extensions.DependencyInjection.IServiceCollection)'" when activating OOB workflows and BPFs strongly indicates the same underlying issue we discussed previously: an assembly version mismatch within your Dynamics 365 environment.
Specifically, the error points to a missing method within the Microsoft.Extensions.DependencyInjection library. This library is used by various components within Dynamics 365, including potentially the workflow and Business Process Flow engines, and also the Business Central Virtual Entity feature as seen in the error details of your previous plugin issue.
Here's why this error is occurring when activating OOB workflows and BPFs:
- Dependency on Shared Libraries: The workflow and BPF execution processes likely rely on shared libraries within the Dynamics 365 platform. If there's an inconsistency in the versions of these core libraries, particularly
Microsoft.Extensions.DependencyInjection, it can lead to these "Method not found" errors.
- Activation Process: The activation of workflows and BPFs might trigger processes that internally utilize the affected libraries.
Troubleshooting and Resolution Steps (Same as Before):
The resolution for this issue is the same as the one for the plugin deletion problem you encountered:
- Verify Environment Version: Check the exact cumulative update version of your problematic Dynamics 365 environment by going to Settings > About. Compare this version with a working Dynamics 365 environment (if you have one). They should ideally be the same.
- Ensure Consistent Cumulative Update: If the versions are different, the most likely solution is to bring the problematic environment to the same cumulative update level as a healthy environment. You will need to schedule an update through the Power Platform Admin Center.
- Investigate Business Central Integration (Again): Even if you are not actively using Business Central Virtual Entities, the underlying components might be installed and causing this dependency issue. Review any Business Central related configurations or connections in your environment.
- Contact Microsoft Support (Recommended): Given that this is a system-level assembly mismatch affecting core platform functionality, opening a support ticket with Microsoft is highly recommended. Provide them with the error details and the steps you've already tried. They have the necessary tools and insights to diagnose and resolve these types of environment-level inconsistencies.
Why This Wasn't Happening Before (Potentially):
- Timing of the Issue: The assembly mismatch might have been introduced by a recent background update or a failed deployment of another component.
- Specific Trigger Points: The activation of workflows and BPFs might trigger the use of the affected libraries in a way that other operations you were performing previously did not.
In summary, the "Method not found" error when activating OOB workflows and BPFs points to the same underlying assembly version conflict, likely related to Microsoft.Extensions.DependencyInjection and potentially influenced by the Business Central Virtual Entity components. Ensuring your environment is on the correct and consistent cumulative update is the most probable solution. If that doesn't work, reach out to Microsoft Support for further assistance.
Share
Report
2,051
All responses (
Answers (
