Error updating a list item unknown error
We have this heavily used Share Point Designer workflow(500 and more instances per day).
(uses infopath to submit data) It is basically an serial Approval workflow involving many approval levels.
Post migration almost 90% of our workflow end in "Error Occurred" state with the following description of the error: The workflow could not update the item, possibly because one or more columns for the item require a different type of information.
I have searched a lot of websites and msdn, tried possibly all solutions given, but none seems to work.
Also I have been searching around and found that most people experiencing this type of problem have a conflicting value in either the Col Name, ID or Name fields.
Get List Item Data With Callback2(IList Item Sql Client p Sql Client, String bstr Url, String bstr List Name, String bstr View Name, String bstr View Xml, SAFEARRAYFLAGS f Safe Array Flags, ISP2DSafe Array Writer p SACallback, ISPData Callback p Paging Callback, ISPData Callback p Paging Prev Callback, ISPData Callback p Filter Link Callback, ISPData Callback p Schema Callback, ISPData Callback p Row Count Callback, Boolean& pb Maximal View) Failed to get document content data. ULS logs gives me: I am pretty sure I have seen the "Failed to do column assignments" error before, when I try to create/edit a list item.
Every great once in a while, the workflow will fail on creating the document set.
We recently migrated from MOSS 2007 to SP 2010 platform.
There is no set pattern for the workflows that result in error and restarting the workflow always resolve the issue.
A lot of sites mention introducing a pause in the workflow before update event, but I am skeptical in doing it. we cannot identify anything that is common or direct us to the root cause among these 90% failing workflows.
Having this option checked without the Content Approval feature in use will result in this error message.
I have recently, and for reasons unknown, started to get errors with a particular list on Sharepoint 2013. To find out what field was causing the problem, I created a view and included all the fields available to me.