2 Replies Latest reply on Feb 26, 2018 4:10 AM by katherinec

    Intermittent Error / Very slow Saving Report changes

    katherinec Apprentice

      Ivanti Service Manager 2017.2 Premise SQL 2014

      We are getting a common error when saving report changes. Is does not seem to prevent the changes from actually saving, however we have on occasion had SSRS report schedules go missing after making certain changes and wondering if it is related.

       

      Unhandled.png

       

      The SSRS log shows:

       

      library!WindowsService_49!74c!01/05/2018-02:07:09:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database.;

      schedule!WindowsService_49!74c!01/05/2018-02:07:10:: i INFO: Unhandled exception caught in Scheduling maintenance thread: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: There are two or more jobs named '621AF34D-B5D6-40D1-883A-812E8C06C1EA'. Specify @job_id instead of @job_name to uniquely identify the job.

       

      All report changes and schedules are made within the HEAT application - we have a lot of custom reports, with multiple report instances based on each template to go to different customers. It takes a very long time to save changes, and the SSRS log suggests that it's making a calls to all subscriptions with every change made (excerpt below - it runs on for 2-3 minutes):

       

      library!ReportServer_0-58!f7e8!01/08/2018-16:01:33:: i INFO: Call to GetSubscriptionPropertiessAction(9BA99D2B-2833-48BD-B7D5-AA36BE1FB083).

      library!ReportServer_0-58!f7e8!01/08/2018-16:01:33:: i INFO: Call to GetSubscriptionPropertiessAction(9BA99D2B-2833-48BD-B7D5-AA36BE1FB083).

      library!ReportServer_0-58!f6ac!01/08/2018-16:01:33:: i INFO: Call to SetSubscriptionPropertiesAction().

      library!ReportServer_0-58!f7e8!01/08/2018-16:01:33:: i INFO: Call to GetSubscriptionPropertiessAction(952B1679-BE58-48EE-8FEE-5C0334437D5A).

      library!ReportServer_0-58!f7e8!01/08/2018-16:01:33:: i INFO: Call to GetSubscriptionPropertiessAction(952B1679-BE58-48EE-8FEE-5C0334437D5A).

      library!ReportServer_0-58!f6ac!01/08/2018-16:01:33:: i INFO: Call to SetSubscriptionPropertiesAction().

      library!ReportServer_0-58!f6ac!01/08/2018-16:01:34:: i INFO: Call to GetSubscriptionPropertiessAction(7FD20951-619E-4C39-9681-EBE020D22962).

      library!ReportServer_0-58!f6ac!01/08/2018-16:01:34:: i INFO: Call to GetSubscriptionPropertiessAction(7FD20951-619E-4C39-9681-EBE020D22962).

      library!ReportServer_0-58!f7e8!01/08/2018-16:01:34:: i INFO: Call to SetSubscriptionPropertiesAction().

      library!ReportServer_0-58!f6ac!01/08/2018-16:01:34:: i INFO: Call to GetSubscriptionPropertiessAction(B83CD435-71D1-4CE3-B203-E43396B86A41).

      library!ReportServer_0-58!f6ac!01/08/2018-16:01:34:: i INFO: Call to GetSubscriptionPropertiessAction(B83CD435-71D1-4CE3-B203-E43396B86A41).

      library!ReportServer_0-58!f7e8!01/08/2018-16:01:34:: i INFO: Call to SetSubscriptionPropertiesAction().

       

      We also appear to have orphaned or duplicate SQL Agent jobs (with guid names) that belonged to HEAT reports at some point. I feel they will need cleaned up but would like to understand how they are being generated in the first place.

       

      We don't use SQL reporting for anything else in the business so i'm not overly familiar - has anyone else had similar issues with SSRS and a large number of custom reports in HEAT?