So we have a SharePoint Designer workflow on list A that runs when an item is created and creates a document set in library B. This is a well established workflow that has been running sucessfully for some time. Post update/fix when the workflow runs I am seeing these errors in the history:
Prior to the update the workflow ran sucessfully like this:
This is not the only workflow where I have observed this behaviour. In another workflow it showed the same symptoms with errors, but eventually completed successfully. It appears the update/fix implemented has had a knock on effect to the workflows.
This is the other workflow ive observed similar behaviour, but eventually completed:
I should mention i dont have access to ULS logs so cannot comment on those.
Cant comment on SharePoint designer workflows, but am sure if other folks have been getting errors after applying the patch there would be quite a bit of discussions on the msdn forums.
I am assuming the workflow failed to execute after throwing these errors ? as in quite some instances I have seen before sometimes such error comes but the workflow still executes properly (case with Nintex would not be applicable to SharePoint Designer workflows)
You would have to check ULS logs for more details. Did you try republishing your workflows again?
This patch is noted to cause issues to SPD and Nintex workflows alike. There has been a lot of discussion on this issue in the MS support forums so a public KB is out (not a hotfix) https://support.microsoft.com/en-us/help/4465015/sharepoint-workflows-stop-after-cve-2018-8421-secur...
That was a really very helpful post...
Part of the issue which Anthony faced was that when he made those necessary config file changes (as you put out in your blog) SPD workflows started throwing some errors. I am assuming it might not be related to this issue and could be something else or ULS should show up. Did you in your experience of this issue face any SPD workflows failing after applying this fix?
Actually we found the issue from SPD workflows first, then also found it for Nintex environments as well. The fix applied to both environments fixed our issue.
Thanks for your input into thread aswell - really appreciated
Out of interest did you need to do an IIS reset/ SP timer service restart also after the fix? Our infrastructure team only applied the first solution (the one linked from your article that didnt include nintex) originally which seemed to fix our SP desinger workflows, but since then only one is completing successfully, but with many errors and others arent staying in progress and just creating lots of errors (as above).
I have asked the infrastructure team to review the KB you linked to earlier and implement a fix for both SP and nintex workflows. I will keep you posted on progress!
I just wanted to put an update in this thread as since my last update we have ran the script linked in article above here including the Nintex elements, did an IIS reset all on SP servers and restarted the SP timer service on all servers and our Nintex workflows are still failing on start.
I have also noted that our SP designer workflows that contain pause steps within them are not completing successfully and getting stuck in an 'error' loop which was what i was first seeing in my earlier post above. Someone in the SharePoint reddit forum had the same issue and posted his resolution here, although I have yet to test it:
We are focussing on getting the Nintex workflows working right now so i will keep this thread updated of any progress but so far:
Is that with old workflows or even any new workflows that are published on Nintex does not work?
1) Try republishing the workflow to see if the error goes off?
2) Try to remove any "Pause" on Nintex workflows to see if its better?
3) Assuming you have also updated the owstimerconfig file as well? As that would directly impact all the workflows that are running by the timer service
4) Assuming you have updated the web.config for your particular web application which has these workflows, I have seen instance where in our infrastructure team modified the config file of Nintex in 15 hive rather that web,.config of the web application
5) Lastly if nothing works you should probably try rolling back the Microsoft patch and wait till the time the hotfix is released.
Again thanks for getting back to me so quickly! I have just tried to republish a workflow that does not have a pause in (to action your points 1 & 2 simutaneously!) and I get the following error message when hitting publish:
In response to 3) we checked the ULS logs and the owstimerconfig and couldnt see anything untowards there. Do you think its worth updating that also? Failing that we are pretty much thinking roll back now, but thanks for the suggestion on 4) will look into that also
Will keep you posted.