Since upgrading to Tessy 10.0.0.1 our scheduled reports queue has been jamming up. Two of our reports appear to be causing this. First, "Payments by Performance" triggers an error window: "Retrieve argument 7 does not match the expected type".
Second, "On Account Tracking Report (local version)", which is a local report causes the error "Reports Path not available in INI file. Your report cannot be run."
Just curious if anyone has experienced similar issues w/ any of their reports?
Hi Jason,
The Payments by Performance report had a new parameter added in v10 (Price Categories). Existing report schedules don't cope at all with new parameters, even when the parameter is optional. The stored procedure is expecting parameter values to be passed in a particular order, and the values stored in the existing report schedule no longer match what the updated stored procedure needs.
I believe you can just update the parameters on your existing report schedule via Tools > Maintain Report/Utility Schedules, and the change will take effect from the next report run.
I'm not too sure about the second error - does the Tessitura.ini file on your Report Server machine contain a path value to the client files? e.g. path=c:\program files\impresario\client
Kim
Thanks for the response. I think you are right regarding the Payments by Performance report. To take this out of the equation for now, I deactivated all jobs for this report.
With regards to the other error, I was mistaken. It occurs on all reports attempting to run (not just the local report I mentioned). Interestingly enough though, if I open the Report Server app and right click on a report and do a Run Now, it works! So why would the app not be able to do this correctly automatically anymore?