When trying to export an report from the adhoc editor to any format it loads for a while, and then gives an "Internal Server Error".
The report has approx. 15.000 rows. But some are filled with large chunks of text.
Any ideas on how to solve this ?
I also looked at the logs but they aren't showing anything. The only thing i get in the browser is
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, root#localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
The jasperserver.log and the catalina.out do not show any error stacktraces.
It looks like i'm getting a timeout ?
Related
We have set up a small NuGet server in our corporate network. It works fine for EVRYONE except me ;-)
When I try to list the available packages in Visual Studio, all I get is this error message:
Unable to load the service index for source (...).
An error occurre while sending the request.
The remote server returned an error: (502) Bad Gateway.
I've been struggeling with this issue for hours without success. Can anyone give me a hint on why this error occurs?
I have an SSRS reporting service which sends reports as email subscription. Everything was working fine.
Now I added a expression to one of the column. After that I was able to view the reports in the URL, but the timely subscribed emails are not flowing out. The status is pending for so long and finally it fails saying "Thread aborted"
Can anyone help on this ?
Usually, the error "System.Threading.ThreadAbortException: Thread was being aborted." occurs when we call Thread.Abort() explicit, or there is unhandled exception occurred.
In this case, it should be unhandled exception, as SQL Server Reporting Services(SSRS) catches almost all exceptions. Maybe you could enable verbose log for SSRS to trace more detailed error log, this may help us to troubleshooting the issue. If there is dump file generated. The dump files will be generated in the same folder of the log files.
Dont have the rep to post this a comment.
I'm trying to set up Frapi on an Debian 9.1 Server.
Not every step from "http://frapi.github.io/installing/" did work.
Since days getting only this answer:
"Internal Server Error The server encountered an internal error or
misconfiguration and was unable to complete your request. Please
contact the server administrator at admin#api.frapi to inform them of
the time this error occurred, and the actions you performed just
before this error. More information about this error may be available
in the server error log.
Apache/2.4.25 (Debian) Server at 141.28.11.40 Port 80"
Someone worked already with this Framework and can tell me where I did wrong?
I downloaded the installer and run it, but I get a message telling me to check my internet connection. My connection works fine, but I suspect there might be a proxy problem. Does anybody know how to remedy this?
I had this issue, but today when I started the installer (the same installer I downloaded two days ago) and there was no error message. I think the problem was caused by the smarface.io server(s).
Thus, when you get this error message while installing smartface:
"Unable to connect to update server. Please check you internet connection and try again. #1"
Just wait for a day or two and start the installer again. The error message will disappear!
I have a code improvement suggestion for smartface.io:
I hope the error message never occurs in the future, but if it does you should correct the spelling: the word "you" in the error message is incorrect. It should be "your".
I’m trying to investigate for which reason sometime my service SQL Server Reporting Services (MSSQLSERVER) is screwed up and doesn’t respond, producing an error in my SSRS reports. When the users run their report they get an ambiguous and confusing error message like: Server Error in ‘/Reports’ application.
This problem was resolved only by stopping and restarting the service. It comes only a few times, but I don't want to get it again.
The stability of the reporting is the first priority for our team. I want to know the reason or how can we prevent this error in the future.