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

Question

Question

Unable to use Invoke Business Process activity in Workflow 10.2

Workflow Version 10
Updated July 2, 2017
asked on March 9, 2017 • Show version history

This activity always returns a 404 since upgrading to workflow 10.2. No known changes have been made to the networking or configuration, all workflows are unable to call forms processes now.

If you put the URL into a web browser running from the workflow server, no 404 error is returned.

Here is a report of the actual communication between the Forms server (.34) and Workflow server (.8) while testing the connection from the Invoke Business Process from Workflow. This is the same test that produces the error message above stating that 404 was returned. I don't see any 404 message here, if a 404 was returned it would be in the packets.

2 0

Answer

SELECTED ANSWER
replied on March 13, 2017

Hey Chad,

I forgot that I had a similar issue in the past for which I had posted a solution.  I haven't had a chance to see if this will fix it for me this time.  I hope so as this is a rather urgent issue.

http://answers.laserfiche.com/questions/66302/Retrieve-Form-Fields-returns-404-Not-found-error#101747

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

 

1 0

Replies

replied on March 13, 2017

I am having the same issue since upgrading to Workflow 10.2 over the weekend.

1 0
replied on July 2, 2017 • Show version history

This bug has been fixed in 10.2.1 Update 1, you can go to https://support.laserfiche.com/kb/1013870/list-of-changes-for-laserfiche-forms-10-2-1-update-1- to check details

1 0
replied on March 13, 2017

I can only get it to work if I put the forms server on the same operating system so that there is no network traffic. I am lost here and I can't think of any workaround. There is no way to run a forms process on a schedule that does a lookup to determine if the process needs to be run and collect the data.

0 0
View 11 previous replies
SELECTED ANSWER
replied on March 13, 2017

Hey Chad,

I forgot that I had a similar issue in the past for which I had posted a solution.  I haven't had a chance to see if this will fix it for me this time.  I hope so as this is a rather urgent issue.

http://answers.laserfiche.com/questions/66302/Retrieve-Form-Fields-returns-404-Not-found-error#101747

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

 

1 0
replied on March 14, 2017

O.M.G. That is an easter egg status find you made there! It worked immediately! Thank you, I was down to only one more week to get a fix in or going back to having the users enter everything manually. Saved me and the client big time!

0 0
replied on March 14, 2017

Any chance we can get someone from Laserfiche to investigate this issue more thoroughly?  It can be a pretty serious issue if you have important processes relying on the integration between Forms and Workflow.  I think that since several people have mentioned this as a problem and very difficult to troubleshoot it warrants some attention.  Thanks!

1 0
replied on May 17, 2017

This issue is still present after upgrading to 10.2.1.

The workaround of checking and unchecking the "Use SSL connection" box still works, but the underlying cause should be investigated and fixed if possible. Thanks!

0 0
replied on May 17, 2017

This is a known issue when upgrade directly from previous version to latest version when use https. We will fix the issue for upgrade to keep the settings for the Api web.config.

0 0
replied on May 18, 2017

Thanks for the reply Xiang.

As a note, my system was not configured to use HTTPS before or after the upgrade. It was a simple local installation that did not use SSL.

I was able to correct the issue by checking the "use SSL connection" box, saving, and then unchecking that box (the opposite procedure as what Rob described above).

0 0
replied on May 18, 2017

It's the same bug though (reference # 28574). Flipping the SSL settings one way or the other, then back to the desired state, just reconfigures the API so Workflow can connect again.

0 0
replied on May 18, 2017

Excellent, thanks for confirming that there aren't two separate bugs. :)

0 0
replied on May 19, 2017

Thank you for posting your resolve @████████. This just saved us a support call. @████████ we look forward to the fix. Will it be available in a hotfix or do we just need to wait for version 11?

 

 

0 0
replied on May 21, 2017

@████████, did you register a database created before instead of create new database after fresh install? And is that database has "use SSL connection" checked under Primary Forms Server URL?

0 0
replied on May 22, 2017

@████████, can you give us more details for the version you upgraded from and the version you upgraded to? We checked upgrade from Forms 10.2.0 to Forms 10.2.1 directly, can't reproduce the issue for Workflow integration doesn't work after upgrade when use http.

0 0
replied on May 22, 2017

I upgraded from 10.1 to 10.2.1. I don't have the precise version of 10.1 handy for you, unfortunately.

0 0
replied on May 23, 2017

Hi Kelsey, we figured out in which case the issue can be reproduced. If you are using http with Forms 10.2.1 and never click save button on Forms Server tab of Configuration site, then workflow won't be able to connect with Forms. The workaround now is to change some setttings on Forms Server tab of Configuration to enable save button(for example, check "use SSL connection" first, then uncheck it)and click save or edit web.config under C:\Program Files\Laserfiche\Laserfiche Forms\Forms\Api to change the security mode to "None".

<webHttpBinding>
        <binding name="streamedBinding" transferMode="StreamedRequest" maxReceivedMessageSize="2147483648" maxBufferSize="1048576" contentTypeMapper="Laserfiche.Forms.Api.Host.RawContentTypeMapper, E-Forms">
          <security mode="None" />
        </binding>
      </webHttpBinding>

 

2 0
replied on May 29, 2017

Thanks Xiang, I have a brand new install of 10.2.1 in which Workflow would not connect to Forms as above.  I changed web.config as you have suggested and now all is OK.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...