Update InfoPath Activity Suspended

A customer is working with InfoPath form with attachment. When the attachment size grows bigger and bigger, the process is suspended at the Update InfoPath Activity. See picture below.

I usually do not recommend to attach large attachment to InfoPath, because the whole xml of InfoPath is submitted to AgilePoint every time the user completes the task. The larger the attachment, the slower the data transfer between SharePoint and AgilePoint.

For large attachment, I suggest to keep that attachment file in a library in SharePoint, then keep the link of that attachment in the InfoPath form. Then user can still open up the attachment from the InfoPath form.

The other thing can be looked into is the maxRequestlength setting in the web.config of AgilePoint and SharePoint. See this KB. But this will not help much on the speed/performance if the file is too large. The bandwidth of the network actually becomes the bottleneck in this case.

ISPOperationQueue Error

 

If you are using AgilePoint Integration for SharePoint and you get an error like this:

2010-12-20 13:11:06.787 >>> UpdateInfoPathFile, System.InvalidCastException: Unable to cast object of type 'Ascentn.Workflow.Base.WFIntegratedApplication' to type 'Ascentn.SharePoint.AgileParts.ISPOperationQueue'.

at Ascentn.AgilePart.SharePoint.SPSAgileParts.DropToQueue(WFProcessInstance pi, WFAutomaticWorkItem w, IWFAPI api, SPOperation operation)

at Ascentn.AgilePart.SharePoint.SPSAgileParts.UpdateInfoPathFile(WFProcessInstance pi, WFAutomaticWorkItem w, IWFAPI api, NameValue[] parameters)

 

That is because you have not set up the AgileConnector info at AgilePoint Server Configuration panel. The assembly, Ascentn.SharePoint.AgileConnector.dll, is located in the bin folder of AgilePoint Server. This dll is available with the installation of AgilePoint Server, but it is not configured by default. See picture below for the configuration example.