Slow Workflow Publishing

asked on June 24, 2019

I have a server where it takes an hour to publish a workflow. I've had this issue since 10.2. I recently upgraded to 10.4 with no change. I have been working with LFC Support for 2 months now and have had no progress. While publishing, the server resources on both the workflow and database servers are minimal. I have "Enable the 'Validate Design' option for new workflows" unchecked. I've tried creating new workflows with one "Rename Entry" activity only, or updating existing workflows - still 1 hour. I've tried publishing from multiple PCs, and even from the server - same across the board. I uninstalled Workflow, deleted all the folders from the install directory, and reinstalled, Guess how long it takes now? Yep, an hour.

So my question is ... where else can I look to troubleshoot what's going on during this hour? I like to nap now while it's publishing, but the problem is, if I have 8 workflows to work on, I end up sleeping all day.

0 0

replied on June 24, 2019 • Show version history

Hi Rich,

Few more things to try:-

Install WF on a different server, but use the same SQL DB. See if the issue changes.
Install SQL Express directly on the WF server box and connect WF there and test. See if the issue changes.
Check that the account the WF server service is running as, is a local admin on the WF server and is DB_OWNER of the WF DB on the SQL box and has full access to c:\programdata\Laserfiche on the WF server.
If you have any anti-virus software installed, try uninstalling temporarily and see if that changes anything.
Check UAC (user access control) is disabled on the WF server
Upgrade to Workflow 10.4.x.

Hopefully one of those give you some clues

0 0

replied on August 7, 2019

Chris!

These were great clues, and I finally had time to try something. The first suggestion worked. I just pointed my test server to production database and it published in a few seconds. Knowing this, though - I'm still at a loss. At one time, I had tried shutting off all other LF services to see if any conflicted, but it was still the same. I'll try anti-virus next, I think - unless you have any other ideas.

Thank You! At least I'm getting somewhere now!

0 0

Question

Question

Replies

Sign in to reply to this post.