Error: The underlying connection was closed - when running revenue reports

When running any revenue report, users may receive the following error:

The underlying connection was closed: An unexpected error occurred on a receive. 
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host.

We are currently evaluating this issue and will update this article when we have more information.

There may be a correlation between this error message and blocking on the SQL server.  If you host your own CRM database, contact support and provide SQL Snaps and a Fiddler trace from the time the report was ran. Instructions on capturing a Fiddler trace can be found in Blackbaud Know How article "Troubleshooting Tools: SQL Snaps, FiddlerCap, and More."  If Blackbaud host your CRM database, please contact support and provide a Fiddler trace taken while running the report, along with answers to the the following questions.

1. What time was the report run?
2. Can this error message be reproduced consistently?
3. Were there any scheduled queues or business processes running during the time you received the error?
4. Which Revenue report are you running?

Environment

 2.9.1001.128

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.