Hi mafab,
Generally, when you create an subscription, several things are added to the RS server:
- A row is placed in the Subscriptions table.
- A row is placed in the Schedule and ReportSchedule tables.
- A SQL Server Agent job is created.
When the subscription runs several things happen:
- The SQL Server Agent job fires and puts a row in the Event table
- The RS server service has a limited number of threads (2 per CPU) that poll the Event table
- When it finds an event, it puts a row in the Notifications table and
starts processing
So, from the snapshot you have provided, we can see that the subscription haven't run yet. the issue can be caused by many facotrs, it can be caused by the SQL Angent Job stoped or your SQL Sever Reorting Service is stoped at the time of the Last Run time,
it can also caused by someone changed the schedule time in the job like below:
Please try to find the details error message in the log file to help us better analysis about the root cause. The path of the log file like:(please find the correct date of the log file)
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles
Good blogs about troubleshooting of the subscription issue:
http://blogs.msdn.com/b/deanka/archive/2009/01/13/diagnosing-and-troubleshooting-subscriptions.aspx
http://blogs.msdn.com/b/deanka/archive/2010/02/16/troubleshooting-subscriptions-part-ii-using-the-report-services-trace-log-file.aspx
If you still have any problem, please feel feel free to ask.
Regards,
Vicky Liu
Other recent topics
