none
Upgrade Issues for SSRS 2016 RRS feed

  • Question

  • After the Reporting Services upgrade from 2012 to 2016 we started receiving errors like below. 

    Old Environment was on Windows OS 2012 r2 and SQL 2012

    New environment was Windows os 2016 and SQL 2016


    The report server encountered an unhandled exception in HttpApplication. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeClientDisconnectionException: A client has disconnected from the Report Server Web service application domain ReportServer_MSSQLSERVER_0-1-131878938927461910. No corrective action is required. An error code has been submitted to ASP.NET to release the connection. The error code is 800708CA. ---> System.Runtime.InteropServices.COMException: This network connection does not exist. (Exception from HRESULT: 0x800708CA)

    e ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: , Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> System.InvalidOperationException: Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.

    Things we did

    <g class="gr_ gr_1018 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="1018" id="1018">In-place</g> upgrade didn't work so we did a side by side with name swapping so that Web URL doesn't change

    Users are complaining they are getting max pool timeout errors. After we reviewed the logs we see a lot of the above errors. We have tried below options

    Increased timeout setting for Data source. Increase memory, CPU. 

    Since we got all the ASP.Net 3.0 errors  have tried repairing the .net framework on windows os box. which didn't help

    However after restarting the services reports are running fine. This looks to me as a memory issue. Any help?

    Thanks




    • Edited by Reddy435 Wednesday, November 28, 2018 8:01 PM
    Wednesday, November 28, 2018 6:35 PM

All replies

  • Hi Reddy435,

    I am not sure which factors cause this: network connection, timeout , memory, max pool setting or service didn't work successfully.

    It seems that your service now is working correctly, right? You could try to reset above setting to see whether this caused by memory. 

    You could refer to this post and this post for details.

    Best Regards,
    Zoe Zhi


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Reddy435 Thursday, November 29, 2018 8:43 PM
    • Unmarked as answer by Reddy435 Thursday, November 29, 2018 8:43 PM
    Thursday, November 29, 2018 2:06 AM
    Moderator
  • We made setting changes to all of it. Bumped up memory from 12 gb to 64GB. Moved those report server and report server tempdb to a dedicated server, performed a network trace to see connection timeouts. Looked for number of connections at peak hours. 

    Nothing helped we see mostly those ASP .Net errors logged every few minutes. 

    Thanks

    Vamshi


    vamshi

    Thursday, November 29, 2018 8:45 PM
  • Hi Reddy435,

    I want to confirm whether SSRS in new environment work or not. In addition, I saw that your environment was been changed to windows OS 2016, and you use SQL SERVER 2016. I want to know how you upgrade SSRS, in-place upgrade? Or Migrate report server?

    Best Regards,
    Zoe Zhi


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, December 3, 2018 5:48 AM
    Moderator
  • Build a new vm, migrate the report server dbs. Keep the ip's and report url same(DNS name swap)

    vamshi

    Saturday, December 15, 2018 12:43 AM