Unanswered

Error when importing solution: Microsoft.Mashup.Web.Dataflow.CrmPlugin.Plugin: System.TimeoutException

(0) Share

Report

Posted on by davidyc

I have encountered the error in the subject (full text below) when importing a solution into a brand new environment. Very little information is given about the root cause of the error. A large xml log file is available after the error is shown, however it appears to contain every action performed as part of the import of the solution and it is unclear where to start in diagnosing the issue.

I wondering if anyone know at least what the error might relate to. Based on the name of the error, I have looked at any dataflows in the solution. I do not have any custom plugins in use.

Any help or ideas on how to diagnose this would be greatly appreciated!

p.s. Microsoft support spent over 2 months on this and weren't able to offer a solution.

Error Description: Solution "1_PM_MDA_COMP" failed to import: An unexpected error occurred from ISV code. (ErrorType = ClientError) Unexpected exception from plug-in (Execute): Microsoft.Mashup.Web.Dataflow.CrmPlugin.Plugin: System.TimeoutException: Couldn’t complete execution of the Microsoft.Mashup.Web.Dataflow.CrmPlugin.Plugin plug-in within the 2-minute limit.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (0)

Sort by

gcmfaizan 1,022 on at

Like (0)

Report
Copy link

Link copied!
Hi @davidyc ,

The error message you're encountering indicates that there was a timeout exception while trying to execute a plug-in related to dataflows during the import of the solution "1_PM_MDA_COMP". The timeout occurred because the execution of the plug-in exceeded the 2-minute limit.
Here are some steps you can take to diagnose and potentially resolve this issue:
Review XML Log File: Although the XML log file might contain a lot of information, it's still a valuable resource. Look for any errors, warnings, or exceptions that occurred during the import process. Focus on the sections related to the plug-in execution, especially any details about the specific plug-in being executed.
Performance Analysis: Dataflows can sometimes be resource-intensive. Check the complexity of the dataflows, the amount of data being processed, and any potential bottlenecks in your environment's resources. If the dataflows are particularly complex or deal with large amounts of data, consider optimizing them by using normalization techniques.
Plugin Dependencies: Even if you don't have custom plugins, there might be system or third-party plugins that are indirectly affecting the dataflow execution. Check if there are any dependencies or prerequisites for the dataflow plug-in that could be causing the timeout.
I hope going through these steps may help you.

If this is the answer for your question, please mark the post as Solved.
If this answer helps you in any way, please give it a like.

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report
Copy link

Link copied!

@davidyc A few questions that might help further troubleshoot:
1. What apps (either first or third party) are installed in the environment?
2. Have you tried turning on tracing in the environment and there reviewing plugin trace logs generated?
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/logging-tracing
3. Have you tried running the Plugin Registration tool to check if the plugin referenced in the error message actually exists in the environment. If it does, you can try to identify it in the default solution, and check it's solution layers which will tell you which solution (and hence publisher) it originates from

Was this reply helpful? Yes No