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

Question

Question

Lookup rule not working on public form

asked on October 3, 2019

I have a public form that I cannot get a lookup rule to work properly, however, when I access the same form through the internal url, it works fine.  The lookup rule is pulling the information from a view that resides on the LF Forms database.  This view is actually querying a different database through a linked server connection.  Has anyone set up a lookup rule for a public form and gotten it to work?

0 0

Answer

SELECTED ANSWER
replied on October 6, 2019

Hey Guys - Thanks for the suggestions.  It turns out that I had the Data Source configured with a AD account and Forms configured with a SQL account.  As soon as I changed the Data Source credentials to SQL everything was fine and the lookup acted normally.

0 0

Replies

replied on October 4, 2019

Do any data sources work externally? It could be an issue with the public facing server communicating with the internal SQL server (i.e., not having ports open for internal communication).

How is your data source configured? If your public form is hosted in the DMZ and your data source is configured with a domain account instead of a SQL user, then that could be the issue.

0 0
replied on October 4, 2019

Considering you are using a linked server, try opening SSMS on the external Forms server and running a basic SELECT query on the same data. We have seen instances in the past with linked servers where we were able to create views off of the data without any errors, but then when trying to actually run a query against it we would receive errors.

0 0
replied on April 22, 2020

I am having the same issue but I am not using a linked server.  The database is on the same SQL server as Laserfiche.  I am using a sql user account to create the data source.  The public forms service is in the DMZ and the SQL server is inside the firewall.  Is is possible to use the data source on a public form without modifying the firewall?

0 0
replied on April 22, 2020

Jim, the DMZ server must be able to communicate with the SQL server that the database you want to communicate with is on. When setting up the datasource, the DMZ server must also be able to resolve the name or ip address you use when configuring it in Forms.

1 0
replied on April 22, 2020

Thank you.  Having my DBA check into this.

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

Sign in to reply to this post.