You are viewing limited content. For full access, please sign in.

Question

Question

Error configuring Workflow Server in Forms Config

asked on March 7, 2019

Hi all,

We recently upgraded LF from 9.2 to 10.3.1 in our test environment.  This included upgrading both Forms (residing on the web server) and Workflow (residing on the app server).

Within Forms Config and in the Laserfiche section, I can specify the Workflow Server.  When I click on Test Connection, I'm getting a "Moved Permanently" error.  If I then check the box to use SSL, the error changes to "The remote server returned an error: (401) Unauthorized".  I can't seem to find what these errors indicate and would appreciate any insight.

Strangely enough, if I point the Workflow Server to our production environment (version 9.2) instead, Test Connection returns a "The connection has been verified" message.

Thanks in advance!

LF Forms-Workflow.png
0 0

Replies

replied on March 7, 2019

It will be difficult to troubleshoot this issue without looking through your specific set up. Please open a support case so we can see what exactly is going on. 

1 1
replied on March 7, 2019

Thanks Jared.

Somehow your response triggered me to check the IIS settings for our Workflow web site and allowed me to discover that its authentication setting was incorrect.

In our production environment which is working, anonymous authentication is Enabled while Windows Authentication is Disabled for the Workflow web site.  However, in our test environment the two are reversed.

After changing the settings in the test environment, the Test Connection button within Forms Configuration now returns a "The connection has been verified" message.

I'm not sure how that got changed and whether or not it's related to the recent upgrade to version 10, but thank you.

3 0
replied two days ago Show version history

It seems to me that only Win Auth being enabled is a standard default configuration. For me, changing the auth like this did not resolve the problem.

Update: In this case it was because someone setup a URL re-write to replace http with https on the workflow site and their Forms config was using no encryption.

If we try to use encryption we also got the 401 error so it seems that is still a problem, but removing the re-write fixed the connection.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.