none
Workflow interop stops working for large lists RRS feed

  • Question

  • Hi,

    I noticed a strange behavior with a SP 2013 workflow that calls a 2010 workflow. I have this in an on-premise 2013.

    First some context, I have created a test library with 55 documentsets, numbered from 01 to 55. In each of these document sets I copied 100 documents, from 100.txt to 199.txt with only one line there. I created two workflows, a 2013 workflow that does call the 2010 workflow. The 2010 workflow writes a "Hello world" to the log history of the workflow. I created the content in sequence, so first the document sets from 01 to 55 and then copying the same documents in each of the document sets, first in document set 01, then 02, up to the end for document set 55

    When I start the 2013 workflow for

    (1) document 100.txt in document set 01, everything works fine

    (2) document 100.txt in document set 55, my 2013 workflow gets suspended with a "Bad request". I have the following error messages from the ULS logs:

    Exception occured in scope Microsoft.SharePoint.WorkflowServices.WorkflowInteropService.EnableEvents. Exception=System.ArgumentException: item   

     at Microsoft.SharePoint.WorkflowServices.FabricInteropProvider.DefinitionsForItem(SPWeb web, Guid listId, Guid itemGuid)   

     at Microsoft.SharePoint.WorkflowServices.FabricInteropProvider.<>c__DisplayClass1.<EnableEvents>b__0()   

     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()   

     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)   

     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)   

     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)   

     at Microsoft.SharePoint.WorkflowServices.WorkflowInteropServiceServerStub.InvokeMethod(Object target, String methodName, ClientValueCollection xmlargs, ProxyContext proxyContext, Boolean& isVoid)   

     at Microsoft.SharePoint.Client.ServerStub.InvokeMethodWithMonitoredScope(Object target, String methodName, ClientValueCollection args, ProxyContext proxyContext, Boolean& isVoid)

    Original error: System.ArgumentException: item   

     at Microsoft.SharePoint.WorkflowServices.FabricInteropProvider.DefinitionsForItem(SPWeb web, Guid listId, Guid itemGuid)   

     at Microsoft.SharePoint.WorkflowServices.FabricInteropProvider.<>c__DisplayClass1.<EnableEvents>b__0()   

     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()   

     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)   

     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)   

     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)   

     at Microsoft.SharePoint.WorkflowServices.WorkflowInteropServiceServerStub.InvokeMethod(Object target, String methodName, ClientValueCollection xmlargs, ProxyContext proxyContext, Boolean& isVoid)   

     at Microsoft.SharePoint.Client.ServerStub.InvokeMethodWithMonitoredScope(Object target, String methodName, ClientValueCollection args, ProxyContext proxyContext, Boolean& isVoid)

    This setup is to simulate the problem I have for migratinga 4000 item document library with some 2000 document sets and 3000 documents that I need to move to the right document set. I do this using a 2013 workflow that calls 2010 support workflows, for example to move the file.

    Any ideas on how to solve this ?

    I tested the same setup on Office 365 and I do not have the error ;-(

    Best regards,

    Marc Nemegeer

    Thursday, October 1, 2015 9:11 AM

Answers

All replies

  • Hi,

    After some work together with Microsoft support it looks like we will have a fix for this :-)

    https://blogs.technet.microsoft.com/stefan_gossner/2015/12/08/december-2015-cu-for-sharepoint-2013-is-available-for-download/

    I checked the release notes and the fix you are waiting for is listed in the release notes : https://support.microsoft.com/en-us/kb/3114352

    A   SharePoint 2010 mode workflow does not start successfully from a SharePoint   2013 mode workflow for a document in a SharePoint Server 2013 document   library that contains thousands of documents.

    We highly recommend you to test the Cumulative Update on a test environment before the deployment on production.

    Best regards,

    Marc

    • Marked as answer by nemegeerm Thursday, December 10, 2015 9:12 AM
    Thursday, December 10, 2015 9:12 AM
  • Hi Marc

    I am currently running into the same issue on SharePoint online. My document Library contains 25K documents.

    when i try to call SPD 2010 WF from SPD 2013 WF for Approval process, i get the same error as above.

    Please tell me if the above issue is resolved in SP online also or if there is any alternative approach i can use to accomplish my approval requirement through SPD 2010 WF.

    Any inputs here would be greatly appreciated.

    Thanks

    Manoj

    Sunday, October 13, 2019 5:15 PM