Hello All,
Recently upgraded code levels and now some of our scheduled reports (both custom and standard) are showing in error for some of our Box Office Managers and Development personnel. They're having to go in and manually run the reports as the scheduled reports have stopped working. We have had our email server cycled and have had a ticket opened around the issue with Tessitura.
Has anyone else seen this with recent upgrades?
Thanks,
Nathaniel
Nathaniel Baker
We saw exactly the same kind of things when we upgraded from V15.0.4 to 15.1.4 with Tessitura Analytics Based Reports. You did not say what kind of reports you were not receiving.
We think that this may be resolved as of today.
I would think that a Support Ticket is exactly the right move. Particularly if you are on RAMP.
Hi Nathaniel,
If there is consistency with the reports all being Infomaker vs SSRS reports, we had an issue when we upgraded where there was a password entered incorrectly in the config file that controls how Infomaker reports were sending. We are not on RAMP so if this is what you're seeing let me know and I can connect you with our network admin who has more details.
-Sheela
We have an issue with scheduled reports running after updating version 15 as well. You might have RAMP check the dbms to make sure it set to OLE DB and restart the TPS.
After some sort of work that has not been well specified by the RAMP team our Tessitura Analytics Reports are working again.
What version of tessitura were you upgrading from? We discovered a problem when going from V12.5.1 to V15.X.X. The system in the earlier version would send out reports for accounts with expired passwords. Somewhere along the way between 12.5.1 and 15.0.4 the system started not allowing this. If you need continuous reports not really associated with a specific user, like the Membership Update Utility and the Credit Card Purge Reports you can do some things in SSMS and or the Security Module to get around these behaviors.
We also had something similar when we updated to 15.14In v. 15.14 a "bug" has been corrected, so now scheduled reports will fail if the owner of the schedule is not an active tessitura user in the security module. The thing is that if you have one report that fails for this reason, a lot of other reports will subsequently fail as well
Could this be the issue.
One more thing. A new column "as_of_datetime" has been added to the table "GOOESOFT_REPORT_SCHEDULE". The column doesn't allow null, and doesn't have a default value. If you have schefules that is automaticelly scheduled from a stored procedure or other code, this will fail on insert.
Hello all! I would like to step in here to say that Nathaniel and the Kauffman Center team are actively working with Support to resolve this issue. Once we have a resolution, we will report back for the group. Thank you all for jumping in to assist.
Noting for reference that the primary issue at hand here was that there was an external SMTP (email) server defined in the TR_EMAIL_PROFILE system table that was rejecting send requests from us. Also, the 'From' address was undefined for one of the profiles used to send report emails. We replaced that address with the standard one we use for RAMP users, and reset a number of requests to be re-run, which then returned successfully.
There is a bug in the V15.1.5 installer that removes a right from the Tessitura WebReports SSRS role, resulting in scheduled SSRS reports being broken. You can workaround this issue by connecting to the SSRS service in SSMS (connect to Server Type "Reporting Services" instead of "Database Engine"), then go to Security -> Roles, Tessitura WebReports, and enable "View folders".
I reported this defect on 11/16 (ticket 87842).