question

AnupriyaAthalye-5496 avatar image
0 Votes"
AnupriyaAthalye-5496 asked Joyzhao-MSFT edited

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

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.First[TSource](IEnumerable`1 source, Func`2 predicate)
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.ApplySelectExpand[T](T entity, ODataQuerySettings querySettings)
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
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@AlbertoMorillo could you please help me here..

0 Votes 0 ·
AlbertoMorillo avatar image
0 Votes"
AlbertoMorillo answered AlbertoMorillo edited

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
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for your reply!

Actually there is no change in SQL Server database. It is still pointing to the existing database. We have just installed reporting services on a new server as our old server got decommissioned.

In this case also will need to re-create the role?

0 Votes 0 ·

Yes, you need to create the ExecRole



0 Votes 0 ·
Joyzhao-MSFT avatar image
0 Votes"
Joyzhao-MSFT answered Joyzhao-MSFT edited

Hi @AnupriyaAthalye-5496 ,

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.


· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.


Thanks for your reply @Joyzhao-MSFT

In our case only reporting services instance has been installed on a new server (as our old SSRS server got decommissioned).
We have not made any changes to SQL Server Instance. We are using the same ReportServer14 database.

0 Votes 0 ·

These are the steps I performed for installation of new SSRS Server:

  • Open SQL Server Enterprise Edition Setup -- New SQL Server Standalone installation -- Perform a new Installation of SQL Server 2016 (selected default values)-- Feature Selection :

  • Database Engine Services

  • Reporting Services - Native

  • Reporting Services - Sharepoint

  • Reporting Services Add-in for Sharepoint Products

  • Data Quality Client

  • Client Tools Backward compatibilty

  • Client Tools SDK

  • SQL Client Connectivity SDK

On next windows for SQL Server added the service account -- Next -- Finish

0 Votes 0 ·

Reporting Services Configuration Manager -

  1. Connect to the Report Server Instance

  2. Service Account Tab -- Use another account -- Added service account credentials

  3. Web Service URL Tab -- Virtual Directory -- ReportServer -- all other values set to default

  4. Database Tab -- Change Database -- Use existing report server database -- selected the existing (old) SQL Server 2014) server name and selected already existing ReportServer14 DB. -- next entered Service Account Credentials and finished.

  5. Web Portal URL Tab -- Default values

  6. Email configured properly.

  7. Execution Account Tab -- Added Service Account Credentials

  8. Encryption -- Restored old SSRS server encryption key


When I open Webportal URL I am able to see all my report on report manager. All reports are working fine. When I got to manage and subscription tab of any report I get the reported error --

In our case SQL Server Instance and DB are the same as previous, do I still need to restore msdb? If yes from where do I need to restore it?

0 Votes 0 ·

@Joyzhao-MSFT I have put all the details here could you please help.

0 Votes 0 ·

Thanks for your feedback. To be honest, since we can’t check the status of your server in the forum, this type of issue is usually difficult to resolve. Just judging from the error log, it looks strange. I suggest you consider using the phone support service provided by Microsoft which can usually help you resolve your issue.
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
https://support.microsoft.com/en-us/supportforbusiness/productselection

0 Votes 0 ·