You are not logged in.
I'm not overly familiar with ReportServer and I'm trying out a lot of tests to check for suitability of this platform, and resolve issues with logos not appearing. Also frequently having to restart and rebuild my test environment from scratch because of a lack of time and enterprise trial time limits.
Due to my unfamiliarity, I have wasted a lot of hours trying to look into problems that don't exist. For example a simple Jasper report crashing because I'd copied and pasted the image URL from the File Server page into a Global Constant, but the internal and external ports on my docker image were different. Internally it was 8080, externally 8081. This caused the following error:
"ConnectException: Connection refused"
I spent several hours trying to work out why my database connection was being refused, it made no sense. That's because it was the connection within ReportServer to fetch the image which was on the wrong port. I only discovered this later by looking some way down in the trace stack. This seems to be a common problem. Email issues get reported with very little context shown on screen, you have to dig deep to find what the reason is.
Please can we have clear and concise error messages that are meaningful shown to the user that don't require a magnifying glass and copy and paste techniques to retrieve the last 150 lines of error messages so you can see the real reason.
Offline
Offline
Hi Eduardo
I think this is clearly a matter of opinion. Personally when I write code I make sure that, wherever possible, I display the root cause of the issue.
In this case admittedly the Connection Refused error is correct, but you are not displaying any sensible context for that. You are relying on the user having to copy and paste error text into another application and wade through the call stack to find out what has happened. Some of the error popups I've encountered in your app can't even display the entire call stack, even when they do you still need to copy and paste.
This is not a very pleasant user experience.
Surely if you have a section of code that is trying to open a web resource, and you trap an exception while you are trying to do that, it makes sense to raise an exception that displays 'An error occurred trying to open the resource http://XYZZY'. This immediately gives context to the problem rather than just dumping the stack trace. This saves the poor user the hassle of cut and paste and frustration of dealing with your application.
User experience is everything. People get really annoyed with stuff like this where 100 lines of error code get chucked at them when doing simple things. It drives people away from your product thinking it's buggy and not fit for purpose. It's a good job I am a determined sort or I would have given up quite a while back.
I am a developer and can deal with stack traces, but it really shouldn't be necessary, and a lot of people won't do that.
Offline
Hello ianef,
if more time for evaluvation is needed our sales team is happy to provide an extended evaluation licence. Please feel free to contact them via sales@infofabrik.de so they can find a fitting option for you.
Kind regards,
Laura
Offline