Question

No account configured to archive the form submission to laserfiche

Forms Administration

Updated July 2, 2015

asked on June 9, 2015

I have a form where I've been running into issues saving a number of form submissions into the repository. Although I have been able to modify the date to the correct format (yyyy-MM-dd, logging onto the Forms server using the account tied to the Laserfiche Forms Routing Service), the submissions are still not saving to the repository, and I'm now getting the following error message in our Error Log:

Message: No account is configured to archive the form submission to Laserfiche
Stack trace: at Laserfiche.Forms.CommonUtils.LFSaveToLfService.GetLFConnectionParameter()
at Laserfiche.Forms.CommonUtils.LFSaveToLfService.GetPDFAndSaveToLF()

Looking at the following submission, this looked to be tied more to a blank form being submitted, but this seems to be tied more to a blank page/submission than my scenario, which is having a completed form still being unable to submit. Regardless, I installed the following patch to the Laserfiche Forms server last night, but this didn't fix any of our existing submissions that won't save to the repository.

So I have a few questions here:

1) Is there anything else we might need to do to get these forms submissions saving to the repository?

2) Previously when a submission was "stuck", and unable to save, we had the ability to go back in and try the submission again. Is there any way to "reset" this submission so we could retry saving a submission to the repository, as we had done before?

3) Is there a way we can have a higher log level than we do currently? In the RoutingEngineServiceHost.exe.config file, the LogLevel, under appSettings, is currently set to 1.

Thanks to anyone who can help at this stage in saving our form submissions to the repository!

Marty Gaffney - Network Technician

Town of Okotoks

0 0

Replies

replied on June 9, 2015

Hello Marty,

1) So does this only affect this one particular business process? or does it affect all Business processes that saves the form into the repository?

0 0

replied on June 9, 2015

It only appears to affect this one Business Process. The change in the default date and time format seemed to fix the other forms/Business Processes that were experiencing problems, however even though it *appeared* that these forms were submitting (for this single Business Process), these specific submissions are stuck on "Save to Repository", and aren't event reverting back to Suspended.

0 0

replied on June 15, 2015

UPDATE:

We had this issue happening on one of our forms, but it was resolved by completing the steps that were involved/required after the stalled Save to Repository step. In this case, with this form, although the Save to Repository step was still marked as In Progress, the workflow still proceeded to the next step, and once the last step was completed, the workflow was marked as Completed as well.

In the case of one of our forms, there are still a number of submissions marked Save to Repository that are "stuck" at this step, where the submissions haven't been saved to repository, and they can't be reversed to a point where the submission can happen again, and they also can't move to a point beyond this in the Process Modeler (where a subsequent step, when completed, completes the process, as was done above).

So we have been able to figure out why one form wasn't submitting (however the way it was done wasn't intuitive), but the other form, and submitted items outstanding, has still yet to be resolved at this point.

0 0

replied on July 2, 2015

We seem to be running into a similar issue. Some of our documents are not saving into the repository and all forms has to say in the log is this:

Message: No account is configured to archive the form submission to Laserfiche

This is the same error we got when SSL 3.0 was disabled so it appears to be default throw.

0 0

You are not allowed to follow up in this post.

Question

Question

No account configured to archive the form submission to laserfiche

Replies

Sign in to reply to this post.