Answered by:
SharePoint Workflow 2013 doesn't run

Question
-
Good day!
I have SharePoint Farm 2016 installed on computer without Internet Connection.
For this computer I installed Workflow Manager 1.0 by this instruction
The step «Add host to Workflow Farm» failed, but previous steps were successful.
I added host to Workflow Manager Farm after ServiceBus-KB2799752-x64-EN installation.
Then I executed PowerShell commands:
Register-SPWorkflowService -SPSite "http://MySiteURL" -WorkflowHostUri ' https://MySiteURL:12290' -AllowOAuthHttp -Force
Register-SPWorkflowService -SPSite "http://MySiteURL" -WorkflowHostUri ' https://MySiteURL:12291' -AllowOAuthHttp –Force
In SharePoint Designer I can create and public SharePoint Workflow 2013. But when I try to run my workflow, I get this error:
«Something went wrong. To try again, reload the page and then start the workflow»
I executed WorkflowMgmtPool recycle and restarted the WorkflowServiceBackend Service likehere https://msdn.microsoft.com/en-us/library/jj193529(v=azure.10).aspx
No results.
I checked the status of all Workflow and Service Bus services. They all was running. I restarted them.
I installed WorkflowManager-KB3104066-x64-EN and restarted machine. No results.
I opened Central Administration site and checked the status of "Workflow Service Application Proxy". Workflow Service is connected.
But I can’t understand why I can’t run Workflow 2013.
I looked this
But it didn’t help. How to fix this problem?
I would be grateful for any help.
Friday, June 1, 2018 1:30 PM
Answers
-
Thanks for reply,
I enabled claim-based authentication for my site collection and workflow 2013 works. The topic about this https://social.technet.microsoft.com/Forums/lync/en-US/e504e159-2f79-4cc4-885a-d1e74250a09a/convertspwebapplication-new-parameter-from?forum=sharepointadmin
https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/convert-spwebapplication?view=sharepoint-ps
https://support.office.com/en-us/article/configure-authentication-providers-ae1b4709-e04b-4870-aee8-8a60a0fa787c?ui=en-US&rs=en-US&ad=US
Workflow Manager 1.0 must be installed by account which runs SP services.
- Proposed as answer by Dennis Guo Monday, June 18, 2018 6:51 AM
- Marked as answer by Secretto Tuesday, June 19, 2018 5:27 AM
Monday, June 18, 2018 6:18 AM
All replies
-
Hi,
For SharePoint 2016, I suggest you refer to the following article to install Workflow Manager.
SharePoint 2016: Step By Step Installation of Workflow Manager
The installation step by step guide is here:
https://gallery.technet.microsoft.com/office/SharePoint-2016-Workflow-acd5ba2a
Best Regards,
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.Monday, June 4, 2018 8:39 AM -
Thanks for reply,
I was following this instructions and reinstalled Workflow Manager. But I can't insrall Web Platform Installer because the computer hasn't Internet Connection. To install Service Bus, Workflow Client and CU2 I used these commands (like here click):
WebpiCmd.exe /Install /Products:ServiceBus /XML:E:\ServiceBus\feeds\latest\webproductlist.xml
WebpiCmd.exe /Install /Products:WorkflowClient /XML:E:\WorkflowClient\feeds\latest\webproductlist.xml
WebpiCmd.exe /Install /Products:WorkflowManagerRefresh /XML:E:\WorkflowManagerRefresh\feeds\latest\webproductlist.xml
CU2 for Workflow Manager was installed after third command execution.
Then I downloaded CU1 for Service Bus, KB3086798 and CU3 for Workflow Manager on the machine with internet access, copied these files to the SharePoint Farm computer and installed them manually.
After that I was able to configure Workflow Manager by instruction.
Workflow Manager 1.0 was successfully configured. The host was added to farm.
I exported the Workflow Certificate and imported it to SharePoint, then registered Workflow Service Proxy. Workflow Service Status is connected.
I can create SharePoint 2013 Workflow, but can’t run it.
When I run Workflow manually, the problem still exists: «Something went wrong. To try again, reload the page and then start the workflow»
- Edited by Secretto Tuesday, June 5, 2018 12:06 PM
Tuesday, June 5, 2018 11:38 AM -
Hi,
Please activate Workflow Manager Logs, and see the detailed information in Event Viewer.
https://msdn.microsoft.com/en-us/library/jj193526(v=azure.10).aspx
And troubleshoot this issue following article below.
Troubleshooting Actions for SharePoint 2013 Workflows
Best Regards,
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.Thursday, June 7, 2018 9:53 AM -
Thanks for reply,
I enabled claim-based authentication for my site collection and workflow 2013 works. The topic about this https://social.technet.microsoft.com/Forums/lync/en-US/e504e159-2f79-4cc4-885a-d1e74250a09a/convertspwebapplication-new-parameter-from?forum=sharepointadmin
https://docs.microsoft.com/en-us/powershell/module/sharepoint-server/convert-spwebapplication?view=sharepoint-ps
https://support.office.com/en-us/article/configure-authentication-providers-ae1b4709-e04b-4870-aee8-8a60a0fa787c?ui=en-US&rs=en-US&ad=US
Workflow Manager 1.0 must be installed by account which runs SP services.
- Proposed as answer by Dennis Guo Monday, June 18, 2018 6:51 AM
- Marked as answer by Secretto Tuesday, June 19, 2018 5:27 AM
Monday, June 18, 2018 6:18 AM -
Hi,
Glad to hear that you solve this issue, thanks for your sharing.
You can mark the reply as answer, it will make others who stuck with the similar issue easier to search for valid solutions in this forum.
Best Regards,
Dennis
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.Monday, June 18, 2018 6:51 AM