Hi everyone,
We're trying to upgrade Laserfiche Workflow 11 from 11.0.2102.264 to 11.0.2306.898 in our prod environment.
The application upgrade itself has no issues, but the problem lies when we try to upgrade the Workflow server via Workflow Configuration Manager. We are essentially keeping all the existing settings:
- using a domain service account with local admin privilege to the server to run the Workflow service
- using the default port 8085
- database details were already populated (db resides on separate server)
Upon trying to finish the configuration, it'll attempt to restart the Workflow service as but would indicate the configuration was unsuccessful, and that connection attempt to net.tcp ://localhost:8085/ManagementService timed out. We tried rebooting the server as well but get this same result each time, so we are unable to complete the Workflow server upgrade.
We tried uninstalling Workflow 11 altogether then installing the target version (11.0.2306.898) directly and would still get the same result, i.e. net.tcp connection error, but if we close Workflow Configuration Manager and reopen it, it would show a green checkmark indicating the upgrade was complete. Yet, if we click Configure Workflow Server again and go through all the screens, it'll still give the same net.tcp connection error. The end result was Workflow components (e.g. Workflow Designer) would sometimes work but other times just timeout.
We ultimately reverted back to the working version, 11.0.2102.264 and are wondering what the problem could be before attempting the upgrade again. We followed the exact same steps to upgrade Workflow in our test environment and didn't run into this problem.
Any insight/suggestions would be appreciated!
Question
Question
Connection issue when upgrading Laserfiche Workflow 11
Replies
We've seen that issue on larger databases. Usually dismissing the error, manually starting the service from Windows Services and relaunching the configuration wizard will clear it up. If the Workflow Server is displayed as "configured" when you reopen the wizard, you're good to go.
Thank you Miruna, that makes sense. Our Workflow database in prod is 120+GB while the one in test is only about 20GB.
The only concern is it seems like even when the Workflow Server shows "configured" in the wizard, we're still seeing connection timeouts sometimes, e.g. scheduled workflows not running as expected or Workflow Designer timing out when trying to connect.
We'll test the upgrade again. Any other suggestions, aside from trying to reduce the Workflow database size?
I would make sure you have a database maintenance plan in SQL that rebuilds indexes and statistics. And that SQL has plenty of CPU and memory.
You could also run SQL's Tuning Advisor and see if it finds anything to recommend.
Anything further might need a support case because there could be different things based on which tables in the database are large.