SharePoint 2019 - Workflow manager 1.0 - Connection

Question

SharePoint 2019 - Workflow manager 1.0 - Connection

durica 40

Hi, I am experiencing an issue with SharePoint 2019 (Two servers) Workflow Manager 1.0 integration where Workflow 2013 platform type is not visible and cannot be created after re-registration.

After removing and re-registering the Workflow Service, the Workflow 2013 platform type is no longer available in SharePoint Designer or when creating workflows.

Steps:

Removed existing Workflow configuration:

# Remove Workflow Service Application Proxy
$wfProxy = Get-SPServiceApplicationProxy | ? { $_.TypeName -like "*Workflow*" }
if ($wfProxy) { Remove-SPServiceApplicationProxy $wfProxy -RemoveData -Confirm:$false }

# Remove Workflow Trusted Security Token Issuer
$wfIssuer = Get-SPTrustedSecurityTokenIssuer | ? { $_.Name -eq "00000005-0000-0000-c000-000000000000" }
if ($wfIssuer) { Remove-SPTrustedSecurityTokenIssuer $wfIssuer -Confirm:$false }

# Remove Trusted Root Authority for Workflow Outbound certificate
Get-SPTrustedRootAuthority | ? { $_.Name -match "00000005-0000-0000-c000-000000000000" } | % { $_.Delete() }

Applied certificates from Workflow Manager:
- AutoGeneratedCA.cer - imported to SharePoint's Manage Trust and also installed on both SharePoint servers in "Trusted Root Certification Authorities" store
- WorkflowOutbound.cer - imported to SharePoint's Manage Trust
Re-registered Workflow Service:

Register-SPWorkflowService -SPSite "https://WebAppUrl" -WorkflowHostUri "https://WfManagerServer:12290" -Force

Verified Trusted Security Token Issuers:

Get-SPTrustedSecurityTokenIssuer

Result shows two valid certificates are present.

Triggered metadata refresh:

$tj = Get-SPTimerJob -Identity "RefreshMetadataFeed"
Start-SPTimerJob -Identity $tj

Also attempted removing workflow proxy separately:

Get-SPWorkflowServiceApplicationProxy | Remove-SPServiceApplicationProxy

Current State:

Registration appears successful with no errors
Trusted Security Token Issuers show correctly
Workflow Manager service is running on the Workflow Manager server
However: Workflow 2013 platform type does not appear in SharePoint Designer or site settings
Cannot create new Workflow 2013 workflows

Any guidance on resolving this issue would be greatly appreciated.

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Hi @durica

Thank you for posting your question in the Microsoft Q&A forum.

It looks like too much was removed in the wrong order, and as a result SharePoint did not fully rebuild its internal trust objects.

The specific trigger is when both of these steps are performed together:

Remove-SPTrustedSecurityTokenIssuer
Delete TrustedRootAuthority

After this, SharePoint often recreates an issuer that appears valid, but the OAuth trust chain no longer matches what Workflow Manager expects. Registration does not throw an error, but metadata refresh fails.

You can try the following steps:

1.Verify the Workflow Service Application Proxy exists

Run:

Get-SPServiceApplicationProxy |Where-Object { $_.TypeName -like "*Workflow*" } |Format-List Name, TypeName, Status

Expected:

-Exactly one proxy

-Status = Online

If nothing is returned, Workflow 2013 will never appear regardless of registration attempts. If missing, do not manually create it, proceed with the steps below.

2.Validate Workflow metadata endpoint

From each SharePoint server, open a browser: https://WfManagerServer:12290

You should see a Workflow Manager service response (XML or landing page). If you encounter a certificate warning, 401 error, TLS error, or a blank page, metadata refresh will fail silently.

3.Confirm there is only one Workflow issuer

Run:

Get-SPTrustedSecurityTokenIssuer |Where-Object { $_.Name -eq "00000005-0000-0000-c000-000000000000" }

If more than one issuer is returned, remove the duplicates:

Get-SPTrustedSecurityTokenIssuer |Where Name -eq "00000005-0000-0000-c000-000000000000" |Remove-SPTrustedSecurityTokenIssuer -Confirm:$false

