Aladdin: You're a prisoner?
Genie: It's all part and parcel, the whole "genie gig":
[
grows to a gigantic size]
Genie: PHENOMENAL COSMIC POWERS!
[
shrinks down inside the lamp]
Genie: Itty-bitty living space!
From Aladdin, 1992, Walt Disney Pictures
Like the genie in the bottle, SQL Server Reporting Services provides a phenomenal platform if its in the hands of an experience report developer. You have to know how to
exactly arrange your expressions.
If you created just one report, you've already encountered multiple error messages. What’s more frustrating is after successfully completing the report, the end user can encounter unforeseen error messages. I thought it appropriate to share the “excuses”
Top 5 excuses to give for a SSRS report failure
5. That’s strange, it works on my computer.
This actually happens. You create the report in the integrated development environment on your computer, deploy it to the server, and the end user views the report based on several permissions. There are many areas where an error can occur. For true effectiveness, follow-up this excuse with some techno-babble explanation.
4. I gave you the wrong link.
Give this excuse if you need a few moments to fix the issue. You can follow-up this excuse that the end-user doesn’t have access to the link provided.
3. It must be an issue with the database, I’ll contact the dba.
When in doubt, blame the dba. Sorry dbas, this is a universally acceptable excuse.It’s like saying I didn’t hang up on you, It was my cell phone carrier’s fault. I passed through a “dead zone”.
2. I forgot to grant you permission to view the report
This excuse is probably the most reliable one to give. It can buy you up to a day to address the real report problem.
1. The leap year caused the report to fail but it’s fixed now
This excuse can be used anytime in a leap year. It’s not restricted to 2/29! Everyone remembers the Y2K computer problems. However, you must be careful who you give this excuse to, it could backfire.
