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

Question

Question

Retrieve Form Fields returns "(404) Not found error

asked on October 30, 2014

I am building a workflow where I am trying to retrieve the field values on a form.  Below is the configuration I'm using to access the form from the workflow.  The form is on a web server in the DMZ and workflow is on an internal server.

When I click the Test URL link I get "The remote server returned an error: (404) Not Found".  On that same server I copied and pasted the URL into a web browser and it brought up the Forms start page.

Any suggestions about what might be wrong?

Thanks

Sandy

Answer

SELECTED ANSWER
replied on October 30, 2014

Also please check the "Use SSL connection" on Forms Server tab in Forms configuration site is checked since you are using https to access Forms.

Replies

replied on July 14, 2016

I am experiencing the same issue on versions 10 of Workflow and Forms.  I couldn't get past the 404 error.  I tried restarting all the services and recreating the Web Service connection and  nothing worked.  I finally went onto the Forms Server configuration and changed it from HTTPS to HTTP and then back to HTTPS and it suddenly started working.   After I got it working on my development environment I tried it on my live environment which was broken too.  I verified that the following fixed it:

  • Go to https://server.domain.com/FormsConfig...Forms Server
  • Under Primary Forms Server URL uncheck "Use SSL connection" then click Save
  • recheck "Use SSL connection" then click Save

 

Although this process probably just triggered some sort of IIS reset and the SSL settings had nothing to do with it.  I'm concerned that this will intermittently happen and break some workflows in the future so I thought I'd attach my notes to this thread in case someone is still looking into a fix.

replied on October 31, 2016

THANK YOU! This solved my issue that also occurred after the upgrade.

replied on March 1, 2017

So crazy. I got this error and did the uncheck SSL and save and then recheck and save and it totally fixed it. Thanks.  

replied on May 19, 2017

This resolved my issue as well. I will say that this occurred on a fresh install of 10.2 on a new server not on an upgrade. Xiuhong Xiang any reason this is still happening a few releases later?

replied on October 30, 2014

I am having the exact same issue and would be very interested if you find a solution.

Thanks.

replied on October 30, 2014

Is your Forms server configured to work with this Workflow server? (on the Forms Configuration page at the bottom of the Repository tab)

replied on October 30, 2014

Here is the kb that Miruna is referring to:
https://support.laserfiche.com/KB/1013142

replied on October 30, 2014

I confirmed:

1. Workflow Web Service is installed and configured

2. There is a Web Service for Laserfiche forms in the Workflow Admin Console (I did notice when I test the link I get the (404) not found error.

3. I put in the workflow server IP address on the Forms Configuration Repository page.

 

Does this mean there's a communication problem between the 2 servers?

Thanks

Sandy

replied on October 30, 2014

Can you double-check the Forms Configuration page and make sure the "use SSL" checkbox is not checked in the Workflow section (or that it matches what you set for the WF web service if you are using SSL for it).

SELECTED ANSWER
replied on October 30, 2014

Also please check the "Use SSL connection" on Forms Server tab in Forms configuration site is checked since you are using https to access Forms.

replied on October 31, 2014

Here are all my settings and I still have the issue

Workflow Admin Console/Web Services

LF Forms configuration LF server (use ssl did not work)

Forms Configuration for the Workflow Server

Forms Configuration - Forms Server

 

replied on October 31, 2014

I have no idea what happened but I just opened the workflow again and now it works!  Not sure why it didn't right after I made the change....

 

Thanks for your help!

You are not allowed to follow up in this post.