SCOM 2012

Hi;
I had added the 3 set of servers in scom 2012 and all of them are showing healthy in management server. But when I am
trying to pull report for cpu & memory, these servers are not showing under "Add Group" / "Add Object" tabs. Refer the below snip. Should
I need to add these servers under any particular group. I can able to pull the reports for other servers. pls guide me or assit if any thing had gone wrong while configuration or adding these servers in group.
Regards, Rajeev Parambil

Hi
If you take the filter out does it show your server?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

SharePoint 2010 SP2 hosted on Windows 2012 R2 NOT discovered by SCOM 2012 R2 + 2 SP MP's

What is the process to get SharePoint 2010 Management Packs loaded in System Center 2012 R2 to discover/monitor SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2?
View of installed system:
System Center 2012 R2 loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
-Microsoft SharePoint 2010 Products Management Pack for System Center Operations Manager 2007
-System Center 2012 Monitoring Pack for SharePoint 2010
SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
The SharePoint 2010 Management Shell works fine!
Result
Event 0, Operations Manager - Cannot identify which SharePoint farm server is associated with. Check the management pack guide for troubleshooting information.
Looked at these already:
KB2690744, Configuring the SharePoint 2010 Management Pack for System Center Operations Manager.
http://om2012.wordpress.com/2013/05/24/sharepoint-2010-mp-on-scom-2012/
Further, if the xml push does have the command get-farm instead of get-spfarm, that could be the issue. i.e.
http://www.scom2k7.com/advanced-troubleshooting-of-the-sharepoint-2010-mp/
Thanks,
+Tony
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

Peter,
I recommend to remove the Windows 2012 R2 server out of the farm and redeploy on W2008 R2.
This issue does not have an easy fix.
Summarizing, this appears to be the issue:
1. Windows Management Framework 3.0 is integrated with Windows 2012 R2, which installs .NET 4 and Powershell 4.0. Not uninstallable.
2. The Add-PSSnapin Microsoft.SharePoint.PowerShell is not supported with Powershell 4.0.
3. The SCOM SP2010 MP puts a package on the defined farm server and when the agent launches the package, it calls Powershell (v4 in theis case) and errors out. The target W2012 server will have an Error 0 in the Operations Manager Event log. See below.
Options:
1. Work around maybe - Develop method for manual discovery (I'm working on that now).
2. Rebuild SP2010 farm on Windows 2008 R2
3. System Center Team - Write a new MP to down version Powershell (Powershell.exe -Version 2)
4. Powershell Team - Write a SharePoint Snapin for Powershell 4
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

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

How to create a group in SCOM 2012 R2 based on SCCM Collection?

Is there a way to create a group in SCOM 2012 R2 based on sccm collection? I am planning to use that group for maintenance mode.
Thanks, Samer

Hi,
I think you could query all the collectin members from SCCM database then use powershell to add them to a specific OU.
How to Create Groups in Operations Manager
http://technet.microsoft.com/en-us/library/hh298605.aspx
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.

Can overrides from SCOM 2007 R2 be used in a new SCOM 2012 R2 installation?

Hi All,
I'm wondering if we can "easily" use our overrides/configuration from our current SCOM 2007 R2 implementation and use them in a new SCOM
2012 R2 environment that we plan on standing up. We are using SCOM to monitor approx. 400 servers (physical and virtual).
We have been using 2007 R2 for a few years and we'd like to start using 2012 R2. Instead of using the update path (2007 R2 to 2012
to 2012 SP1 to 2012 R2), we are planning on setting up a new 2012 R2 environment and configuring our servers to start reporting to 2012 R2 (after it has been configured in such a way as to "mimic" our 2007 R2 environment).
Ideally, we'd like to avoid going through the upgrade path. (We'll leave our 2007 R2 environment running so that we can still access "historical
data" until the new 2012 R2 environment has had a chance to build up its own "historical data".)
So ... I was thinking we could export our overrides from 2007 R2 and import them into 2012 R2, but I'd like to verify that this approach makes
sense. We haven't done extensive customizations to 2007 R2 in terms of Distributed Applications or Management Pack Objects (although we have made some changes - which I guess we could manually configure in 2012 R2 to offer the same "experience").
The following are some of the Management Packs that we are using in 2007 R2:
Microsoft Windows Active Directory
Active Directory Certificate Services
EMC Storage Monitoring
IBM Hardware
Microsoft Exchange Server 2010
McAfee
Microsoft Forefront Server Protection 2010
Microsoft Office SharePoint Server 2007
Microsoft SQL Server
Microsoft Windows DNS Server
Microsoft Windows WINS
Microsoft Windows Hyper-V
Microsoft Windows Internet Information Services
Microsoft Windows Server
Microsoft Windows DHCP
NetBackup Operations Manager
Office Communications Server
OpsLogix (BlackBerry)
Service Level Dashboard for OpsMgr 2007 R2
SolarWinds Orion
Schedule Maintenance Mode
Team Foundation Server 2010
Virtual Machine Manager
Microsoft Windows Cluster
Operations Manager 2007 R2
I appreciate all feedback and the sharing of you expertise.
Thanks, Joe.

