When any of our users chooses the print option from the thank you page, the printed document is not a copy of the applicable form, but rather a printed error message stating: Laserfiche Forms has encountered a problem. Sorry, but the page you requested cannot be found. Be sure that you entered the URL correctly, and then refresh your browser. This same error appears in the LFForms event log on the server with no other explanation of the root cause of the error. Has anyone experienced this before?
Question
Question
Replies
Clicking "print" button just calls browser print on current webpage and there is no request to Forms; do you mean the "download" option? If so, can you check if the Primary Forms Server URL is correct on FormsConfig -> Forms Server page?
If that's not the case, can you open a support case? We need more detailed environment information to check the issue.
Hello Rui,
I have had to instruct our users to use the download button as a workaround for the issue at hand, as download, open in Adobe Reader, and print works as expected. Clicking the embedded print button on the thank you page, does indeed make a call back to the LF server. It would not if the user was right clicking and choosing print or using the print function in their browser of choice.
Hi Glenn,
That was strange and we need more information to check the issue:
Which version of Forms are you using? Which kind of browser?
Can you use Chrome Developer Tools or Fiddler to get the request URL and the response?
And does the issue apply to all processes? Can you try create a new process with no fields and see if the issue happen?
Any resolution on this issue? I'm experiencing the same thing. Can't print any of my submitted forms.
Hi Andres,
Is there any error when you print in Forms? Same error as Glenn's?
Can you check if printing works in other applications?
Hello Andres / Rui,
I apologize for not updating you earlier on this issue. I migrated our repository, previously planned, to a RIO installation rather than Avante on a new server weekend before last and I am no longer experiencing the issue. I was experiencing the issue on both I.E. and Chrome. Unfortunately, I did not check the dev tools and record what the response was in the browser. I will also note that other browser based applications we use were able to print on the same systems without issue.