AR17 - Updating from AR11 - Bad response export content

Posted by: mgrove on 29 September 2023, 2:39 am EST

    • Post Options:
    • Link

    Posted 29 September 2023, 2:39 am EST - Updated 29 September 2023, 2:45 am EST

    I went through the update process for ActiveReports from AR version 11 to AR version 17 using the “Convert to ActiveReports 17”. I got some errors, I had to load some different references, etc.

    Now that I’m not getting any errors in Visual Studio 2022 just by loading, cleaning and rebuilding the project, I am getting an error upon trying to view the reports, as noted in the attachment screenshot.

    • This is a web form using aspx.
    • Using WebViewer, version 17.1.2.0
    • Using sectionreports at this time
    • Load the report into the page, putting it in rptMAIN

    if (rptMAIN != null) {
         WebViewer1.Report = rptMAIN;
         WebViewer1.ReportName = "thing";
         rptMAIN.ShowParameterUI = false;
         SetWebViewer1();
         WebViewer1.Visible = true;
    }
    


    Code for SetWebViewer1:

    protected void SetWebViewer1 () {
    	/* For the Acrobat viewer */
    	WebViewer1.ViewerType = GrapeCity.ActiveReports.Web.ViewerType.AcrobatReader;
    	WebViewer1.PdfExportOptions.DisplayMode = DisplayMode.None;
    	WebViewer1.PdfExportOptions.FitWindow = true;
    	WebViewer1.PdfExportOptions.ImageQuality = ImageQuality.Highest;
    	WebViewer1.PdfExportOptions.ExportBookmarks = true;
    	WebViewer1.PdfExportOptions.HideMenubar = false;
    	WebViewer1.PdfExportOptions.HideToolbar = false;
    	WebViewer1.PdfExportOptions.HideWindowUI = false;
    	WebViewer1.PdfExportOptions.CenterWindow = false;
    }

    Help?

    Michael

  • Posted 2 October 2023, 5:35 pm EST

    Hi Michael,

    The error ‘Bad response export content’ can be thrown due to various reasons, mainly due to missing references in a project.

    We will suggest you uninstall the ‘GrapeCity.ActiveReports.Export.Pdf’ package and then reinstall the same (v17.1.2).

    However, if this does not resolve your issue please try providing a simplified sample that emulates the issue. So we can narrow down the issue.

    Regards,

    Anand

  • Posted 12 October 2023, 1:56 am EST

    Sorry, I’ve been busy with a number of things and trying different things. :slight_smile:

    The uninstall and reinstall of GrapeCity.ActiveReports.Export.PDF (and all the other pieces that went with it) didn’t help fix the issue.

    I have created a simple web app to test and it doesn’t work there either.

    Here is a link to the 7-zip file:

    https://boycesystems-my.sharepoint.com/:u:/p/mgrove/ESHfcD2OXKtGjI-cGYEUQUkBwf6uBmrbbVvlmAb0xWS2IQ?e=iXZHiI

    Hopefully you can quickly see what stupid thing I did or didn’t do. :slight_smile:

    Thanks!

    Michael

  • Posted 12 October 2023, 4:42 pm EST

    Hi Michael,

    We could observe you have specified a “Viewer.ReportName” after specifying a “Viewer.Report”, due to which the Viewer searches for a Report with the specified name in your project’s directory instead of using the Code-Based SectionReport that you assigned to the Report property of the Viewer.

    Commenting out the 'Viewer.ReportName" line fixes the issues.

    Please find attached an updated sample for the same.

    Regards,

    Anand

    Updated_Project.zip

Need extra support?

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

Learn More

Forum Channels