SCOM 2012 SP1 Reporting Services empty

Hello,
When i open Reporting from management console, reporting work space empty, but when i turn off windows firewall (Windows 2008R2 SP1) on my SQL server 2008 R2 SP2 i can see all MP/Data in Reporting action panel.
I've opened these ports :
1433/TCP, 1434/UDP, 5723/TCP, 137/UDP, 138/UDP, 139/TCP, 445/TCP,135/TCP,
But it did not help.
What is the configuration of the firewall for Reporting Service?

Hello !
Could you check this post please :
http://social.technet.microsoft.com/Forums/en-US/c219058f-d10d-48ca-8a61-ca9f1340bfdb/scom-2012-empty-reporting-workspace?forum=operationsmanagergeneral
Hope this helps.
Note: This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights. Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and
recognises useful contributions.

Similar Messages

SCOM 2012 SP1 Report Timed out

Hi All,
My large reports are timing out after 30 minutes in SCOM 2012 SP1, with the error: The Operation has timed out
I'm trying to run the Performance Detail report from Microsoft Generic Report Library against Windows Server 2008 Operating System group (1400 servers) for last 1 year for Percent memory used. I can run the same report for Windows Server 2012 Operating System
group (200 servers) sucecssfully.
I've already verified and configured the reporting services for reports to not time out.
http://www.systemcentercentral.com/forums-archive/topic/scom-reports-large-reports-time-out/
http://anoopcnair.com/2011/07/20/configmgr-sccm-sql-server-reporting-service-timeout-expired/
Any suggestions?
Thanks,
Harry
Thanks, Harry :-)

Hi There,
Based on my knowledge, When ever a SQL query is ran against any database the query output is executed and stored in TempDB and then it is shown to your SSMS or reporting application.
So i would suggest you check the size of the temp SQLDB and see if auto growth is enabled for that and does your drive as well have enough space to hold that temp DB in its local drive if the DB grows its self.
As querying 1 years data for 1400 servers is a huge data and requires lot of time and space.
I had a similar issue here, Look here:
https://social.technet.microsoft.com/Forums/en-US/6420f4e1-fc21-49c9-8fed-eddbe6cecabf/my-sql-server-seems-to-be-creating-huge-tempdbmdf-file-post-database-migration?forum=sqlservermigration
Gautam.75801

SCOM 2012 R2 Reporting Services High Availability Configuration Setting

Can u guys tell me how I can make a scom 2012 r2 report server high availability configuration kindly share the steps or screen of it.

SCOM reporting feature is depend on SQL reporting and as a result you may refer to SQL reporting service high availability.
For detail, pls. refer
http://technet.microsoft.com/en-us/library/bb522745.aspx
http://www.mssqltips.com/sqlservertip/2335/scale-out-sql-server-2008-r2-reporting-services-farm-using-nlb-part-1/
http://www.mssqltips.com/sqlservertip/2336/scale-out-ssrs-r2-farm-using-windows-network-load-balancing-part-2/
http://technet.microsoft.com/en-us/library/hh882437.aspx
Roger

SCOM 2012 R2 Reporting services installation error - data reader account

I have successfully installed SCOM 2012 R2 and SQL 2012 SP1 on the same server. I was trying to install the reporting server piece of SCOM.
When I get to the part that asks for a domain account, I get this error:
"Data Reader account provided is not same as that in the management server"
The account is not the same as the management server, and it does have read access to the data warehouse and reporting databases. Is there some other permission this account needs for reporting services?
Thanks.

Adding more info：
I usually create the following account for SQL:
AD accounts for the following to be used with SQL Services:
SQL Agent for SQL Server Agent
SQL Analysis Services for SQL Server Analysis
SQL Database Engine for SQL Server Database Engine
SQL Reporting Services for SQL Server Reporting Services
For SCOM I create the following accounts:
SCOM DR - Used to deploy reports
SCOM DWR - for writing data from the management server to the reporting DW
SCOM MSA - Performs default actions
SCOM SDK - Used for updating/reading information from the operations Manager Database - Needs to be local administrator on the SCOM server
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SQL 2012 SP1 Reporting Services for SharePoint (2013) - Install-SPRSService Not Available

