scom 2022 reporting services configuration issue

Question

question

RenePaquin-3677 asked May 11, '22 RenePaquin-3677 published May 12, '22

scom 2022 reporting services configuration issue

Currently upgrading my test scom environment from 2019 to 2022 and having issues with installing SCOm reporting services. I did install srss 2019 on the same sql 2019 server as the OperationsManager and DW databases. I have an account that si my data reader account but it is not recognized. I have gone through the various permissions and I feel that I have covered them all. What could I be missing?

Thanks,
Rene

msc-operations-manager

scom-issue.png (79.2 KiB)

5 |1600 characters needed characters left characters exceeded

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

Answer 1 · 2022-05-12T06:31:26.88Z

StoyanChalakov answered May 12, '22

Hi Rene,

do you use Group Managed Service Accounts or standard service accounts?
Can you please paste the relevant chunk of information from the Setup Log?

The path is: %LocalAppData%\SCOM\Log or by default c:\users\<UserName>\Appdata\Local\SCOM\Logs where <UserName> is the name of the user, who does the installation

Please scroll to the latest log entries and paaste whatever errors or exceptions you find there. We should be able to find a clue there.

Can you please also scroll quickly over the links, proovided in the following thread, maybe you wiil find something that you have missed:

Reporting Install fails - Data Reader account is not the same as in management group
https://social.technet.microsoft.com/Forums/en-US/f878f756-b483-489d-aa30-8999cb5e10cd/reporting-install-fails-data-reader-account-is-not-the-same-as-in-management-group?forum=operationsmanagerdeployment

Thanks in advance!

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

5 |1600 characters needed characters left characters exceeded

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

Answer 2 · 2022-05-12T07:40:41.757Z

SimonRenMSFT-3639 answered May 12, '22

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

1,May we know what version of SQL you are using? Operations Manager 2022 supports SQL 2019 with CU8 or later. Refer to the official article:
SQL Server Design Considerations

2,Similar threads for your reference:
SCOM 2012 Reporting installation issue
Deploying Reporting in the Multiple Server, Single MG - Stuck in Account Verification for Data Reader Account

Hope it helps. Thanks for your time.

Best regards,
Simon

If the response 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 |1600 characters needed characters left characters exceeded

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

Answer 3 · 2022-05-12T13:44:52.95Z

RenePaquin-3677 answered May 12, '22 RenePaquin-3677 published May 12, '22

Thanks for the responses. I am using SQL2019 with the latest CU. Here is the last little bit of the log. It appears that it cannot find he management server. This enry baffles me as I am entering in the fqdn of the management server.

[09:39:51]: Info: :Could not connect to Management Server: DEVSCOM01.local with exception: Threw Exception.Type: System.ApplicationException, Exception Error Code: 0x80131600, Exception.Message: We found 0 servers but expected only 1. This is a fatal error.

[09:39:17]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.

[09:39:17]: Error: :The management server specified would lead to an invalid scenario. Setup will attempt to find a valid scenario mgt server.

[09:39:17]: Info: :Server Installed:False InstallingNow:False

[09:39:17]: Error: :No Management Server property was provided and Setup could not find a valid Management Server. Please rerun setup with a valid management server.

[09:39:17]: Always: :Entering Page: InstallationLocationPage

[09:39:33]: Info: :Info:User specified valid installation path of: H:\OperationsManager

[09:39:33]: Always: :Entering Page: PrerequisitesProgressPage

[09:39:33]: Debug: :LoadPrerequisites: Start adding ComponentTitles

[09:39:33]: Always: :LoadPrerequisites: Start adding DataItems

[09:39:33]: Always: :memoryCheckTitle

[09:39:33]: Always: :ntfsCheckTitle

[09:39:33]: Always: :DriveSpaceCheckTitle

[09:39:33]: Always: :OSVersionCheckTitle

[09:39:33]: Always: :PowershellCheckTitle

[09:39:33]: Always: :DomainControllerCheckTitle

[09:39:33]: Always: :WindowsInstallerCheckTitle

[09:39:33]: Always: :PendingRebootCheckTitle

[09:39:33]: Always: :WinRMCheckTitle

[09:39:33]: Always: :RemoteRegistryCheckTitle

[09:39:33]: Always: :ClusteredServerCheckTitle

[09:39:33]: Always: :ActiveDirectoryCheckTitle

[09:39:33]: Always: :IsComputerNameValidTitle

[09:39:33]: Always: :SEViewerInstalledCheck

[09:39:33]: Always: :AVIcodeAgentCheck

[09:39:33]: Always: :MOMASPAgentInstalledCheck

[09:39:33]: Always: :IISCheckTitle

[09:39:33]: Always: :IISMetabaseCheckTitle

[09:39:33]: Always: :AspNetCheckTitle

[09:39:33]: Always: :WindowsAuthRoleCheckTitle

[09:39:33]: Always: :StaticContentRoleCheckTitle

[09:39:33]: Always: :DefaultDocumentRoleCheckTitle

[09:39:33]: Always: :DirectoryBrowsingRoleCheckTitle

[09:39:33]: Always: :HttpErrorsRoleCheckTitle

[09:39:33]: Always: :HttpLoggingRoleCheckTitle

[09:39:33]: Always: :RequestMonitorRoleCheckTitle

[09:39:33]: Always: :RequestFilterRoleCheckTitle

[09:39:33]: Always: :StaticContentCheckTitle

[09:39:33]: Always: :IsapiAllowedCheckTitle

[09:39:33]: Always: :IsAspNetIntegratedHandlerInstalledTitle

[09:39:33]: Always: :HttpActivationCheckTitle

[09:39:33]: Always: :LoadPrerequisites: Done adding prerequisites checks