This blog post will be a short one and will be focused on a particular problem I faced while installing the SCOM reporting services for System Center Operations Manager (SCOM) 2022.
Backstory:
I have already successfully installed System Center Operations Manager 2022 and was preparing to install the last infrastructure component – Reporting Services. As you all know, the SCOM reporting services installation consists of two logical parts – SQL Reporting Services and SCOM Reporting Services.
So as always, I started with the installation of SQL Server 2022 Reporting Services and after it completed successfully, I did the basic configurations, tested the Web Service and Web Portal URLs before proceeding with the installation of the SCOM reporting services role.
Issue:
I started the installation (elevated as always), and went ahead to grab a cup of coffee, but to my surprise when I got back, I noticed that the installation has failed and the rollback was in progress. It happens sometimes that I overlook things, so in this case I automatically assumed that I had missed something, so I uninstalled SSRS, cleaned up and did the installation again. To my disappointment, shortly after starting the SCOM reporting installation, it failed again.
Error:
As always when troubleshooting a failed installation, I start with the setup logs. Here is what I found in the setup log (OpsMgrSetupWizard.log, located under C:\Users\<UserName>\Appdata\Local\SCOM\Logs):
[15:10:20]: Error: :ModifySRSServiceAccount failed.: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message:
[15:10:20]: Error: :StackTrace: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingConfigurationHelper.ReportingConfiguration.ModifySRSServiceAccount(String userName, String userPassword, String sqlSRSServer, String srsServiceName, String sqlServerForSRSDatabase, String srsDBName)
[15:10:20]: Warn: :Message:SetSRSSecurity Exception Exception: . Will retry..
[15:10:20]: Debug: :Now Sleeping for : 60000 milliseconds
[15:11:20]: Debug: :More: 4 rety to go..
[15:11:20]: Info: :Attempting to get the SSRS version from: \\Servername\Root\Microsoft\SqlServer\ReportServer\RS_SSRS:__NAMESPACE
[15:16:20]: Error: :ModifySRSServiceAccount failed.: Threw Exception.Type: System.InvalidOperationException, Exception Error Code: 0x80131509, Exception.Message: Cannot stop SQLServerReportingServices service on computer ‚.‘.
[15:16:20]: Error: :StackTrace: at System.ServiceProcess.ServiceController.Stop() at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingConfigurationHelper.ReportingConfiguration.ModifySRSServiceAccount(String userName, String userPassword, String sqlSRSServer, String srsServiceName, String sqlServerForSRSDatabase, String srsDBName)
[15:16:20]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131509, Exception.Message: The service has not been started
[15:16:20]: Error: :InnerException.StackTrace:
[15:16:20]: Warn: :Message:SetSRSSecurity Exception Exception: Cannot stop SQLServerReportingServices service on computer ‚.‘.. Will retry..
So looking at the errors you will immediately assert that the error messages and exception are versatile:
- ModifySRSServiceAccount failed.: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057
- Message:SetSRSSecurity Exception Exception: . Will retry..
- ModifySRSServiceAccount failed.: Threw Exception.Type: System.InvalidOperationException, Exception Error Code: 0x80131509, Exception.Message: Cannot stop SQLServerReportingServices service on computer ‚.‘.
- Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131509, Exception.Message: The service has not been started
- Message:SetSRSSecurity Exception Exception: Cannot stop SQLServerReportingServices service on computer ‚.‘
So immediately after seeing those, I knew I would not recognize the cause for the failed installation from the logs, so as I usually do I did a quick internet search. After some searching, I found a reddit post, answered not by whoever it is, but by Kevin Holman himself. Although the post initially described another issue („Can’t install SCOM 2022 on 2022 OS and SQL“), it contained a valuable piece of information, which helped me resolve resolve the issue:
Can’t install SCOM 2022 on 2022 OS and SQL
https://www.reddit.com/r/scom/comments/1cow3bf/cant_install_scom_2022_on_2022_os_and_sql/
In the post Kevin Holman mentions that the error message:
„:PopulateUserRoles: failed : Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057“
might relate to a bug in SSRS 2022 version 16.0.1115.92, which seems to be incompatible with the SCOM Reporting Services setup. Although in my case, the error was slightly different („ModifySRSServiceAccount failed“, instead of „PopulateUserRoles failed“ :
„:ModifySRSServiceAccount failed.: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057“
I decided to verify this and checked the version of my SSRS 2022 setup.
[15:00:13]: Info: :Attempting to get the SSRS version from: \\Servername\Root\Microsoft\SqlServer\ReportServer\RS_SSRS:__NAMESPACE
[15:00:14]: Debug: :Path is \\S801640A\Root\Microsoft\SqlServer\ReportServer\RS_SSRS\V16:MSReportServer_Instance
[15:00:14]: Always: :SRS instance on Servername SSRS. Version .
[15:00:14]: Info: :Info: Servername\SSRS SRS version = 16.0.1115.92
So immediately I went ahead and got another version of the SSRS 2022 and this time, the installation completed successfully.
Summary:
To summarize, while installing SCOM 2022 Reporting Services with SQL Server Reporting Services (SSRS) 2022, I encountered issues due to an incompatible SSRS version. By switching to a different SSRS version, I successfully completed the installation without further problems.