Report Errors when Scheduled

  • I'm running on SQL 2000 with SRS. Standard install (I think, it was all set up by IT)

    I have reports that run fine in the Report Manager but when they are run through a schedule (email) some of them (albeit most) "rsProcessingAborted" because of a report error.

    Looking at the logs it seems generally based around comparison failure because of datatypes, eg (from the logs):

    • Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: The processing of sort expression for the list 'List1' cannot be performed. The comparison failed. Please check the data type returned by sort expression.
    • Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: The processing of group expression for the table 'tblGroupTable' cannot be performed. The comparison failed. Please check the data type returned by group expression.

    Now, when I remove sorting/grouping the reports run through the schedule OK; but that is obviously NOT what I want the report to look like. But it proves that the sorting/grouping has something to do with the problem.

    I'm pretty sure that they are NOT the problem though, as the reports render in Report Manager fine with all the original sorting/grouping in place (ie no problems during development, just when we wanted them served to the employees Isn't that always the way it goes??). We've even had some reports which scheduled OK previously, but throw errors now.

     I'm at a loss!!

    • Could it be a time-out issue somewhere? If so: where?
    • Looking at the Execution Logs, the reports that fail have unusually long Process Times, with a Data Retrieval Time of 0. I guess that the process time is longer because of processing the error, but does the Data Retrieval time of 0 mean that no data was delivered to the report? How can that be?
    • IT tell me it can't be memory issues as it's sitting on a 2GB machine, but could there be something else with SQL set-up?
    • I googled the error and found a few pages where people said that puting SRS in its own application pool fixed their problem. When I passed this on to IT they said that would only help memory... Any ideas????

    Any suggestions greatfully appreciated (by myself and my hair)

     

     

  • What sort of expression do yuo have for the sort expression e.g. is it VB.net code doing something neat or just simply "sort this field ascending"?

    Steve.

  • most likely a time out issue


    Everything you can imagine is real.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply