SharePoint Workflow Manager (2023) HTTP Error 500.19

Question

Installing the new SharePoint Workflow Manager ver 16.0.15601.20418 (released 12/26/2022) on a Windows 2016 app server following this guide: https://www.microsoft.com/en-us/download/details.aspx?id=104867.

Using a computer certificate requested from our domain Certificate Authority (CA). Configuration completes successfully with databases and accounts etc. No connection to the SharePoint farm is done yet at this point. When browsing the local website - https://localhost:12290 - it fails with internal error:

IIS web site with only https activated (as default for SharePoint Workflow Manager):

Trying the URL (servername FQDN to match the CA certificate) from a SP server (same LAN):

Certificate looks OK. Something wrong with the SharePoint Workflow Manager config file?

Same error when trying to create a certificate authority on the SP farm server using the WFM endpoint for the WF Farm:

Any tips?

PS! Used these sources (and more) for reference/guide:

https://learn.microsoft.com/nb-no/sharepoint/governance/install-and-configure-workflow-for-sharepoint-server

https://spgeeks.devoworx.com/configure-workflow-manager-sharepoint-2016/

http://www.harbar.net/articles/wfm4.aspx

https://learn.microsoft.com/en-us/sharepoint/governance/video-series-install-and-configure-workflow-in-sharepoint-server-2013

Answer 1

Hey there, found a solution for my problem, try if this fixes yours:

In my scenario I have a Standalone Installation with IIS Webserver on a dedicated Windwso Server 2022.

I recognized that my installation was missing IIS features wich lead to the exact error that you have.

Features that I installed:

IIS > Webserver > Common HTTP Features

• Default Document
• Directory Browsing
• HTTP Errors
• Static Content

IIS > Webserver > Health and Diagnostics

• HTTP Logging
• Logging Tools
• Request Monitor
• Tracing

IIS > Webserver > Performance

• Static Content Compression
• Dynamic Content Compression

IIS > Webserver > Security

• Request Filtering
• Basic Authentication
• Windows Authentication

IIS > Webserver > Application Development

• .NET Extensibility 4.8
• ASP.NET 4.8
• ISAPI Extensions
• ISAPI Filters

After installing those features from "Add Roles and Features" my workflow farm threw no more errors.

Cheers,

Kai

Answer 2

It may be caused by wfupgrade targetVersion in the configuration file mismatches with StoreVersionTable in the SQL table.

You could try to refer this article to solve this issue.

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

---

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.

Answer 3

Checked the values in the config file and in SQL and it was the same: 1.5. Did run the queries mentioned in the article though and restarted the systems. Open IIS again to https://bgo-sp2016-wfm.hl.ad:12290 and it prompted a logon window - tried to logon with the WFM setup and the service accounts but ends up with this error:

Same error occurs when running New-SPTrustRootAuthority in the SharePoint 2016 farm.

Get-WFFarmStatus:

WorkflowServiceBackEnd = Running

WorkflowServiceFrontEnd = Stopped

Answer 4

Hey guys,

just wanted to tell you, you're not alone and I am facing the same issue in some of my customers dev-farms.

If I find a solution for this I'll let you know ;-)

Cheers,
Kai