JS Viewer AR 13 - Bad error reporting - Production Server Only

JS Viewer AR 13 - Bad error reporting - Production Server Only

Posted by: coreyp on 4 June 2019, 1:58 am EST

• 

  coreyp

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 4 June 2019, 1:58 am EST - Updated 30 September 2022, 6:47 am EST

  I have created a report using the JSViewer in AR 13 in an Angular application. It works fine in my local dev environment, however, when I deploy it out to the server I get a real generic error from the jsViewer.min.js file. I have attached what we are seeing in Chrome’s DevTools, it isn’t much. If we had access to an non-uglyified and un-minified version of the jsViewer.js file we might able to help nail this one down. Things we’ve ruled out: (1) the components are licensed properly, we know this because we are allowed to generate a report server side and have it emailed as a PDF. (2) we’ve tried using the exact same backing data in our local environment to avoid the possibility that our own data is causing the problem.

  Any assistance or intel is greatly appreciated, we are quite stumped. Thanks!

  

  1447×644 61.6 KB

• 

  coreyp

  • Post Options:
  • Link
    Copy

  Posted 4 June 2019, 5:26 am EST

  Just for further usage, here is my configuration code. I am loading the report custom so that I can make the data source a custom array and not a direct tie to the database. The report is now empty with no data bindings, just in an effort to rule out data being the problem. Again, this works in my local environment but does not work when I deploy to my web server.

  
    .UseReporting(config => {
      config.UseCustomStore(args => {
        var sectionReport = new SectionReport();
        var reportFile = System.IO.Path.Combine("C:\\WebPortalG5\\04162019\\WebPortal.API", 
          "Reports", "PrintBillPortalReport2.rpx");
        sectionReport.LoadLayout(reportFile);
        return sectionReport;
      });
    });
  
  

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 6 June 2019, 1:54 am EST

  Hello,

  Your query is being addressed on the corresponding SupportOne ticket(383387).
  
  Please follow and respond to the same, to avoid confusion.

  Thanks