As long as the base pack works and you wish to retain the customisation then you should be ok, there’s a good article
here which explains how to perform the migration and some of implication/things to check.
There will be complications if you’ve stored anything in the default mp but this is explained in the above article.

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]

Getting Error code -2130771961 while Discovering Cross platform server from SCOM 2012 r2.

Below is the Error
Unexpected DiscoveryResult.ErrorData type. Please file bug report.
ErrorData: Microsoft.SystemCenter.CrossPlatform.ClientLibrary.Common.SDKAbstraction.TaskInvocationException
Task invocation failed with error code -2130771961. Error message was: Creation of module with CLSID "{ED8C18C7-FEF4-488D-AAAF-830366BF0B40}" failed with error "Illegal operation attempted on a registry key that has been marked for deletion."
in rule "Microsoft.Unix.HostEntryResolution.Task" running for instance "Linux Resource Pool" with id:"{7337E4AE-136A-1099-B024-2F4633B1AE1A}" in management group "pslmgmt".
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.SystemCenter.CrossPlatform.ClientActions.DefaultDiscovery.InvokeWorkflow(IManagedObject managementActionPoint, DiscoveryTargetEndpoint criteria, IInstallableAgents installableAgents)
can some one please help me ?

Hi Pandit,
Have you tried restarting the SCOM service on the management server that you are performing the discovery on? Refer below articles for more information.
http://social.technet.microsoft.com/wiki/contents/articles/4966.troubleshooting-unixlinux-agent-discovery-in-system-center-2012-operations-manager.aspx
http://www.systemcentercentral.com/forums-archive/topic/scom-2012-r2-discovery-was-not-succesful-for-solaris/
Thanks,
Janaka
Janaka Rangama MCT MIEEE MBCS (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable.)

Issue upgrading SCOM 2012 SP1 to SCOM 2012 R2

I have been having a really fun time trying to get my test SCOM 2012 SP1 environment upgraded to SCOM 2012 R2. I initially had an issue with the DB server not accepting connections to SMB which was causing the upgrade to fail stating database permission
issues (that was a fun one to troubleshoot). Once I figured out that problem I am now getting an error in the OpsMgrSetupWizard log that is stating the following:
[14:46:47]: Always:
:LaunchMsiSetup: Complete: 2 seconds
[14:46:47]: Error:
:LaunchMsiSetup: Failed, return code: 1612
[14:46:47]: Error:
:Error:Failed to uninstall previous MOM product on this machine, cannot proceed with upgrade
[14:46:47]: Error:
:Error:Failed to uninstall Operations Manager Agent on this machine. This is fatal error, we cannot proceed with upgrade
[14:46:50]: Error:
:LaunchMSI: MSI E:\Setup\AMD64\Server\OMServer.msi returned error 1603
[14:46:50]: Error:
:ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
In the application log I am getting the following error:
"Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service
Manager is already installed. These must be uninstalled to proceed."
I have verified that I don't have any of these installed and have even gone so far as to remove my Config man agent and System Center Endpoint Protection just in case it was getting confused with System Center Essentials.
I am at a loss as to what to try next. Any suggestions?

