AnsweredAssumed Answered

Getting a NWException: Error getting context data for 'WorkflowOwner' while trying to delegate a task

Question asked by akrasheninnikov Expert on Apr 1, 2015
Latest reply on Apr 2, 2015 by akrasheninnikov

Hi everyone,

 

One of our NW 2013 Request approval workflows wouldn't complete and the user asked me why. After a close look I told the guy that one more approver was expected to have their say.

 

The user then deleted the task that was unnecessary, but that didn't result in a successfully completed approval.

 

Then someone restored the task from the recycle bin and tried to delegate it and, BOOM, the workflow errored, all approvals must be requested once again?

 

04-01-2015 12:17:38.67
w3wp.exe (0x1AF0)        0x869C  Nintex
Workflow 2013 
General              
00000  
Unexpected              
(https://intranet.contoso.com/_layouts/15/NintexWorkflow/DelegateTask.aspx?List=529e8456-3c0d-41fa-8834-50b47570a1d3&ID=25&Source=https://intranet.contoso.com/sites/team/WorkflowTasks/AllItems.aspx&ContentTypeId=0x0108010079DBDE612F7B46928C6A2516BA2CAE37007353FF47553A4049AE1BE94EC7A515CA):
Nintex.Workflow.NWException: Error
getting context data for 'WorkflowOwner'
. --->
System.NullReferenceException: Object reference not set to an instance of an
object.     at Microsoft.SharePoint.Workflow.SPWorkflow.get_OwnerUser()   
at Nintex.Workflow.CommonDataItems.GetWorkflowOwner(ContextDataOptions
options)     at
Nintex.Workflow.NWWorkflowContext.VRw=(ContextDataOptions Vhw=, Boolean
Vxw=)     --- End of inner exception stack trace --- (Build:3110)    
2167f89c-ff13-006c-f5f4-c58248a3e0ca

 

I'm sure this is a valid support case, but maybe someone has already seen something like this and knows how to fix or prevent such issues going forward. At least you'll know that we have faced it already

Outcomes