Just after our V11 upgrade I'm getting this error on a couple of reports. Has something changed with Tessitura control group security that I've missed or forgotten about? The parameter in common to the reports having this error involves pulling a list of post_nos and checks against VRS_BATCH_TYPE. The parameter pull downs are fine in the client, but I observe that selecting directly against that table as dbo returns no results: perhaps the initial pull of data happens in the context of the client user, but then immediately control is passed over to ImpUser or the like, and ImpUser no longer has access to those rows in TR_BATCH_TYPE?
Any clues or suggestions would be appreciated,
Gawain
Gawain,
I would definitely check the security permissions as Wayne suggested. Particularly on any local views or tables that are involved. It was sporadic, but after the last V11 upgrade I went through, there were a few objects in the database that no longer had ImpUsers assigned to a role.
If that isn't the case, the next thing I would check would be gooesoft_request_parameter for the particular report request to see if perhaps one of the parameter values is being inserted there in a way that makes a select against it fail.
So, for my view, VRS_BATCH_TYPE, VRS_BATCH_TYPE_GROUP and the table TR_BATCH_TYPE_GROUP, all have Impuser/Database role with at least select permissions. The table TR_BATCH_TYPE also has Tessitura.app in an Application role: none of the others do.