System error when choosing FreeHand SQL
Hi ,
Yesterday we have increased the Java memory from 1GB to 10 GB and today, not sure if related, we are not able to use FreeHand SQL, we get "System error".
I am attaching one gif to see what i get with the mention that one data source is not available for myself whereas that is available for my manager but when selected produces more detailed error, i am attaching that also maybe you are able to figure what is wrong.
Below the log:
YF:2017-09-28 01:43:58: INFO (MIReportInitAction:execute) - MIReportInitAction entered
YF:2017-09-28 01:43:58: INFO (MIReportInitAction:execute) - MIReportInitAction exiting with action: MIReportSQL
YF:2017-09-28 01:43:59: INFO (MIPreReportSQLAction:execute) - MIPreReportSQLAction entered
YF:2017-09-28 01:43:59:ERROR (MIReportProcess:loadSourceParameterList) - Error: java.lang.NullPointerException
YF:2017-09-28 01:43:59:ERROR (MIReportProcess:buildCacheMapTablesAndViews) - Error: java.lang.NullPointerException
java.lang.NullPointerException
at com.hof.mi.process.MIReportProcess.buildCacheMapTablesAndViews(MIReportProcess.java:19488)
at com.hof.mi.web.action.MIPreReportSQLAction.execute(MIPreReportSQLAction.java:204)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:229)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at com.hof.servlet.BrowserHeaderFilter.doFilter(BrowserHeaderFilter.java:43)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:108)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:589)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:784)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
The same problem 
Hi Stefan,
as far as I'm aware, there was never a Freehand SQL issue for calculated fields. What you're experiencing could be due to security on the Yellowfin data source - if the data source is set as Private then any users not listed in the security list won't have Freehand SQL in their reports (including calculated fields):
So can you please check whether your data source(s) has been configured with the private security setting and if so, then check the list of users.
regards,
David
Hi Stefan,
as far as I'm aware, there was never a Freehand SQL issue for calculated fields. What you're experiencing could be due to security on the Yellowfin data source - if the data source is set as Private then any users not listed in the security list won't have Freehand SQL in their reports (including calculated fields):
So can you please check whether your data source(s) has been configured with the private security setting and if so, then check the list of users.
regards,
David
Hi Stefan,
this is actually a known bug and has already been raised as defect YFN-7452 and will be fixed soon.
In the meanwhile thankfully there is an easy workaround. If you create just one Freehand SQL View (using any source, doesn't have to be the one you want to report from) then after that all Freehand SQL Reports will work (for any source). This fix will last until Yellowfin is restarted, in which case you'll have to create one more Freehand SQL View to get all Freehand SQL Reports working again.
regards,
David
Hi Stefan,
this is actually a known bug and has already been raised as defect YFN-7452 and will be fixed soon.
In the meanwhile thankfully there is an easy workaround. If you create just one Freehand SQL View (using any source, doesn't have to be the one you want to report from) then after that all Freehand SQL Reports will work (for any source). This fix will last until Yellowfin is restarted, in which case you'll have to create one more Freehand SQL View to get all Freehand SQL Reports working again.
regards,
David
Hi Stefan,
no problems, we'll notify you when the bug is fixed. At the moment the notifications aren't automatic but at some point they will be.
regards,
David
Hi Stefan,
no problems, we'll notify you when the bug is fixed. At the moment the notifications aren't automatic but at some point they will be.
regards,
David
Dave, ive seen the same behavior on Reports too but this time its nastier as we have to apply the workaround every time you log into the system. So its pretty ugly as it needs to be applied by every individual and its working only one session. The view workaround lasts till the server is rebooted but the report one only till you log out. Do we have an estimated time to get a fix for this ?
Dave, ive seen the same behavior on Reports too but this time its nastier as we have to apply the workaround every time you log into the system. So its pretty ugly as it needs to be applied by every individual and its working only one session. The view workaround lasts till the server is rebooted but the report one only till you log out. Do we have an estimated time to get a fix for this ?
Hi Stefan,
At the moment it'd probably be the end of November, so what we're trying to do is to move this up higher in the developers' queue so that it gets fixed sooner. I'll contact you at the end of this week and let you know what we think the ETA of the fix will be.
regards,
David
Hi Stefan,
At the moment it'd probably be the end of November, so what we're trying to do is to move this up higher in the developers' queue so that it gets fixed sooner. I'll contact you at the end of this week and let you know what we think the ETA of the fix will be.
regards,
David
Hi, do we have any updates on this issue? Seems it gets very bad, like the option is not available at all to some users.
We are several admins (full rights) and some see this option other dont.
Hi, do we have any updates on this issue? Seems it gets very bad, like the option is not available at all to some users.
We are several admins (full rights) and some see this option other dont.
And the initial workaround doesn't work also since there is no more option to create a freehand sql View.
And the initial workaround doesn't work also since there is no more option to create a freehand sql View.
Hi Stefan,
this defect has definitely been fixed, so if you download and run the latest build of the 7.3 Upgrade Installer then you will find the issue has been resolved.
regards,
David
Hi Stefan,
this defect has definitely been fixed, so if you download and run the latest build of the 7.3 Upgrade Installer then you will find the issue has been resolved.
regards,
David
Hi Stefan,
as far as I'm aware, there was never a Freehand SQL issue for calculated fields. What you're experiencing could be due to security on the Yellowfin data source - if the data source is set as Private then any users not listed in the security list won't have Freehand SQL in their reports (including calculated fields):
So can you please check whether your data source(s) has been configured with the private security setting and if so, then check the list of users.
regards,
David
Hi Stefan,
as far as I'm aware, there was never a Freehand SQL issue for calculated fields. What you're experiencing could be due to security on the Yellowfin data source - if the data source is set as Private then any users not listed in the security list won't have Freehand SQL in their reports (including calculated fields):
So can you please check whether your data source(s) has been configured with the private security setting and if so, then check the list of users.
regards,
David
Replies have been locked on this page!