Reports failing during execution through CMC

Question

Currently we have the following configuration in our development and QA environments
Crystal Reports Server XI R2
Windows 2003 Server
Data used to generate reports is kept in Oracle 10G running on Red Hat
Both servers are virtual environment - they run on VMWare
We have a particular report that basically bails out 1/2 way through execution for a particular schema. The report uses a SQL command - the SQL query itself can take sometime when executed through SQL Developer - depending of the size of the data set in the schema can take between 5 to 10 min to execute.  When running the report itt fails with the following message:
A Request was canceled. The necessary security privileges could not be verified. This indicates a problem with the security server.
In the windows event viewer we can see the following entries
Security policies were propagated with warning. 0x4b8. An extended error has occurred
A failure occurred while the Page Server was processing report .... (Event 42452)
A Page Server subprocess in the processing server was forced to terminate (Event 42445)
Your request cannot be processed due to low system resources. Please contact your system administrator (Event ID 42443)
A Page Server subprocess was forced to terminate (Event 42451)
There is nothing unusual in the logging folder.
We already look through the knowledge base and the only article that sort of resembles the situation is article 1407795. We confirmed that the report has no printers associated to it.
The report work with a smaller data set in a different schema.
We are at a lost - we have changed the JVM parameter to allocate more memory to Tomcat but it does not seem to address the issue.
Any insight would be appreciated

Answer 1

When CRS is installed, it defaults to run under the Local System account on the server where it's installed.  This account is local to the server and does not have access to anything on the network.  It sounds like this may be part of your problem. 
In the CCM, stop each of the "servers", including TomCat, go to its properties and change the login in at the bottom of the first tab to an account that has network access, save and restart the server.  Best Practice is to have a special "services account" on the network where the password doesn't expire to use for this purpose.
If that's not the issue, I would verify the login being used for the report and also that there's nothing on the database end that would be causing this.  There is no "Security Server" in CRS, so this is a problem that is occuring outside of CRS but is affecting how CRS runs.
-Dell