SP2013 Designer Workflow Error : There was no endpoint listening at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message

Hello Guys,

Recently I got a requirement to work on SharePoint 2013 Designer Workflow. In my server all the required configurations like WF Manager, Service Registration etc  is already setup in the server, But when i started publishing the workflow i have got this below error message

"Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : ba605d9d-e11c-606d-5c6c-4dac94c6c3a1. ---> System.Net.WebException: The request was aborted: The request was canceled. ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc that could accept the message. This is often caused by an incorrect address or SOAP action."

I googled it for some time and checked the service application status, logs, "Refresh Trusted Security Token Services Metadata feed timer job" etc etc. But no luck. After spending some (of course hours :) ) i came to know that the below windows service should be running to publish the workflow (some how this is stopped in my machine)

Once start the service, i could successfully publish the designer workflow.

Thanks
Purna

AppManagement Shared Service Proxy is not installed : Error in SharePoint 2013 designer workflow when publishing

Hello,

I configured the workflow manager and created a SharePoint designer workflow and tried to publish the workflow and got the following error.

“Errors were found when compiling the workflow. The workflow files were saved but cannot be run. Microsoft.SharePoint.SPException: App Management Shared Service Proxy is not installed”

Causes for this : 

• App Management service is stopped (or)
• No App Management service application is exist (or)
• The App Management service appn is not associated with the default proxy group

Resolution :

AppManagement service is stopped :

Go to Central Administration àManage services on server under system settings section à Start the AppManagement Service if it is in stop mode

No App Management service application is exist (or not created yet) :

Go to Central Administration àManage service applicationsà Create AppManagement Service if already not exist

The App Management service appn is not associated with the default proxy group

Go to Central Administration àApplication Management Tabà  Configure Service Application associations under Service Applications section à Add App management service app proxy to default group if not already added.

Thanks

The Option for the SharePoint 2013 workflow platform is not available because the workflow service not configured on the server with new sitecollection

Hi,

This error you get generally if you are not configured the WorkFlow Manager.But here i am giving solution for the unavailability of the sp2013 workflow option with the new sitecollection 

Here i configured the Workflow manager and I registered the workflow service too. But still I am not seeing the option of SharePoint 2013 workflow in the designer with the new site collection i created.

The reason for this is , the template which we choose while creating the sitecollection(in my case blank template) might not have all the dependency features to create the SP2013  workflow.

To resolve this issue activate the " Workflow Service Store" Feature.This is hidden by default.

Below is the powershell command to activate it.

Enable-SPFeature -Identity WorkflowServiceStore –Url http://spserver:8899/sites/pcm

Close and reopen the designer, you will be finding the option like this.

Hope helps some one.

Thanks,

SharePoint Designer 2013 Workflow error :Microsoft.Workflow.Client.ActivityValidationException: Workflow XAML failed validation due to the following errors: Activity 'someXActivity' has 58 arguments, which exceeds the maximum number of arguments per activity (50).

Hi Guys,

[Update: You can achieve this solution using powershell as well, please refer the link provided at bottom of this post]

Recently I got this workflow error while working with the SharePoint designer workflows in 2013. The error is about the creation of workflow variables/arguments more than 50 in number. By default max variables/arguments allowed in workflow is 50. If we create more than this, we encounter with the following error while publishing the workflow.

“Microsoft.Workflow.Client.ActivityValidationException: Workflow XAML failed validation due to the following errors: Activity “SomeXActivity” has 58 arguments, which exceeds the maximum number of arguments per activity (50).”

The resolution is like this:

Change the default settings of the workflow variable limit in the Workflow Manager table as follows.

Go to SQL where your Workflow Manager Db is stored and set these.

DataBase : WFResourceManagementDB

Table : WorkflowServiceConfig

Rows :  

WorkflowServiceMaxVariablesPerActivity  :   set it to required value and  WorkflowServiceMaxArgumentsPerActivity  : set it to required value.

like this

UPDATE :

You can also set these configurations using power shell Set-WFServiceConfiguration command, please refer below msdn link for more details :

https://blogs.msdn.microsoft.com/feseca/2015/02/27/error-publishing-a-sharepoint-workflow-into-workflow-manager-exceeds-the-maximum-number-of-arguments/

Thanks

SharePoint 2013 Work Flow cancelled automatically due to error :HTTP 401 {"error_description":"The server was unable to process the request due to an internal error...}

Hi Guys

Recently I have installed and configured the WorkFlow Manager for my project and i got succeded in doing that. And then I have created a spd workflow and published it, but when I see the history it is saying the workflow is  started but after that it got cancelled automatically by saying this below error

RequestorId: 26f1da47-f3e6-0816-0966-df958cd57c7d. 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":["26f1da47-f3e6-0816-0966-df958cd57c7d"],"request-id":["26f1da47-f3e6-0816-0966-df958cd57c7d"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["252"],"SPIisLatency":["1"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["Bearer realm=\"73b2c214-338d-4c93-937f-5852744a020d\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000- ---

This issue comes because, the Workflow Manager tries to authenticate SharePoint with the OAuth. Here only the Identity information is passed through the OAuth token. The rest of the information about the user is picked from the User Profile Service Application by the SharePoint.  So the UPS service application should be up and synchronized. 

Follow/Check  these below steps to resolve the issue :

• First Check the user(  with whom you are publishing the workflow  )should not be a system account
• Check that the User Profile Synchronization service is running and Full Synchronization is done
• Make sure that the user with whom you are publishing the workflow should be available in User Profile List. If not add the user by going  this below path  Central Administration--> Manage Service Applications --> Select User Profile Service --> Manage --> Manage User Profiles --> New Profile and then fill the details.

This will resolve your issue..

-Thanks