HELP!!! Cannot install SCOM 2012 R2 Reporting Server on my SQL server 2012 stand alone server

OK.  When I try to verify the SQL Server SCOM Reporting Services on the SQL Server standalone system is working correctly according to this article,  https://technet.microsoft.com/en-us/library/hh298611.aspx , I receive this error during the "Verify that Reporting Services is configured correctly" section of that article.

See attached pic for further details on the error.

Of course, this is after trying to install the SCOM Reporting Server on the SQL Server standalone system.
SQL-Server-SCOM-ReportingServices-Error.

According to the Reporting Services Configuration Manager on the SQL Server standalone system, everything seems configured correctly and working as should, but when I actually attempt to go to the web URL for the Reporting Services SCOM site that is when I receive that error as previously mentioned in the attached pic (screenshot).  

Of course, this is after attempting to install the SCOM Reporting Server on to the SQL Server standalone system.  I read another article that mentioned it would corrupt or stop the Reporting Services from working correctly after a failure install of the SCOM Reporting Server.  So, I guess this is expected now when I try to verify it.


I had read another article that mentioned something about the SSL being an issue when trying to install the SCOM Reporting Server on the SQL Server standalone system.  However, the SCOM is installed on a separate Windows Server 2012 R2 - Standard system from the SQL Server.  So, I am not sure how that all works/relates.

Also, the article mentioned something about if I am planning to use the SCOM management server web console to view reports then I need to install the Report Server on it NOT the SQL Server standalone system.  Is that correct?

OK.  I found where to rename the existing file that was never renamed back during the SCOM Reporting Server installation.  So, now the SQL Server Reporting Services (SSRS) is working again.

However, when I attempted to install the SCOM Reporting Server on the SQL server again, it failed or actually timed out.  It took probably close to 20 minutes or so before coming back with the failure and rolling back from the installation attempt.

So, how do I go about getting the SCOM Reporting Server installed on the SQL server.  It is the last major step before I am ready to use the SCOM in my production environment.


Please any help is greatly, greatly appreciated.


Thanks.

Nobody?

Anyone?  Please help?  I have the Web Service URL of the SCOM Reporting Services working, but the Report Manager URL is still not working.  However, I contribute that to the failure of the SCOM Reporting Server installation on the standalone SQL server (Windows Server 2012 R2 - Standard with SQL Server 2012 with SP2).

The SCOM server (Windows Server 2012 R2 - Standard with SCOM 2012 R2) is running IIS with SSL, but not required at the Default Web Site.  It is allowed and enabled on all the current virtual directories created (AppAdvisor, AppDiagnostics, MonitoringView, OperationsManager).

How can I resolve my issue of the failing of the SCOM Reporting Services installation on my standalone SQL Server?

No one?

I am not sure what to do now.  I have everything else installed , except the SCOM Reporting Server part and not sure how to accomplish it.

Thanks in advance.

Do you a single Server for all features of SCOM or do you have a Server by feature?
Do you a single Account for all features of SCOM or do you have an Account by feature?

Do you have a local SQL Reporting Services instance installed in the same Server for the Reporting Server feature?

Vitor,
Thank you for replying. I am going to try and answer your questions, but if I don't make it clear please just ask for further details.

I have a separate SQL server (Windows Server 2012 R2 - Standard with SQL Server 2012 / SP2) that is hosting the SCOM databases and Reporting services in a dedicated (named instance) but no default instance has been installed at this time because I was told that I didn't have to to install SCOM.  Both the SQL server and the separate SCOM server (Windows Server 2012 R2 - Standard with SCOM 2012 R2) running all the SCOM features except the Reporting Server feature along with IIS that is using a SSL self signed certificate are on the same domain.

The SCOM features / SQL databases have separate accounts for a best security approach to the initial installation.

I already installed successfully SCOM in my virtual test environment, but the only differences between my test and production SCOM environments is I didn't use SSL on my test environment and I originally installed SQL server as a default instance in my test environment. The rest I kept similar, like same features on SCOM test/production servers and reporting services / servers on test/production servers, using unique accounts to separate out, make more secure features, etc.

Any ideas, suggestions? Need further details?