Hi,
Check if you have the following registry. If so, please back it up first, then delete for a test.
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\C96403E8AD6025B4F9E1FE9C574E34AE
Also, please uninstall MOM product and Operations Manager Agent manually to check the result.
Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
http://technet.microsoft.com/en-us/library/dn249707.aspx
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.

Manage DPM servers, running DPM jobs, etc from SCOM 2012 SP1

Hi,
Little background about our systems.
We have a dedicated SCOM 2012.
We have 22 DPM servers, DPM 2010 and DPM 2012 (we are upgrading to 2012 SP1, we have customers that still using Windows 2003 servers) to be managed by SCOM
We have a few DPM servers that are not located on the same domain as the SCOM server (untrusted domain).
Some problem we have
1. When we try to manage the DPM servers from the SCOM server.
From SCOM 2012 server I can “Manage DPM server” that are located in our domain but I cannot manage DPM servers located on untrusted domains (customer’s domains). I receive the below error message
"Unable to connect to <untrusted domain DPM SERVER> ID: 948
Verify that the DPM service is running on this computer"
I guess it’s because the account that I’m using to run SCOM server located in our domain and does not have the permission to open the DPM console on the untrusted domain. So I wonder if it is possible to use “RUN AS profiles/accounts”
to solve this issue, and how?
2. I have installed SCOM 2012 Operations Manager Console on my computer and then installed DPM Central Console.
When I select one dpm server (from my computer), that is on our domain, and then click “Manage DPM server” I got this error message
"Unable to connect to <our domain DPM SERVER> ID: 33333
1. Verify that the DPM service is running on this computer (YES)
2. Verify that the current user has been added to at least one of the roles in Operations Manager. (YES)
3. Open Operations Manage console and then try launching the DPM Console (THAT IS WHAT I AM TRYING TO DO)
4. If you have re-imported the management pack recently, the role configuration may be corrupt. Open the DPM-specific roles and check if the roles have task assigned to them. If not, delete the roles and recreate the...."
When I click on “Get more information” I get this error message.
"You don´t have access permission to connect to the System Center Data Access service on <SCOM SERVER>. Please check if it is a permission issue".....
Do you know why I cannot connect to any DPM server on our own domain?
Why do I get access permission error on my computer but not on the SCOM server (using the same account)?
What should we do to be able to connect to DPM servers that are on untrusted domain?
3. Is it possible to see Last Recovery Point date/time in SCOM alerts?
For me it is the first thing I look at. If it has failed 10 min ago it is not critical.
But if it is a date and time more than 1 day old, then it is critical.
I hope someone can help us with this
Br
SvBoho

Hi,
To manager DPM, I think we may need to add the account to local admin group of the DPM server.
In addition, to connect to DPM the user needs permissions to DPM/SQL Server DPMDB.
For your DCs, have your enabled agent proxy option? If not, please enable that option for all DCs.
To monitor DPM with SCOM, please also go through the below links:
http://kevingreeneitblog.blogspot.com/2011/10/managing-and-monitoring-system-center.html
http://damatisystemcenter.com/2013/10/14/monitor-data-protection-manager-2012-using-scom-2012-sp1/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Yan Li
Regards, Yan Li

Upgrade to R2 from SCOM 2012 SP 1 UR 4 - Final configuration failed to install

