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

Question

Question

Forms Portal in the DMZ after 10.3 update

Forms
Updated April 15, 2018
asked on January 25, 2018 • Show version history

I have recently upgraded to 10.3 including Forms and the Forms Portal in the DMZ.  The portal no longer works properly.  Forms can be submitted and they make it through to the repository, but then the Process suspends because it cannot send out the Email notification.  Looking at the logs it appears as though the email task is trying to happen out on the Forms server in the portal not the internal forms server.  When we submit the form inside the domain the process works as it should.  So for now we have to click retry on all of the suspended processes to get them to complete.

Thank you.

0 0

Answer

SELECTED ANSWER
replied on February 1, 2018

Part of this statement was missing:

<endpoint address="net.tcp://localhost:8268/lfpushnotification" binding="netTcpBinding" bindingConfiguration="timeoutBinding" contract="Laserfiche.PushNotificationService.SharedContracts.IPushNotificationService" name="" />

Everything inside the first set of quotes did not exist and neither did the firewall rule.  This must be a change in our environment from our previous version.

0 0

Replies

replied on January 26, 2018

Can you please double check the configure files in the DMZ to see whether it matches the white paper https://support.laserfiche.com/resources/3481/hosting-laserfiche-forms-10-in-a-perimeter-network-dmz ? There are some updates for the white paper. If you can still reproduce the issue after double check with the white paper, can you please open a support case with your VAR for more details?

1. Provide the process xml and screenshot at which step it is suspended;

2. Provide the error log;

3. Provide the web.config files for the internal Forms server and external Forms server.

1 0
replied on January 26, 2018

It appears as though our web.config file within the Program Files/Laserfiche/Laserfiche Forms/Config folder is incomplete.  We do not have the lfPushnotification, lfautotrigger and lfformexport defined in the statement.  Should we add these statements to this file?

0 0
SELECTED ANSWER
replied on February 1, 2018

Part of this statement was missing:

<endpoint address="net.tcp://localhost:8268/lfpushnotification" binding="netTcpBinding" bindingConfiguration="timeoutBinding" contract="Laserfiche.PushNotificationService.SharedContracts.IPushNotificationService" name="" />

Everything inside the first set of quotes did not exist and neither did the firewall rule.  This must be a change in our environment from our previous version.

0 0
replied on April 8, 2018

Just upgraded from 10.1 to 10.3. All the configuration files in the DMZ were just replaced and all the services in DMZ are back to start automatically. All configuration lost and needs to be re-done. Additional ports need to be opened or DMZ forms will not make in to the internal server. Until those ports are open I have to monitor the incoming submissions, which get suspended until I retry them from the inside. Suggestion: how about an upgrade documentation that lists all relevant configuration changes that should be addressed ahead of time and to be floated to all VARs so they know what to warn us about.

Thanks... :-(

0 0
replied on April 15, 2018

A week later additional ports are open and forms can now "complete" without intervention. :-)!!!!

Just make sure to restart the forms routing service on your internal forms server (not in the white paper).

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

Sign in to reply to this post.

Details
Related Posts
Loading ...