Report Subscription Running Twice if not completed within 30 minutes

Aidan Grant 1 Reputation point
2020-08-17T13:33:45.027+00:00

I have an SSRS subscription which is meant to run once at 6:45 am. It normally takes just a few minutes to process, but occasionally (often on Monday mornings when the server is very busy) it takes over half an hour. When this happens, the report executes again after half an hour, meaning that eventually duplicate reports are sent out.

I've checked the Job, and it only has history of running once, at 6:45, duration 0 seconds, as is normal for SSRS jobs.

Looking in dbo.ExecutionLog I can see both exectuions, at 6:45 and 7:15.

So it looks like the SQL agent isn't doing anything wrong, and the issue lies with the report server's handling of the dbo.AddEvent command?

I've looked for other subscriptions which can take over half an hour and they do not send out a second report in the way this one does, so it appears to be specific to this one.

No idea where to look next!

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,798 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Joyzhao-MSFT 15,566 Reputation points
    2020-08-18T03:41:51.717+00:00

    Hi ,
    According to your description, your report subscription running twice if not completed within 30 minutes, Right?
    If you have one subscription failed to send at the proper time and it have delayed, it may be send at the next time.

    Does the report server run in SharePoint integrated mode or native mode?
    If in SharePoint integrated mode, it might be related to the recycling of the Application Pool of the SharePoint site.
    If in native mode, it might be caused by the lock caused by the concurrent processing of subscriptions and notifications.

    When a scheduled operation is defined, the report server creates a corresponding job in SQL Server Agent and runs the job on the date and time specified in the schedule. If somebody run the subscription manually after the job executed, the users can got two emails, so please make sure the subscription isn’t run manually during the time by someone.

    The SQL Server Agent service calculates an incorrect NEXT_RUN_TIME value for the job. Therefore, the job does not always run at the correct times. This issue occurs because an error causes a date value to be changed unexpectedly, the date value is used to calculate the NEXT_RUN_TIME value. If you got the subscription execute twice many times, please edit reset the subscription.
    Regards,
    Joy

    0 comments