I was upgrading our test SCOM 2012 SP1 UR 4 sever to R2 and ran into the following issue:
Setup cannot be completed… Final configuration failed to install.
Everything else upgraded fine.
There was no rollback performed…. The log states “Skipping rollback for install item Final Configuration as it was not successfully installed”
Looking in OpsManagerSetupWizard.log in the section for Final Configuration I see the following:
[16:00:43]:           Always: :!***** Installing: POSTINSTALL ***
[16:00:43]:           Info:      :SetProgressScreen: StartMinorStep.
[16:00:43]:           Warn:    :ApplyUpdates: Unable to load QFE file.
[16:00:43]:           Always: :Doing Preinstall task for POSTINSTALL
[16:00:43]:           Warn:    :CheckAndLoadUpdateFiles: Unable to load QFE file.
[16:00:43]:           Always: :Doing Install task for POSTINSTALL
[16:00:44]:           Debug: :DoInstallTask: Found Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall;PostInstallProcessor as type and method.
[16:00:44]:           Info:      :Type: Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall Method: PostInstallProcessor
[16:00:44]:           Info:      :SetProgressScreen: Init Exe Install progress.
[16:00:44]:           Info:      :AddUninstallChangeEntry: Cleaning out existing files at the ARP file cache location D:\Program Files\System Center 2012\Operations
Manager\Setup
[16:00:44]:           Error:     :InstallActionProcessor.DoInstallTask: method PostInstallProcessor threw exception. We will return installSuccessful = false.:
Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[16:00:44]:           Error:     :StackTrace:   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallActionProcessor.DoInstallTask(InstallItemsInstallDataItem itemToInstall)
[16:00:44]:           Error:     :Inner Exception.Type: System.UnauthorizedAccessException, Exception Error Code: 0x80131604, Exception.Message: Access to the path 'EULA_EN_EVAL.RTF'
is denied.
[16:00:44]:           Error:     :InnerException.StackTrace:   at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean
throwOnTopLevelDirectoryNotFound)
   at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.ARPFileCache()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.AddUninstallChangeEntry()
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall.PostInstallProcessor(Func`3 setProgressScreen)
[16:00:44]:           Error:     :ProcessInstalls: Install Item Final Configuration failed to install. We did not launch the post process delegate.
[16:00:44]:           Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Final Configuration
[16:00:44]:           Info:      :SetProgressScreen: FinishMinorStep.
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Always: :****Starting*RollBack*******************************************
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Info:      :SetProgressScreen: StartMinorStep.
[16:00:44]:           Always: :ProcessRollback: Skipping rollback for install item Final Configuration as it was not successfully installed.
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Always: :****Ended*RollBack**********************************************
[16:00:44]:           Always: :****************************************************************
[16:00:44]:           Always: :Entering Page: FinishPage
The log states “Access to the path 'EULA_EN_EVAL.RTF' is denied.” I was able to find this file in D:\Program Files\System Center 2012\Operations Manager\SetupTemp\EN, but when viewing its contents I see it
was from the SP 1 upgrade as it starts off with “MICROSOFT EVALUATION SOFTWARE LICENSE TERMS MICROSOFT SYSTEM CENTER 2012 STANDARD SERVICE PACK 1.” Based on everything else referenced in the log file previously, it seems like it was trying to locate
this file in D:\Program Files\System Center 2012\Operations Manager\Setup. Also, I applied the product key after installing SP1 previously, so it was not running with an evaluation license.
Running Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a
gives me:
SkuForLicense Version     TimeOfExpiration
       Retail 7.1.10226.0 12/31/9999 11:59:59 PM
The version (7.1.10226.0) is that of SCOM 2012 R2 (as I noted before, there was no rollback.) Everything seems to be functioning fine (Console, Web Console, Reporting Services.)
Is there a way to get it to re-run only the Final Configuration steps (which will probably fail again as the EULA file does not exist where it expects it)? I am not sure if there were supposed to be any further
configuration steps that did not get completed, so i dont know how stable SCOM is now. Should I re-run the R2 installer? Or is it OK as is? The only info online about a SCOM Install where the final configuration failed to install dealt with
an error upgrading the SCOM Console, which is not relevant to my situation. This is my test SCOM environment, running on a VM. I could revert to the pre-upgrade snapshot and see if another upgrade attempt completes successfully, but if that does
work I am concerned that something like this may happen in my prod environment, which is not running on a VM, so has no ability to revert to a snapshot.

Hi,
Please refer to the following links:
Do I need a specific Cumulative Update Release (UR) in order to upgrade to SCOM 2012 or 2012 SP1 or 2012 R2?
http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
Upgrading Operations Manager from 2012 SP1 to 2012 R2 step by step
http://www.systemcentercentral.com/upgrading-operations-manager-from-2012-sp1-to-2012-r2-step-by-step-upgrading-to-2012-r2-series/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcenterforum+%28System+Center+Central+Rollup%29
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
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.

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

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

Three agent UR versions gets installed from gateway - SCOM 2012 SP1 UR4

Hi,
We have a SCOM 2012 SP1 UR4 installation with several gateways that servers connect to and get installation from.
We noticed that when the agent get installed on a client server it gets first the agent itself, then UR1, UR2 and last UR4.
From the XML-section in the task that has installed the agent one can read the following:
SoftwareUpdateInstalled KB2784734-amd64-Agent.msp;KB2826664-amd64-Agent.msp;KB2880799-amd64-Agent.msp; SoftwareUpdateInstalled
Below is from the application log of a newly installed server that got the agent installed.
The question I have is if this is correct? Why are all three UR installed?
Shouldn't it be enough with the latest version of UR? Are they not cumulative?
Can I simply delete the older versions in the agent directory of the Gateway?
Regards S-E
Windows Installer installed the product. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR1 Update Patch.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR2 Update Patch.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR4 Update Patch.
Installation success or error status: 0.
Windows Installer installed the product. Product Name: Active Directory Management Pack Helper Object.
Product Version: 1.1.0. Product Language: 1033. Manufacturer: Microsoft Corporation.
Installation success or error status: 0.

Hi,
This should be normal, as we can see in the below two articles. When applying Update Rollup 2, UR1 is listed there, and when applying Update Rollup 3, UR1 and UR2 is listed there also.
http://blogs.technet.com/b/kevinholman/archive/2013/04/11/applying-update-rollup-2-ur2-to-opsmgr-2012-sp1.aspx
http://blogs.technet.com/b/kevinholman/archive/2013/09/27/applying-update-rollup-3-ur3-to-opsmgr-2012-sp1.aspx
For example, UR3 can be applied to System Center Operations Manager 2012 SP1 (as released) or a SCOM 2012 SP1 deployment that has had UR1 or UR2 already applied.
Regards,
Yan Li
Regards, Yan Li

Exchange 2013 SP1 and SCOM 2012 R2

Hi there,
Hopefully someone can assist me with this issue, if it is one...
I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
76 users in total, roughly 80GB of Public Folders.
I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected.
Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues.
Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well.
Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010.
A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect.
Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy.
Attempted to reran the probe for EWS and got the error below:
Is there perhaps anyone that can assist me with these errors?
Cheers

FYI... IIS ARR is not supported for Exchange Server.
Check in event log if you are getting anything related to the issue.
About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
Are those mailboxes still moving or in move request?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

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

Monitoring servers in SCOM 2012 via different locals within the same management group

Hi,
I have 2 management servers in a same management group. The 1st one is having English (US) locale while other is installed on Swedish locale. Both are accessed by different users having same admin rights.
Once a USER 1 try to register a server through authoring tab from 1st management server(installed on English locale), a profile/group wrt the server registered is created successfully but the USER on 2nd management server (installed on Swedish locale) can
not see the same in Authoring tab. He can view it in Monitoring tab as as well as Administration tab.
The Vice versa is also true.
Does any one have idea that is it SCOM 2012's expected behaviour wrt 2 2 different users on 2 different locales within a same management group ?
Thanks in advance.

Hi,
I am a little confused, what do you mean by "register a server through authoring tab"?
Do you mean that when you discover a server on 1st MS with discovery wizard then you cannot see it on 2nd MS(and the vice versa)?
As far as I know, all those information should be stored in the operation database which is shared to both MSs within the same management group.
We may use SQL query to find the discovered server on the operation database. Please also check operation manager event logs to get more information to troubleshoot this issue.
Regards,
Yan Li
Regards, Yan Li

SCOM 2012

Similar Messages

Maybe you are looking for