Hi All,

when we create default sharepoint 2013 workflow on a list, it is getting cancelled automatically with the error.

RequestorId: 2f5df02f-a0bb-f5a0-5664-0a261d1d990c. Details: System.ApplicationException: HTTP 401 {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this resource."}}} {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["8665c583-bf54-4c5f-b350-3e8de7c09726"],"request-id":["8665c583-bf54-4c5f-b350-3e8de7c09726"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"Cache-Control":["max-age=0, private"],"Server":["Microsoft-IIS\/7.5"],"WWW-Authenticate":["Negotiate","NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"],"MicrosoftSharePointTeamServices":["15.0.0.4569"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"Date":["Wed, 05 Nov 2014 06:37:01 GMT"]} 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 user profile service is working and synchronization is done.

also checked for feature"workflows can use app permissions" but did not help.

did anyone have similar issue?

 Assign permission policy to Web Application level in Central Admin site

1. Central Administration >Application management> Manage Web application

2. Go to permission policy, then create a new permission level. This permission level contains all edit item" permission.

3. Select user policy, then I assign it directly to the Users creating workflow

Now Assign the edit item permission at Site Collection level

1. Site Settings >Site permission

2. Assign "Edit" permission to user creating workflow.

In my case the user starting the 2013 workflow is the SystemAccount. Shouldn't that account be able to do whatever it needs?

Is this the same thing that plagued 2007 on declarative workflows?

Do you know where it crashed? If not, add "Write to Worfklow History" at different stages to get a general idea where it stopped.
View the workflow history as the workflow is running. During each step, press the blue "i" button at each step. Often, before becoming suspended and giving you the generic error, it will give you a more descriptive one, telling you that for example it stopped on the SendMail activity. It will also give you a correlation ID that you can check in ULS. That should give you a better idea of where to continue