So, at this point, I've blown away an otherwise functional SP2013 + SQL2012SP1 multi-server farm trying to get this to work, only to end up with the same results. Irrespective of whether I install Reporting Services before or after the SP2013 server is in
a farm, SSRS does not seem to be enabled in the farm. I cannot add a new SSRS service application (the menu item does not exist); I cannot start the SSRS service on server (because it isn't here); I cannot execute the Install-SPRSService cmd in SP (yes, the
SharePoint) Powershell (PS comes back with this error:
Install-SPRSservice : The term 'Install-SPRSservice' is not recognized as the
name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Install-SPRSservice
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Install-SPRSservice:String) [],
CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Quite simply, something's broken. I've followed a couple of detailed how-to's on technet and elsewhere... Right at the point when I should be able to create the SSRS service application, the wheels come off the cart. I've tried Import-Module'ing the SQLCMDLETS
and SQLPS PS modules...nothing... The strange thing is that after the installation of the SSRS, if I happen to go into the General Application Settings in Central Admin, I see a new item after Content Deployment:
$Resources:ReportServerResources,AdminReportServerGroupTitle;
$Resources:ReportServerResources,ManageIntegrationSettings; |
$Resources:ReportServerResources,AddTrustedAccounts; |
$Resources:ReportServerResources,SetServerDefaults;
When I uninstall, this goes away.
Greatly appreciate any suggestions you can offer because this is driving me crazy, and I have tried everything I can think of to get this going...

Make sure you are running SharePoint 2010 Management Shell not PowerShell.
Also make sure you are running SharePoint 2010 Management Shell with administrator privileges. Right click the icon and click, "Run As Administrator".
You must have installed "Reporting
Services add-in for SharePoint Products" on the server where you are executing "Install-SPService".
You also may be interested to check this tutorial: Install
Reporting Services SharePoint Mode for SharePoint 2013

CM 2012 SP1 Reporting services SPN question

Hi
I have a issue where a remote console or web browser cannot see any reports. When logging onto the site locally they can access reports fine with the console.
Primary site with all roles CM and SQL local.
SSRS service is running under a domain user account
In the AdminUI.log there are HTTP 401 unauthorized errors. Will i find this error on the server in any logs?
There is no SPN registered for SSRS service account to the server
My suspicions are that a SPN needs to be registered, but if i register a SPN for (HTTP/server domain user acc) how can i find out if i will have a problem with other web apps (i have MP, DP on box) like suggested below
HTTP is
the service class. The Report Server Web service runs in HTTP.SYS. A by-product of creating an SPN for HTTP is that all Web applications
on the same computer that run in HTTP.SYS (including applications hosted in IIS) will be granted tickets based on the domain user account. If those services run under a different account, the authentication requests will fail.
http://msdn.microsoft.com/en-us/library/cc281382.aspx

I added the service account to the WAA group and it did not resolve the issue.
I removed the RSWindowsNegotiate setting
and it works fine... I guess its due to a SPN not being set, I dont want to have any webserver conflictions if I set the SPN for HTTP so i went for removing the above setting.
For information:
After you confirm the problem, you can address it in the following ways:
Register an SPN for the Report Server service under the domain user account. For more information, see How to: Register a Service Principal
Name (SPN) for a Report Server.
Change the service account to run under a built-in account such as Network Service. Built-in accounts map HTTP SPN to the Host SPN, which is defined when you join a computer to your network. For more information, see How
to: Configure a Service Account for Reporting Services.
Use NTLM. NTLM will generally work in cases where Kerberos authentication fails. To use NTLM, remove RSWindowsNegotiate from the RSReportServer.config file and verify that only RSWindowsNTLM is
specified. If you choose this approach, you can continue to use a domain user account for the Report Server service even if you do not define an SPN for it.

SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

Hi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li

Audit collection services SCOM 2012 SP1

Hi all,
sorry for my englich . I have trouble with ACS . I set in the DC audit logs :
http://www.techrepublic.com/blog/data-center/reporting-on-security-with-microsoft-audit-collection-services/.
After this I try look to report Domain and Bultin administrators membwrschip changes . But the report is empty after i try change domain admins groups....
And second questation :
what mean report usage_sensitive security groups changes ?
thank you .....
Falcon

Hi,
You may first check your secutiry logs to make sure those membership change event is generated.
In addition, did you follow the link below when deploying ACS:
http://blogs.technet.com/b/fesiro/archive/2013/01/08/how-to-deploy-audit-collection-services-acs-in-scom-2012.aspx
Hope the article below can be helpful for you:
http://scomandplus.blogspot.ca/2012/08/error-in-scom-2012-acs-report-sensitive.html
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM 2012 SP1 availability report in MS Generic Report Libary shows inaccurate data

