SharePoint Designer Workflow UnauthorizedAccessException

I’ve run into issues with a SharePoint Designer workflow recently, not starting for some users. Well, it actually DID start, but then got canceled after a few seconds. No log history to be found and the following error message:

RequestorId: 44c5e543-de6a-c614-1959-863a8d5d4219. 
Details: System.ApplicationException: HTTP 401 
{
 "error": {
 "code": "-2147024891, System.UnauthorizedAccessException",
 "message": {
 "lang": "nl-NL",
 "value": "Toegang geweigerd. U bent niet gemachtigd om deze bewerking uit te voeren of deze bron te openen."
 }
 }
}{
 "Transfer-Encoding": ["chunked"],
 "X-SharePointHealthScore": ["0"],
 "SPRequestGuid": ["683d2096-377b-407f-b7ad-5a39abf17548"],
 "request-id": ["683d2096-377b-407f-b7ad-5a39abf17548"],
 "X-FRAME-OPTIONS": ["SAMEORIGIN"],
 "MicrosoftSharePointTeamServices": ["15.0.0.4841"],
 "X-Content-Type-Options": ["nosniff"],
 "X-MS-InvokeApp": ["1; RequireReadOnly"],
 "Cache-Control": ["max-age=0, private"],
 "Date": ["Mon, 21 Aug 2017 09:55:43 GMT"],
 "Server": ["Microsoft-IIS\/8.5"],
 "WWW-Authenticate": ["NTLM"],
 "X-AspNet-Version": ["4.0.30319"],
 "X-Powered-By": ["ASP.NET"]
}
at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) 
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) 
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation

The Dutch error

Toegang geweigerd. U bent niet gemachtigd om deze bewerking uit te voeren of deze bron te openen.

translates to:

Access denied. You do not have permission to perform this action or access this
resource.

I’ve tried many things to debug the workflow (Windows Workflow Foundation – SharePoint Designer 2013 workflows) but to no avail.

Then I found the following post: SharePoint 2013 Workflow Permissions. As not all users have this issue, I thought I’d go ahead and give the users that have the issue explicit permissions instead of using an AD group.

And what do you know, the bug that was around in 2013 is still around.

In the long run, this is of course not a good solution as adding users explicitly everywhere isn’t manageable at all…

Seems like another reason to go to Nintex workflow after all 🙂

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s