Timeout errors when trying to log-in and when trying to open constituents

When trying to log-in and when trying to open consituent records, users may receive Error:  The operation has timed out.  A user may also receive Error:  No database available.
To resolve this issue we changed the selections used in their Notifications from Dynamic to Static to help with performance.  We also advised to run reports with reasonable parameters.  Example:  Don't run the appeal performance report with no filters because it will attempt to pull information for all of the appeals in your database. 

Environment

 2.9.1001.82

Was this article helpful?