We also had a number of scheduled reports which failed to run after upgrading to v14. After logging a TASK ticket and looking at the logs we realised that this was actually a combination of Tessitura tightening up the security and us changing the user a scheduled report was allocated to - user_id in gooesoft_request.
Each scheduled report has a user_id and and user group id (ug_id). We had updated the user_id for request owned by users who had left. However in doing so the new user was NOT assigned to the user group of the left user. As soon as we updated the user group to a valid one for that user the reports started working.
Therefore might be worth checking that the user and user group combination is valid in Tessitura security.
Alex
Further digging and we do have a custom job running that Inactivates users that haven't logged in in the past 90 days. As Standard Functionality locks the account if the password has expired I'm tempted to disable that custom code. As long as the reports will still run on a locked account. Can anyone confirm that?
Kathleen -
Thanks for giving Jill Z a heads-up about this. We upgraded this week, and I reanimated your old account until tonight when I had time to change the users in gooesoft_request.
Clarke
Hi All,
I'm taking over from a predecessor Tessitura admin who associated all of the important reports (Member Update Utility, Billing, Attribute Maintenance, "etc, etc, etc, and so forth"...) with their personal login account in Tessitura. So at some unknown date in the not-so-distant future, this account's password is going to expire because it has not been re-set. Or I'm going to come along and inactivate this account. And these business processes will come to a halt.
In the past, I would create an API account for these must-run reports. Set its password to something long and crazy and its expiration date way in the future through SQL on the backend. And then Associate important reports/utilities that just have to run with the captive report running account.
Going way back when the report server was less reliable. I knew a DBA who decided to make a SQL Server Job out of each of these must-run reports/utilities. The challenge with this is as an organization changes its Tessitura Admin / DBA over time. Finding these "must-run" reports get to be a challenge. And one is concerned about locking down a past admin account for the fear of breaking these critical business functions.
I'm looking for community best practices on this point before making changes at my current organization.
How do you run those "reports/utilities" that just have to run? Why do you do it that way? What will happen to your organization when you are no longer around to supervise the process?