saving workflow in pdm admin tool results in hang that eventually effects all users!

I am running SP3 and do not have a problem saving my workflows.  They are from half that workflows size to more than twice as large.

It does sound like you are stuck inside some kind of loop but not sure how that would happen.  If you had some conflicting conditions that would only show up when something transitioned through it.

Have you tried to break it down and only save it after adding one state or one transition just to see where it fails?  If you created a simple two state transition with nothing special in the transitions does it still fail?

Hi Barry,

Recently experienced this behavior with a client vault. The only difference is there were lots of other behaviors that accompanied the workflow freezing like transitions not completing and displaying errors, datacard edits couldn't be saved,

Checked the logs in the admin tool and found the error messages:

1. Could not access item in the database
2. The transaction log for database 'tempdb' is full

Their server ran out of disk space and so lots of operations were being affected.

If this is your problem, open the PDM installation guide to around p.181 and see "Managing the SQL Transaction log size" section for the procedure for increasing that size.

Hope this helps,

Tim CEPA

http://www.equivaq.com

Barry,

It can also do this when saving the workflow with states in it that have notifications going to users who no longer exist.

Hope this helps,

Tim CEPA

http://www.equivaq.com

Do you have any Notifications that might have had Deleted Users still listed in them? I haven't specifically seen WFs hang from this, but I know you can't export a WF with Deleted Users still in the Notifications. The problem is, you have to go through each Transition one by one to find them.

Also, I would check your Local Log and Archive server logs. Look for "Could not send data to <ip address> ...Windows Socket Errors" entries. These are sometimes OK to see unless there are lots of them. Look at the data/time stamp and see if it correlates to your hitting the save button. This would indicate communication errors which are never fun to troubleshoot.

Any updates on this issue?  Did you get it resolved?

We are facing similar issues in 2016 SP5.  Our System is quite complex and I am starting to pace all the proposals.  Might save quite some time if I had a direction of where to look first...

Thanks

Matthias

I am experiencing this behavior too.  Workflows are taking forever to save, and I dread saving them during work hours because it leads to tasks failing and transitions hanging for other users. We have a number of complex workflows but we are using the software as we need to.  We have a database that has much more than the minimum requirements in all areas but it still seems to be hanging up.  We do not delete users, we move them to an obsolete group and we only use groups for permissions. I wish there was an easier way to troubleshoot what the issue is.  I will contact my VAR and report back on anything that they can provide for information on this.