Skip to main content

Assign a task action in SharePoint 2013 Workflow generates a KeyNotFoundException

Problem
You have added an "assigned a task" action to your SharePoint 2013 Workflow. The associated workflow task list has broken inheritance with custom permissions. When you start your workflow and the task is assigned and you get a KeyNotFoundException.

Fix the problem
Don't break the inherit of permission on the associated workflow task list.

Comments

Popular posts from this blog

The form cannot be submitted because of an error

Problem I created a reusable approval workflow in SharePoint Designer 2010. I initiated the workflow. Then when I filled in the Assigned To field I got an error pop up saying: "The form cannot be submitted because of an error". Solution Uninstall the KB2553322 for SharePoint Designer. I didn't uninstall KB2553322 for Microsoft Office. Restart SharePoint Designer. Recreate the workflow.

Can't read from source file or disk

When you are using Windows Explorer View in SharePoint you can't MOVE a file from one site to another if it's not directly below the root site, but you can copy the file. See the different scenarios below. Working Scenario Moving files between libraries within the same site. For example: "http://sharepointsite/sites/site1/site2/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination) Moving files between libraries across different sites as long as they are directly below the root site. For example: "http://sharepointsite/site1/library1 (source) "http://sharepointsite/site2/library2 (destination) Non-working Scenario Moving files between libraries in sub-sites that are more than 1 level below the root site. For example: "http://sharepointsite/sites/site1/site1/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination)

Application Server Administration job failed

Problem CPU 99%. User Profile Synchronization is stuck on Running. SharePoint Timer Service is eating up the whole CPU and the event viewer says: Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by xxxxxxxx, in the OWSTIMER process, on machine xxxxxxx.  View the tracing log for more information about the conflict. Technical Support Details: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by xxxxxxxx, in the OWSTIMER process, on machine xxxxxxx. View the tracing log for more information about the conflict.    at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()    at Micro...