Skip to main content

Hi all,


I am working with K2 Studio to integrate a workflow with InfoPath in Sharepoint Server 2010. The InfoPath form has a couple of views. Each view is associated with some client event and in each view some extra fields are added to fill in by a different user.


There is one user at the end of the workflow that has the "final" command: he can approve the form, or reject it. When rejected, the flow returns all the way to the beginning. This is where it fails: when the first user receives his task when the form was "rejected", an error appears in the Error Logs: The file <task xml> is locked for exclusive use by <originator>. The <task xml> is the name of the InfoPath task hidden inside the workflow.


The strange thing is that the form is successfully submitted, and after that the InfoPath task (with the same name as found in the error logs) appears in the document library to which the workflow is attached.


I googled a bit first, and I only found one solution that made sense: configure the workflow timer job to schedule faster (e.g. on a 1 minute base) and inject a Pause in the K2 blackpoint flow. I implemented this solution, but with no success.


Has anyone encountered the same problem and knows how to help me out?


Any help would be appreciated, I'm kind of stuck :-)


 


Kind regards,


Klaas Lauwers


 

Probably a hack around but have you tried creating a dummy activity and configure a start rule on it to maybe continue a minute later?


However, I would suggest logging a support ticket on this to get the labs team to look at your scenario.

Johnny,


Thanks for the reply. I read somewhere that this issue is a SharePoint workflow timer job issue and that I need to pause my action for 10 minutes to be sure the timer job freed all of the locks. This is not feasible for my workflow, so I just logged a ticket. I'll keep you up to date with the solution.


Wkr,


Klaas Lauwers

Hi there,


Did you ever find out how to resolve this issue?  I am experiencing this myself also.  K2 Error Logs show the same error, and its the .xml file which is locked by the user.  It does however happen at different steps, and does not happen every time, so it's a bit random.


Regards,


Elrico Heinen

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings