Microsoft 365 and Office | SharePoint Server | For business
A family of Microsoft on-premises document management and storage systems.
Missing SharePoint 2013 platform type - error install Windows Server AppFabric
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 34%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECY%3C/text%3E%3C/svg%3E)
Chen Yung Pui
22
Reputation points
Hello, I need help with below environment
1 SharePoint 2019 (App/FE) server
1 SQL Server 2016
The first issue found is cannot associate SP2013 Workflow platform in SP Designer 2013. Tried the Register-SPWorkflowService and hit error:
Register-SPWorkflowService : A response was returned that did not come from the Workflow Manager. Status code = 404 Code:ScopeNotFoundError; Message: Scope '/SharePoint' was not found.
Referred to thread to further check, I found the 'Windows Fabric Host Service' is missing.
Web Platform Installer with installed components are:
Error found when install Windows Server AppFabric.
83654-webpi3-20210401.txt
After that noticed the Service Bus Message Broker hanging with "Starting" status. Please advice.
Microsoft 365 and Office | SharePoint Server | For business
Microsoft 365 and Office | SharePoint | For business | Windows
Microsoft 365 and Office | SharePoint | For business | Windows
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
{count} votes
-
Jerry Xu-MSFT 7,961 Reputation points2021-04-02T09:23:16.93+00:00 Hi, @ChengYungPui-2885 ,
I am now looking into this issue and doing tests in my end. Posts will be updated as soon as I get some findings.
-
Chen Yung Pui 22 Reputation points
2021-04-02T10:15:45.237+00:00 Noted. The workflow manager is installed on a server that is part of the SharePoint server farm (SP App/FE server). Communication takes place by using HTTP.
I not sure why the 'Windows Fabric Host Service' is not listed in Services.
I've tried enable TLS 1.2 following the steps here and restarted the server. The status of service Bus Message Broker still same hanging with 'Starting'.
-
Chen Yung Pui 22 Reputation points
2021-04-07T04:01:35.33+00:00 Hi @Jerry Xu-MSFT . Is there any finding from your test?
I have another question. The Workflow Manager for SP2019 farm requires 'Service Bus 1.0' or the 'Windows Azure pack: Service Bus 1.1'?
By rights the WF Manager configuration wizard will installed the Service Bus itself, correct?Is it which service bus to use depends on use case/environment requirement?
Related thread did mention for Service Bus 1.1:
https://learn.microsoft.com/en-us/answers/questions/63306/workflow-manager-installation-issue.html
https://www.reddit.com/r/sharepoint/comments/m435of/what_version_of_service_bus_is_needed_for/ -
Jerry Xu-MSFT 7,961 Reputation points
2021-04-07T09:25:48.603+00:00 Hi, @Anonymous ,
Sorry for keeping you waiting for the response. I test in my end and reproduce your issue with the problem that Microsoft Windows Fabric V1 RTM cannot be downloaded properly. This shall be the current issue. The Workflow refresh CU2 installation will handle the service bus part so no need to worry about it. It will be automatically installed with the proper version. I am still contacting with my colleagues about this Web Platform Installer issue and will let you know the update ASAP.
-
Chen Yung Pui 22 Reputation points
2021-04-07T10:57:33+00:00 Hi @Jerry Xu-MSFT ,
For your info, I have uninstalled all WF Manager related app and services. Then reinstalled everything again for WFM. I did encounter the same issue as yours, I managed to complete setup with the workaround from this helpful thread.
After all WFM setup, the related services seems all running (screenshot below for you to check). However I still encounter the issue to register Workflow Proxy. I did try few times to delete existing Workflow proxy and register again but still no luck. It seems the issue is not because of the bus service problem. Need your advice how to troubleshoot & identify the root cause.
-
Chen Yung Pui 22 Reputation points
2021-04-07T11:44:00.04+00:00 Attached filter ULS log for additional info.85341-reg-spworkflowservice-ulslog.txt
-
Jerry Xu-MSFT 7,961 Reputation points
2021-04-08T08:17:56.817+00:00 Hi, @Anonymous ,
As you mention, you managed to complete setup with the workaround. Does the following steps in configuration work in your end? Just following the tutorial here. And have you installed workflow client on each server which has SharePoint installed?
-
Chen Yung Pui 22 Reputation points
2021-04-09T02:28:07.153+00:00 Hi @Jerry Xu-MSFT ,
I have only 1 SP App (also as front end) server and 1 DB server. The WF Manager is setup on the same SP App server. Workflow client has been installed too.
I have done the configuration steps (without export certificate steps as we go for http) until step 'Register workflow proxy' failed as shown in previous reply screenshot. I have searched around with the error message but not much info I could get. Please advise.
Browse WF Manager port 12991:
WF proxy service status:
-
Jerry Xu-MSFT 7,961 Reputation points
2021-04-12T06:14:40.923+00:00 Hi, @Anonymous ,
It seems you are using a non-SSL SharePoint site and not using a SharePoint 2019 Management Shell. Please Open "SharePoint 2019 Management Shell" as an administrator and run the following command:
Register-SPWorkflowService -SPSite "https://www.domserver.com" -WorkflowHostUri https://workflow.domserver.com:12290 -force -AllowOAuthHttpFor a non-SSL SharePoint site, the parameter "-AllowOAuthHttp" must be added.
-
Chen Yung Pui 22 Reputation points
2021-04-12T07:21:05.917+00:00 Hi @Jerry Xu-MSFT ,
I did try using SharePoint 2019 Management Shell, still facing the same issue. Any info about the Register-SPWorkflowService event and what the event trigger does?
Sign in to comment
Sign in to answer