cancel
Showing results for 
Search instead for 
Did you mean: 

exceeded the query meter length

Pamela_Carolina
Champ in-the-making
Champ in-the-making

User is getting "Error processing request" error when using document reterieval. When I checked the Diagnostics Console, it says user "has exceeded the query meter length". Please advise what the error means and the fix for the issue.

       <col name="Datasource">SG-OB</col>
      <col name="IpAddress">::1</col>
      <col name="MachineName">::1</col>
      <col name="Result">0x80004005</col>
      <col name="Message">User 'CEA' with session ID '95254' has exceeded the query meter length.</col>
      <col name="Module">Hyland.Common.Core</col>
      <col name="Class">Guard</col>
      <col name="Method">ThrowOptionalInvalidOperationException</col>
      <col name="SourceFile"></col>
      <col name="SourceLine">0</col>
      <col name="Severity">Error</col>

1 ACCEPTED ANSWER

Not applicable

Hi Pamela,

Thank you for posting your question to the OnBase Community. This type of message indicates that the request made by the user hit the internal metering check used to prevent abuse of Client licenses. This can happen when using the API and exceeding the maximum queries per hour or, like I believe is happening in this instance, if the Document Retrieval request runs two queries and fails to clean up the results element for one of them.

This type of behavior was addressed in SCR#122564 and is fixed in OnBase 11.0+. If this issue is occurring in a build that is newer than 11.0, please reach out to your first line of support for additional assistance.

 

Thank you,

Doug Stoots

Tech Support Associate Analyst

Hyland, creator of OnBase®

View answer in original post

1 REPLY 1

Not applicable

Hi Pamela,

Thank you for posting your question to the OnBase Community. This type of message indicates that the request made by the user hit the internal metering check used to prevent abuse of Client licenses. This can happen when using the API and exceeding the maximum queries per hour or, like I believe is happening in this instance, if the Document Retrieval request runs two queries and fails to clean up the results element for one of them.

This type of behavior was addressed in SCR#122564 and is fixed in OnBase 11.0+. If this issue is occurring in a build that is newer than 11.0, please reach out to your first line of support for additional assistance.

 

Thank you,

Doug Stoots

Tech Support Associate Analyst

Hyland, creator of OnBase®

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.