Question

Workflow Connect Error After Server Migration

Workflow

Updated April 11, 2014

asked on March 27, 2014

Hey,

I just moved my Laserfiche 9 installation from one server to another. I have a single server environment that is running Avente (Laserfiche Server, Workflow and Web Access) all on one box. After installing everything and moving the databases over then updating all the connection strings I'm recieving an error message in Workflow when it is trying to run a Route to Folder process.

The error is "Could not connect to the Laserfiche Server."

Now, I have going into the Workflow Manager and updated (I also created a new) connection string to the server. When I go to this step in workflow, and ensured that it is using the correct connection, I did a test which passed but when the process actually runs on the server it fails.

Does anyone have any ideas on this. I should also add that there are number of other steps in this workflow, this is the last one and the only step that I'm having issues with. I have verified that my Workflow user does have security to the folder where the file is both coming from and going to.

Thanks.

Answer

APPROVED ANSWER

replied on April 11, 2014

This issue was related to routing documents to a dynamic folder path that used multiple tokens. The error occurred when the tokens didn't have any data, thus resulting in an invalid path. A check is needed to confirm the tokens have valid data before routing.

Replies

replied on March 27, 2014

The connection profile in the Designer are for building workflows. They're not updated on the server until you publish the workflow definitions. You will have to open each published workflow, update them and republish them.

Another way to handle this issue would be to DNS alias the new server to the old one so your domain controller would automatically redirect attempts to connect to the old server on to the new one. This would be the easiest solution.

If you're running Workflow 9.1 or higher, you can also define redirects on the WF Server side. See the help file for more information.

replied on March 27, 2014

I have republished the workflow in question a few times so I think that should have updated the string. But to be safe, I have created the server redirect as well. But I'm still not able to get this workflow to connect correctly and move this file.

replied on March 27, 2014

Could you open a support case so we can take a closer look?

You are not allowed to follow up in this post.