Thanks again.

I think you did almost everything right. There's no difference about the MSSQL instances being named or the default.
The only thing I can recommend you is to install the SCOM Reporting Services in the same server of the SQL Server Reporting Services as I understood you don't have this configuration.

Vitor,
Thanks for the response. Yes, I am trying to install the SCOM Reporting Server services on the SQL Server that is hosting the Reporting Services, but it keeps failing whenever I attempt to install it on the SQL server using the SCOM 2012 R2 installation media.

How do I resolve this issue? Any other suggestions / ideas?

Thanks.

I'm sorry rsnellman but I don't have any idea why you're getting the error.
There's any installation log to check for more information? Or maybe in Event Viewer you can find something also.

Rats!!!  I was hoping someone could assist me.

Hmmm....now what do I do?

Did you check the logs for errors?

Yes, I did check logs for errors, but it didn't point to anything significant.

Thanks again anyways.

Anyone else?  I still cannot resolve this issue.  However, I did successfully install it in my test environment, but the only difference is I am using SSL (self-signed certificate) in my production environment.

Is there any issues or tricks/tips to installing SCOM using SSL, especially the SCOM Reporting Server features on the standalone SQL server?


Thanks.

I guess I need to wipe it away and start over.


Thanks for all your help though.

rsnellman, what do you want to do with this question?

I would like to find an answer, but not sure if there is one...I am sure there has be one out there somewhere.

You can always use the "Request Attention" button and ask for assistance. I'm sure they will re send this question to all available Experts so maybe someone will come with better solution.

Dear rsnellman,

To be able successfully help you resolve that issue I need to ask to upload SSRS Report Service log file.
You can find it in Reporting Services installation folder, most probably yours will look like:

C:\Program Files\Microsoft SQL Server\MSRS11.SCOM\Reporting Services\LogFiles

Select allOpen in new window

In case you need to anonymize your data please strip/edit unwanted lines off the log file or send log to me directly by private message.

Regards,
Daniel

Here is my log from the attempt to install SCOM Reporting Server services on the standalone SQL server.

Remember, I have a SCOM 2012 R2 virtual machine and a separate SQL server 2012 virtual machine that is hosting the Reporting Services, etc.

If you need any other logs, please just let me know and I will get them to you.



Thanks.
ReportServerService_09_23_2015_17_01.txt

Thanks Daniel.  

Yes, I located former copies of those files you mentioned based on another article I found which has the SSRS back up and running as expected.  However, I have attempted to install the SCOM Reporting Server services at least 3 times in the last few months with the same results.  So, I am familiar with the process to get the SSRS back up and running prior to each attempt of installing the SCOM Reporting Server services on the SQL server running the SSRS.

The http://SQLServer/ReportServer_SCOM service/page is working from the Reporting Services Configuration Manager / Web Service URL.


However, the http://SQLServer:80/Reports_SCOM service/page isn't working from the Reporting Services Configuration Manager / Report Manager URL.

