atifoxon Posted May 17, 2015 Share Posted May 17, 2015 I am trying to integrate an existing report using visualize.js and its giving me error in chrome console. The report is working fine when invoked externally through jaspersoft. See below the error, I have also attached sceen shotGET http://172.16.32.84:8080/jasperserver-pro/rest_v2/reportExecutions/6ce7479b…2-d1f544b5e65c/exports/2925c367-b606-44fd-91fb-d87db9c45a94/outputResource 404 (Not Found)[/code]16:17:34.530 [bi/report/Report] [ERROR] - resource.not.found : Resource 2925c367-b606-44fd-91fb-d87db9c45a94 not found.[/code]Report is initialized fine as no error is logged in v.report({ error: function (err) {...} });[/code]Even this method is invoked fineevent: {reportCompleted: function (status) {...}}[/code]JS Fiddle snippet, available at http://jsfiddle.net/atifoxon/4wujkm3y/2/Error I am getting in this methodreport.run().fail(function (err) {...}}[/code]One more thing I observed: I receive same error while running a sample report instead of one our report? See in Link to comment Share on other sites More sharing options...
hozawa Posted May 18, 2015 Share Posted May 18, 2015 Try entering the url causing the error in your web browser to see if the file can be found. JasperReports Server, also, protect against cross site scripting so the js files must be in the same domain as the report file. Link to comment Share on other sites More sharing options...
atifoxon Posted May 18, 2015 Author Share Posted May 18, 2015 @hozawa I cannot access the url by typing it in the URL. Furthermore I have digged through this error and it seems to be related with Restuful webservice Requesting Report Output. Does at the backend is it using web services? Link to comment Share on other sites More sharing options...
atifoxon Posted May 21, 2015 Author Share Posted May 21, 2015 Can any one help whats the issue with simple report rendering here? Link to comment Share on other sites More sharing options...
nicknxswart.nl Posted August 5, 2019 Share Posted August 5, 2019 Probably you already got the answer but I got the same problem. The fix is the headers from the first request should be passed to the next request. If you do so it will work. Link to comment Share on other sites More sharing options...
rakeshdn97 Posted January 20, 2021 Share Posted January 20, 2021 @nick_39 could you please provide some more details on how to solve this issue, even i'am facing this problem Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now