none
FEP 2010 - subreporting issue

Answers

  • The cause for the problem seems to be insufficient space in the “memory-to-leave” area of SQL Server. The size of this memory area is 256 Mbytes by default and can be increased with the startup parameter “-g” for SQL Server.

    Solved by increasing “memory-to-leave” to 384 Mbytes. Needed a MS support ticket to help out. 

    http://msdn.microsoft.com/en-us/library/ms190737.aspx

    • Marked as answer by rellingsen Thursday, August 04, 2011 8:43 AM
    Thursday, August 04, 2011 8:43 AM

All replies

  • Hi,

    Have you checked the SRSRP.log to be sure that you have the same error ? If so, yes the link is correct and you can follow it.


    Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/ | Time zone : GMT+1
    Monday, June 20, 2011 7:49 PM
  • The patch worked, reports are now ok. 

    @Bechir - do you have any experience with SQL 2008 SP2 for SCCM 2007? 
    Thinking of performance or other behaviour.  

    Wednesday, June 22, 2011 7:35 AM
  • @Bechir - do you have any experience with SQL 2008 SP2 for SCCM 2007? 
     


    It is supported and it works like a charme :)
    Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/ | Time zone : GMT+1
    Wednesday, June 22, 2011 7:57 AM
  • The issue returned yesterday, anyone who can recommend something?
    Thursday, July 14, 2011 6:25 AM
  • The log file for reporting services (C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles) gives me a lot of red
    webserver!ReportServer_0-2!2644!07/14/2011-09:48:11:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'dsMalwareDetectionsSummary'. ---> System.Data.SqlClient.SqlException: A severe error occurred on the current command.  The results, if any, should be discarded.
    A severe error occurred on the current command.  The results, if any, should be discarded.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)


    Thursday, July 14, 2011 8:21 AM
  • The cause for the problem seems to be insufficient space in the “memory-to-leave” area of SQL Server. The size of this memory area is 256 Mbytes by default and can be increased with the startup parameter “-g” for SQL Server.

    Solved by increasing “memory-to-leave” to 384 Mbytes. Needed a MS support ticket to help out. 

    http://msdn.microsoft.com/en-us/library/ms190737.aspx

    • Marked as answer by rellingsen Thursday, August 04, 2011 8:43 AM
    Thursday, August 04, 2011 8:43 AM