Workflow Error: Internal constraint exception while running constraint...

Question

User2011366442 posted

Hi everyone,

I have been developing a workflow which checks a service level of a company and depending on the outcome of which either sends in email or not - in simple terms. Before this point, I have had no problems running the workflow and I have made no changes. This error appears at every stage of the workflow and variable reference displays the same error which has completely dumbfounded me as to why it is happening.

Error: 
"Internal constraint exception while running constraint with name 'Constraint<Activity>' against activity of type Microsoft.CSharp.Activities.CSharipValue'1[[System.Boolan, mscorlib, Version=4.0.0.0, culture=neutral, PublicKeyToken=b77a5c561934e089]] with name 'CSharpValue<Boolean>'. Exception was: SystemInvalidOperationException: Values must be bound at System.Activities.WorkflowApplication.Invoke(Activity workflow, IDictionary'2 inputs, workflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowApplication.Invoke(Activity workflow, IDictionary'2 inputs, workflowInstanceExtensionManager extensions) 
at System.Activities.WorkflowApplication.Invoke(Activity workflow, IDictionary'2 inputs)
at System.Activities.Validation.ActivityValidationServices.RunConstraints(ChildActivity childActivity, AcivityCallStack parentChain, IList'1 constraints, ProcessActivityTreeOptions options, Boolean suppressGetChildrenViolations, IList'1& validationErrors)"

The error varies at the type - which I have made in bold - to the specific type that is being used (e.g. TimeSpan, Int32 etc.

Any help is much appreciated

- Dan

Answer 1

User2011366442 posted

On further investigation, another error, at root Sequence in the .xamlx, was stating that it could not "find" a couple temp files as they were already being used by another process (C:\Projects\...\...\ProjectName\obj\Debug). I had another solution open in a seperate instance of Visual Studio which referenced this WF Service project, in addtion, I had AppFabric in IIS set up using the same (development) location.

I would say that it is most likely the multiple solutions of VS I had open. The same location used in IIS and in VS was simply not good practice and a one for anyone else to bare in mind.

Answer 2

User-1436635217 posted

I had a smilar issue recently. I got the same "Internal constraint exception..." error and it turned out that there was a compilation error in an activity used inside my workflow. At first, I overlooked that compilation error because it showed up in the error list after the internal constraint exception.

As soon as the compilation error in the activity got fixed, the internal constraint exception went away.