June 14, 2010 at 4:46 pm
Greetings all.
First I will preface this with the fact that I am not a Reporting Services person. I am a DBA, but our Reporting person left recently so I am attempting to patch a few issues while that role is waiting to be refilled.
I am having some difficulties with report subscriptions, that are seemingly random to me. I have one in particular that sends out a total of 55 reports (as excel files) that is a data driven subscription. I know it is not the size of the email, and I am fairly sure it is not the email that is having the issues...as I would be getting email errors and not errors in the status messages under My Subscriptions. I checked the logs within the report server database and they are not very intuitive to me.
In the status column I have gotten the following 4 errors; rsCRIProcessingError, rsInternalError, rsProcessingAborted, and rsReportServerDatabaseError.
I have double checked some of the reports that failed (reverse logic finding which ones didn't mail out), and I find if I pass the parameters of the ones that fail then they process fine. I have also ran this a few times and the ones that fail are not consistent. Is there some sort of setting I should be modifying here? It seems like some sort of resource conflict however the server has 50GB of memory and 16 processor cores. Plenty of hard drive space, and a rather well designed hard drive architecture with the database files spread across them.
we are on Windows server 2003 64bit as well as sql server 2008 64bit
Link to my blog http://notyelf.com/
June 15, 2010 at 7:46 am
Hi,
Check the status of the subscription for the report in report manager, there should be a row for each subscription.
The status should read something like ' Done: 422 processed of 422 total; 5 errors.'
If there are errors then I would check the sql script in the dds, the sql script normally builds the list of recipients and could contain parameters and other info.
You will need to check that the data returned from sql script in the dds works properly and that any parameters returned will run the report.
This is a starting point, I don't know of any easier way of checking this.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply