Hello there,
I need a help on this situation that i'm stuck with. The scenario:
A SharePoint 2013 default portal with a custom Solution that we created to our costumer demands. This Solutions is a Farm Solution that uses the most of SharePoint features to run, like lists, securities, document library, and everything else. The major business process runs with a workflow that we created using Visual Studio 2015 and Workflow Manager features in order to keep everything up to date with the lastests releases from MS.
Everything WORKS!!!!!! ... until yesterday.....
For some reason, now the worklow throws an Exception when it try to update the item field with a new value (this field is a default text column). The value, that WF tries to update is a simple text like "IN PROGRESS" status, and it uses the WF default activity UpdateItem
I troubleshooted and found this: when it tries to update, the activity call a method from a REST API (that i think is the default way to Interact with its item). I debuged it with Fiddler and got this message:
Fiddler debugging:
This is wieard because the WF uses the SystemAccount Identity to run, and no matter what users i'm logged on portal and run WF on item again , the results is Always the same one: "HTTP 500", Microsoft.SharePoint.SPException and this message: "relatedModifyPermissions:Attempted to perform na unauthorized operation" (even if it's a site Collection admin, full control user, etc..). Of course I checked the permission on the item and the permissions applied is correctly (but no matter, 'cause WF are using a elevated privileges account to run... however.. i checked)
There are no related messages on event viewer log, nor on SharePoint ULS log.
I tried:
- Re-created ALL Workflow Manager farm;
- Uninstalled and Installed again all Workflow Manager and Service Bus application (with the releated CU's and Other KBs availables)
- Re-created WF Service Application with a different scope names (yes, i removed all scopes before registering the new ones)
- Tried in different farm, like DEV virtual machine, and I don't get this error!
Why only now, and after a several workflows worked correctly?
Anyone knows what is going on this workflow?
Someone please!!!
Thanks in advance