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

Question

Question

Forms 10 not saving anything to the repository.

asked on April 19, 2016 Show version history

I am on the latest version of Forms 10, running a VAR kit demo on my computer. All LF components are on this same machine. I recently upgraded from Windows 7 to Windows 10 on this computer, and now none of my Forms will save to the repository. The form submission appears successful, but the Save to Repository task ends up as suspended in the instance reporting section. There are no messages in the event viewer (Application, System, LFForms, LFNotificationService), and there are no messages in the event log you can access by clicking the ellipses next to the instance from within Forms. The FormsConfig page Primary Forms Server URL is correct (http://machine/Forms)  and I am not using SSL. This was all working perfectly before the upgrade to Windows 10. One peculiar thing I noticed, is that the process DOES create any folders in the path to where the document should go. It does not create the actual document, however. I have tried both PDF and TIFF formats.

Is there anywhere I can check to get more information? This is tough to pinpoint without any errors to look at.

0 0

Answer

SELECTED ANSWER
replied on May 2, 2016

Confirmed that this was an Antivirus issue. Thanks for helping me find the component that was being blocked! Adding the appropriate exceptions for wkhtmltopdf.exe and wkthmltoimage.exe sovled the problem.

0 0

Replies

replied on April 19, 2016

Have you tried running a repair of Forms? Sounds like the html to PDF converter is having issues.

0 0
replied on April 20, 2016

If it creates the folder in LF but not the document I would look more towards Security in LF.  Make sure the account has sufficient rights to create a document where forms is trying to and same template if you're assigning one in forms, and make sure that you are setting the Volume, I've seen it be goofy if you leave it at Parent Default volume.

0 0
replied on April 20, 2016

Thanks for the suggestions, but I actually tried both of these already. My forms user is an Admin, with access to everything. I am able to create documents in the destination area when I login to the client directly as this user. I did explicitly set the volume to "DEFAULT" also. Typically when I've had problems with either of those things, it's been pretty clear from some kind of message in the Event Viewer. In this case I still see no errors.

 

I have also run a repair on the installation, and done a full uninstall/reinstall. I even removed and reinstalled Saxon and wkhtmltox components after reading other answers posts. No luck... still behaving the same way.

0 0
replied on April 20, 2016

Hmm...  Could it be windows security for whatever directory forms uses as a temp location for the file it generates?  Maybe elevate the account the FormsAppPool is using to a local admin and see if it works then?  Not a fix, but might rule out windows folder security since the windows upgrade is what caused it to break.  

0 0
replied on April 20, 2016

If it fail to save the generated pdf to repository, it will save it under Program Files\Laserfiche\Laserfiche Forms\Forms\TempFile, can you check whether there are pdf files saved in this folder when you run to the Save to repository step?

0 0
replied on April 21, 2016

OK, permissions should be fine. I made FormsAppPool a local admin, but it still behaves the same. The TempFile folder does contain a single PDF (it appears to be from the first instance for which I noticed the problem based on the Submission ID in the file name). The pdf does not contain the form image, it is a "Service Unavailable - Http 503 error" message.

Also, I tried upgrading to Forms 10.1 yesterday. This did not resolve the issue either.

0 0
replied on April 21, 2016

"Service Unavaliable-Http 503 error" indicate something wrong with IIS when get html page to generate pdf/tiff. Can you check whether it help if restart FormsAppPool from IIS Application Pool. Also can you check whether it works when you download submission from thank you page? The will use same method to generate pdf as Save to repository.

0 0
replied on April 22, 2016

This seems to be along the right track. I don't know what's wrong exactly, but the Download button does not work either. It spins a while and then shows an error page: " Laserfiche Forms has encountered a problem. Laserfiche Forms was unable to generate a PDF or TIFF. Contact your Laserfiche administrator for more information."

Any suggestions on what could be causing it? I see no problems with permissions for the application pool to access anything within the Forms directory. I even gave Everyone full rights to the Forms directory temporarily to test. Still no success.

0 0
replied on April 22, 2016

wkhtmltopdf.exe is giving a TimoutError when trying to load the page. I can see this clearly if I try to use the tool from the command line directly. I can't figure out what's wrong. I tried installing the newest version of wkhtmltox from online, but that didn't resolve the issue either. Oh well... back to google. At least I have an error message now.

0 0
replied on April 24, 2016

Have you tried this procedure: uninstall wkhtmltopdf->restart machine->install wkhtmltopdf ? Sometimes strange issues get resolved just by reboot the machine.

0 0
replied on April 26, 2016

No luck with that. Another person on our sales team who just upgraded to Win10 is having the same problem as me though. I'm actually starting to suspect it may be the new version of the Antivirus software on the Win10 machines... I'll follow up with my IT and post here if that resolves the issue. Looks like it's turning out that this is not a Laserfiche issue, but something else.

0 0
SELECTED ANSWER
replied on May 2, 2016

Confirmed that this was an Antivirus issue. Thanks for helping me find the component that was being blocked! Adding the appropriate exceptions for wkhtmltopdf.exe and wkthmltoimage.exe sovled the problem.

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

Sign in to reply to this post.