Wednesday 25 February 2015

SharePoint 2013: Workflow

Workflow Manager 1.0 for Sharepoint 2013 - forbidden error (error 403)

This Workflow forbidden error (error 403) came up from no where. I had this SharePoint farm configured with the workflow farm which was running fine for about 2 months, but from no where the error popped up.

This may occur when you try to activate the workflow feature which you deployed through Visual Studio 2012 or when you try to start a designer WF you may get "Something went wrong". You check the log then it says "Workflow Manager forbidden error :403"

Below are the few steps you can follow to solve this error

1) Go to central Admin click on "Workflow Service Application" and check in properties you find on ribbon if you have assigned the Administrator .If not provide the service account as Administrator

2)It is always good to have the Administrator  assigned to "User Profile Service Application "
in the same way

3)Try opening the url in IE http://localhost:12291 for http based web service where the Workflow Manager is installed
               It might give you the forbidden error again
4)Open the IE as Admin and try opening the same url http://localhost:12291 if u dont get the XML schema then there is problem with the credentials the services are running
      You don't get the run as Admin option for IE if your server OS is windows server 2012
to open IE with run as Admin privileges you need to navigate to folder where the IE is installed
C:\Program Files\Internet Explorer then open iexplorer.exe  as Admin

5)Go to the data base and check for service bus databases , if the service account with which the services are running has the required privileges
6) Open event viewer and check for the error and I found that the service bus message broker service was not in running state from this.

7)Last but not least this the reason where you may get forbidden error for workflow service most of the time

  • Go to services and check if the below service are running

  1. Service Bus Gateway
  2. Service Bus Message broker service
  3. Windows Fabric host service

I had this situation of  Service Bus Message broker service in  Starting state

you can stop the Windows Fabric host service and restart again. This should trigger the service bus services to start again. If not check the service account and password with which the services are running.

Open the Workflow Management Shell  and Get-SbFarm , Get-SbFarmStatus you should be able to see all the services are running in it ..If not it is a problem.


In my case the above happened and all I wanted is to start these service !! so I performed below items


  • I planned to re configure the Service Bus farm unlike SharePoint you don't have the option to run the config wizard again
  • So I opened Service Bus Configuration wizard  and chose the option to Leave Farm
  • Went to services and saw neither service bus gateway nor Service Bus Message broker service was present
  • Next step was to open the Service Bus Configuration wizard  again and instead of creating new farm I chose  "Join the old Farm " option and gave the server and db name as old config since I had this SbManagementDB and SBMessageContainerDB were already present with data


This created Service bus gateway and Service Bus Message broker newly and in running state !!


Sharepoint 2013 workflow + The server was unable to process the request due to an internal error


RequestorId: 321d7a5c-ca52-907e-0000-000000000000. Details: RequestorId: 321d7a5c-ca52-907e-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 <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":["321d7a5c-ca52-907e-aab4-69867fb6c2f8"],"request-id":["321d7a5c-ca52-907e-aab4-69867fb6c2f8"],"X-FRAME-
":["SAMEORIGIN"],"SPRequestDuration":["64"],"SPIisLatency":["3"],"Cache-Control":["private"],"WWW-Authenticate":["Bearer realm=\"3eafb22a-93a3-48a8-9c32-16829fce2722\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000-000000000000@*,00000003-0000-0ff1-ce00-000000000000@3eafb22a-93a3-48a8-9c32-16829fce2722\"","NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"MicrosoftSharePointTeamServices":["15.0.0.4481"],"Date":["Mon, 28 Oct 2013 10:49:09 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
System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)


I found this error when I attached a designer List workflow and tried to start the workflow

Solution: Your User Profile Sync Service Should be running .If not add the user to the "Manage User " of User Profile server ,this is the user who triggers the workflow


Basic principle behind this is every user triggering the WF should have a profile of him in User Profile Application Service.

SharePoint 2013 Workflow

The concept of Workflow in SharePoint 2013 is changed a whole lot.

The three thing which you need to take care while configuring the workflow to run on SharePoint 2013 is that

  1. Workflow Manager 1.0
  2. Workflow client 1.0
  3. Workflow Manager Tool for Visual 2012
  4. Developer Tools for Visual studio.

As the Workflow does not run inside the share point  you can install Workflow Manager 1.0  on different server or on same server where share point is hosted ..You can follow the MSDN link below to install and configure the Workflow Manager 1.0.

http://technet.microsoft.com/en-us/library/jj658588.aspx

Workflow client 1.0 - This has to be installed on all the sharepoint server (Web fornt end,App).This has API which communicates with the Workflow Manager.

Workflow Manager Tool for Visual 2012 - This has to be installed on the server where you create Visual studio 2013 SharePoint Workflow.Assuming that VS2012 is already installed .
2013 Sharepoint WF template is named as "Workflow"  in VS the "sequential and state machine" template is legacy now and it is not used in SharePoint 2013.

Developer Tools for Visual studio- Is to be installed on server where the Visual studio 2012 is installed.This provide new activities in Tool Box of VS12.


Along with this when you try to install the WorkflowManager through webPlatform installer .
Service Bus and cummunlative updates will be installed automatically.If you are installing it manually you need to install all the updates and Service bus.


Even after having all this there will be few problem with sending mails from VS12 WF.To overcome the issue You need to Install the MARCH-PU sharepoint 2013 updated and configure the same.


Plese follow the below link to install and configure it

http://www.deliveron.com/blog/post/Installing-March-2013-Public-Update-on-SharePoint-Server-2013.aspx


After all these are done you also need
  • App Management Service to be running
  • User Profile Service to be running
  • User Profile Sync Service to be running
Only then your WF runs without any problem :)
 
Ref:http://sharepointerthilosh.blogspot.in/search/label/workflow
 
Posted by at

1 comment:

  1. Unknown26 March 2016 at 04:52

    An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 403 {"error":{"code":"1030, Microsoft.ProjectServer.PJClientCallableException","message":{"lang":"en-US","value":"PJClientCallableException: ProjectHasWriteLock\u000d\u000aProjectHasWriteLock"}}} {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["205"],"SPRequestGuid":["213bc435- 



    Can u help Plz workflow gets suspended at last stage

    ReplyDelete

Subscribe to: Post Comments (Atom)