You’re offline. This is a read only version of the page.
288
We are seeing the import of our latest solution fail in some environments and work fine in others.
Typically, the message fails on importing a flow but the flow in question varies - see below for failure message re the flow.
We also get the below message re 'solution must both be managed' - which of course they are.
We have a case open but I am wondering if anyone else has experienced the same issue?
Note - we tried a classic upgrade in one env and that failed, but a classic update succeeded. We don't want to recommend the latter until we have some clarity on root cause.
| Error while importing workflow {697a6d80-f1a1-eb11-b1ac-000d3a32c5f1} type ModernFlow name Get list of Microsoft Teams: Flow server error returned with status code "InternalServerError" and details "{"error":{"code":"InternalServerError","message":"Http request failed with unhandled exception of type 'Exception' and message: 'Type: System.Threading.Tasks.TaskCanceledException\nMessage: A task was canceled.\nStackTrace: at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.WindowsAzure.ResourceStack.Common.EventSources.IHttpEventSourceExtensions.<TraceHttpOutgoingRequest>d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()\r\n at Microsoft.Azure.ProcessSimple.Data.DataProviders.XrmDataProvider.<>c__DisplayClass134_0`1.<<CallXrmApiHelper>b__0>d.MoveNext() in C:\\__w\\1\\s\\src\\processsimple\\Roles\\ProcessSimple.Data\\DataProviders\\Services\\XrmDataProvider.cs:line 3027\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()\r\n at Microsoft.Azure.ProcessSimple.Data.DataProviders.XrmDataProvider.<CallXrmApiHelper>d__134`1.MoveNext() in C:\\__w\\1\\s\\src\\processsimple\\Roles\\ProcessSimple.Data\\DataProviders\\Services\\XrmDataProvider.cs:line 2970\nInternalException: '."}}". |
There are about a million ways that solution import validation can throw errors like this, so it is very hard to give you a clear answer, but I can tell you one mistake I've made before that resulted in a similar error:
When you get a "both must be managed" error, this is not necessarily referring to the solutions, but may be referring to individual solution components and the solutions they came from in their source environment. Yeah, I know that's a bit weird, but stick with me and I'll explain... So let's say that your problem solution here has component X (let's call it a Table) as Managed with no managed source solution dependency because you built table X in the unmanaged layer in the Source environment, but your Destination env might have Table X already from a different managed solution (i.e. you already imported a different managed solution that also includes Table X).
I agree the wording of the error message is very confusing, but what it's trying to tell you is that in the Target env Table X was originally imported in a Managed Solution (and carries that dependency), whereas in your Source env, that Table was built in an Unmanaged layer, then packaged in this different Managed Solution. Dataverse is trying to stop you from doing something silly and importing a solution that could cause unexpected complications in a managed solution already in place.
Unfortunately, this can sometimes happen for totally benign reasons like, "this is just a different Managed Sol from the same Source" and that can cause a lot of headaches.
Luckily, this issue has an easy fix (sometimes). If you are certain that importing this other copy is safe, you can just manually edit the solution.xml in the zip file to either remove the dependency reference or insert a matching managed solution id to trick your Target env into thinking that they match. Dataverse only does this validation during initial import and not during the actual installation of components, so by tricking the solution.xml reference, you can bypass the check... But don't do this if you aren't TOTALLY sure the two solutions will play nicely together.
#1
WarrenBelz
87
Most Valuable Professional
#2
mmbr1606
71
Super User 2025 Season 1
#3
Michael E. Gernaey
65
Super User 2025 Season 1
Share
Report
All responses (
Answers (
