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

Question

Question

Laserfiche Forms - Issue after upgrading to 12 spring update. LFF329-TimeoutWkHTMLToPDF]

Forms
Updated May 7
asked on May 7 • Show version history

This error is popping up across forms, for email and save to repo task. I tried resetting services, increase the timeout but nothing has worked. The event viewer mentions the notification service is not running but I have reset it multiple times. 

 

Timeout expired for exiting call to Puppeteer.

[LFF329-TimeoutWkHTMLToPDF] Details:

URL: Error: TimeoutWkHTMLToPDF

Date: 5/7/2025 12:23:04 PM (Pacific Standard Time)

HTTP Status Code: 408 Business Process ID: 1061 Instance ID: 20185 Business Process Name: CAF/CSA - New Other: aux: Timeout of 180000 ms exceeded Stack Trace: Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException Message: Timeout expired for exiting call to Puppeteer. [LFF329-TimeoutWkHTMLToPDF] at Laserfiche.Forms.CommonUtils.HtmlToPdfConverter.<BaseConvertAsync>d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Laserfiche.Forms.CommonUtils.MultiFormHtmlToPdfConverter.<ConvertAsyncWithRetry>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Laserfiche.Forms.CommonUtils.MultiFormHtmlToPdfConverter.<ConvertAsyncWithRetry>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Laserfiche.Forms.CommonUtils.MultiFormHtmlToPdfConverter.<ConvertAsyncWithRetry>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Laserfiche.Forms.CommonUtils.MultiFormHtmlToPdfConverter.<ConvertAsyncWithRetry>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Laserfiche.Forms.CommonUtils.MultiFormHtmlToPdfConverter.<ConvertAsyncWithRetry>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Laserfiche.Forms.CommonUtils.MultiFormHtmlToPdfConverter.ConvertAsync(PuppeteerOptions puppeteerOptions, Int32 retryCount) at Laserfiche.Forms.CommonUtils.MultiFormHtmlToPdfConverter.Convert() at FormsModel.RoutingModels.Services.SaveFormToLaserficheStrategy.SaveMainFormToLaserfiche(Session session, XmlDocument datasetXml, STLConfigurationObj conf, SaveToLaserficheParameters saveToLaserficheParameters)

0 0

Replies

replied on May 7

Was able to get this fixed, still waiting to hear back from our departments using this. But it looks like Chromium was not allowing the PDF's to be created. To fix the issue, I went into the form's configuration page, and update the PuppeteerExecutablePath * to point to Chrome via C:\Program Files\Google\Chrome\Application\chrome.exe

I used these resources to help resolve the issue

 

https://support.laserfiche.com/kb/1014357/using-either-google-chrome-or-microsoft-edge-for-pdf-generation-with-forms-11-update-2-or-later

 

https://answers.laserfiche.com/questions/198166/Google-Chrome-instead-of-Chromium-for-Forms-11-PDF-generation

1 0
replied on May 7

We had a similiar support case before and the issue was caused by antivirus software blocking Chromium executing.

If Chrome worked for you it was likely your antivirus software allowed it.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...