SharePoint 2013 Workflow Suspends
-
Hi All, I am facing an issue with SP2013 Custom Workflow developed using Visual Studio 2012. Objective of the Custom workflow: User fills the form and submit, list get updated and workflow will initiate and go for the process. Issue: After the deployment of WF, for first time when user is filling the form and submit, list is getting updated. But the Workflow Goes to "Suspend" mode. (This Custom Workflow has a configuration file where we are providing other details including ID of Impersonator (farm is running under Claim Based Authentication). Work flow works fine once when the Impersonator initiate the workflow (Fill the form and submit for approval) and everything works fine after that. Following steps are already performed 1.Make sure User profile synchronization is started. 2.Make sure the user is not the SharePoint system user. 3.Make sure the user by whom you are logged is available in User Profile list. 4.Step full synchronization of User Profile Application. From the ULS logs it seems the user's security token from the STS service and User profile service is not being issued. Appreciate any thoughts or solution. Following are the log files. <-------------------------------Information taken from "http://YYYY.XXXXX.com/sites/xxxx/\_layouts/15/wrkstat.aspx" where it is showing workflow status as "Suspend"-------> http://yyyy.XXXX.com/sites/xxxx/\_vti\_bin/client.svc/sp.utilities.utility.ResolvePrincipalInCurrentcontext(input=@ParamUser,scopes='15',sources='15',inputIsEmailOnly='false',addToUserInfoList='False')?%40ParamUser='i%3A0%23.w|XXXXX\sps\_biscomdev' Correlation Id: f5bd8793-a53c-2127-bfb1-70bc172425e8 Instance Id: 14a985a0-60c8-42db-a42c-c752190b8106 RequestorId: f5bd8793-a53c-2127-0000-000000000000. Details: RequestorId: f5bd8793-a53c-2127-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception 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 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\""],"SP
-
Hi All, I am facing an issue with SP2013 Custom Workflow developed using Visual Studio 2012. Objective of the Custom workflow: User fills the form and submit, list get updated and workflow will initiate and go for the process. Issue: After the deployment of WF, for first time when user is filling the form and submit, list is getting updated. But the Workflow Goes to "Suspend" mode. (This Custom Workflow has a configuration file where we are providing other details including ID of Impersonator (farm is running under Claim Based Authentication). Work flow works fine once when the Impersonator initiate the workflow (Fill the form and submit for approval) and everything works fine after that. Following steps are already performed 1.Make sure User profile synchronization is started. 2.Make sure the user is not the SharePoint system user. 3.Make sure the user by whom you are logged is available in User Profile list. 4.Step full synchronization of User Profile Application. From the ULS logs it seems the user's security token from the STS service and User profile service is not being issued. Appreciate any thoughts or solution. Following are the log files. <-------------------------------Information taken from "http://YYYY.XXXXX.com/sites/xxxx/\_layouts/15/wrkstat.aspx" where it is showing workflow status as "Suspend"-------> http://yyyy.XXXX.com/sites/xxxx/\_vti\_bin/client.svc/sp.utilities.utility.ResolvePrincipalInCurrentcontext(input=@ParamUser,scopes='15',sources='15',inputIsEmailOnly='false',addToUserInfoList='False')?%40ParamUser='i%3A0%23.w|XXXXX\sps\_biscomdev' Correlation Id: f5bd8793-a53c-2127-bfb1-70bc172425e8 Instance Id: 14a985a0-60c8-42db-a42c-c752190b8106 RequestorId: f5bd8793-a53c-2127-0000-000000000000. Details: RequestorId: f5bd8793-a53c-2127-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception 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 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\""],"SP
Please do not crosspost. SharePoint 2013 Workflow suspends[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson