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

Question

Question

Forms 10.2.0.834

asked on March 13, 2017

I have installed Forms 10.2.0.834 as I had 502 errors with Forms.

I now need to change all of my Forms Configuration, Workflow Configuration and connections to Forms through Retrieve Business Process Variables to fully qualified domain names with uses SSL on.

Has anyone else had this issue?

 

1 0

Replies

replied on March 13, 2017

You got a 502 error when open the Forms site? Can you check from the Forms server event log->Windows Logs->Application to see what is the detail error and post here?

0 0
replied on March 14, 2017

I received help through Laserfiche Chat to resolve the issue. Please refer to Case 185482.

Basically my customer's Forms and Workflows were working fine with 10.2 that I installed in January.  It did not require fully qualified naming (FQDN) and was using 'domain\server' in Forms and Workflow configuration.

I had to upgrade to 10.2.0789 for another issue.  It was still working OK but at some point I received a 502 error.  I am still not sure why.

Having read the release notes for 10.2.0834 I decided to upgrade it to this latest version using the patch.

The 502 error did not go away.  I had to change my Forms and Workflow Web Service Configurations to use FQDN and set SSL On.  I also had to change all of my Workflow connections and Retrieve Business Process connections.

All is now working OK with these settings.

0 0
replied on April 3, 2017

Hi Peter,

 

Can you elaborate on the solution for what you did? I am experiencing the same issue and am trying to fix this, but I am not sure what to change when you said the following:

 

"I had to change my Forms and Workflow Web Service Configurations to use FQDN and set SSL On.  I also had to change all of my Workflow connections and Retrieve Business Process connections."

 

Can you tell me what sections you changed?

0 0
replied on April 3, 2017

@████████opened a support case for this matter. It was unrelated to SSL settings. The form was using a custom submit button that wasn't passing the required parameters. That issue is mentioned here.

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

Sign in to reply to this post.