Greetings!
I think a TASK ticket may be in my future but thought I'd start here in case someone has solved this problem in the past.
I have a new SSRS report which I built. It runs perfectly in the client and in Visual Studio - no errors at all. However, when you try to schedule the report, it doesn't send. It gives this error on the Tessitura Report Server:
Error creating report shapshot: Service URI: ... (more content) Error Message: The parameter value provided for 'snapshotID' does not match the parameter type. (more content)
I do not have a parameter of snapshot ID. I've built other reports in SSRS and have not had this issue.
Thoughts?
Thanks in advance,
Jenny
That error is always super unhelpful—I think I’ve seen it be fixed by like three different things.
A few months ago I think it surfaced in a similar situation for us—a scheduled report request refused to run no matter how many times it was resubmitted. The report would run fine manually, and subsequent schedule requests also worked fine. So I just had to ignore it and let it work itself out.
it doesn’t sound quite like the same thing that you’re seeing now.
I can tell you what I know of the mechanism by which SSRS reports are scheduled, in as much as it differs from running a typical foreground report. Instead of just doing a one-off request from the SSRS server, the report scheduler creates a “linked report” under Tessitura/ScheduledReports (in SSRS) named with the report schedule ID. The scheduled requests hit that linked report instead of the actual report object.
So, you might try poking around SSRS and see if there’s anything odd with the linked report. If your parameters are out of sync on the link, you could try refreshing the link on the properties tab—this can happen if, during report development, you deploy the report, schedule it, then redeploy a modified parameter setup. Tessitura will let you update the schedule parameters, but SSRS’s linked report won’t get updated automatically.
Thank you so much! Your response pointed me in the right direction. I appreciate your help more than you can know!!
Turns out, we had a data source that wasn't pointing to the correct credentials to create the snapshot. It was actually affecting multiple reports that just hadn't been reported to me yet. Fixed!
Thanks again!