Submit error (500): Internal Server Error” problems with 6.2 and 6.3 when trying to use storyboards
20 June, 2013
Hi,
I've been getting "Submit error (500): Internal Server Error" problems with 6.2 and 6.3 when trying to use storyboards.
I thought I'd try upgrading tomcat as a starting point but the above link here (http://www.yellowfinbi.com/YFForum-Tomcat-6-upgrade-?thread=115119#p1) to the zip file is dead.
I tried using tomcat 6.0.37 from the apache website but there's obviously a lot of configuration you guys have done already.
I also tried deleting the install directory and using the full 6.3 installer over the existing database (postreSQL on RedHat 6) but this failed with a database error.
I'd like to try updating tomcat before handing over the logs for you to look at the 500 error, so is there a way of getting the preconfigured zip of 6.0.35?
I've been getting "Submit error (500): Internal Server Error" problems with 6.2 and 6.3 when trying to use storyboards.
I thought I'd try upgrading tomcat as a starting point but the above link here (http://www.yellowfinbi.com/YFForum-Tomcat-6-upgrade-?thread=115119#p1) to the zip file is dead.
I tried using tomcat 6.0.37 from the apache website but there's obviously a lot of configuration you guys have done already.
I also tried deleting the install directory and using the full 6.3 installer over the existing database (postreSQL on RedHat 6) but this failed with a database error.
I'd like to try updating tomcat before handing over the logs for you to look at the 500 error, so is there a way of getting the preconfigured zip of 6.0.35?
Hi,
Unfortunately we lost all forum attachments a little while ago, and slowly re-uploading. The problem with this ZIP is that it was custom made, and took a long time to put together.
It will be recompiled and uploaded however it's not going to happen in the coming days :(. Though in saying this we don't believe your issue is related to Tomcat at all, so you should not need to perform the upgrade.
We have actually encountered similar issues in testing and working on having it fixed in time for the 6.3 June release.
We ran into these errors when the storyboard is still trying to load, and we are performing another task , e.g close the storyboard, open report.
Are you able to provide some more information on how you get this error?
Is it only certain dashboards/reports/methods?
Also, are you also able to get the Yellowfin logs when this error occurs, and note the time they get this error (to help us find it in the logs).
Thanks,
David
Unfortunately we lost all forum attachments a little while ago, and slowly re-uploading. The problem with this ZIP is that it was custom made, and took a long time to put together.
It will be recompiled and uploaded however it's not going to happen in the coming days :(. Though in saying this we don't believe your issue is related to Tomcat at all, so you should not need to perform the upgrade.
We have actually encountered similar issues in testing and working on having it fixed in time for the 6.3 June release.
We ran into these errors when the storyboard is still trying to load, and we are performing another task , e.g close the storyboard, open report.
Are you able to provide some more information on how you get this error?
Is it only certain dashboards/reports/methods?
Also, are you also able to get the Yellowfin logs when this error occurs, and note the time they get this error (to help us find it in the logs).
Thanks,
David
Hi David,
In 6.2 the 500 errors occurred when trying to setup a theme, and then when creating a storyboard and whenever I tried to open /review that storyboard.
Once I upgraded to 6.3 I imported the standard demo content and I got the error when I tried to open the 'Welcome to Yellowfin' storyboard, or the storyboard I'd started to create in 6.2.
I was keen to get this working for an upcoming prospect demo, so I ended up doing a complete fresh install with a higher version of Java and also getting the Tomcat 6 upgrade. The 'Welcome to Yellowfin' storyboard no opens correctly.
I've yet to try some of my own content, I didn't export my previous effort in case the theme or storyboard contained corruptions.
Andy.
In 6.2 the 500 errors occurred when trying to setup a theme, and then when creating a storyboard and whenever I tried to open /review that storyboard.
Once I upgraded to 6.3 I imported the standard demo content and I got the error when I tried to open the 'Welcome to Yellowfin' storyboard, or the storyboard I'd started to create in 6.2.
I was keen to get this working for an upcoming prospect demo, so I ended up doing a complete fresh install with a higher version of Java and also getting the Tomcat 6 upgrade. The 'Welcome to Yellowfin' storyboard no opens correctly.
I've yet to try some of my own content, I didn't export my previous effort in case the theme or storyboard contained corruptions.
Andy.
Hi Andy,
I've tried replicating this following your steps , but still unable.
I know you have since reintalled, though wondering if you still have the original YF directory so we can grab the log files.
To let you know what we're up against with this error, have a read of what it actually means : Error 500 Explained.
After a lengthy discussion with the QA department, they did find that some 6.2 'interim releases' contained issues with creating storyboards, so any storyboards created in this build are corrupted, and need to be blown away.
However if you were ever only using the released versions (from our web-site) this will not be the case.
Please let me know your findings.
If none of this helps us move forward and you're able to reproduce it with a specific data set, it might be a good idea to setup your environment here in the office so we can test it out.
Apologies for the inconvenience.
Regards,
David
I've tried replicating this following your steps , but still unable.
I know you have since reintalled, though wondering if you still have the original YF directory so we can grab the log files.
To let you know what we're up against with this error, have a read of what it actually means : Error 500 Explained.
After a lengthy discussion with the QA department, they did find that some 6.2 'interim releases' contained issues with creating storyboards, so any storyboards created in this build are corrupted, and need to be blown away.
However if you were ever only using the released versions (from our web-site) this will not be the case.
Please let me know your findings.
If none of this helps us move forward and you're able to reproduce it with a specific data set, it might be a good idea to setup your environment here in the office so we can test it out.
Apologies for the inconvenience.
Regards,
David
im also having issues with attempting to export. what can be done to fix this in DB?
Thanks,
Jamie
Thanks,
Jamie
Hi Jamie,
thanks for the screenshot of the error although unfortunately that error message is a generic one and doesn't give us any clues as to what may have caused the problem. Are you able to zip up the log files and attach them to this post?
Regards,
Dave
thanks for the screenshot of the error although unfortunately that error message is a generic one and doesn't give us any clues as to what may have caused the problem. Are you able to zip up the log files and attach them to this post?
Regards,
Dave