none
Last run date blank in Report Manager

    Question

  • Since migrating Reporting Services from SQL 2005 to SQL 2008, the Last Run date, visible on the Details view of reports in a folder under Report Manager, has been blank.  I would hope that this is supposed to be populated and equivalent to the "When Run" date visible in the 2005 version of Report Manager.  Does anyone know of any setting that needs to be configured in order for this to show, or if this has been reported as a bug?
    Thursday, January 06, 2011 8:14 PM

Answers

  • This issue was first fixed in the following cumulative updates of SQL Server.

    • Cumulative Update 1 for SQL Server 2014 SP1
    • Cumulative Update 6 for SQL Server 2014
    • Cumulative Update 3 for SQL Server 2012 SP2

    https://support.microsoft.com/en-us/kb/3003102

    • Proposed as answer by JJordheim Friday, June 26, 2015 3:02 PM
    • Marked as answer by Tim Peters Friday, June 26, 2015 3:15 PM
    Friday, June 26, 2015 3:02 PM

All replies

  • The "Last Run Date" of the report is stored in the Report Server database in the execution log table.  Are you purging data?  Otherwise this only saves for 60 days by default.  When pulling from this table you'll have to pull the "Max(lastrundate)" to get the date.
    Thursday, January 06, 2011 9:10 PM
  • I am not referring to a table or a date column which I would have to query on my own.  My question is in regard to the Report Manager web application, and, specifically, the Details View of a folder in Report Manager.  This view has a column with the heading "Last Run", which is followed by a column headed "Modified Date": there are actual dates and times under the latter column; however, the column underneath "Last Run" is empty.  I would expect Report Manager to populate this column by default, but, that does not seem to be the case. 

    Is there any way to attach an image of the browser application to this posting, so that I can better illustrate the issue?

     

     

    Friday, January 21, 2011 2:22 PM
  • Are you referring to the "When Run" column in the details view?
    Wednesday, January 26, 2011 6:22 PM
  • Hi Tim Peters,

    I am sorry for misunderstanding your requirement, after your detailed information. I get your meaning completely. It does exist one clumn called "Last run" on report manager, however this column is relevant to SubScription, if you create a subscription and set a schedule for a report. After the schedule time, you will see a value in the "Last run" column. If you want to view the Last execution time, you could achieve this requirement on report, there is a build-in datafield called Globals!ExecutionTime, you could add a textbox on the report then type in the expression =Globals!ExecutionTime. Then you could see the execution time when some body open the report.

    Thanks,
    Challen Fu


    Challen Fu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, January 27, 2011 2:53 AM
    Moderator
  • Did any one solw this issue ?

     

    I have the same problem no last run date on report menager :(

     

     

    Deniz

    Friday, June 17, 2011 8:49 AM
  • When one is viewing the Subscriptions Page for a report, there is. indeed. a column labeled "Last Run", and, for those reports for which we've defined subscriptions, that column on that page is populated.

    However, when one is viewing the Detail view of reports in a folder (i.e. the Contents Page), there is a column there that is also labeled "Last Run"; however, one would expect that column to contain a value relative to the context in which the page operates; that is, a Last Run, or Last Execution, date for that report.  This column contains no value (neither a last subscription execution date, or a last execution date), despite the report having been executed regularly on a schedule. 

    I'm not clear on how to use a built-in field called Globals!ExecutionTime to correct what appears to be, to me anyway, a bug in the Report Manager application.

    Friday, June 17, 2011 3:35 PM
  • Deniz,

    This issue has not been solved, based on my readings of the posts to date.  Sorry.  If you find an answer, please post it here.

    Friday, June 17, 2011 3:36 PM
  • Has there been any progress/corrections/workarounds on this? I am in the same boat and my users want to know why it doesn't work. I have not been able to find anything anywhere.
    Wednesday, September 28, 2011 4:51 PM
  • This is a known issue with the new Report Manager layout in 2008 R2 and is being looked at for a future release. You can monitor the progress on this issue at the MS Connect site where the issue has been submitted. You can also vote on the issue to show that it is an important fix for you.

    https://connect.microsoft.com/SQLServer/feedback/details/684537/last-run-date-missing-in-report-manager-detailed-view


    Josh Gerszewski, MSFT
    Thursday, January 19, 2012 9:24 PM
  • Anyone anywhere got any latest update around this bug ?? Or is it still pending resolution ? I am also struggling with this issue as the business users would ideally like to see this field populated.

    Can someone please update this thread accordingly.

    Thanks in advance !!

    Thursday, August 01, 2013 10:41 AM
  • Another year passed, we still have this issue with no workaround....?


    Mahesh


    Monday, November 17, 2014 8:26 PM
  • Yup and another year again has passed without a fix and/or workaround... Microsoft COME ON...
    Thursday, June 11, 2015 2:00 PM
  • Reviewing the Microsoft Connect page for this issue, i would appear that the issue will not be addressed until SQL Server 2016 is released.

    ------------------------------------------------------------------

    Posted by Microsoft on 9/11/2014 at 12:32 PM
    Hello,

    Thank you for your feedback, this issue is fixed in the next major release of SQL Server Reporting Services

    Michael Griscom
    SSRS Tiger Dev

    ---------------------------------------------------------------------

    SQL Server 2014 was released April 1, 2014, so the post cannot be referring to SSRS 2014.  It's possible they may address it in a Cumulative Update or Service Pack to 2014, and if you're lucky 2012.

    • Proposed as answer by JJordheim Friday, June 26, 2015 3:02 PM
    Friday, June 12, 2015 1:33 PM
  • This issue was first fixed in the following cumulative updates of SQL Server.

    • Cumulative Update 1 for SQL Server 2014 SP1
    • Cumulative Update 6 for SQL Server 2014
    • Cumulative Update 3 for SQL Server 2012 SP2

    https://support.microsoft.com/en-us/kb/3003102

    • Proposed as answer by JJordheim Friday, June 26, 2015 3:02 PM
    • Marked as answer by Tim Peters Friday, June 26, 2015 3:15 PM
    Friday, June 26, 2015 3:02 PM
  • I don't know when we'll be updating, either to SQL Server 2012 or 2014, but I guess this suffices as an answer to my posting.
    Friday, June 26, 2015 3:15 PM
  • This issue was first fixed in the following cumulative updates of SQL Server.

    • Cumulative Update 1 for SQL Server 2014 SP1
    • Cumulative Update 6 for SQL Server 2014
    • Cumulative Update 3 for SQL Server 2012 SP2

    https://support.microsoft.com/en-us/kb/3003102


    Will there not be a fix for report manager 2008?
    Sunday, July 12, 2015 3:03 AM
  • This issue was first fixed in the following cumulative updates of SQL Server.

    • Cumulative Update 1 for SQL Server 2014 SP1
    • Cumulative Update 6 for SQL Server 2014
    • Cumulative Update 3 for SQL Server 2012 SP2

    https://support.microsoft.com/en-us/kb/3003102


    Will there not be a fix for report manager 2008?

    Doubtful. Mainstream support for that version has ended.  Any update to address that would have been released in that time period.

    https://support.microsoft.com/en-us/lifecycle?c2=1044&wa=wsignin1.0

    Monday, July 13, 2015 12:59 PM
  • I am running SQL 2014 SP2 and this issue is still not fixed.  What's the deal, Microsoft?  This bug was first reported in January, 2011 and its STILL isn't resolved?  (first reported in this forum, anyway ... I suspect it had been reported long before 2011)  We have a division that I deliberately migrated from 2008 R2 to 2014 SP2 just to get this feature working, using a clean install then migration of the .rdl files, and I'm looking at it now hanging my head.  I advised them based on the misinformation provided by Microsoft in this thread, and now I have to go tell them it was wrong? 

    The reason for this request is abundantly clear ... business needs to know if reports are being run, or used at all.  They need to verify that people are looking at information that needs to be reviewed periodically.  Looking at the "Last Run" field in Report Manager would tell them at a glance what they need to know. 

    SQL Reporting Services has always been one of the weakest of Microsoft's products, at times even lamer than SharePoint.  Do I need to file a Premier Services case to get someone to prod you guys to fix this?  Right now that seems to be my only option. 

    It is very clear that this constitutes a "bug" (not a "feature") in Reporting Services.  This should be fixed, or the column removed from the Report Manager interface.

    Thursday, February 02, 2017 8:52 PM
  • AlaskanRick,

    Are you thinking that the last run is used to report the last time someone executed (i.e., last ran/run) the report? If so, that's not the intent of that column. That column will only populate a date and time if you configured execution snapshots on the report. In fact you have to be very specific in how your configure the report for it to populate. That is to say you need to select the drop down for a report, click "Manage", and go to "Processing Options". I've attached a screenshot below with settings that resulted in me seeing that column have data in it.

    

    The connect article and the KB article referenced in this forum post are very clear that they relate to this feature.

    I do have good news for you though if you were looking for what reports were executed and when. There is a view in the database, ExecutionLog3, that exposes this data. I've provided a link below with details. You can create a system report against this and expose it in SSRS. There are settings that govern how long these records are kept too. For more questions this topic probably deserves a new forum post as this one has been closed.

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

    Friday, February 10, 2017 3:31 PM