ERROR: Unable to load the master report

Posted by: travis.beltrametti on 4 December 2019, 4:38 am EST

    • Post Options:
    • Link

    Posted 4 December 2019, 4:38 am EST - Updated 30 September 2022, 5:25 pm EST

    On AR 11.3.13058.0 I have the following problem. (The problem seems to be occurring just recently).

    Reproduce steps:

    1. Open a report using a master-report in the Report Designer
    2. Click “Preview”
    3. Change a Parameter value and click “View report” (Maybe twice)
    4. The Error “MasterReportNotFoundException” is thrown with Message "Unable to load the master report for the specified content report.

    When I open exactly the same report on the SP1 version of AR11 it seems to work fine. Also the problem is not related to the report itself I’ve create a blank report/master which also produces the same error. (See attachment)

  • Posted 4 December 2019, 4:39 am EST

  • Posted 4 December 2019, 4:53 am EST

    Hello,

    Could you please check with the last hotfix version of AR11 Sp3 as I am not able to reproducible the issue with the same. You can download it from the following link;

    http://cdn.grapecity.com/ActiveReports/ar11/hotfixes/ActiveReports-v11.3.13822.0.msi

    Thanks,

    Mohit

  • Posted 4 December 2019, 6:56 am EST - Updated 30 September 2022, 5:26 pm EST

    Unfortunately it does not resolve the issue. Might it be due to Windows Updates? Please try on a Win 10 Machine with all current updates. I believe I haven’t experienced this 1 Month ago with the exact same installation.

  • Posted 4 December 2019, 6:58 am EST

    Thats the full Exception:

    Exception details:
    GrapeCity.ActiveReports.PageReportModel.MasterReportNotFoundException: Unable to load the master report for the specified content report.
       bei #qAA.#G5e.#hFf(String masterReportUri)
       bei #qAA.#G5e.#fFf(Report report)
       bei #qAA.#G5e.#WEf(TextReader reader, Action`1 setter)
       bei GrapeCity.ActiveReports.PageReport.Load(TextReader reportDefinitionReader)
       bei GrapeCity.ActiveReports.PageReport.#vtf(PageReport source)
       bei GrapeCity.ActiveReports.Document.PageDocument.#2Kf(PageReport pageReport)
       bei GrapeCity.ActiveReports.Document.PageDocument..ctor(PageReport pageReport, ReportRenderingContext renderingContext)
       bei GrapeCity.ActiveReports.PageReport.get_Document()
       bei GrapeCity.ActiveReports.Rendering.Subreports.SubreportService.<.ctor>b__3(PageReport x)
       bei GrapeCity.ActiveReports.Extensions.FunctionalExtensions.IfNotNull[T,TR](T value, Func`2 selector)
       bei GrapeCity.ActiveReports.Rendering.Subreports.SubreportService..ctor(ResourceLocator resourceLocator, IConfigurationProvider configProvider, Report report, PageReport parent)
       bei GrapeCity.ActiveReports.ReportsCore.DataBuilder.ReportBuilder.Context..ctor(PageReport report, ReportStore reportStore, Context parent)
       bei GrapeCity.ActiveReports.ReportDataProcessor.#CfJ(PageReport report, IExpressionContext evaluationContext, ReportStore reportStore, #ja0 makeDocument, Func`3 getCommandBuilder, InteractiveSortState sortState)
       bei GrapeCity.ActiveReports.ReportsCore.Rendering.ReportProcessor.#Tol(Boolean skipValidation)
       bei GrapeCity.ActiveReports.ReportsCore.Rendering.ReportProcessor.#fn(Boolean forceDataRefresh, Boolean forceParameterDataRefresh, Boolean skipValidation)
       bei GrapeCity.ActiveReports.Document.PageDocument.#0Kf(Boolean forceDataRefresh, Boolean forceParameterDataRefresh, Boolean skipValidation)
       bei GrapeCity.ActiveReports.Document.PageDocument.Render(IRenderingExtension renderingExtension, StreamProvider streams, NameValueCollection settings, Boolean forceDataRefresh, Boolean forceParameterDataRefresh)
       bei GrapeCity.ActiveReports.Viewer.Win.Rdlx.RdlReport.<>c__DisplayClassf.#7yz()
       bei GrapeCity.ActiveReports.Viewer.Win.AsyncLoader.<>c__DisplayClass7.#cAz(Object param0, DoWorkEventArgs param1)
       bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    
  • Posted 5 December 2019, 1:25 am EST - Updated 30 September 2022, 5:26 pm EST

    Hello Travis,

    I have checked with the latest version of Windows 10(refer to the attached image) and still not able to replicate the issue at my end. Could you please check after reinstalling the AR or check with the latest version of AR. You can download the same from the following link:

    http://cdn.grapecity.com/ActiveReports/AR13/hotfixes/ActiveReports-v13.2.18668.0.msi

    If the issue also replicates with the latest version of AR then please share the following thing:

    1: Full OS Version

    2: Culture of OS

    3: FW installed on the system.

    Thanks,

    Mohit

  • Posted 5 December 2019, 6:39 am EST - Updated 30 September 2022, 5:26 pm EST

    Hello!

    I’ve the same problem. Latest Windows 10 Version, latest Visual Studio 2019 Version and installed the hotfix for AR11 SP3 you provided.

    For the error to show up, you need to click on “Gallery Mode” in the AR Designer, see attached screen shot:

    A wider description of the problem is, that when you have a child report, the master report does get displayed, as if everything would work, but the parameters you set in the child report somehow get ignored, and not passed to the query in the Data Source.

    Only when you click on “Gallery Mode” does an error pointing to the master report show up.

    Appreciate your help!

    Obed

  • Posted 5 December 2019, 7:11 am EST

    Hello,

    Thanks for the information. I am able to replicate the issue now. However, AR11 is out of development mode so there is no fixing will be done in AR11. I have checked with AR13 SP2 and no issue is replicate at my end, You need to upgrade to our latest version to have this fix.

    Sorry for the inconvenience caused.

    Thanks,

    Mohit

  • Posted 5 December 2019, 10:13 am EST

    Ok thats bad news. :frowning:

    I deinstalled AR 11 SP3 and installed v11.2.10750.0 which doesn’t seem to have this bug.

    Thanks anyways

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels