SSRS Schedules not running

The SSRS_CUSTOM_PATH default value in T_DEFAULTS is set to a blank value for backwards compatibility. This is an optional value for v11+, which is provided as a means of providing a starting path for all custom reports on a Tessitura environment.  If all of your custom SSRS reports exist in the “TessituraCustom” folder, you can put this into the SSRS_CUSTOM_PATH default value and all custom reports will have “TessituraCustom/” added to their report path.  This is useful when working in multiple test or development environments when you keep custom reports in separate folders on the SSRS Server instead of multiple SSRS instances.  You can alter the default value to swap folders in a single location.

If your Custom SSRS Report had a path of “TessituraCustom/PerformanceSales” in v10, it should have “TessituraCustom/PerformanceSales” in v11 as long as the value for SSRS_CUSTOM_PATH remains blank.  If this default has a value, it is prepended to the report setup’s path. 

All scheduled SSRS report requests, whether standard or custom, should be created in  /Tessitura/ScheduledReports where “Tessitura” is the default value for SSRS_STANDARD_PATH in T_DEFAULTS.  This default setting, under most circumstances, should not be changed, as it’s setting also needs to correspond to the setting in TIM which is used during installation.  Scheduled Reports are maintained by standard system processes (WebReports and the Tessitura Report Server) and are handled only in the /Tessitura/ScheduledReports folder path.

I can see there is a small defect in v11.0.3.  When CUSTOM_REPORT_PATH has a value, a ScheduledReports folder is being created in the path defined in CUSTOM_REPORT_PATH.  No report schedules/snapshots are actually stored in this location and the folder should remain empty.  This is incorrect and will be fixed in a future release.  If you are seeing something contrary to this, please open a support ticket or we can reopen the existing ticket where RAMP staff were helping you.

I hope this clarifies SSRS/Tessitura a bit for everyone.

+Ryan Creps

+Tessitura Network

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Christopher Sherwood
Sent: Friday, September 21, 2012 6:13 PM
To: Ryan Creps
Subject: Re: [Tessitura Technical Forum] SSRS Schedules not running

Thanks for the replies-

Turns out that there are some quirks with the T_DEFAULTS settings where the reports should now be listed in GSR/the gooesoftreport tables as 'ReportName' and not 'path/ReportName' with the report path being held in the T_DEFAULTS table (Seems this may be a requirement, apparently) .

After this was sorted out we needed to then add a second SecheduledReports folder within the custom report folder as it was no longer going to use the folder in the main directory.

Finally it was found that there were some permissions missing on required folders to allow the snapshots to be written at all (this may have been the original issue?)

Thankfully Jennifer (RAMP) and Brian Pedaci were able to help us sort this out. Seems as if there are quite a few quirky differences in the setup introduced with updates to the paths. If anyone is having any similar issues I'd suggest really going through and utilizing all the new settings to their full intention.

Thanks-

Chris

The SSRS_CUSTOM_PATH default value in T_DEFAULTS is set to a blank value for backwards compatibility. This is an optional value for v11+, which is provided as a means of providing a starting path for all custom reports on a Tessitura environment.  If all of your custom SSRS reports exist in the “TessituraCustom” folder, you can put this into the SSRS_CUSTOM_PATH default value and all custom reports will have “TessituraCustom/” added to their report path.  This is useful when working in multiple test or development environments when you keep custom reports in separate folders on the SSRS Server instead of multiple SSRS instances.  You can alter the default value to swap folders in a single location.

If your Custom SSRS Report had a path of “TessituraCustom/PerformanceSales” in v10, it should have “TessituraCustom/PerformanceSales” in v11 as long as the value for SSRS_CUSTOM_PATH remains blank.  If this default has a value, it is prepended to the report setup’s path. 

All scheduled SSRS report requests, whether standard or custom, should be created in  /Tessitura/ScheduledReports where “Tessitura” is the default value for SSRS_STANDARD_PATH in T_DEFAULTS.  This default setting, under most circumstances, should not be changed, as it’s setting also needs to correspond to the setting in TIM which is used during installation.  Scheduled Reports are maintained by standard system processes (WebReports and the Tessitura Report Server) and are handled only in the /Tessitura/ScheduledReports folder path.

I can see there is a small defect in v11.0.3.  When CUSTOM_REPORT_PATH has a value, a ScheduledReports folder is being created in the path defined in CUSTOM_REPORT_PATH.  No report schedules/snapshots are actually stored in this location and the folder should remain empty.  This is incorrect and will be fixed in a future release.  If you are seeing something contrary to this, please open a support ticket or we can reopen the existing ticket where RAMP staff were helping you.

I hope this clarifies SSRS/Tessitura a bit for everyone.

+Ryan Creps

+Tessitura Network

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Christopher Sherwood
Sent: Friday, September 21, 2012 6:13 PM
To: Ryan Creps
Subject: Re: [Tessitura Technical Forum] SSRS Schedules not running

Thanks for the replies-

Turns out that there are some quirks with the T_DEFAULTS settings where the reports should now be listed in GSR/the gooesoftreport tables as 'ReportName' and not 'path/ReportName' with the report path being held in the T_DEFAULTS table (Seems this may be a requirement, apparently) .

After this was sorted out we needed to then add a second SecheduledReports folder within the custom report folder as it was no longer going to use the folder in the main directory.

Finally it was found that there were some permissions missing on required folders to allow the snapshots to be written at all (this may have been the original issue?)

Thankfully Jennifer (RAMP) and Brian Pedaci were able to help us sort this out. Seems as if there are quite a few quirky differences in the setup introduced with updates to the paths. If anyone is having any similar issues I'd suggest really going through and utilizing all the new settings to their full intention.

Thanks-

Chris