SCSM 2019 DW Install Error - An error occurred while executing a custom action:_CreateSrsFolder_SC

Alex Marsh 1 Reputation point

Having the above issue trying to install SCSM DW on a new 2019 server with SQL 2019 CU8 and Reporting Services 2019.
Full admin permissions provided to the reporting services instance for all accounts running SCSM DW services.
Timeout registry key set for the services on the server, made no difference and not seeing a timeout error in event logs.

At a loss to work out what the issue is causing the error. Any ideas?

Service Manager
Service Manager
A family of System Center products for managing incidents and problems.
209 questions
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Andreas Baumgarten 95,731 Reputation points MVP

    Maybe this is helpful:

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Andreas Baumgarten

    0 comments No comments

  2. Alex Marsh 1 Reputation point

    Found that article and followed all of the steps within it but still getting the issue

    0 comments No comments

  3. Alex Marsh 1 Reputation point

    After examining the setup logs I can see the following

    alling custom action ReportingCAManaged!Microsoft.Reporting.Setup.ReportingManagedCAs.CreateSrsFolder
    CreateSrsFolder: Report Server URL: http://<servername>:80/ReportServer
    CreateSrsFolder: Parent Folder:
    CreateSrsFolder: New Folder to create: SystemCenter
    CreateSrsFolder: full SRS URL: http://<servername>:80/ReportServer/ReportService2005.asmx
    CreateSrsFolder Error: System.Net.WebException : Unable to connect to the remote server

    I see the reporting services service start, stop, the failure occurs, then it starts again. I can browse to that URL on localhost and on the server name without issue

    0 comments No comments

  4. Andreas Baumgarten 95,731 Reputation points MVP
    0 comments No comments

  5. Alex Marsh 1 Reputation point

    Not sure what did it this time round but I started SSRS again during the install, used a different account and enabled named pipes which seems to have done the trick.