Hi,
in SCOM 2012 sp1, we have the generic availability report showing many of our web sites with no up time beyond a certain date. The web sites are ok, the web availability monitors are all healthy and the monitors test ok
None of these web availability tests are in Maintenance mode although what we are observing certainly makes us think that they are.
We also have a Web transaction login monitor for WEBSITE(A) that does not show this same outage for a login test.
However WEBSITE(A)'s availability monitor shows the same downtime as the other web availability tests.
Any thoughts on where to look for this problem? Im guessing its a problem placing the data in the Warehouse?
Thanks Lance

Hi,
Based on my understanding, the report shows there is downtime for the web site, but the web site did work well always.
It seems like that there is old data stored in data warehouse, would you please check the report for recent date, such as one day or two days.
Regards,
Yan Li
Regards, Yan Li

System center data access service crashes with event id 26339 ad 26380 in SCOM 2012 Sp1 RTM

hi all,
I have deployed scom 2012 sp1 rtm on Os 2012 std and database is on another VM Machine having SQL 2012 sp1 with OS 2008 R2 SP1 std, suddenly sql vm get stopped and unable to start , so I have delete it from hyper-v 2012 console and imported the VM again
in Hyper-0S 2012 cluster.
Now, System centre data access service get crashed again and again with mentioned events
event 26339, OpsMgr SDKService
event 26380, opsmgr SDkService
An exception was thrown while initializing the service container.
Exception message: Initialize
Full exception: HTTP could not register URL
http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application.
The System Center Data Access service failed due to an unhandled exception.
The service will attempt to restart.
Exception:
System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://+:51905/ConnectorFramework/ because TCP port 51905 is being used by another application. ---> System.Net.HttpListenerException: The process cannot access the file
because it is being used by another process
   at System.Net.HttpListener.AddAllPrefixes()
   at System.Net.HttpListener.Start()
   at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
   --- End of inner exception stack trace ---
   at System.ServiceModel.Channels.SharedHttpTransportManager.OnOpen()
   at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
   at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
   at System.ServiceModel.Channels.HttpChannelListener`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.EnterpriseManagement.ConnectorFramework.ServiceDataLayer.ConnectorFrameworkDataAccessChannel.Initialize()
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.Initialize(InProcEnterpriseManagementConnectionSettings configuration)
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.InitializeRunner(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
Kirpal Singh

Hi Kirpal
Can you try this it might help as its an known issue of getting event id 's 26361,26380 try out & lets see if it helps.
The manifest files are located on the RMS at the \Program Files\System Center Operations Manager 2007\ root directory. The manifest files will need to be edited for the config and sdk service on affected RMS. The file names are:
Microsoft.Mom.Sdk.ServiceHost.exe.config
Microsoft.Mom.ConfigServiceHost.exe.config
In between the EXISTING <runtime> and </runtime> lines – you need to ADD a NEW LINE with the following:
<generatePublisherEvidence enabled="false"/>
This solution disables CRL checking for the specified execute-ables, permanently.

Stop SCOM services before installing UR5 for SCOM 2012 SP1?

Hello,
Shall I stop SCOM services on management server before upgrade to UR5?
ENV: 3 SCOM 2012 SP1 management servers without UR.

You didn't need to stop services within upgrade.
To upgrade to UR5, you can refer below link
http://www.ms-opsmgr.eu/?p=488
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical

SCOM 2012 SP1 Upgrade - RMS fine but can't upgrade reporting or web console

Hi,
We've just upgraded our RMS to SCOM 2012 SP1 and everything went smoothly as per the documentation. However when I next try to upgrade the Reporting or Web Consoles (located on separate servers) to SP1 I am presented with a message saying:
"The management server to which this component reports has not been upgraded".
At that point we cannot proceed past the prerequisite checker.
I am totally confident that the SP1 upgrade went through on the RMS and all file versions are at SP1.
Can anyone help please?
Thanks,
Tim

Hi Retee,
I was not able to find a fix for this but I did find a workaround.
1. I copied the installation files from the SCOM 2012 SP1 DVD/ISO to a folder, SCOM_2012_INSTALL on the reporting server.
2. Browsed to the following folder ..\SCOM_2012_INSTALL\setup\AMD64\ and commented out the following section of the IntermilestoneUpgradePrereqs.xml file:

3. Ran ..\SCOM_2012_INSTALL\setup.exe and the upgrade was successful.
Our SCOM infrastructure has now been at 2012 R2 for a couple of months and I have not seen any issues caused by commenting out this section. But as always, use at your own risk.
Hope this helps.
Thanks,
Iain

SQL version could not be verified error while installing the SCOM 2012 R2 reporting component

I have the below SCOM server roles in my SCOM 2012 R2 set up
1) All servers with Windows Server 2008 R2 SP1, MS - SCOM1, DB & DW - DB1, Reporting Server - DB2
2) All the DB servers with SQL 2012 SP1
3) Windows firewall is turned off on all the servers.
4) Success fully installed all the components except SCOM reporting.
While installing the SCOM 2012 R2 reporting component on DB2 ( Iam running this set up on the server where I instllaed the SQL DB engine and reportin services in Native mode. Configured the SQL reporting database and reporting URLs successfully in SQL reporting
configuration manager) getting the below error in the Rporting server instance page. Kindly advise.
I ran mofcomp.exe and there is no firewall restrictions. My account also has DB owner & sysadmin permissions.
Also tried re installing the SQL on Reporting server.
"The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information".

Hi,
As far as I know, after installing SSRS, we don't need to configure the database and reporting URLs manully. When we install the reporting service for SCOM, it will configure those automatically.
If possible, you may re-install SSRS and then install SCOM reporting service.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Is it possible to deploy 2 SCOM 2012 R2 reporting in a SQL server which already has SCOM reporting of a different management group but with 2 different reporting instance.

Hi Experts,
I have a typical situation in the LAB environment. Hope some one helps. I have Installed a SCOM 2012 R2 with SQL 2012 SP1 in a single server (Management group 1). I have installed another management group on another server using this SQL server for its database
so i have everything going fine.
The first management group has its reporting installed in the SQL server. For the second i created a new named instance for that. But i cannot run the SCOM setup in the SQL server (Also holding the Management group 1 MS) as 1 st reporting is already there.
When i run the setup it is asking me to repair it. I don't get the install option so i can install the reporting for management group 2 in the named instance.
Default instance is being used by the 1st management group.
Can any one figure a possibility for installing 2 SCOM reporting services for different management groups in a same SQL 2012 server please.
Gautam.75801

Hi Yan Li,
Thank you for the reply. So as you are aware If i need to instal reporting, i need to run the SCOM 2012 R2 setup in the SQL server and select reporting and select the
instance and then mention the management server there right. I am not getting that option there it is asking me to remove or repair the existing installation as there is already a SCOM entire setup including reporting there. As it is a lab there is no problem
in testing. I have 2 reporting instances. Any suggestions for me on how to overcome this issue and deploy the second reporting in the new named instance ?
Below is the screenshot of the error what i am talking about when i run SCOM 2012 R2 setup to install reporting in the SQL server
When i click on add feature reporting is greyed out (As already 1st management groups reporting is installed)
When i click on remove or repair it
uninstalls the existing one. But i want both SCOM 2012 r2 reporting to be there(For both Management group). Is it possible ? If yes What is the trick to run the setup ?
Gautam.75801

Trouble Installing 2012 R2 Reporting Services - Version Mismatch Error in logs

I recently upgraded an instance of SCOM 2012 SP1 to 2012 R2.
I got no errors installing the all of the components except for the reporting services.
As part of my troubleshooting, I ended up just uninstalling the SP1 version of reporting services and just tried a fresh install of R2 Reporting Services.
When installing reporting services, I get to the step it asks you to put in your management server. I do that, and I get an error about the versions not matching. If I look in the OpsMGrSetupWizard.txt in the setup logs, I see the following error.
Error:The management server is a different version than the current setup build. Please use a different management server or the correct version of setup. Server Version: 7.0.9538.0
On both of my management servers, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup shows 7.1.10226.0 for currentversion, ServerVersion and UIVersion
I've tried running the install from the Action account, the SDK Account and my own account, all having admin privileges on the system, same error. I've run the resetSRS.exe against the SQL server in case there were leftovers from the previous SP1 install
of reporting services.
My searches here and google haven't found anything that has helped.

OK, after digging around some more I found the following.
In the SCOM Console, my management servers were still in maintenance mode from the upgrade somehow, and in the agent managed section for management servers, the version still listed the 7.0.9538.0 version. I removed them from maintenance mode, and within
a few minutes their returned to a monitored state, and the version updated to the 7.1.10226.0 version.
Once that was up to date, I reran the reporting services install on my db server, and it went through properly.
So it looks like the reporting services install is dependent on some part of the management servers updating their version in the db.

SCOM 2012 SP1 Reporting Services empty

Similar Messages

Maybe you are looking for