none
Installation of SQL Server 2019 Reporting Services RRS feed

  • Question

  • My question is about installing SQL Server 2019 Reporting Services. I have a valid SQL Server 2019 key which has successfully been used on an installation of SQL 2019. Using the same key, copied and pasted from not only the setup but also the ini file in x64 installation to preclude any typos, the install keeps asking me to restart the server in order to continue with the setup. This has been done numerous times without success. The SQLServerReportingServices.exe has been downloaded directly using the hyperlink in SQL Server 2019 installation package. I have also tried installing as Administrator and Domain Admin but no joy. The latest update for the SQL Server is CU5. Might I be missing something? 
    Tuesday, July 7, 2020 6:44 PM

All replies

  • Hi billmarmcswss,

    Could you please check the setup log to see if there are any error message?

    The setup log is in %temp% folder ->SSRS.

    For example:

    Best Regards,

    Amelia


    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.

    Wednesday, July 8, 2020 2:41 AM
  • There appears to be an issue with the load?

    [1CA0:1CE0][2020-07-08T07:47:20]w120: Detected partially cached package: SSReportingServicesSetup, invalid payload: SSReportingServicesSetup, reason: 0x80070570
    [1CA0:1CE0][2020-07-08T07:47:20]i101: Detected package: DotNetFx, state: Present, cached: None
    [1CA0:1CE0][2020-07-08T07:47:20]i101: Detected package: vc_redist.x64.exe, state: Present, cached: Complete
    [1CA0:1CE0][2020-07-08T07:47:20]i101: Detected package: SQLSysClrTypes.msi, state: Absent, cached: Complete
    [1CA0:1CE0][2020-07-08T07:47:20]i101: Detected package: adalsql.msi, state: Absent, cached: Complete
    [1CA0:1CE0][2020-07-08T07:47:20]i101: Detected package: SSReportingServicesSetup, state: Absent, cached: Partial

    This part keeps calling for a restart:

    [1CA0:1CE0][2020-07-08T07:47:46]e000: UnexpectedError: Burn engine encountered error. PackageId: , ErrorType: 5, ErrorCode: 350, Data: , ErrorMessage: No action was taken as a system reboot is required. , UIHint: 16
    [1CA0:1CE0][2020-07-08T07:47:46]i000: User: Error: : No action was taken as a system reboot is required.
    [1CA0:1CE0][2020-07-08T07:47:46]e000: UnexpectedError: setup failed for packageId: , package: , errorCode: 350, errorMessage: No action was taken as a system reboot is required.
    [1CA0:1CE0][2020-07-08T07:47:46]i000: Setup: A restart is required.
    [1CA0:1CE0][2020-07-08T07:47:46]i052: Condition 'RebootPending = 1' evaluates to false.
    [1CA0:1CE0][2020-07-08T07:47:46]e000: UnexpectedError: Bundle action failed: No action was taken as a system reboot is required (0x8007015E)
    [1CA0:1CE0][2020-07-08T07:47:46]i399: Apply complete, result: 0x8007015e, restart: Required, ba requested restart:  No

    I even tried an install package that we used last week on another sql server 2019 reporting service that was set up successfully last week, but is asking for restart also on the new 2019 server. I did forget to mention that the Windows 2019 server is a virtual machine, and the server set up last week is also a vm.

    Thank you.




    Wednesday, July 8, 2020 11:51 AM
  • Hi billmarmcswss,

    Could you please check the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager \PendingFileRenameOperation

    If it exists, you can try deleting or renaming this value and try set up again.  Please remember backing up the key first.

    In addition, please make sure the anti-virus software has been temporarily turned off.

    Best Regards,

    Amelia


    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.

    Friday, July 10, 2020 7:26 AM
  • Did that, still no joy. Trying to connect the SQL Server Mobile Report Publisher on the server itself with SPCSQLSRVR/Reports comes up with an error: Server error This server does not support mobile reports. The PendingFileRenameOperation key does not exist. I forgot to mention that the account signed in on the server is an administrator account. Thank you.
    • Edited by billmarmc Thursday, July 16, 2020 1:55 PM
    Thursday, July 16, 2020 1:54 PM