Subscription Failures

  • Subscription Failures

    Posted by DSC Communities on June 11, 2019 at 3:40 pm
    • LaDonna Stephens

      Member

      June 11, 2019 at 3:40 PM

      We just upgraded our Report Server to the January Version from SSRS 2005(made the hop to 2008 then to the latest version). Now some of our subscriptions are failing to run correctly and I have not been able to determine what is causing the errors. We have subscriptions that send emails, use our own delivery extension and save to a file share. There is no pattern that I can find as to which ones are failing. We even have cases where the report has mutliple subscriptions an only some of them fail.

      I have been trying to google and research this issue, but have only found references to fixes that were needed in the August release, but the issue was supposed to have been fixed in the January release.

      I have tried resaving the reports to the report server, and that has worked for a few of the subscriptions, but not all of them.

      Each report that fails shows the following two errors in the log:

      e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Unable to load assembly Microsoft.ReportingServices.Cloud.DataExtensions, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.ReportingServices.Cloud.DataExtensions’ or one of its dependencies. The system cannot find the file specified.

      e ERROR: Exception caught instantiating DAX report server extension: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.ReportingServices.Cloud.DataExtensions’ or one of its dependencies. The system cannot find the file specified.

      ——————————
      LaDonna Stephens
      Sr Software Developer
      Dallas TX

      ——————————

    • Hasham Niaz

      Member

      June 12, 2019 at 12:58 AM

      Hi,

      As a best practice when you migrate from 1 version to other, you check these report subscriptions manually to verify they are transferred properly & running as well.

      When you transferred reports from 1 version to another, some of the report GUID gets broken & that’s the reason why those subscriptions are not triggered because in new version they have a new GUID and subscriptions table have old GUID.

      You can try creating a query to check GUID between subscription table & report table in [ReportServer] database to see what are the GUID’s which are unavailable in reports table.

      If no. of report subscriptions are low you can set those up manually.

      Hope this will help you get started in the right direction.

      Regards,

      ——————————
      Hasham Bin Niaz
      Director Data & Analytics
      Karachi, Pakistan
      ——————————
      ——————————————-

    • LaDonna Stephens

      Member

      June 12, 2019 at 12:55 PM

      Thanks for the suggestions.Ā  Datasources and everything are good as the reports run just fine.Ā  I’ve also been using the Catelog and Subscription tables to monitor the for failures, so I know that they are all tying together correctly.

      The interesting part is a subscription will fail.Ā  We can select it, click Run Now and it will fail again.Ā  Without making any change at all to the subscription, report, etc we select and hit Run Now again and the subscription fires successfully.Ā Ā 

      I have tried deleting a report from the server and republishing it and resetting up subscriptions, still seeing failures on say 2 or the 3, but when you run a second time the ones that failed succeed.Ā Ā 

      Hard to track down an issue with you can’t get consistent results!

      ——————————
      LaDonna Stephens
      Sr Software Developer
      Dallas TX
      ——————————
      ——————————————-

    • Michael Foss

      Member

      June 12, 2019 at 9:51 AM

      I would suggest verifying your datasource credentials are accurate on the reports that are failing. Also verify subscriptions are enable, lastly double check any default parameters or parameters that are set on the report. ?Also make sure you have a service account associated to the report server in the report server manager.

      ——————————
      Michael Foss
      Functional/Business Systems Analyst
      ——————————
      ——————————————-

    DSC Communities replied 6 years, 2 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Subscription Failures’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!