Error Message

DTRACE for EVDeployreports shows the following lines.

{RsHelper2005.PublishReports} Exception: System.Web.Services.Protocols.SoapException: An attempt has been made to use a data extension 'EVDataExtension' that is either not registered for this report server or is not supported in this edition of Reporting Services. ---> Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException: An attempt has been made to use a data extension 'EVDataExtension' that is either not registered for this report server or is not supported in this edition of Reporting Services.| at Microsoft.ReportingServices.Library.ReportingService2005Impl.ExecuteBatch(Guid batchId)| at Microsoft.ReportingServices.WebServer.ReportingService2005.ExecuteBatch() Info: Diag: Type:System.Web.Services.Protocols.SoapException ST: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)| at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)| at ReportingService2005_Proxy.ReportingService2005.ExecuteBatch()| at Symantec.EnterpriseVault.Reporting.RsHelper2005.PublishReports(String evInstallPath, ArrayList reportList, String folderPath) Inner:None

While implementing a Custom Deployment in SSRS using a custom Data Extension and modifying the SSRS config files to add the extension, prior to SSRS 2019, Reporting Services would recognize changes made to its config files and a restart of the Reporting Services was not required.

When custom deployments were done for SSRS 2017 and the earlier versions and SSRS config files were modified to include the custom extensions, Reporting Services would identify the modifications done to its config files and initiate an automatic restart of Reporting Services for the changes to take effect. When custom deployments are used with SSRS 2019, Reporting Service does not initiate recycling when the SSRS config files are modified.

There is a published Technote from Microsoft for the same https://techcommunity.microsoft.com/t5/sql-server-support-blog/difference-in-handling-config-file-changes-between-ssrs-2017-and/ba-p/3570839

Restarting SSRS 2019 service fixes the issue. Configuration of EV Reporting goes through successfully.