4.Clear SharePoint config cache

On both SharePoint servers:

-Stop timer service:

Stop-Service SPTimerV4

-Go to: C:\ProgramData\Microsoft\SharePoint\Config\<GUID>

-Delete all XML files except cache.ini

-Edit cache.ini and set the value to 1

-Restart the timer service:

Start-Service SPTimerV4

Wait 5–10 minutes for the cache to rebuild.

5.Re-register Workflow Service

Register-SPWorkflowService `
  -SPSite https://WebAppUrl `
  -WorkflowHostUri https://WfManagerServer:12290 `
  -Force

Then trigger a metadata refresh:

Get-SPTimerJob RefreshMetadataFeed | Start-SPTimerJob

I hope this helps resolve the issue.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
durica 40 Reputation points

2026-02-06T15:48:09.8433333+00:00

Hi, thanks for your response, I followed your advice step by step, but without results.

Proxy is running

From both sharepoint servers

There was only one wf issuer

I cleared the cache on both SharePoint servers and waited about 20 minutes before proceeding to the next step.

Re-register Workflow Service and then trigger a metadata refresh

WF Status:
Teddie-D 12,845 Reputation points Microsoft External Staff Moderator

2026-02-09T05:49:48.09+00:00

Hi @durica

Thank you for sharing the details. Everything you’ve shown indicates that the Workflow Manager side is healthy. If the SharePoint 2013 Workflow platform still does not appear, the following causes can still hide it even when the farm looks healthy.

1.Workflow Manager Client is missing or mismatched

-SharePoint Designer and the farm will not surface the Workflow 2013 platform unless Workflow Manager Client 1.0 and Service Bus Client are installed on every SharePoint server.

-Verify via Control Panel > Programs and Features. If missing, install the same version used in your Workflow Manager farm.

2.App Management Service & Subscription Settings Service not configured

-Workflow 2013 depends on the App Model infrastructure.

-If either service application is missing or not associated with the web application, the platform will disappear.

-Verify with:

Get-SPServiceApplication | Where-Object { $_.TypeName -like "*App Management*" -or $_.TypeName -like "*Subscription Settings*" } Get-SPServiceApplicationProxy | Where-Object { $_.TypeName -like "*App Management*" -or $_.TypeName -like "*Subscription Settings*" }

3.Proxies not connected to the web application

In Central Admin > Web Applications > Service Connections, select your web app and confirm the following are checked:

-Workflow Service Application Proxy.

-App Management Service Application Proxy.

-Subscription Settings Service Application Proxy.

Answer 2

It seems you have followed the necessary steps to remove and re-register the Workflow Service in SharePoint 2019, but the Workflow 2013 platform type is still not appearing. Here are a few suggestions to troubleshoot this issue:

Verify Workflow Manager Configuration: Ensure that the Workflow Manager is properly configured and that all necessary services are running. You can use the Workflow Manager Configuration Wizard to check the settings.
Check Service Account Permissions: Make sure that the service account used for the Workflow Manager has the necessary permissions in SharePoint. It should have at least "Full Control" permissions on the site collection where you are trying to create workflows.
Re-run the Workflow Manager Configuration Wizard: Sometimes, re-running the configuration wizard can help resolve issues with the registration and configuration of the Workflow Manager.
Check Event Logs: Look at the SharePoint and Workflow Manager event logs for any errors or warnings that might provide additional insight into what might be going wrong.
Ensure Latest Updates: Make sure that both SharePoint and Workflow Manager are updated to the latest cumulative updates. Sometimes, compatibility issues arise from outdated versions.
PowerShell Cmdlets: After making changes, ensure to run the necessary PowerShell cmdlets to maintain the connection between SharePoint and Workflow Manager. This includes the cmdlets to copy activities to the workflow service.
Metadata Refresh: Since you've already triggered a metadata refresh, ensure that it completes successfully and check if it resolves the issue.

If the issue persists after trying these steps, consider checking Microsoft documentation or forums for any similar issues encountered by others, as there may be specific fixes or updates available.

Share via

SharePoint 2019 - Workflow manager 1.0 - Connection

1 additional answer

Your answer