Database Error: Resource Limit Reached While Processing Operation

Follow

Date: August 25, 2016
Revision: 2.1

Problem

In Enterprise Random Password Manager, when performing an operation in the management console or website, you may receive the following error: Database Error: Resource limit reached while processing operation. This message may appear on screen (website) and/or in the operation logs.

Cause

There are a few likely causes:

  1. Your database is server is overloaded because it is shared by this and other high level applications.
  2. Your database and/or its logs have reached the maximum DB/log size as defined in the DB properties in SQL.
  3. Your database is unable to comply with the request within the query timeout window and the query is timing out.
  4. Your database needs some tuning.

Resolution

Case 1:Move the ERPM database to a new DB server that is not so loaded or try to adjust the OLEDB timeout value by manipulating the settings in the console (Settings | Data Store Configuration | Basic Settings) and set the value. You then need to update the website with the new settings and restart the COM object. To update the website, click on Manage Web App in the console, right-click on the website instance and select “Replace instance options with default web application options”.

Case 2: Have your DBA increase the size of the logs or database or perform a full backup and have the DB logs truncated to reclaim space according to the database.

Case 3: Move the ERPM database to a new DB server that is not so loaded or try to adjust the OLEDB timeout value by manipulating the settings in the console (Settings | Data Store Configuration | Basic Settings) and set the value. You then need to update the website with the new settings and restart the COM object. To update the website, click on Manage Web App in the console, right-click on the website instance and select “Replace instance options with default web application options”.

Case 4: This is most often the cause. In the management console. Without involving a DBA to analyze your usage and make educated changes, ERPM can read the statistics and other related information from SQL Server directly. Go to Settings | Data Store Configuration and start with the “SQL Server Auto-index Tuning”. Starting from the top, add each item it recommends one at a time. The go to “SQL Server Index Defragmentation”. Defrag or rebuild anything listed, again going one index at a time. Finally, after the indexes are created and defragged, run the “SQL Server Generate Full Stats Full Scan” which is the last item on that menu. To perform these steps on the E/RPM database will require the server level permission for "View Server Status". If this permission is not granted, the DBA will need to perform these steps locally in the DB.

For the website specifically, if the web server configured to perform recursive group membership lookup this will also impact performance as all groups the user is a member of must be fully recursed so E/RPM can successfully evaluate all applicable permissions. Recursion can greatly impact both website login time and permissions evaluation as this cannot be done in the background.

Applies To

  • Enterprise Random Password Manager (ERPM)
  • Random Password Manager (RPM)
Was this article helpful?
0 out of 0 found this helpful

Comments

Powered by Zendesk