• Replies 13 replies
  • Subscribers 338 subscribers
  • Views 146 views
  • Users 0 members are here
Related

Scheduled SSRS report issue

Jeff Stahel
$organization

Hello,

We have a custom SSRS version of the Ticket Sales by Period report that we are having trouble with when running it as a scheduled report.

The report server seems to process the report, but fails to send an email when either one of two seasons are selected in the parameters. Also, the report does not show up  in the 'View Reports' area.

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?

Thanks!

Jeff

Parents
  • $organization
    Jeff-

    We had this issue, as Chris mentioned - and I also had your issue with the specific production season as a problem. Run that prod season in the query or sproc, and see if you get irregular data, like a null value or something. For us it was a perf that had no sales that triggered the problem.

    ------
    Beth Gilliland
  • $organization in reply to Beth Gilliland

    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

  • Former Member
    Former Member $organization in reply to Jeff Stahel

    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

  • $organization in reply to Former Member

    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

Reply
  • $organization in reply to Former Member

    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

Children
  • $organization in reply to Beth Gilliland

    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...

  • Former Member
    Former Member $organization in reply to Chris Jensen

    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!

  • Former Member
    Former Member $organization in reply to Former Member

    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!