Yef7/Linux Chrome-Browser hangs on “Loading Report”
27 December, 2013
Hallo,
I have update to Yef 7.0 (24.Dez.Vers, Linux).
It looks good but the Chrome-Browser hangs on "Loading Report / Bericht wird geladen".
The Firefox-Browser runs without problems.
Thanks
Ernst
I have update to Yef 7.0 (24.Dez.Vers, Linux).
It looks good but the Chrome-Browser hangs on "Loading Report / Bericht wird geladen".

The Firefox-Browser runs without problems.
Thanks
Ernst
Hi Ernst,
Most of us here use Chrome and have not had this happen before, so I'm thinking there is something specifically with that dashboard tab that Chrome is not handling too well.
Are you able to open the tab in Firefox so we can see how that tab is built, so we can try and replicate here in the office.
Also, can you get any browser related errors from the console.
You can do this in Chrome by hitting "CTRL + SHIFT + J"
Thanks,
David
Most of us here use Chrome and have not had this happen before, so I'm thinking there is something specifically with that dashboard tab that Chrome is not handling too well.
Are you able to open the tab in Firefox so we can see how that tab is built, so we can try and replicate here in the office.
Also, can you get any browser related errors from the console.
You can do this in Chrome by hitting "CTRL + SHIFT + J"
Thanks,
David
Hallo David!
Firefox View
Chrome Error
Firefox View
Chrome Error
Thanks for that,
I have passed on the errors to the dev team.
However out of curiosity, if you setup your chart so that it displays correctly, does Chrome then load the page?
Thanks,
David
I have passed on the errors to the dev team.
However out of curiosity, if you setup your chart so that it displays correctly, does Chrome then load the page?
Thanks,
David
Hi David!
same behavier, same errors.
Firefox
same behavier, same errors.
Firefox
Hi Ernst,
Thanks for the additional info.
It looks like there is code that is not being passed to Chrome, though it's not telling us exactly what part is not getting through.
I'm thinking it's specific to a chart/report setting that we have not tested with.
Are you able to send across the relevant yellowfin.log (located under Yellowfinappserverlogs) that captures the time when the error occurred.
Hopefully this can give us more information on what is tripping it up.
Thanks,
David
Thanks for the additional info.
It looks like there is code that is not being passed to Chrome, though it's not telling us exactly what part is not getting through.
I'm thinking it's specific to a chart/report setting that we have not tested with.
Are you able to send across the relevant yellowfin.log (located under Yellowfinappserverlogs) that captures the time when the error occurred.
Hopefully this can give us more information on what is tripping it up.
Thanks,
David
Hi David,
here are the log files.
here are the log files.
Thanks Ernst,
We have found the problem.
It looks like there is an issue with some parts of our German translations, and some bad text is being passed to Chrome which cannot be handled.
The translation file will be fixed in the January 7 release.
In the meantime when using a report with German translations you are going to have to say away from Chrome.
Sorry for the inconvenience.
Regards,
David
We have found the problem.
It looks like there is an issue with some parts of our German translations, and some bad text is being passed to Chrome which cannot be handled.
The translation file will be fixed in the January 7 release.
In the meantime when using a report with German translations you are going to have to say away from Chrome.
Sorry for the inconvenience.
Regards,
David
Thanks,
Ernst
Ernst
Hi David,
I have update to yellowfin-20140326-update.jar and know I have the same problem again.
Thanks
Ernst
I have update to yellowfin-20140326-update.jar and know I have the same problem again.
Thanks
Ernst
Hi Ernst,
Can you please send across the browser console errors and YF logs again so I can pass to the dev team.
Sorry for the inconvenience.
Regards,
David
Can you please send across the browser console errors and YF logs again so I can pass to the dev team.
Sorry for the inconvenience.
Regards,
David
Hi David,
here are the log files.
here are the log files.
Hi Ernst,
Thanks for the files, it looks like the problem resurfaced after making some changes to the German translation .
I have raised a task and given it a HIGH priority (TASK ID = 159926) .
This will need to be fixed asap, but I'm worried it won't make it into the April release.
Sorry for the inconvenience.
Can you use IE or Firefox in the meantime?
I am aware there is an issue with Firefox and co-display reports showing a 'grey' overlay.
That till will be fixed soon, but probably not in time for the April release .
Regards,
David
Thanks for the files, it looks like the problem resurfaced after making some changes to the German translation .
I have raised a task and given it a HIGH priority (TASK ID = 159926) .
This will need to be fixed asap, but I'm worried it won't make it into the April release.
Sorry for the inconvenience.
Can you use IE or Firefox in the meantime?
I am aware there is an issue with Firefox and co-display reports showing a 'grey' overlay.
That till will be fixed soon, but probably not in time for the April release .
Regards,
David
Hi David,
thanks for the support.
It works with the Firefox, because I don't have choosen the german language.
If I also choose german, I have the same Problem. There must be a problem with the German translation.
Regards,
Ernst
thanks for the support.
It works with the Firefox, because I don't have choosen the german language.
If I also choose german, I have the same Problem. There must be a problem with the German translation.
Regards,
Ernst
Hi Ernst,
Thanks for the extra info, that makes sense.
Got some good news.
Looks like this issue has been fixed, I have re-tested in the latest interim build, the official release will be available for download in the first week of May.
The grey overlay has not been fixed as yet.
But the dashboard reports are now loading :).
Regards,
David
Thanks for the extra info, that makes sense.
Got some good news.
Looks like this issue has been fixed, I have re-tested in the latest interim build, the official release will be available for download in the first week of May.
The grey overlay has not been fixed as yet.
But the dashboard reports are now loading :).
Regards,
David
David,
I have a few German customers who are having significant problems operating in Yellowfin and I wonder if this issue is related. However, they're pretty heavy users and have told us that the issues have only been occurring for the last few weeks. Here they are:
1) Their dashboards appear to display results but also say they're loading interminably. So the dashboard is not functional for them.
2) The admin console freezes up entirely and they can't click anything.
3) In the view builder if they attempt to drag a field into a category in page 2, Yellowfin seems to think they're performing an illegal operation (screenshot attached).
Here are the logs:
From the web browser:
GET http://bi.croptrak.com/includes/SessionUtilJS.jsp 500 (Internal Server Error) MIPreAdminConsole.i4:91
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. jquery-1.7.2.min.js?20140326:3
Uncaught ReferenceError: SessionUtil is not defined TemplateLocaliser.js?20140326:186
Uncaught ReferenceError: SessionUtil is not defined
From yellowfin.log
YF:2014-04-17 15:09:18:ERROR (SessionUtilJS_jsp]:invoke) - Servlet.service() for servlet com.hof.jsp.includes.SessionUtilJS_jsp threw exception
java.lang.IllegalArgumentException: Unmatched braces in the pattern.
at java.text.MessageFormat.applyPattern(MessageFormat.java:508)
at java.text.MessageFormat.(MessageFormat.java:363)
at org.apache.struts.util.MessageResources.getMessage(MessageResources.java:346)
at com.hof.util.UtilString.getResourceString(UtilString.java:2888)
at com.hof.util.UtilString.getResourceString(UtilString.java:2809)
at com.hof.util.UtilString.getLocalResourceProperties(UtilString.java:4418)
at com.hof.jsp.includes.SessionUtilJS_jsp._jspService(SessionUtilJS_jsp.java:48)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:722)
YF:2014-04-17 15:09:18: INFO (ErrorAction:execute) - ErrorAction entered
YF:2014-04-17 15:09:18: INFO (ErrorAction:execute) - ErrorAction exiting with action: success
I have a few German customers who are having significant problems operating in Yellowfin and I wonder if this issue is related. However, they're pretty heavy users and have told us that the issues have only been occurring for the last few weeks. Here they are:
1) Their dashboards appear to display results but also say they're loading interminably. So the dashboard is not functional for them.
2) The admin console freezes up entirely and they can't click anything.
3) In the view builder if they attempt to drag a field into a category in page 2, Yellowfin seems to think they're performing an illegal operation (screenshot attached).
Here are the logs:
From the web browser:
GET http://bi.croptrak.com/includes/SessionUtilJS.jsp 500 (Internal Server Error) MIPreAdminConsole.i4:91
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. jquery-1.7.2.min.js?20140326:3
Uncaught ReferenceError: SessionUtil is not defined TemplateLocaliser.js?20140326:186
Uncaught ReferenceError: SessionUtil is not defined
From yellowfin.log
YF:2014-04-17 15:09:18:ERROR (SessionUtilJS_jsp]:invoke) - Servlet.service() for servlet com.hof.jsp.includes.SessionUtilJS_jsp threw exception
java.lang.IllegalArgumentException: Unmatched braces in the pattern.
at java.text.MessageFormat.applyPattern(MessageFormat.java:508)
at java.text.MessageFormat.(MessageFormat.java:363)
at org.apache.struts.util.MessageResources.getMessage(MessageResources.java:346)
at com.hof.util.UtilString.getResourceString(UtilString.java:2888)
at com.hof.util.UtilString.getResourceString(UtilString.java:2809)
at com.hof.util.UtilString.getLocalResourceProperties(UtilString.java:4418)
at com.hof.jsp.includes.SessionUtilJS_jsp._jspService(SessionUtilJS_jsp.java:48)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:722)
YF:2014-04-17 15:09:18: INFO (ErrorAction:execute) - ErrorAction entered
YF:2014-04-17 15:09:18: INFO (ErrorAction:execute) - ErrorAction exiting with action: success
Hi David
I have the same problem as Ernst. Can you please provide me the interim build?
Thank you
Klaus
I have the same problem as Ernst. Can you please provide me the interim build?
Thank you
Klaus
Hi Billy/Klaus,
Firstly, Billy what your German clients are facing is exactly what has been fixed.
Admin page freezing, dashboard reports freezing, co-display reports freezing.
This has all been fixed and was related to a bad German translation file.
I can provide a link to the interim build if you email support and reference this post.
Thanks,
David
Firstly, Billy what your German clients are facing is exactly what has been fixed.
Admin page freezing, dashboard reports freezing, co-display reports freezing.
This has all been fixed and was related to a bad German translation file.
I can provide a link to the interim build if you email support and reference this post.
Thanks,
David
Hi David,
Yellowfin BI 7 - build 20140502 has solved my problem, looks good!
Thanks
Ernst
Yellowfin BI 7 - build 20140502 has solved my problem, looks good!
Thanks
Ernst