(NOTE:  I am receiving the SQL Server Reporting Services Error (An internal error occurred on the report server.  See the error log for more details. (rsInternalError) message.)


Yes, I saw that the omdas account in the logs.  I have verified that the account is a member of the domain security group that is part of the local administrator group on each of the servers (SQL & SCOM).

However, I am wondering if I am missing a firewall port that needs opened or maybe just temporarily opened for the installation of the SCOM Reporting Server services to be successfully installed on the SQL server that is running the SSRS already.

Hi,

However, the http://SQLServer:80/Reports_SCOM service/page isn't working from the Reporting Services Configuration Manager / Report Manager URL.

Ok, by installing SCOM role you are giving SCOM server permissions to authenticate users (by implementing some dll's). Please verify whether account you're using to launch http://SQLServer:80/Reports_SCOM page has permissions in SCOM. Have you tried launching that address from browser started with elevated permissions (RunAs Aministrator option)?

I have verified that the account is a member of the domain security group that is part of the local administrator group on each of the servers (SQL & SCOM)

For completeness, account used for reporting must also belong to System Administrators group in the SQL Server itself.

ALTER SERVER ROLE [sysadmin] ADD MEMBER [domain\account | group];

Select allOpen in new window

Regards,
Daniel

OK.  I am no SQL guru.  How do I check/verify that the omdas user is part of the System Administrators group in the SQL server itself?


(I feel like we are now getting somewhere with this issue.)


Thanks.

No problem, we're here to help you out ;)
Login to your SQL Server thru SQL Server Management Studio (e.g. start->run->ssms.exe), then connect to your SQL Server instance. (you can follow this guide: https://msdn.microsoft.com/en-us/library/ms345332.aspx).
Next you can create new query window and execute xp_logininfo 'domain\username'; (change domain to your domain and username to your user)
or follow this: http://blog.sqlauthority.com/2008/12/27/sql-server-add-any-user-to-sysadmin-role-add-users-to-system-roles/

Regards,
Daniel

Also, I am not sure if it was previously mentioned but I have the SCOM system (IIS) setup for HTTPS.  Not sure if that may be playing a factor in this issue too or not, but thought it should be mentioned just in case.

OK.  If I open SQL Server Management Studio (SSMS) and the instance (SCOM).

Then expand the Security/Logins tree on the left and select (properties) of omdas account.

Go to the Server Roles page the only role that is checked is public.


Do I check the sysadmin too and that is it?

OK.  I think I figured it out based on your second link provided.

So, once I have verified that the omdas wasn't part of the sysadmin server role in the SQL server and then added it (checkmarking it), what next?

Recreate config files for SSRS (don't forget to restart SSRS) and retry installation of SCOM Reporting Role.

OK.  Refresh my memory on how to recreate the config files for SSRS.

Thanks again for all your awesome help.  Again, I feel like I am seeing the light at the end of the tunnel and cannot wait to be finished with this production installation of SCOM.

Review my Comment ID: 41268804.
Get to the location of Report Server

C:\Program Files\Microsoft SQL Server\MSRS11.SCOM\Reporting Services\ReportServer

Select allOpen in new window

and rename originally backed up rsreportserver.config and rssrvpolicy.conf files - they should have some number in the name (*.0, *.1, etc.).

Regards,
Daniel

Daniel,
OK.  There might be an issue.  I found the rsreportserver.config (2) backup file, but I do not have a rssrvpolicy.config backup file.  I wonder if that is part of the issue as to when I had the failures of installing the SCOM Reporting role on the SQL server and it broke the SSRS then when I performed the steps  you are mentioning the http://SQLServer:80/ReportServer_SCOM (Web Service URL) worked, but the http://SQLServer:80/Reports_SCOM (Report Manager URL) didn't.

OK.  I will give it a try tomorrow when I get back into the office.


I just checked the current code of the rssrvpolicy.config file and the only reference I could find was <CodeGroup> ..............Microsoft Operations manager Reporting Code Assembly....... </CodeGroup>


Is that what you are referring to to remove in case of another installation failure of the SCOM Reporting role on the SQL server?


Also, I have a folder on the SQL server that I guess is reminence of the prior attempts to installing the SCOM Reporting role on the SQL server.  The folder is Operations Manager and has a subfolder called Setup that hosts probably about 20 - 30 files like Microsoft.EnterpriseManagement.... application extension files and XML files.

Should I remove that Operations Manager folder prior to attempting the installation of the SCOM Reporting role again?



Thanks.

In case of failure during reinstall you can try to remove additional <CodeGroup> item. If you first back up that Operations Manager folder I think then you might have to delete it.
However, I would try to just reinstall first without removing anything.
Don't forget to ensure you're in local administrators group before installing anything :)

Good luck.

Regards,
Daniel

OK.  I tried to install it again and same results.  So, now I should try to remove all <CodeGroup> </CodeGroup> items referring to Operation Manager in the  rssrvpolicy.config file, correct?  Or is there another file too?


Thanks.

Hi,
Would be usefull to see current log. However you may try to proceed with last guidance.

Regards,
Daniel

Which log, I am more than happy to provide it, if I know which log you are referring to.  Whatever it takes to get this installation completed successfully.

I am starting to wonder if I should remove the SSRS part of the SCOM SQL database and reinstall it/configure it.  However, I am not sure if I will need to uninstall the SCOM server prior to doing that.


Let me know what log you are referring to and I will get that to you asap.


Thanks again.

Hi,
Reporting Service log, same as before, but current copy.

Daniel,
I apologize for the delayed response, but I was out for the holidays.

Here is the Reporting Service log as requested.



Let me know if you need anything else, as well as, what are my next steps/options.


Thanks in advance.
ReportServerService__11_19_2015_12_2.log

Hi,
Please try to recreate url registrations.

Confirm registered url's:

netsh http show urlacl | find "Report"

Select allOpen in new window

Delete SSRS url's:

netsh http delete urlacl http://+:80/ReportServer_SCOM/
netsh http delete urlacl http://+:80/Reports_SCOM/

Select allOpen in new window

Then start Reporting Services Configuration Manager, get to the Web service URL option and click Apply to register URL again.

After above is done try to browse both addresses.

Regards,
Daniel

I tried running the confirmation registered url's command you provided in PowerShell as Administrator and it responds with "FIND: Parameter formate not correct"

What am I doing wrong?

OK.  I ran netsh http show urlacl and it displayed all URL Reservations, which two of them were the SSRS SCOM ones.

Reserved URL                    : http://+:80/ReportServer_SCOM/
      User: NT SERVICE\ReportServer$SCOM
            Listen: Yes
            Delegate: No
            SDDL: D:(A;;GX;;;S-1-5-80-84406978-.....)

Reserverd URL                  : http://+:80/Reports_SCOM/
       User: NT SERVICE\ReportServer$SCOM
            Listen: Yes
            Delegate: No
            SDDL: D:(A;;GX;;;S-1-5-80-84406978-....)


Any ideas?

OK. I figured out what I did wrong, I ran your command via PowerShell instead of Command Prompt.

Command Prompt results:

Reserved URL               : http://+:80/ReportServer_SCOM/
         User: NT SERVICE\ReportServer$SCOM

Reserved URL               : http://+:80/Reports_SCOM/
         User: NT SERVICE\ReportServer$SCOM


Now I need to delete those URL's, correct?

OK.  I ran your other commands via Command Prompt to delete the existing registered URL's relating to the SCOM SSRS.  Then I opened up the SSRS Reporting Services Configuration Manager, but the Web Service URL and the Report Manager URL are still showing registered...the Apply button is grayed out.

Now what?


Do I need to stop and start the SSRS SCOM services?

Change anything on this screen and then set back to original value, then Apply button will work :)

E.g. delete port value and put it back again to 80.

Regards,
Daniel

OK.  I was able to reapply/register the URL's again.

However, when I opened the links ( http://SQLServer:80/ReportServer_SCOM & http://SQLServer:80/Reports_SCOM ), it failed again.

Reporting Services Error
The report server has encountered a configuration error. (rsServerConfigurationError)

SQL Server Reporting Services



Error
The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version.


Argh...it is getting frustrating.

OK.  Thanks Daniel.  If I decide to go with your second suggestion of removing the SSRS installation, restarating host, reinstall SSRS would I need to completely remove the SCOM role installations on the separate SCOM server or just focus on the SQL server?

Indeed, if SCOM has visible Reporting Server you should deinstall it. However, from this conversation, I think you don't have Reporting role installed and visible in SCOM mgmt.

Can you just confirm that after last attempt there are 'file not found' errors in the SSRS log? If so, it is tgrying to load security extension for SCOM which is missing or not properly registered. I believe you didn't have enough permissions during initial installation of SCOM role.

I would give it a try to start SSRS without loading those extensions (by removing additional <CodeGroup> elements from config)

Regards,
Daniel

OK.  I will try that first thing when I get back in the office tomorrow morning.


Thanks again for all your help.

OK.  Here is my SCOM Setup Wizard log.


Any other ideas what is the issue?


Thanks.
OpsMgrSetupWizard.log

OK.  I removed <CodeGroup> elements from the rssrvpolicy.config file.  I reverted back to an earlier copy of the reportserver.config file.  I recreated the SSRS database (ReportServerSCOM) within the Reporting Services Manager.  I restarted the system/ReportServerSCOM Reporting Services.

I then opened up the Reporting Service Manager and went to the Web Service URL and click the "Report Server Web Service URLs" hyperlink.  I entered the credentials (MyDoman\omdas).  It opened up fine within the IE browser.

However, when I went to the "Report Manager URL" Report Manager Site Identification and clicked on URLs: hyperlink, it failed with the same error as before "SQL Server Reporting Services Error" (An internal error occurred on the report server. See the error log for more details. (rsInternalError).


So, I think we are getting no where this route and probably would be faster if I just rebuilt the entire thing.  So, do you know if I need to uninstall the SCOM management server from the separate (SCOMServer) system prior to removing the ReportingServerSCOM database on the SQLServer within the SQL 2012 media then restart the SQLServer and reinstall the ReportingServerSCOM database?


Or should I just blow the entire SQLServer databases related to SCOM away and start completely over from scratch?


The sad/funny thing is I already got this up and running successfully in my virtual test environment months ago, but because it has been months ago, I cannot recall if I am missing a step during the production installation. However, the only difference between my successful virtual test environment installation and the virtual production environment is I made the IIS sites on the SCOMServer https rather than leaving it default of http like I did for the test environment.  Not sure if that is causing my issues or not, but I researched and couldn't find anything on it, which is why I reverted to the gurus here at Experts Exchange for further assistance.  Talk about being frustrated and defeated.  :-(


Thanks again for all your help so far.

Hi,

However, when I went to the "Report Manager URL" Report Manager Site Identification and clicked on URLs: hyperlink, it failed with the same error as before "SQL Server Reporting Services Error" (An internal error occurred on the report server. See the error log for more details. (rsInternalError).

This means that SSRS is still trying to load additional libraries which are missing or installed incorrectly, to confirm I need current SSRS log file.

You don't need to uninstall SCOM management server since it is working fine. The SCOM role shouldn't be visible as installed. Therefore I think you may try to remove SSRS and reinstall it back again.

You configured SSL for access to SCOM webconsole as far as I'm concerned. I verified OpsMgrSetupWizard.log file you posted. It seems that your first error was due to failed connection with SQL Server. I'm unsure why installer didn't restore SSRS config but this cause SSRS to fail. I still think that correcting SSRS is crucial at this task. You can do it either by fixing config file(s) or reinstalling SSRS (uninstall it first).

Regards,
Daniel

OK.  I will try uninstalling and reinstalling the SSRS tomorrow when I am back in the office.


Thanks again for everything.

Oh, one other thing I forgot to mention that I did differently when installing the test virtual environment and production virtual environment of SCOM 2012 R2.

In the test SCOM, I installed the SQL Server from scratch as a default instance then added the SCOM instance (databases (SCOM & Reporting Services/Server).)

With the production SCOM, I installed the SQL Server from scratch without a default instance and just created the custom instance of SCOM with the Reporting Services/Server databases.


So, now if I try to uninstall the Reporting Services on the SCOM database it is greyed out and will not let me select it to uninstall it.  Not sure what I am doing wrong. Of course, I am no SQL guru either, so that could be a factor too.

Any ideas?

OK.  Scratch the issue I mentioned of it being greyed out...I was using the media to try and uninstall SQL features when I needed to go to Programs & Features to uninstall from.  (NOTE: You will still need the media in the optical drive prior to this too.)


With that being said, do you think the differences of the way I installed the SQL server instances of SCOM amongst my test & production environment could be playing a factor in my current SCOM Reporting Server role installation issues?


Thanks.

OK.  I was able to uninstall the current SSRS for my SCOM database.  However, it left the folder D:\Program Files\Microsoft SQL Server\MSRS11.SCOM

Should I manually remove / delete that folder (MSRS11.SCOM) before restarting the SQL server and attempting to reinstall a fresh copy of the SSRS for the SCOM database on the SQL server?

Hello,
I don't think using named instances is causing any problems for either SCOM server database or SCOM Reporting Role. In my environments we have

Please note that I've found additional lines which you may need to remove from installed SSRS to remove security extensions. These lines are in rsreportserver.config file. Sorry, I missed them initially :/

<Security>
    <Extension Name="Windows" Type="Microsoft.EnterpriseManagement.Reporting.Security.GroupAuthorization, Microsoft.EnterpriseManagement.Reporting.Security">
        <Configuration>
            <Connection>
                <ServerName>your SCOM server name</ServerName>
            </Connection>
        </Configuration>
    </Extension>
</Security>
<Authentication>
    <Extension Name="Windows" Type="Microsoft.EnterpriseManagement.Reporting.Security.GroupAuthentication, Microsoft.EnterpriseManagement.Reporting.Security">
        <Configuration>
            <Connection>
                <ServerName>your SCOM server name</ServerName>
            </Connection>
        </Configuration>
    </Extension>
</Authentication>

Select allOpen in new window

Regards,
Daniel

Thanks Daniel.  No problem missing those lines in the rsreportserver.config file.  I am just tickled that someone is helping me resolve this issue.


As for removing those lines, does it really matter now that I have the SSRS native completely removed from the SQL server?

Should I just remove the entire folder (MSRS11.SCOM) containing those config files and all?

In case your SSRS is no more you don't need to bother these lines. You may remove whole folder if uninstall succeeded, in case of any errors you can zip it and keep until installation of SSRS is completed successfully again.

Regards,
Daniel

OK.  Great idea.  I have successfully reinstalled/recreated the SSRS SQL server database for my SQL Server SCOM database.  I was able to verify both URL links worked.  Now I am in the process of making a snapshot (checkpoint) of the VM state before proceeding with installing the SCOM Reporting Server role on the SQL server VM.  Then I will try to install the SCOM Reporting Server role on the SQL server VM and report back my findings/results.  No pun intended.  :-)

Thanks again for all your help so far.  I think we are very close to resolving this issue and as usual, I couldn't do it without the guru's like yourself on Experts Exchange.

OK.  I have discovered a discrepancy between my testing SCOM installation and my production SCOM installation.  There is a MyDomain\SQLServiceSCOM account.  This account is present in the testing SCOM SQL database, but not the production SCOM database.

Not sure, cannot recall, if it is because the SCOM Reporting server role that was successfully installed on the testing environment and not the production environment or something else.

I am sure that I used the MyDomain\omdas account for the data reader & writer for the SCOM Reporting server role installation for the testing environment.

I just cannot recall where or for what the MyDomain\SQLServiceSCOM account is being used for at the moment.

Hello,
I'm not sure either. Basing on information posted here only account you needed to add manually to SQL Server was MyDomain\omdas account. Since you already did that, only thing before another attempt to install SCOM role is to save copy of SSRS configuration files (installer should create such copies, but to be 100% sure just copy them).

Regards,
Daniel

OK.  A little more information about the MyDomain\SQLServiceSCOM account.

The production environment does have it present in the SQL server instance found under the Security\Logins like the testing environment.  However, the differences are in the accounts User Mapping section.  The testing environment has the following settings under the User Mapping:

Map              Database                    User                                                             Default Schema
checked       master                        Contoso\SQLServiceSCOM                 Contoso\SQLServiceSCOM
unchecked   model                          blank                                                           blank
checked        msdb                          Contoso\SQLServiceSCOM                Contoso\SQLServiceSCOM
unchecked   OperationsManager     blank                                                        blank
unchecked   OperationsManagerDW      blank                                                 blank
checked       ReportServer$SCOM     Contoso\SQLServiceSCOM              Contoso\SQLServiceSCOM
checked       ReportServer$SCOMTempDB   Contoso\SQLServiceSCOM  Contoso\SQLServiceSCOM
unchecked  tempdb                            blank                                                         blank


And the production SQL server does not have these settings in the User Mapping of the MyDomain\SQLServiceSCOM.  It has all the rows as mentioned, but they are all blank.


Also, if I view the Schemas for the databases, the testing SQL server instance has the Contoso\SQLServiceSCOM there, but the production SQL server instance doesn't have the MyDomain\SQLServiceSCOM account in as a Schema option.


Not sure how to make the production SQL server instance reflect my testing SQL server instance, but I did notice that difference.  Maybe it will help you shed some more light on my issue(s).


Thanks again.

I think this account is for SSRS service account. Perform configuration of SSRS using Reporting Services Configuration Manager, during configuring database part choose to use service account to connect to database. Then you should see additional account on the list with correct permissions.

I was wondering about that...more research/investigating on the testing environment SQL server SCOM instance revealed that the Contoso\SQLServiceSCOM account isn't seemingly being used by the SQL Server SCOM SSRS, but rather the Contoso\omdas account.  Reason I say that is when I view the details in the Reporting Services Manager under Service Account, Execution Account and Database they display the Contoso\omdas account.

So, now I am not so sure of this mystery Contoso\SQLServiceSCOM account other than maybe it was created during the initial installation of the SSRS for the SCOM instance then I switched it over to the omdas account, maybe?

Either way, once I have created the snapshot/checkpoint of the SQL server, copied the SCOM SSRS folder....is there anything else I should backup/copy before attempting the SCOM Reporting server role on the SQL server again?

NOTE: I have verified the SQL server SCOM instance SSRS is working as expected via Reporting Services Configuation Manager (Web URL & Report Manager URL) after the reinstallation of the SSRS.

Hello,
If all prerequisites are met (I mean Kevin Holman's blog post in your initial post here) and you are running setup using account which is member of OMAdmins group, has local Administrator privileges, has sysadmin SQL privileges; SQL and SSRS are up and running all should be fine :)

Regards,
Daniel

OK. Thanks.  I will proceed forward then.  One last quick question, how would I create/add a domain account to a SQL instance as if I added it to the SQL Server - Database Engine Configuration - Server Configuration - SQL Server administrators installation?

Please refer to attached screenshot for further details.

(NOTE: I know it is for my VMM SQL database/instance install, but unfortanutely I didn't do screenshots of my SQL server database/instance installations of the SCOM, which was the first production install, but rather remembered to do it during my VMM SQL database/instance install.  However, the installation is very similar to the SCOM and VMM.)

Just was wondering.


Thanks.
SCVMM-SQL_Installation-Database_Engi.jpg

You posted screen from SQL Server installer, now to add an account to SQL just start SQL Server Management studio and connect to your SQL Server instance. Then open Security, right click Logins and choose New login. In the next window write down your account (you can search for it also there) and switch into Server Roles and/or user mapping to grant permissions.

However for now you shouldn't grant permissions to any accounts besides one which you are using to install the software. All permissions will be granted during install process. So, account which you are logged on must have OMAdmin permission, local Administrator permission and SQL Server sysadmin permission.

Regards,
Daniel

OK.  I have verified that the MyDomain\omdas account is a part of the MyDomain\OMAdmin security group.  Also, confirmed that the MyDomain\OMAdmin security group is part of the local administrator group of both the SQL server and SCOM management server.

However, the MyDomain\omdas account isn't part of the SQL Server sysadmin rights, but rather the MyDomain\SQLServiceSCOM account has it along with public server role.

So, just to make sure, should I add the MyDomain\omdas account to the SQL Server sysadmin server role prior to installation attempt of the SCOM Reporting Services again?

I noticed that is the difference between my testing SQL Server for SCOM and production SQL Server for SCOM.

Also, the other reason I am asking is the MyDomain\SQLServiceSCOM account is the one being used to run (Logged on as) the SQL Server SCOM instances (SQL Server (SCOM) and SQL Server Agent (SCOM), but the SQL Server Reporting Services (SCOM) is Logged on as MyDomain\omdas.

So, I am guess what I am trying to figure out is when I go to install the SCOM Reporting Server role on the SQL server, which domain account should I be using when it asks for the Data Reader account at the Configure Operations Manager accounts window?

MyDomain\omdas

or

MyDomain\SQLServiceSCOM

HOLY TOLEDO!!!  It worked.  I finally was able to successfully install the last part to the SCOM server roles (Reporting Server).  Thank you, thank you, thank you.  I have been working on and off on this since April.  I am just so relieved and excited that I am not sure what to do next.  LOL


So, it seems that the solution was to uninstall/reinstall the SSRS part for the SCOM instance on the SQL server.


Thanks again Daniel.  I couldn't have done it without your assistance.


Have a great day and amazing holidays.  Merry Christmas.