Pages

Friday, December 22, 2017

SharePoint 2013 workflow got cancelled with HTTP 401

SharePoint 2013 workflow got cancelled and found the below error

RequestorId: 2835896c-3aff-232c-10b0-da0b18ec10de. Details: System.ApplicationException: HTTP 401 {"error_description":"The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs."} {"x-ms-diagnostics":["3001000;reason=\"There has been an error authenticating the request.\";category=\"invalid_client\""],"SPRequestGuid":["2835896c-3aff-232c-10b0-da0b18ec10de"],"request-id":["2835896c-3aff-232c-10b0-da0b18ec10de"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["32"],"SPIisLatency":["5"],"Cache-Control":["private"],"WWW-Authenticate":["Bearer realm=\"9a5e4a6b-4ab4-4cd5-a2c2-b1b60f387c21\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000-000000000000@*,11111111-1111-


      Resolution:     

  •      Don’t use system account for workflow creation and publishing.
  •      Ensure User profile synchronization service is started (also ensure both FIM Services are started).
  •      Ensure user profile service application has been associated to the web application

If the above solution are not working then follow the below links which may resolve the issue.




For my case the user profile service application not associated to the web application.