I'll be able to run 5-10 reports and then start getting that error. I reset IIS and it starts working again. Then the error comes back. Can't find a pattern.

Event Viewer:

There was an unexpected error attempting to generate a report. Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Sage.SalesLogix.Reporting.Server):    at Sage.SalesLogix.Reporting.Server.WebReportingServerHttpHandler.ProcessRequest(HttpContext context)

The Crystal Reports Server is deliberately throttled down for the licensing agreements\price point that SLX was able to acquire the licenses. I've run into all sort of issues with running lots of reports, big reports, multiple users running reports, all clog up the works. I don't know what version of SLX you are on, or even of Crystal. I know that running big reports at night on the LAN and distributing them to user's takes the load off of the Web Reporting Server....

We also found out the hard way that running very simple reports on the main level, and driving Sub-Reports off of the simple report, was more efficient and performed better on the web.

Take a look at the Event Viewer logs for the Web Host and Web Reporting Servers.....we spent a bunch of time adjusting permissions, shares, patching\repairing errors and warnings, and they all helped Web Reporting Server performance in 7.5.4.