Report contains no data. at Microsoft.Office.RecordsManagement.Reporting.Report.Generate(Hashtable query) at Microsoft.Office.RecordsManagement.Reporting.ApplicationPages.GenerateReport.Generate(String strReportId) at Microsoft.Office.RecordsManagement.Reporting.ApplicationPages.GenerateReport.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint
Workaround
After lot of frustrations and trials and errors, I discovered that this report is only get generated if you have some entries in the hidden "Workflow history" list. The only way to put something int he history list from SharePoint designer is to have a "Log to History" list action item as shown below
The assembly responsible for generating these reports are mostly obfuscated. I have a support ticket open with Microsoft with no luck. So far can not figure out how this report is suppose to be generated and why this report is available for Visual studio generated workflow and NOT for SharePoint designer
If someone know the solution, please send me an email
1 comment:
Hi
I had exactly the same problem when I ran audit logs.
I have two site collections
1. https://topsite
2. https://topsite/sites/subsite
I activated the Reporting feature at the subsite level first and enabled all the auditing settings. All the auditing is now working at the subsite level. Great!
Then the reporting feature was activated at the topsite level and the following error appeared:
Report contains no data. at Microsoft.Office.RecordsManagement.Reporting.Report.Generate(Hashtable query)
at Microsoft.Office.RecordsManagement.Reporting.ApplicationPages.GenerateReport.Generate(String strReportId)
at Microsoft.Office.RecordsManagement.Reporting.ApplicationPages.GenerateReport.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
However the audit settings were not modified for the topsite.
Configuring the audit settings for the topsite fixed this issue for me.
Thanks,
Pieter Veenstra
Content and Code
www.contentandcode.com
Post a Comment