We recently announced the release of SharePoint Workflow Manager which is a replacement for Microsoft Workflow Manager.
Meanwhile new documentation has been released covering the installation and configuration of SharePoint Workflow Manager:
We recently announced the release of SharePoint Workflow Manager which is a replacement for Microsoft Workflow Manager.
Meanwhile new documentation has been released covering the installation and configuration of SharePoint Workflow Manager:
Permalink
Hi Stefan,
My farm consists of 3 server: Web, Search and one just for the Microsoft Workflow Manager.
I was reading the documentation where I found “Install SharePoint Workflow Management Client on each server in the SharePoint Server farm after uninstalling any previous versions.”
Do I have to install them on the 2 SharePoint Server or can keep this 3 server configuration where the Manager is just on the 3rd one?
Permalink
Hi Borsoi,
this is about the SharePoint Workflow Manager CLIENT component – not about SharePoint Workflow Manager.
The Client component is required to ensure that the workflow code running in the IIS worker processes can communicate with your Workflow manager server.
Cheers,
Stefan
Permalink
Ok thanks.
What about compatibility of the already deployed workflows? We have a plugin/solution installed, which extends the Workflows actions and are wondering if our workflows will still run.
Permalink
Hi Borsoi,
I would recommend to evaluate the 3rd party component in a test environment first before performing the upgrade of the production farm. If any issues occur the first step would be to contact the provider of the relevant 3rd party to allow them to investigate the issue and if required update the component. If the 3rd party component provider needs assistance from Microsoft he can open a support case to get assistance from developer support.
Cheers,
Stefan
Permalink
This documentation lacks the most important (most error-prone, most complicated) part: the actual configuration of Workflow Manager.
Permalink
Hi Dirk, as the article has a long section about configuring SharePoint Workflow Manager with SharePoint. What exact information are you missing?
Permalink
Not sure whether I understood the process correctly – but in order to do this (i.e., to have a workflow host URI endpoint) …
Register-SPWorkflowService -SPSite “http://myserver/mysitecollection” -WorkflowHostUri “http://workflow.example.com:12291” -AllowOAuthHttp
… you will need to run the Workflow Manager Configuration Wizard, that will create the corresponding databases, start services, …, right?
Permalink
TBH the previous instructions didn’t cover that part of the setup either, so the updated documentation is no worse. Tucked away in the following section is a video series that covers the whole setup process, including the configuration wizard – https://learn.microsoft.com/en-us/sharepoint/governance/video-series-install-and-configure-workflow-in-sharepoint-server-2013. It could possibly do with a refresh, but the workflow configuration part is still valid.
Permalink
Got it! I have sent the feedback to the relevant team.
Permalink
Hi,
Best documentation is still the one from Spencer Harbar.
The most detailled end usefull information…
http://www.harbar.net/archive/2013/07/26/Article-Workflow-Manager-Farms-for-SharePoint-2013-Part-One-Core.aspx
Permalink
Hi Stefan, die MS Anleitung haut nicht hin.
Wenn man der WF Farm rejoined, sagt die Config am Ende, dass wir noch part of the farm, wären und bricht ab. Das stimmt aber nicht.
Permalink
Hi Marcel,
it looks as if something went wrong on step 2: “Select Leave Workflow Manager Farm.”
If you need assistance for this I would recommend to open a support case with Microsoft.
Cheers,
Stefan
Permalink
Hi Stefan,
just for info. We opened a case with this problem.
Configuration progress..
Add host to Service Bus farm – failed
This host wvxxx.ppro.xxx.de is already part of Service Bus farm.
Check:
get-sbfarmstatus : This host is not joined to any Service Bus farm. To join a farm run Add-SBHost cmdlet.
Greetings
Permalink
There is a missing point in the MS documentation (Section:Upgrade tu SP Workflow Manager)
Missing is “To Leave also the Service Bus Farm”
MS Support will later try to clean up the wrong Service Bus connection.
Permalink
Hi Marcel,
just to clarify – you mean to remove the current server from the Service Bus farm using “Remove-SBHost”?
Permalink
I mean, open Service Bus Configuration, than choose „Leave Service Bus Farm.“
Permalink
SharePoint Workflow Manager Upgrade Summary
Our problem:
We did not leave the Service Bus farm because it was not in the MS documentation.
So we could not join our WF Manager farm later.
Solution:
Remove SBHost
Remove-SBHost -HostName xxxx.xx.xx.de -SBFarmDBConnectionString “Data Source=server\instance;Initial Catalog=TEST_Sb_ManagementDB;Integrated Security=True;Encrypt=False”.
After that it still did not work.
Normally two local groups should be created when installing MicrosoftServiceFabric, but were not!
We created these,
ServiceFabricAllowedUsers
ServiceFabricAdministrators
Member in each group is the account of the WF Manager.
With this we already got further…
But we still had to remove the WFHost.
Remove WFHost
Remove-WFHost -HostName xxxxx.xxx.xx.de -WFFarmDBConnectionString “Data Source=server\instance;Initial Catalog=TEST_WF_ManagementDB;Integrated Security=True;Encrypt=False”
After that we could finally join the WF farm and when reopening the WF configuration select the item “Upgrade Workflow Manager Farm”.
Translated with http://www.DeepL.com/Translator (free version)
Permalink
Thanks for sharing these details! I have informed the relevant team in the product group about your experience. The info I got is that In general the step to leave the wf farm should automatically also perform the operation to leave the sb farm. They are now investigating what might have gone wrong here.
Permalink
Hi Stefan – short update.
Today, we installed WF Manager Client on SP server. Trust and proxy looks ok, but a workflow doesn`t work. We are waiting for next support meeting with MS.
Permalink
Some clear instructions on installing the prerequisite Azure Fabric would probably also be exceedingly helpful because the existing documentation on that product isn’t really targeted at what you need to do with that installation to specifically support this workflow product.
Permalink
Hi Deanna,
thanks for the feedback – I have forwarded your suggestion to the relevant team.
Cheers,
Stefan
Permalink
Thanks Stefan – Perhaps to clarify a bit, for workflow manager I believe the idea is to use the “MicrosoftServiceFabric executable rather than the Microsoft.Azure.ServiceFabric.WindowsServer ZIP package and having done the latter for other projects I didn’t realize this the first time through.
Permalink
Hi Deanna,
indeed – the link in the article has been corrected today and now points to
https://download.microsoft.com/download/b/8/a/b8a2fb98-0ec1-41e5-be98-9d8b5abf7856/MicrosoftServiceFabric.9.0.1048.9590.exe
Cheers,
Stefan
Permalink
That is interesting because MS support told me to use ZIP file and install windows fabric using powershell script just as it was in older documentation.
Anyway on fresh install I had issue that below groups were not created
ServiceFabricAllowedUsers
ServiceFabricAdministrators
MS Support also advised me to manually add IIS role, that part is missing in documentation.
Permalink
I just want to add information on updating the Service Fabric, as the current version of 9.1.1048.9590 is considered a finding on ACAS scans with DoD. Must now be 9.1.1583.9590. Since no real information or guidance on how to just update the SF after you have SP Workflow Manager running, I ran through scenarios until something worked. You need to download the runtime version exe. First, you must leave the WFM farm. Then uninstall the current ver of SF. Install new version with /AcceptEULA in PS or CMD prompt. If the uninstall of current version doesn’t remove the files under c:\Program Files\Microsoft Service Fabric, the install of updated SF with fail. You’ll have to reboot and then remove leaselayr.sys file. Install the updated SF again. Rejoin Farm. Run Upgrade Workflow Manager. Test your workflows.
Permalink
Would like to add additional info for Marian: The ServiceFabricAllowedUsers and ServiceFabricAdministrators are 2 groups that are added to the Local Users and Groups when installing the Service Fabric runtime. When you rejoin the farm, it will put the WFM service account back into these groups.
Permalink
hi,
we need to update Microsoft Azure bus version from 9.1.1583.9590 to 9.1.1799.9590 (9.1 CU4) that is insalltd as a prequisit to SharePoint Workflow Manager.
not able to find any Microsoft documetnation on how to do so, can you help here?
Permalink
Hi Stefan,
we have problems creating a new Workflow Manager farm.
Our environment:
SharePoint 2019, CU May 2024 on Windows Server 2022
– .Net 4.8
– sharepointworkflowmanager.msi 16.0.15601.20418
– sharepointworkflowmanagerclient_x64.msi
– Azure Fabric 9.1.1583.9590
SQL Server 2022 (16.0.1000.6) on Windows Server 2022
We followed the instructions provided here:
https://learn.microsoft.com/en-us/sharepoint/governance/install-and-configure-workflow-for-sharepoint-server#install-workflow-manager
When executing the Workflow Manager Configuration we receive this error message:
Error] [06.09.2024 11:08:43]: System.Management.Automation.CmdletInvocationException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as “” or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as “” or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as “” or [] are not allowed. Change the alias to a valid name. —> System.Data.SqlClient.SqlException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as “” or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as “” or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as “” or [] are not allowed. Change the alias to a valid name.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action
1 wrapCloseInAction)
1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource
1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
3 updateProgress)at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
at Microsoft.ServiceBus.Commands.Common.ServerManagementStoreDataContext.CreateServerAdministratorLogin(String loginName)
at Microsoft.ServiceBus.Commands.Common.ManagementDbContext.CreateServerAdministratorLogin(String loginName)
at Microsoft.ServiceBus.Commands.Common.SecurityHelper.CreateServerAdministratorRole(String accountName, String connectionString)
at Microsoft.ServiceBus.Commands.NewSBFarmBase.InstallManagementDB(String connectionString)
at Microsoft.ServiceBus.Commands.NewSBFarmBase.ProcessRecordImplementation()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action
at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.CreateSBFarm(FarmCreationModel model)
In the SQL server error log we see this:
09/06/2024 11:10:47,spid135,Unknown,RBPEX::NotifyFileShutdown: Called for database ID: [24] file Id [0]
09/06/2024 11:10:47,spid135,Unknown,RBPEX::NotifyDrop: Called for database ID: [24] file Id [0]
09/06/2024 11:10:44,spid135,Unknown,Setting database option SINGLE_USER to ON for database ‘SbManagementDB’.
09/06/2024 11:10:43,spid135,Unknown,Parallel redo is shutdown for database ‘SbManagementDB’ with worker pool size [8].
09/06/2024 11:10:43,spid135,Unknown,Parallel redo is started for database ‘SbManagementDB’ with worker pool size [8].
09/06/2024 11:10:43,spid135,Unknown,RemoveStaleDbEntries: Cleanup of stale DB entries skipped because master db is not memory optimized. DbId: 24.
09/06/2024 11:10:43,spid135,Unknown,RemoveStaleDbEntries: Cleanup of stale DB entries called for database ID: [24]
09/06/2024 11:10:43,spid135,Unknown,Starting up database ‘SbManagementDB’.
Any ideas how to resolve this?
Permalink
Hi Thomas,
sorry – haven’t seen this.
I would suggest to open a support case with Microsoft to get this analyzed.
Cheers,
Stefan
Permalink
Hello Stefan and everyone,
I have installed SharePoint Workflow Manger following the official documentation and video series in a Single Server SharePoint Server 2016 Dev Environment with a SQL 2016 Backend, everything installs and configures just fine, all services are running as they should, both WFFarm and SBFarm statuses return fine via PowerShell, I can open both http and https endpoints without issues or certificate errors, etc. but I’m unable to successfully run the Register-SPWorkflowService cmdlet, I honestly have exhausted the very few articles out there for this version of Workflow Manager and even tried some old tricks and things from the previous version and unfortunately nothing worked. It always fails with the following error:
Register-SPWorkflowService : A response was returned that did not come from the Workflow Manager. Status code = 404:
ScopeNotFoundError
Scope ‘/SharePoint’ was not found.ScopePath/SharePointEntityName/SharePoint HTTP
headers received from the server – ActivityId: a9eae066-b770-4c96-bfe7-53d9e14e2a80. NodeId: SERVERNAME. Scope: /SharePoint. Client ActivityId :
69605fa1-8216-e0c0-6f75-ff1bd34c7bae.
At line:1 char:1
+ Register-SPWorkflowService -SPSite “https://mydomain.mycompany.net/sites/default …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share…WorkflowService:RegisterSPWorkflowService) [Register-SPWorkflowService], WorkflowManagementException
+ FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell.RegisterSPWorkflowService
Any ideas where should I be focusing my troubleshooting efforts?
Thanks,
Alex