Question

ClientAutomation- ERROR: The current request could not be performed because there are too many existing operations running. [9035]

SDK

Updated March 19, 2015

asked on April 30, 2014

Hi, I'm getting an error "

The current request could not be performed because there are too many existing operations running.[9035]"

When using the SDK's Laserfiche.ClientAutomation to perform searches. I see some answers/forum articles on this, talking about disposing of search objects, but they don't seem to be using ClientAutomation or ImageEnable. I'm not sure what I should be disposing of, or what to do in this case. Is there any way to dispose of what needs to be disposed without closing the Laserfiche Client windows that are opened when performing the search? Thank you.

The error occurs after attempting to launch approximately 10 searches in a row. Closing document viewer windows seems to free up room for more searches to be performed.

This is a portion of the code that executes the search:

        SearchOptions searchoptions = new SearchOptions();
        searchoptions.NewWindow = false;
        searchoptions.OpenIfOneResult = true;
        searchoptions.EagerlyRetrieveResults = false;
        searchoptions.Query = searchString;
        mainwindow.LaunchSearch(searchoptions);

0 0

Answer

SELECTED ANSWER

replied on April 30, 2014

The simultaneous search limit is an intentional limitation to prevent the LF server from being overloaded. Each open search has a result listing stored in the database scratch table, and each client window has to keep its search open.

To get around this, try logging in with a new instance of the client once you hit 10 open searches.

0 0

replied on March 19, 2015

I have a client who is experiencing this problem after calling searches several times throughout the day. They are using a custom app for search and scan, they are on LF 9.2 RIO, Windows 7 pro 32/64 bit mix. They use windows authentication. I have a couple of questions;

1. Programmatically, how would you determine that the limit is reached or close to being reached?

2. When you say, login with a new instance of the client, this client is using RIO 9.2, I have noticed that only four sessions are allowed. If you login with a new instance , don't you run the risk of having too many sessions for that login?

search and scanning error on cl.pdf (65.05 KB)

| Download

0 0

replied on March 19, 2015 • Show version history

It is difficult to know exactly how many operations you are using at any time. The limit enforced by the 9035 error doesn't correspond directly to the number of searches, instead it limits the number of simultaneous operations that a session can use. Each running server request, open entry listing, open search and running background operation counts against this limit. I suggest your application keeps track of how many open searches there are and limit it to 4 at a time.

0 0

Replies

replied on May 6, 2014

Thanks Robert, that seemed to do the trick!

0 0

You are not allowed to follow up in this post.

Question

Question

ClientAutomation- ERROR: The current request could not be performed because there are too many existing operations running. [9035]

Answer

Replies

Sign in to reply to this post.