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

Question

Question

Forms 11- Trying to edit Variables in an "In Progress" Forms instance throws [LFF706-UnableToTriggerRouting] error

asked on August 19, 2022

Hello,

Customer built out a form and they kicked it off.  It is sitting at "In Progress" at a Timer Catch Event using the following variable:

Customer is trying to edit the variable but when they hit save they are getting the below error message:

"An error occurred while running the process. Please make sure Laserfiche Forms is configured properly. Manually restart Laserfiche Forms Routing Service to ensure that all necessary changes take effect."

We have tried restarting the Forms Routing Service, but no luck.

Forms, LFDS, LF Server are all on the same VM. 

In further testing we get the same error if we try edit other variables and hit save.

There is nothing logged in the Forms->App->Admin or Operational Logs for this error.

Anyone else seen this error in the scenario I have provided? If so, would love some feedback on how you fixed it.

Thanks for the feedback,

Jeff Curtis

0 0

Replies

replied on August 22, 2022

Hi Jeff, 

The error message indicates that somehow the Forms IIS Server cannot connect to the Forms Routing Service. Are they also on same vm?

Could you confirm the configuration by checking endpoint for lfrouting in Forms/Web.config on Forms IIS Server?

0 0
replied on August 22, 2022

Hello Ziyan,

Thanks for the reply.

Yes IIS is on the same server as Forms.  

Forms App Pool is running as Local System

Forms Routing Service is running as Domain Service account which is in the Local Administrator group on the VM

Not sure what you need confirmation on in the web.config file for lfrouting but it looks correct, as this is an internal Forms install:

contract="FormsModel.SharedContracts.IRoutingLookupService" name="" />
      <endpoint address="net.tcp://localhost:8168/lfrouting" binding="netTcpBinding" bindingConfiguration="timeoutBinding" contract="Laserfiche.Forms.Routing.IRoutingEngineService" name="" />

Thanks,

Jeff

0 0
replied on August 23, 2022 Show version history

Correction for my previous post: Forms IIS Server will talk to routing service via lfinstance (not lfrouting) for editing variables. I assume it is also using default endpoint with address net.tcp://localhost:8172/lfinstance, right?

It is weird that Forms Server and routing service are on same machine, while there is no detailed error in event log.

 

Could you check whether the service has been successfully started on routing service restart? There should be message like 'Instance Processing WCF service started successfully' in Forms event log Operational channel around routing start time.

We've seen that port 8172 is taken by other process so that the wcf service cannot be successfully started and connected though routing service appears running.

0 0
replied on August 23, 2022

Hello Ziyan,

I just restarted the Forms Routing service and WCF started successfully:

As for your note about the Port Conflict, I initially did a search here on LF Answers and found the following post that talked about the Port Conflict, but I ran the netstat command, listed in the post and there are no conflicts

https://answers.laserfiche.com/questions/197901/How-We-Solved-LFF706UnableToTriggerRouting-and-LFF3004UnableToOpenServiceProxy-After-Upgrading-to-Forms-11

Thanks for the feedback,

Jeff Curtis

0 0
replied on August 23, 2022 Show version history

Hi Jeff, I am running out of idea. Maybe someone else has a clue.

 

Please open up support case if further help for troubleshooting is needed.

0 0
replied on February 3

Was there ever a solution found for this issue?

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

Sign in to reply to this post.