Has anyone else seen this error when sending an email with attachments from Laserfiche Forms?
System: Rio 10.2
Also have tested removing any script created. Also created a dummy form with just an email address and I still got the error.
Has anyone else seen this error when sending an email with attachments from Laserfiche Forms?
System: Rio 10.2
Also have tested removing any script created. Also created a dummy form with just an email address and I still got the error.
The reseller reached out to us and opened a support case. I'll update back when we reach a resolution.
I'd love to know if there's been any internal findings, or possibly a resolution to this issue. We're experiencing the same problem when attempting to save a Form to a repository (not an attachment) as either a TIFF or PDF.
The repository profile is valid and the correct parent folder is being created, but the actual form in never saved and we're forced to cancel the process at that point due to task being "suspended".
Any insight would be greatly appreciated.
NOTE: Laserfiche Forms 10.2 Update 1 (Rio)
Thank you!
This is happening on all previously working instances since installing Update 1.
I've included the detailed error message below:
Failed to generate a html perhaps caused by the inability to load an external script file. [LFF4117-FailedToGeneratePage] Details: URL: Error: FailedToGeneratePage Date: 5/11/2017 8:50:10 AM (Pacific Standard Time) HTTP Status Code: 404 Business Process ID: 16 Instance ID: 58 Business Process Name: Classified Employment Form - (dynamic routing v.2) Stack Trace: Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException Message: Failed to generate a html perhaps caused by the inability to load an external script file. [LFF4117-FailedToGeneratePage] at Laserfiche.Forms.CommonUtils.HtmlToPdfConverter.GeneratePrint(String& pdfFileLoc, String& tifFileLoc) at Laserfiche.Forms.Routing.SaveToLaserficheService.Execute(Int32 instanceId, IRoutingContext routingContext, RoutingInstanceStatus OriginalStatus)
There has not yet been a response to the case in a week but at last update, changing the primary Forms server URL from that of an internal Forms server to a public-facing server resolved the issue. The process which was examined in the case did have external script references, so it seems likely at this point that the issue was related to the internal Forms server not being able to resolve these references, which was exactly what the error message had said. However the process described which had no external references was never presented in the case, and it was never confirmed whether that also was resolved by the change made.
For issues such as this where form submissions fail to save to the repository, the two leading causes are an invalid primary Forms server URL or external scripts unable to be referenced. You could start by looking there, if not please feel free to reach out to your reseller for more in-depth troubleshooting.
James,
I suppose I'll have to contact my reseller as we do have a public facing 'primary Forms server URL' which is actually the host name of our dedicated web proxy. All other Forms functionality seem to be working correctly. Additionally, I've now stripped the form itself down to bare bones, making certain to remove any external scripts or files and we still receive the same results.
Unfortunately as you can see in my previous post, the error log never gives "Details" or "URL" information for me to further examine.
I appreciate your response though... Thanks!
Roberto, we also created a dummy form with just and email field and we got the error. It was solved by changing the some of the configurations with ssl connections.
This button was unchecked and my VAR made some slight changes in the configurations.
Unfortunately, I'm not the best to tell you what was the problem, but it had zero to do with our script, because the form process now works.
Chynna, thanks for the update. We've opened up a case with our VAR last week and we're awaiting their response. I too created a very simplified form and had the same errant results.
So it's definitely not an external script issue on our end either, as I've removed all external scripts, and the error itself never did reference any specific script.
I appreciate your insights though, and I think I'll look at our current configuration while I wait for support. If by chance you are able to gather any additional details from your VAR, I'd definitely be interested in learning more about what specifically resolved the issue for you.
Thanks again!
Ran into this issue after an upgrade. Looks like what Chynna ran into was our issue.
What resolved it for us was verifying the Primary Forms Server address and making sure SSL was checked. After the upgrade, it was left blank, so filling it in with //localhost/Forms and checking the SSL box made it work.
Cheers,
Carl
Failed to generate a html perhaps caused by the inability to load an external script file. [LFF4117-FailedToGeneratePage]
I've seen this error with a custom HTML field containing an <img> tag referencing an external url that would resolve to a 404 page. The Forms error was happening at the Save to Repository step.
Just had this issue and resolved it by making sure all the custom HTML was valid.
Some of the HTML text was not wrapped in any kind of tag, but wrapping all the text resolved the issue.
Is the attachment a PDF? If so, check you have adobe reader installed on the Forms and LF server.