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

Question

Question

Forms doesn't save to repository

asked on June 26, 2014

 In this process there are multiple steps each with a different forms to be completed by the participants. At the end of the process there is a master form which contains sections from all other forms (variables really helped in this) which is to be saved to a folder in the repository.

 

We tested this process severally and it worked perfectly. However, when deployed there are few instances which the master form is saved but recent instances don't save the master form. The save to repository task just remains running in all cases the folders are created but forms aren't saved. This issue isn't with just one process there are similar multiple processes having the same issue. 

 

The user specified in the setup has full access rights to the destination folder also the credentials are up-to-date. I can't understand why this is happening

 

I need help please. 

0 0

Replies

replied on June 26, 2014

Segun, when you look at the instance that isn't saving to the repository, does it say the current step is the save to repository step? If so, you may need to apply the latest Forms hotfix that can be found here. You will need to alter the HtmltoPdfTimeout value that it talks about.

2 0
replied on June 27, 2014

Thank you Blake. 

 

Yes, the status of the save to repository step just gets stuck on running. I have applied the hotfix but the existent process instances are still the same but haven't tried initiating any new instance. Does this hotfix exclude existent instances ?  

1 0
replied on June 27, 2014

It does. Did you make the change to the HTMLtoPdfTimeout value? You may need to increase it. After you make that change you will need to restart the server or the Forms process in Services. Once that has happened, I think you can go to the affected instances and tell it to retry when you are looking at the Results.

0 0
replied on June 27, 2014

I have altered the HTMLtoPdfTimeout value and the step doesn't get suspended but remains active. 

0 0
replied on June 9, 2015

I also tried adjusting this value, and restarted the Server and Forms Routing services, but I wasn't able to attempt any of the "stuck" Forms submissions again.

Has there been any discoveries recently on getting the "play" button back on the Save to Repository step after following the above steps?

0 0
replied on June 27, 2014

I'm having a similar issue on 9.1.0 FORMS, sometimes it stores and other times it does not.   Am I going to have to update to 9.1.1 and then do the hot fix?   I'm a little confused why it is a pdf setting that is interfering, - is that the default setting for storing?  The ones I have gotten to store  are showing tif format - or am I missing something obvious here?

0 0
replied on June 27, 2014

Yes, the hotfix applies to 9.1.1 of Forms. It's not necessarily a PDF setting despite the name. It serves other functions.

0 0
replied on July 1, 2014

Besides security rights for your connection profile, field data can also cause this issue to occur. Even when the connection profile account has full rights to the folders and fields in the repository, if you're configuring fields with your Save to Repository task you'll want to double check your field values! Leaving a required field blank or placing incorrectly formatted data into a formatted field with your Save to Repository service task can prevent the task from completing.

 

To see more details about why your task isn't completing, look at the event log of the Laserfiche Forms server. From there you should see any error messages that are being thrown when the service attempts to save your forms into the repository.

0 0
replied on July 1, 2014

Thank you Kelsey. 

 

I have double-checked to ensure all fields are accurate. Also, the Save to Repository task doesn't suspend, time-out it status just remains running. There weren't any errors reported on the LF forms server event log. 

 

Upon applying the hotfix suggested no new instances have been initiated so there is a possibility this issue might not happen again. 

 

 

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

Sign in to reply to this post.