Scheduled SSRS report issue

Unknown said:

The report runs perfectly with those seasons when run from within Tessitura, and also runs perfectly when the selected output for the schedule is 'data center'.

The issue occurs when selecting any of the 'Email as' output options selections. The report runs fine when scheduled for any other season. Anybody have ideas about this one?

We used to have this issue. Please see this thread:

http://www.tessituranetwork.com/Community/forums/p/8099/27220.aspx#27220

...particularly Beth Gilliland's post of Dec 12 2012 12:11 PM.

Thank you Chris. Unfortunately those ideas do not apply to our situation, as scheduled SSRS reports run and email just fine, except for this one. The report in question only fails to email when it is scheduled to run against one of two specific seasons. Otherwise it runs and emails correctly.

Weird. Are your seasons control grouped?

Yes, they are control grouped, but the control groups are correct and match other seasons that the report works for.

We had an issue like this a few months ago.  Tessitura support finally sussed out that it was a link in the report causing it.  I had added code to make the constituent number clickable to take you to the patron record.

Not sure if you have that in your report.  But if you do, try removing it and seeing if the scheduled report works?

- Levi

Yet another good thought, but there are no links in the report. I was finally able to trace it down to one production season that is making it bomb. Not sure what the issue is yet, but at least it's a start. Thanks for the input!

Jeff

Thanks Beth. We found that the production season that was causing the problem is actually a reservation event, so as you said, no sales.

Thanks everyone for all the input!!

Jeff

We had exactly the same problem yesterday.  In our case, we have data to list in the custom report though.  Can you think of anything else I should look into?  I have asked RAMP to check for us what was suggested in a different thread referred to here earlier.

Thanks, Ahmet - Touhill PAC at UMSL

Ahmet-

Run the query or sproc used to create the data and see if there are any fields that are NULL. You could still get some data back, but sometimes the SSRS report does not appreciate the NULL and throws some type of error. It could even be a formatting issue of an actual field value that just has a bad Format applied in to the box in SSRS.

I'm slogging through another SSRS report today in fact. Must be the weather... :)

Beth

Re: SSRS and NULLs, I am finding output font bugs in SSRS that manifest themselves with non-int columns that contain NULLs (particularly in the first row) such that I am trying to output "" rather than  NULL in such cases these days. May not be applicable in this case, but you never know...

Beth, the SP does not create any data with NULL values, but there is a temporary table involved in the SP.  I will check to see if there are any errors involved due to it.  I hope the weather got better over there.  It is gorgeous here today.

Chris, I will keep your tip in mind.

Hopefully, we will get to the bottom of this eventually, and I will let everyone know.  Thank you!

Our problem turned out to be due to the SSRS_CUSTOM_PATH field value in T_DEFAULTS.  Because SSRS_CUSTOM_PATH was left null, the scheduled report failed according to the support ticket. Entering the proper SSRS_CUSTOM_PATH value, which is non-null in our case, resolved our problem.  If I understood correctly, this is related to a bug in Tessitura that seems to be fixed in v12.

Thanks again to all who contributed towards resolving this issue!