Post reply

Reporting Services Error

  • August 29, 2007 at 6:07 am

    #176156

    SQL Server 2000, building an RS Report in Visual Studio:

    I suddenly get the message:

    "an error occurred during report processing.

    Exception of type Microsoft.ReportingServices.ReportProcessing.af was thrown."

    I receive this message when I click View Report. I have successfully viewed this report many times during the course of building the report. Now I cannot stop it from displaying

    Google usually provides info, but not this time. I need help,

    Thanks

    MB

  • August 29, 2007 at 12:01 pm

    #730219

    Take a look here and see if comes out the same.

    http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=307988

  • August 30, 2007 at 6:07 am

    #730392

    Thanks, but I am not using the Code section of the report. I do have lost of code in expressions, however. I have created a calculated field am using the calculated field as part of another expression, which should work.

    MB

  • August 30, 2007 at 6:36 am

    #730401

    Have removed the last change you made to the report?  Have you tried using debug mode and running the report?

    Jack Corbett
    Consultant - Straight Path Solutions
    Check out these links on how to get faster and more accurate answers:
    Forum Etiquette: How to post data/code on a forum to get the best help
    Need an Answer? Actually, No ... You Need a Question

  • August 30, 2007 at 10:18 am

    #730496

    Can you just check by adding a new report and viewing it. A simple one. If you are getting the error or not.

    I had encountered a sort of this issue earlier. But not sure how i resolved it. I feel there might be some configuration changes. You might have to update the reporting services config file. Its just a thought. If i remember the solution i will reply to the post. :- Sameer

  • August 30, 2007 at 10:54 am

    #730512

    I just figured it out, as I was rebuilding the report. In this situation I received the peculiar message because: I had created a calculated Field to use in the report. At some point I added the calculation to the SQL code, with the same name. I then forgot that this "calculated" field was still in existence. RS must have been confused and produced the odd error message. By eliminating the calculation and defining it as a database field the error went away.

    Thanks to all for your suggestions.

    MB

     

Viewing 6 posts - 1 through 5 (of 5 total)

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