Question

Save to Laserfiche Maximum Connections

Forms

Updated April 28, 2016

asked on January 27, 2015

When using the Save to Laserfiche task, is there a maximum number of connections that Forms can make to a Laserfiche repository using a Laserfiche account that has a full license? I have an issue where so many forms are being simultaneously submitted that it is causing the following error in event viewer:

My guess is that it is too many attempted connections to the repository using the same account but has anyone else run into this issue?

0 0

Answer

APPROVED ANSWER SELECTED ANSWER

replied on February 2, 2015 • Show version history

Beau, sorry there was an bug where you could get the locked error in STR forcing you to restart the process if two Laserfiche repository submissions occurred simultaneously . This issue has been replicated, fixed and in the process of being tested for a release in Forms 9.2.1.

1 0

Replies

replied on January 28, 2015

The same user is used in the Save to Laserfiche task of 80+ forms for this user so there is the possibility that multiple forms can be submitted at the same time. The issue in this case is that they have a form that all employees (2000+) had to submit on the same day. These employees all waited until the last minute and thus hundreds were submitted at the end of the day. The issue appears to be when a single process has many submitted at the same time and thus there are no open connections for the task to use. It should queue them up but it appears to time out and give up until they manually tell it to try again.

0 0

replied on January 29, 2015 • Show version history

Forms does have queue system for processing save to repository service task. We have tested that submitting the same form following a save to repository service task with 30 users at the same time, all the submitted form can be saved to repository.

There are some possible situations for the "Entry Lock" error:

1. All the submitted form or all the attachment for the form are save to same place with same document name or use variable such as "{/dataset/_submission_time}" in the document name. If multiple users submit the form at the exact same time, it may cause different document with same name save to same place, this will get "Entry lock" error.

The solution for this issue is to use another variable such as "{/dataset/_submission_id}" in document name/attachment name to guarantee the unique.

2. The document is put under version control in the repository, the save to repository task will add new version to it. When run the save to repository task, some one else or other application such as Workflow is editing it.

Can you please confirm which case you may belong to?

0 0

replied on January 28, 2015

Beau brings up a good point. I would imagine that most of us try to use the same user for all of our Save to Laserfiche tasks. It would be very useful, in order to avoid this situation, if the save to repository task could use a Forms user that doesn't have that restriction. I would imagine this to be similar to the Workflow user that shows up in the Admin Console.

0 0

replied on January 28, 2015

Beau, is this happening when the form is first saved to Laserfiche? Or is it a form that has been saved and it is now updated?

0 0

replied on January 28, 2015

It is the last activity in the Process where it is saving the Form into Laserfiche.

0 0

View 3 previous replies

replied on January 29, 2015

What are the document name and path set to?

0 0

replied on February 2, 2015

Document name = {/dataset/_form_name} {/dataset/_initiated_time}

Path = \zzWork Queue\HR\zzIncoming Forms

0 0

replied on February 2, 2015

That does not guarantee unique document names if multiple users submit at the same time. Is there a field you can add to make the names unique?

0 0

replied on February 2, 2015

That is the default name that the Save to Laserfiche task uses so we assumed it would work correctly. Shouldn't the documents still be able to be named appropriately with the trailing (1), (2), ...? I've updated it to include the instance ID in the name but have to wait for the next time their are a bunch of forms submitted simultaneously to test. Do you believe the name was the issue?

0 0

APPROVED ANSWER SELECTED ANSWER

replied on February 2, 2015 • Show version history

1 0

replied on February 3, 2015

Awesome to hear Robert. Thanks for the help with that.

0 0

replied on April 28, 2016

Hi,

This issue is fixed in Forms 9.2.1 hotfix.

Thank you.

0 0

You are not allowed to follow up in this post.

Question

Question

Save to Laserfiche Maximum Connections

Answer

Replies

Sign in to reply to this post.