Hello all.
I recently discovered that one of our local SSRS reports is having this problem for scheduled runs. In GOOESOFT_REQUEST, scheduled runs (type = 's') always have result_code = 's' and result_text = 'Error creating report snapshot'. The Maintain Schedules shows that the Next Run Date is incremented, but Last Run Date says "Never Run". The report runs fine when done manually.
So it seems like an issue with the snapshot folder, but I checked our settings in T_DEFAULTS and they're good. In fact, this is the only report that consistently has this problem. And it happens for anyone who schedules it (including myself, an admin), even people who have other scheduled reports that don't have problems.
My next step is to trouble-shoot the SSRS report itself, but I'm not sure where to start. Has anyone seen this behavior? Any suggestions?
Thanks very much!
Nathan
We have been having loads of problems with our SSRS reports and scheduling, we quite often get the snapshot error or an error saying that the report server can't find the file.
First check the logs of the Web Reports service as this gives really good information about why the report failed. Often it can be a problem with a parameter if you have updated the underlying report.
Though sometime we even get issues with reports that usually work fine.
We have also found that if you reschedule the report from the database table, the report will run fine! You can reschedule a report by updating gooesoft_schedule_queue. When a report throws an error it will change the status of the request to "e". So to reschedule a report we just change the "e" to "s" and then the report is rescheduled.
Next time the report is run it picks up the snapshot and is sent through fine! Not sure why but it works for us. It has reduced the number of report producing errors no end!
We have setup a scheduled job to run every hour which runs the following script.
update gooesoft_schedule_queueset status = 's'where status = 'e'and computed_date > '01 Aug 2013'
I was seeing the folowing
ErrorError creating report snapshot: Service URI: https://<rest api serevr>/WebReports/Snapshot/Create/379863?auth=K%2fV6R1a1dgHBqh57QyrYZZgVuOy5YYzJzDnsiuPnvkdUW6W18yM%2fZsT7YBDW4Jtz Verb: POST StatusCode: 400 StatusDescription: Service Response: ErrorMessages: The operation has timed out XML Request: (None)
I ended up running Application Error Log every 30 minutes to try to get more of a grip on what the error was but that also seemed to solve the issue, so am not sure whether by doing this I was keeping the Web Reports, and therefore also SSRS and Rest Services, "warm" enough that they prevented that time out.
That has stopped the error being obvious now
Mark
Thanks for all the feedback. It looks like Beth's suggestion worked - I found that I was getting a "warning" in BIDS when running the report, but it didn't stop the report from rendering. I resolved that issue, and the schedules started working after that. It's an interesting insight, and I might have to re-visit some of my other reports as I probably have "warnings" like that in several of them (possibly ones that haven't been scheduled yet).