workflow manager
3 TopicsSharePoint Workflow Manager service constantly restarting - InvalidCastException
We recently started encountering an issue with the Microsoft Workflow Manager. Every few minutes the Workflow Manager service will crash and restart. We have 3 hosts to manage 2013 workflows in our SharePoint 2016 environment. Workflows in the environment continue to work, but sometimes delayed or unavailable. We went ahead and upgraded to the SharePoint workflow manager that was released this year (2023) as the Microsoft one has been deprecated, still with 3 nodes in the farm. We are still encountering the same issue. All that is recorded in the event viewer is "Failed Service Bus Operation: System.InvalidCastException: Specified cast is not valid." Which is then followed by "Application: Microsoft.Workflow.ServiceHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception." And after a moment or two, the Workflow Service comes back online. My best guess is that there is an offending workflow that is trying to cast an incompatible value? I can't seem to find it though, and I find it odd that it crashes the workflow service and there is no further information on what workflow or where to look to fix it. Nothing in the SPLogfiles that jumps out either. Here are the screenshots from the Event Viewer:2.7KViews0likes3CommentsUpdate a filed using sharepoint workflow 2013 without affecting its modified date & version
I am working on a sharepoint online classic team site. and i have a custom list which contain a field named "Formatted ID" , which is formatted as follow "ITEMID-IT", so the field will hold values such as "1-IT", "2-IT", ...."500-IT". to achieve this i want to create a workflow 2013 which get triggered on item added, to set the formatted id value. but my question is; if i can force the workflow to update/set the "formatted ID" field without affecting the item version or the item modified date? something similar to how "SystemUpdate" works when writing power-shell scripts?872Views0likes2CommentsHow to migrate the SP 2013 workflows from one Scope to new Scope in SharePoint Server 2016
I have a SharePoint farm with Dedicated WFM farm which is working fine, Now i am splitting SharePoint farm in to two farms (Farm A and Farm B) but workflow manager farm will be remain same. Everything is working fine after the split expect SharePoint 2013 workflows. I am getting the Scope not found error when i try to run the workflows in farm B (it is expected that scope of the WFM change in farm B). getInstances threw exception: Microsoft.Workflow.Client.ScopeNotFoundException: Scope '/SharePoint/default/ad2f730d-7d0c-417d-972f-df9a2d992506/c352cde2-28b2-4b54-a7ee-3ad215a6b726' was not found. HTTP headers received from the server - ActivityId: dsdd9142-62af-4df0-ad2b-297f6713e70. NodeId: KFWFM. Scope: /SharePoint/default/0d-7d0c-417d-972f-df9a2d992506/cde2-28b2-4b54-a7ee-3ad215a6b726. Client ActivityId : aebf9e-b173-a0e9-9225-ccda760a9ba5. ---> System.Net.WebException: The remote server returned an error: (404) Not Found. at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result) at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest r... 64aebf9e-b173-a0e9-9225-ccda760a9ba5 Now question, what is process to move the workflows related to these sites to under new scope.1.1KViews0likes0Comments