Error retrieving results
Answered
Hi,
Often I get the error message "Error retrieving results" when I open a report in the morning. Every night the Tomcat is restarted.
When I go to data sources and open / save the specific data source; open the report again. The problem is gone and the report shows the results.
We have a lot of data marts stored in about 14 different data sources.
We did not customize any XML's or configs.
How can we keep this connection 'alive'?
Kind regards,
Roger
Files:
011111111.PNG
The same question 
Hi Roger,
Thanks for your post.
I believe you need to enable the Volatile Data sources. What this does is, it will check the data source connections for every 30 seconds and if the connection is closed, it will reset the connection. For more information on how to set this up, please follow the article by clicking here.
See how you go with it and let me know if you have any questions or any issues.
Regards,
Mahe
Hi Roger,
Thanks for your post.
I believe you need to enable the Volatile Data sources. What this does is, it will check the data source connections for every 30 seconds and if the connection is closed, it will reset the connection. For more information on how to set this up, please follow the article by clicking here.
See how you go with it and let me know if you have any questions or any issues.
Regards,
Mahe
Hi Mahe,
Thanks for the reply.
I will consult the DBA and see he can do on short term.
Kind regards,
Roger
Hi Mahe,
Thanks for the reply.
I will consult the DBA and see he can do on short term.
Kind regards,
Roger
One more question concerning the insert statements.
Will these be affected when YF is updated to a newer version (7.4)?
One more question concerning the insert statements.
Will these be affected when YF is updated to a newer version (7.4)?
Hi Roger,
I believe the new version (7.4) will not affect the changes, unless if there are any changes in the database schema.
As of now, I am not aware of any DB schema changes.
Let me know if you have any changes.
Regards,
Mahe
Hi Roger,
I believe the new version (7.4) will not affect the changes, unless if there are any changes in the database schema.
As of now, I am not aware of any DB schema changes.
Let me know if you have any changes.
Regards,
Mahe
Hi Roger,
Hope you are doing well.
Please let me know if you have any more questions.
If everything is good, I may close this ticket.
Regards,
Mahe
Hi Roger,
Hope you are doing well.
Please let me know if you have any more questions.
If everything is good, I may close this ticket.
Regards,
Mahe
Hi,
Sorry I didn't reply. This fixed the issues as mentioned.
The only issue we still have is that the dashboard generates a time-out.
See screen below
The second or third time the report is displayed.
I hoped this issue would also be fixed. But it's the same.
Do you have a solution for this problem?
Kind regards,
Roger Smits
Hi,
Sorry I didn't reply. This fixed the issues as mentioned.
The only issue we still have is that the dashboard generates a time-out.
See screen below
The second or third time the report is displayed.
I hoped this issue would also be fixed. But it's the same.
Do you have a solution for this problem?
Kind regards,
Roger Smits
Hi Roger,
Regarding a solution for the browser error message of ERR_CONNECTION_TIMED_OUT, please be aware that this is not a Yellowfin issue, a quick search of the internet with your favourite search engine will show you that it is most likely a browser issue or maybe a network congestion or a routing issue. I would recommend trying some of the many solutions suggested on the internet such as this one, or contacting your Network Administrator about this.
regards,
David
Hi Roger,
Regarding a solution for the browser error message of ERR_CONNECTION_TIMED_OUT, please be aware that this is not a Yellowfin issue, a quick search of the internet with your favourite search engine will show you that it is most likely a browser issue or maybe a network congestion or a routing issue. I would recommend trying some of the many solutions suggested on the internet such as this one, or contacting your Network Administrator about this.
regards,
David
Hi Roger,
yes, unfortunately there isn't one "easy fix" as such, however, you never know - there might be an "easy fix" out of the many possibilities suggested in that example article and other articles.
Good luck with it!
David
Hi Roger,
yes, unfortunately there isn't one "easy fix" as such, however, you never know - there might be an "easy fix" out of the many possibilities suggested in that example article and other articles.
Good luck with it!
David
Replies have been locked on this page!