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

Question

Question

Workflow Server - The remote server returned an error 500

asked on November 19, 2015

Client is having issues adding a Laserfiche Forms Web service. The issue that they are encountering is that when configuring (Adding Web Service) Laserfiche Forms Web service in Workflow, they encounter an error message:

The Remote server returned an error: (500) Internal Server error

 

The URL being used is https://LFFORMS01.<company>.com/Forms/

This site is only accessible internally at this point. There are separate servers for Forms & Workflow. Client is able to access  the forms site [url above] using IE/Chrome on the Workflow server.

 

The Forms server doesn't have a binding for port 80. I have also confirmed that the Workflow Server is configured in Forms settings as this is a pre-requisite.

 

Any ideas?

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on November 20, 2015 Show version history

Hi, 

You can try this first: 

  1. go to your Forms server (the machine has Forms installed on)
  2. open a bowers and go to this url https://localhost/Forms/Api/help 
  3. see if it returns a page like this:

if it fails to show this page, here's the thing you need to do:

1. go to the Forms installed directory (by default it should be C:\Program Files\Laserfiche\Laserfiche Forms)

2. go to ..\Forms\Api and open web.config

    

3. edit this file:

  • 3.1  in section <service name="Laserfiche.Forms.Api.LfFormService">,  make sure  the line with 
bindingConfiguration="streamedBindingSecure"

is in unblocked, and block/delete the line with 

bindingConfiguration="streamedBinding"

e.g.

  • 3.2  in section <bindings> <webHttpBinding>, make sure the line with 
name="streamedBindingSecure"

is unblocked and block/remove line with 

name="streamedBinding"

e.g. 

 

PS:

1. basically you want to make sure in this web.config file that all the "secured" bindings (a.k.a. your https binding in IIS) are activated while all "no-secured" bindings (a.k.a. your http binding in IIS) are inactivated, if you want your Forms site to be accessed through "https" only.

2. Make sure there's no duplicated lines (two or more lines that're exactly the same) in this file - if there's any, remove it and leave only one of them there.

 

after you make these changes, please restart routing service and IIS on your Forms server, and recheck this page https://localhost/Forms/Api/help - it should work and solve the 500 error in your Workflow

3 0
replied on November 23, 2015

Thanks Lifei. Your instructions resolved the issue.

0 0

Replies

replied on April 20, 2016

The above instructions posted by Lifei Yang works , particularly in upgrades. One minor note, in addition to  steps 3.1 and 3.2.

Under section <bindings> <webHttpBinding> locate section "security mode="None" and change the value to "Transport" . 

1 0
replied on November 19, 2015

Is the Forms server configured to use this Workflow server?

0 0
replied on November 19, 2015

Yes, the forms server is configured to use Workflow

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

Sign in to reply to this post.