Problem
Your users report that, when they launch a 2013 workflow, nothing happens for a minute or two, and then they are presented with the Sorry, something went wrong, page (below). Workflow foundation is installed to a SharePoint application server. Your farm is patched through June 2015.
Troubleshooting
Solution
Your users report that, when they launch a 2013 workflow, nothing happens for a minute or two, and then they are presented with the Sorry, something went wrong, page (below). Workflow foundation is installed to a SharePoint application server. Your farm is patched through June 2015.
Troubleshooting
- Tested all 2013 workflows available from the web application and found that all 2013 workflows failed.
- Testing 2010 workflows and found that they continued to function as expected.
- Checked that the following services were started on the server hosting Workflow Foundation:
- Service Bus Gateway
- Service Bus Message Broker
- Windows Fabric Host Service
- Workflow Manager Backend
- Checked the Unified Logging System (ULS) logs and found a block of messages associated with the correlation ID. Some examples:
andA runtime exception was detected. Details follow. Message: Thread was being aborted. Technical Details: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result) at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content) at Microsoft.Workflow.Client.HttpWorkflowNotificationPublisher.OnPublishNotification(String address, WorkflowNotification notification, ICredentials credentials, String userCulture, Guid traceActivityId, TimeSpan requestTimeout) at Microsoft.Workflow.Client.WorkflowNotificationPublisher.PublishNotification(String address, WorkflowNotification notification, ICredentials credentials, String userCulture, Guid traceActivityId, TimeSpan requestTimeout) at Microsoft.Workflow.Client.WorkflowManagementClient.PublishNotification(WorkflowNotification notification, IDictionary`2 activationMetadata, Int64 expectedScopeRevision) at Microsoft.SharePoint.WorkflowServices.WorkflowProxy.PublishEvent(String eventSource, String eventType, IDictionary`2 payload, SPUserToken userToken)
and others This block of messages recurred whenever a 2013 workflow was initiated.Leaving Monitored Scope (Event Receiver (Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, Microsoft.SharePoint.WorkflowServices.ContentSubscriptionEventReceiver)). Execution Time=118831.7039 - Launched elevated SharePoint Management Shell, and then executed the following to check on Workflow and Service Bus configuration status:
Get-WFFarm Get-WFFarmStatus Get-SBFarm Get-SBFarmStatus
- Opened a browser, and then connected to:
where FQDN is the fully qualified domain name of the server hosting the farm's workflow foundation.https://[FQDN]:12290 or http://[FQDN]:12291 - Check installed versions
- Workflow Manager 1.0: 2.0.20922.0
- Workflow Manager client 1.0: 2.0.40131.0
- Service Bus 1.0: 2.0.20922.0
- Windows Fabric: 1.0.960.0
Solution
- Perform upgrade using: Psconfig.exe -cmd upgrade -inplace b2b -wait -force.
References
- SharePoint logging and troubleshooting using ULSViewer
- Troubleshooting Workflow Manager 1.0 Management and Execution
- Workflow Manager
- Getting started with SharePoint Server 2013 workflow
- SharePoint 2013 workflow fundamentals
- Debugging SharePoint Server 2013 workflows
- Psconfig command-line reference (SharePoint Server 2010)
- SharePoint PSConfig
Notes
- I discovered this solution accidentally: after installing the July 2015 patches, which requires you to execute psconfig in order to do the upgrade, and then doing the usual regression testing, I found that, as a bonus, the workflow problem was resolved. Later, I was informed by Microsoft Support that psconfig was one of the options they were considering to resolve our workflow problem (I had previously opened a support ticket with them).
No comments:
Post a Comment