TOPIC: Out of Memory error running report

Out of Memory error running report 25 May 2012 16:10 #997

  • markrich
  • markrich's Avatar
  • Offline
I have identically set up six reports to run on a schedule. They have been set to run smallest to largest. The first five seem to run fine, but the last, and largest, report fails with an Out Of Memory" error. This same report has run fine manually in Crystal Reports for months. It also runs fine in Logicity Desktop.

Why won't it run completely via the Solution Builder schedule?
The administrator has disabled public write access.

Out of Memory error running report 13 Aug 2013 13:51 #1434

  • hitesh.shah@ccscollect.co
  • hitesh.shah@ccscollect.co's Avatar
  • Offline
I too have the same problem. This used to work fine before the SQL server was rebooted. Since then it won't run completely via the Solution Builder schedule.
Has anyone found a solution?
The administrator has disabled public write access.

Out of Memory error running report 13 Aug 2013 14:04 #1435

  • bellis
  • bellis's Avatar
  • Offline
Are you running them all from the same solution? Could you try scheduling them as separate RRDs as a test?

Thanks!
Brian
The administrator has disabled public write access.

Out of Memory error running report 13 Aug 2013 14:07 #1436

  • hitesh.shah@ccscollect.co
  • hitesh.shah@ccscollect.co's Avatar
  • Offline
It is just one report scheduled with one RRD.
The administrator has disabled public write access.

Out of Memory error running report 13 Aug 2013 14:09 #1437

  • bellis
  • bellis's Avatar
  • Offline
How big of a dataset are we talking about? Enough that we could be hitting 32-bit memory limits?
The administrator has disabled public write access.

Out of Memory error running report 13 Aug 2013 14:25 #1438

  • hitesh.shah@ccscollect.co
  • hitesh.shah@ccscollect.co's Avatar
  • Offline
The dataset is big. We have actually installed Logicity Pro on a Windows 2008 R2 Server 64-bit and of course SQL is SQL2008 R2 on Windows 2008 R2 Server, with 24GB Memory.
This was working fine before we decided the SQL server was rebooted, so do not understand why it is doing this.
Last Edit: 13 Aug 2013 14:27 by hitesh.shah@ccscollect.co. Reason: additional comment
The administrator has disabled public write access.

Out of Memory error running report 13 Aug 2013 14:32 #1439

  • bellis
  • bellis's Avatar
  • Offline
Gotcha... Logicity is 32-bit but if it ran before that shouldn't be the issue.

I wonder if SQL Server is killing the connection (it views it as a slow running query) which explains why it ran before but does not run now.
The administrator has disabled public write access.

Out of Memory error running report 13 Aug 2013 14:35 #1440

  • hitesh.shah@ccscollect.co
  • hitesh.shah@ccscollect.co's Avatar
  • Offline
It is a slow running report. When we run the crystal report, it does complete without any error. It just takes its time.
The administrator has disabled public write access.