SSRS 2016 Subscription Issue - Not able to see existing subscription after migration to 2016 - Error Something went wrong please try again later.

Anupriya Athalye 1 Reputation point
2021-10-12T09:17:44.743+00:00

Hi have upgraded my Reporting Services server to 2016. However it still points to the old SQL Server Database (SQL 2014).

I am able to see all the reports. Everything is working fine except I am not able to see my existing subscriptions. Whenever I try to open the Subscription page it gives error - "Something went wrong please try again later."

I checked the log file (ReportServerService__10_12_2021_04_42_59 ) and it gives the following error -

library!ReportServer_0-1!f48!10/12/2021-04:44:08:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedNativeModeException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedNativeModeException: This operation is not supported on a report server that runs in native mode.;
schedule!WindowsService_0!f34!10/12/2021-04:45:02:: i INFO: Handling event with data: TimeEntered: 10/12/2021 04:45:02, Type: Event, EventType: TimedSubscription, SubscriptionID: 0d5698c7-bbdd-4948-81ef-eb9fc83ce930.
library!WindowsService_0!f34!10/12/2021-04:45:03:: i INFO: Schedule 80d86f6f-69ac-4587-b4bd-b125cc01178a executed at 10/12/2021 04:45:03.

Another log file (Microsoft.ReportingServices.Portal.WebHost_10_12_2021_04_43_00) gives this error -

Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!11!10/12/2021-04:44:08:: e ERROR: [wnivykk5]: OData exception occurred: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Sequence contains no matching element
at System.Linq.Enumerable.FirstTSource
at Microsoft.ReportingServices.Portal.Repositories.SystemService.PopulateLocalizedExtensionNames(IPrincipal userPrincipal, List`1 subscriptions)
at Microsoft.ReportingServices.Portal.Repositories.CatalogItemRepository.GetSubscriptions(IPrincipal userPrincipal, String itemPath)
at Model.ReportRepository.LoadSubscriptions()
at Model.Report.get_Subscriptions()
at lambda_method(Closure , ReportRepository )
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Web.OData.Query.Expressions.SelectExpandBinder.Bind(Object entity)
at System.Web.OData.Query.SelectExpandQueryOption.ApplyTo(Object entity, ODataQuerySettings settings, IAssembliesResolver assembliesResolver)
at System.Web.OData.Query.ODataQueryOptions.ApplySelectExpandT
at System.Web.OData.Query.ODataQueryOptions.ApplyTo(Object entity, ODataQuerySettings querySettings)
at System.Web.OData.EnableQueryAttribute.ExecuteQuery(Object response, HttpRequestMessage request, HttpActionDescriptor actionDescriptor)
at System.Web.OData.EnableQueryAttribute.OnActionExecuted(HttpActionExecutedContext actionExecutedContext)
at System.Web.Http.Filters.ActionFilterAttribute.OnActionExecutedAsync(HttpActionExecutedContext actionExecutedContext, CancellationToken cancellationToken)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext().
Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!11!10/12/2021-04:44:08:: i INFO: [wnivykk5]: 10.158.159.179: GET /api/v1.0/CatalogItemByPath%28path%3D%40path%29 - Response 500 - 0:00:38.1523916

Kindly help!

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,790 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alberto Morillo 32,806 Reputation points MVP
    2021-10-12T14:32:31.457+00:00

    Please make sure RSExecRole has permissions for the Agent SPs, and tables in master and msdb databases. When you move a report server database to a new or different SQL Server Database Engine, must re-create the role in the Master and MSDB system databases.

    Is SQL Server Agent running?

  2. Joyzhao-MSFT 15,566 Reputation points
    2021-10-13T02:18:13.68+00:00

    Hi @Anupriya Athalye ,

    However it still points to the old SQL Server Database (SQL 2014)

    Uninstall the previous version of Reporting Services if you no longer need it. This step does not delete the following items, but you can manually remove them if you no longer need them:

    1. The old Report Server database
    2. RsExec role
    3. Report Server service accounts
    4. Application pool for the Report Server Web service
    5. Virtual directories for Report Manager and the report server
    6. Report server log files

    Did you configure the report server after the migration? Can a new subscription be created after migration? Please check the following migration and installation steps：Migrate a Reporting Services Installation (Native Mode).
    When you migrate an SSRS instance from one server to another, unless you also restore msdb those subscription jobs won't be coming with you. The subscriptions still exist in your ReportServer database.

    You also need to check whether your SQL Sever Agent is running and whether it is still executing the subscription plan.
    Best Regards,
    Joy

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.