Workflow

Re: Workflow stuck in Starting state

Jim Cantwell — Mon, 19 Aug 2013 04:29:14 GMT

The first thing to check is that DBXL is running as the same account as the SharePoint site. Using the same account makes sure that DBXL has sufficient permissions to override the Modified By column.

You may also need to edit the DBXL web.config. Please refer to this document:

http://www.infopathdev.com/files/folders/integration_with_sharepoint/entry67954.aspx

Re: Workflow stuck in Starting state

TomRenfro — Wed, 14 Aug 2013 16:32:37 GMT

Ok, here's what I'm observing. The content type form is published to DBXL and is mapped to SharePoint, using different expressions on what library to post the form. The initial submit goes to a library called AdditionApprovals. When the first form is filled out, the Modified by column on the library shows "System Account". The first iteration doesn't start at all. If I go to DAT and reshred that document with no changes, it gets stuck in the Started state. If I delete the document from the library, then reshred that document, the workflow starts correctly, and the Modified by column now reads "s_SPFarm_Prod", which is the system account that DAT runs under.

So it looks like it has something to do with the System Account user.

Re: Workflow stuck in Starting state

TomRenfro — Wed, 14 Aug 2013 16:17:45 GMT

No I created it under my credentials. And it's working as is on other libraries as intended. I'm currently testing deleting the library, creating again with the same name, and adding the same workflow. I'll let you know what happens.

Re: Workflow stuck in Starting state

Jim Cantwell — Wed, 14 Aug 2013 16:12:47 GMT

Did you happen to create the workflow using the system account? If you did, you will need to edit and save the workflow using a domain account with the necessary permissions on the site.

Re: Workflow stuck in Starting state

TomRenfro — Wed, 14 Aug 2013 16:03:24 GMT

Ok, an update. I found a blog post regarding stuck workflows in SharePoint, which were related to a hotfix applied a few months back. Basically, items created with system accounts won't start automatically without changing a workflow property on the server. A stsadm command needs to be executed on the server as such:

stsadm –o setproperty –pn declarativeworkflowautostartonemailenabled –pv yes.

While this solved the issue of my workflow getting stuck in the Started state, I still have an issue with new items not starting at all. Anybody have data on this issue? Please help, I'm stuck and need to get this solution into production.

Thanks.

Workflow stuck in Starting state

TomRenfro — Tue, 13 Aug 2013 20:41:23 GMT

Hi, I've developed a reusable workflow in SharePoint Designer 2010 with the intent of using it with a specific InfoPath 2010 form content type. When I bind the workflow to different libraries for new items or changed items, it starts successfully except one library. Every new iteration of a form for this solution submits to an approval library. In this library only, the same workflow gets stuck in the Starting state. I can change the workflow settings to manually start it and it runs just fine. It gets stuck when new items hit the library or if they are changed.

Any wisdom or ideas?