Angular 4 Report View Component

3 posts, 1 answers
  1. Chris
    Chris avatar
    4 posts
    Member since:
    Feb 2015

    Posted 26 May Link to this post

    Hello!  I have installed the Angular 4 component.  My Angular project is up and running, but the component is acting funny.  It isn't even TRYING to connect to the report server before throwing the classic "Error loading the report viewer's templates. " error.  I've seen all the FAQ stuff about making sure that the reporting api is running, and it definitely is.  The weird thing is that the component doesn't even try to connect.  I'm monitoring the requests in the browser, and nothing ever goes toward the reporting api at all.

     

    I'd love to be able to use this component, but I'm having trouble even getting off the ground with it.

    Yes, I have Angular 4 and jQuery 3.2.1.  I installed the component off NPM.

    Thanks for any help you can provide!

     - Chris

  2. Answer
    Katia
    Admin
    Katia avatar
    490 posts

    Posted 30 May Link to this post

    Hello Chris,

    You can check if serviceUrl (reportServer) properties are set correctly. Using Fiddler or another proxy tool you can check if the paths are resolved correctly (in Fiddler - Inspectors - Raw tabs).

    We would recommend using jQuery version which is tested with required Kendo UI libraries - Requirements. This is to avoid possible issues with a newer version of jQuery.

    If the issue persists it would be best if you send us a project that demonstrates the current settings of the viewer in a support ticket so we can review them locally.


    Regards,
    Katia
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. Chris
    Chris avatar
    4 posts
    Member since:
    Feb 2015

    Posted 31 May in reply to Katia Link to this post

    Hello, and thanks for the reply!  I'm not quite sure how I fixed this, but I ended up trashing all of my node_modules folder, then rebuilding it, and upgrading some of the modules I had installed, and it is working now.  I wish I could give you a better idea of what fixed it, but after just messing around and cleaning up a bunch of modules, it started working.

     

    So thanks!

      - Chris

Back to Top