none
Report works in Studio; fails to run when deployed

    Question

  • Our SSRS developers claim their reports work fine when run on their desktops, but not when deployed to the SSRS server. They blame the SS2008 R2 database server for some reason.  They say the reports which fail tend to be the larger reports with the most columns / rows returned by their queries.  I do not have any access to the SSRS server and I would like to spend my time doing something other than defending the database.

    What should the SSRS developers do?  What can I do to help?

    Thanks,

    Michael

    Thursday, August 14, 2014 1:39 PM

Answers

  • I would recommend looking at the ExecutionLog views.  There is a pretty good article on how to determine where the slowness is coming from by looking at these views...

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

    If it is truly failing and producing an error, they all get logged to the SSRS logs on the server.  That should also be a source to look at.  You will have to work with whomever runs the SSRS instance to look at the log files on the server and to access the views on the databases.

    • Marked as answer by Mysetdancer Thursday, August 14, 2014 2:53 PM
    Thursday, August 14, 2014 2:16 PM

All replies

  • I would recommend looking at the ExecutionLog views.  There is a pretty good article on how to determine where the slowness is coming from by looking at these views...

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

    If it is truly failing and producing an error, they all get logged to the SSRS logs on the server.  That should also be a source to look at.  You will have to work with whomever runs the SSRS instance to look at the log files on the server and to access the views on the databases.

    • Marked as answer by Mysetdancer Thursday, August 14, 2014 2:53 PM
    Thursday, August 14, 2014 2:16 PM
  • Can you give more information on the issue? Whats the error they're getting when trying to access the report from report server?

    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

    Thursday, August 14, 2014 2:20 PM
  • It appears that some report implementations/options/choices on SSRS 2008 R2 have bugs, and those bugs have to be coded-around, which is what our SSRS developer did.  He simply created the report a different way.  As DBA I am happy that the database was not a part of the issue.

    I appreciate the input received.

    Michael

     
    Thursday, August 14, 2014 2:56 PM