You need to sign in to do that
Don't have an account?
dl-knowledge
INVALID_QUERY_LOCATOR
I have developed an adapter for a third-party indexing engine that uses the sforce soap service as one of its data sources. When I test the adapter outside of the indexing engine environement, as a standalone java app, I get all of my data. However, when the indexing engine executes the adapter, I receive only the first set of data (1000 records). When the source requests the second recordset, I receive an "INVALID_QUERY_LOCATOR" fault. Anybody have any idea why? Originally, the binding timeout was set to 0. I have modified it to 300000, with no success. Also, the adapter continues to function after that, querying the salesforce soap service for several other data types successfully. I query for Accounts, which is where it fails, then Campaigns, Contacts, Events and Opportunities. I modified the order of querying, and it failed when accessing the Contacts. There are 43500 Account records. There are 116,000+ Contact records. Any help would be appreciated.
Depending on which exact soap stack & version your using it might be called _QueryOptions or QueryOptions.
The final batch size will depend on a number of factors include api version # used, QueryOptions header and the type and number of fields you selected.
You can call always call support and open a case.
However, in addition, I reviewed the logged output to determine how long it had been between the initial query and the queryMore call. It was less than 1 minute. :( So, that must not be my problem. Any other ideas? I'll let you know if the batchSize has any affect. And I'll call to open a case as well.
Thank you for your suggestions, though.
So if you make five queries, you have 5 cursors. On your sixth call, your first query is invalidated, because you already had 5 open.
Just like only you can prevent forrest fires, only you can determine your number of active cursors.