none
An unexpected error occured in report processing. (rsInternalError) RRS feed

  • Question

  •  

    Hi all,

    Our application that uses Reporting Services for it's Reports.

    On one customers build it appears to keep falling over.

    Restarting the server seems to resolve the problem for a short period

    and then it happens again.

    The exception that is returned to our application is

    "An unexpected error occured in report processing. (rsInternalError)"

     

    The customer has sent me the log files from

    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Reporting Services\Logs

     

    I've tied the time that the issue occurs to this section

    w3wp!chunks!1!04/11/2008-10:27:35:: e ERROR: GetChunkPointerAndLength: System.Data.SqlClient.SqlException: Database 'ReportServerTempDB' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.

    and

     

    w3wp!processing!1!04/11/2008-10:27:35:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing., ;
     Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.Data.SqlClient.SqlException: Database 'ReportServerTempDB' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.

     

    I doubt that the disk is full as our database is sitting on the same drive and presumably the whole system would have stopped working by now. 

     

    Any thoughts as to what the problem might be?
    We've not seen this before.

     

    Cheers,

    Chris

    Friday, April 11, 2008 4:21 PM

Answers

  • The ReportServerTempDB has a lot more activity then the ReportServer database.  Most report session information is contanined in this Database, so it is entirely possilbe that the database disk is full and only this DB is returning the error.  You should have your customer check this first before ruling it out.

     

    -Daniel

    Friday, April 11, 2008 5:01 PM

All replies

  • The ReportServerTempDB has a lot more activity then the ReportServer database.  Most report session information is contanined in this Database, so it is entirely possilbe that the database disk is full and only this DB is returning the error.  You should have your customer check this first before ruling it out.

     

    -Daniel

    Friday, April 11, 2008 5:01 PM
  •  

    You maybe onto something there Daniel,

     

    It turned out the disk our database was on and the disk reporting services was on

    were two different disks.

     

    The one with reporting services had got down below 1GB.

    We've free'd up 5GB's now, so we'll give that a spin and see if it resolves the issue.

     

    Cheers,

    Chris.

    Monday, April 14, 2008 1:34 PM