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?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.