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.

Enable PowerShell commandlets for SharePoint 2013 in PowerShell ISE

Open the PowerShell ISE and create a profile by running the following code: if (!(test-path $profile.AllUsersAllHosts)) { new-item -type file -path $profile.AllUsersAllHosts-force } Open the newly created profile with the following command: psEdit $profile.AllUsersAllHosts The profile will be open in the PowerShell ISE. Add the following code to the profile: (If the profile for some reason doesn't open then you can get it here: C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1) if ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null ) { Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell } Save the profile. Next time you open the PowerShell ISE you will have all the Microsoft.SharePoint.PowerShell commandlets.

Problem installing service pack 1 for SharePoint Foundation 2010

I have a SharePoint farm with one application server, two WFE servers and one db server. When I ran the configuration wizard after I installed service pack 1 on the application server and the WFE servers I got an error that said that the service pack was missing on the WFE servers. Solution: Open your powershell editor and execute the following command on the WFE servers. Get-SPProduct –local Then run the configuration wizard again.