Installing SCOM 2012 SP1 Error

Hi.
When we try to install the SP1, the installation fails.
We are using Server 2008 R2 Datacenter 64 bit.
I have started the installation with elevated rights. The windows eventlog says:
Product: System Center Operations Manager 2012 Agent -- The System Center 2012 - Operations Manager agent cannot be installed on a computer on which the Operations Manager management server, gateway server, Operations console, operational database, web console,
System Center Essentials, or System Center Service Manager is already installed. These must be uninstalled in order to proceed.
Event though the agent is not installed (not possible since its the Operations Management server)
This are the programs that are installed on the server:
I have zipped the log files and uploaded them
to skydrive.

Looking at the log files, the pre-reqs are fine. It detects that a previous version of the SCOM MS is installed and tries to upgrade:
[15:06:16]: Debug: :isProductInstalled: product with {7348450D-5558-4CA6-8E71-044720D304F2} product code is installed on this machine
[15:06:16]: Debug: :GetServerInstallState: OpsMgr Server is installed on this machine
[15:06:16]: Debug: :isProductInstalled: product with {95241780-B772-4A42-A1F0-8FA951FAF619} product code is installed on this machine
[15:06:16]: Debug: :GetUserInterfaceInstallState: OpsMgr UI is installed on this machine
[15:06:16]: Debug: :isProductInstalled: product with {20F530CC-FD73-43FE-ABD3-138D140A77A9} product code is installed on this machine
[15:06:16]: Debug: :GetWebConsoleInstallState: OpsMgr Web Console is installed on this machine
What I see a bit further down is:
[15:06:50]: Info: :Info:preparing for MS upgrade
[15:06:50]: Always: :Operations Manager Agent is also installed on the machine. Since we are upgrading Server we will remove Agent from this machine and add back the Agent Management group after server upgrade.
[15:06:50]: Always: :uninstalling product with product code: {5155DCF6-A1B5-4882-A670-60BF9FCFD688}
[15:06:50]: Debug: :GetFullPathBasedOnSetupLocation: Attempted to resolve a file at C:\apps\sc2012sp1\Setup\AMD64\ but it wasn't found there. Will return an empty string.
I don't know if this is causing the issue but it fails just after this point. Perhaps try downloading a new .iso and re-mounting (rather than extracting).
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Similar Messages

SCOM 2012 SP1 is failing to install - SQL not compatible

I'm getting an error when installing SCOM 2012 SP1 stating the SQL is not supported. I have seen a few posts on the forum about this error message but so far none of the resolutions resolved my issue.
Using named instance on port 2433. Entering SQL\instance and port 2433 yields same message as seen in another post:
"The installed version of SQL server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation. Please see the Supported Configurations document for further information."
I noticed I get this in my OpsMgrSetupWizard.log
[15:03:28]: Error: :StackTrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[15:03:28]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
Notice the last line - IsSQLOnAValidComputer is null/empty. The solutions I found are to open the ports between these servers but the SQL server and SCOM server are on the same network - no firewall between them. The registry key for domain firewall
policy to 'EnableFirewall' is 0. The firewall service is disabled on both machines.
I am running the installation as a domain service account - for the DAA. It has local admin on the SQL and SCOM server. It has sysadmin DB access to the instance.
SCOM Server:
Server 2008 R2 Standard SP1
SQL Server:
Server 2008 R2 Enterprise SP1 | SQL 2012 RM 64-bit version 11.0.2100.60
Any help is greatly appreciated.

Glad to hear the issue has been resolved. Thanks for the update.
Niki Han
TechNet Community Support

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

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

Non supported version of SQL with new install of SCOM 2012 SP1

I have SQL 2012 SP1 running on Server 2012. I have tried the SCOM installation with and without CU2 (to fix the 1618 installation error)
SC VMM installed cleanly and appears to work.
The install for SCOM produces an error that says, "The installed version of SQL Server is not supported". I have not been able to find any log from the install that has that error in it.
Also, I have not been able to determine the true requirements of the SQL server for SCOM. (I found dock SCOM 2012 RTM and SQL 2008 R2, but noting for 2012 SP1.
Can someone point me to the correct place for the install log with (hopefully more information) and/or the requrements for the SQL installation?
Roy

The log is not created yet because it has not started the install.
The firewall is the most common issue indeed. Temporarily Disable the firewall and see whether you can continue.
Are you using a developers edition? The only 2 editions supported are standard and Enterprise.
The true requirements for SCOM 2012 sp1:
We recommend that you check for updates and hotfixes for SQL Server. Note the following database considerations for Operations Manager:
SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise editions. Operations Manager will function with both editions.
Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation
settings are supported.
The SQL Server Agent service must be started, and the startup type must be set to automatic.
Side-by-side installation of System Center Operations Manager 2007 R2 reporting and System Center 2012 Service Pack 1 (SP1), Operations Manager reporting on the same server is not supported.
The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start.
For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
tempdb Database.
Found here:
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_OperationsDatabase
It's doing common things uncommonly well that brings succes.

Error 1723 when removing scom 2012 sp1 agent

Hi All,
I am trying to remove the scom 2012 SP1 agent from a machine and i get an error - 'Error 1723. There is a problem
with this Windows Installer package. A DLL required for this install to complete could not be run.
Any idea how can i remove the agent from the box. Let me now if any other info required to give a hint to the problem.
Durgesh Kumar

Hi,
Reinstall the agent, and the uninstall ? If possible, reboot the server and then uninstall?
Same issue here:
http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/get-error-1723-there-is-a-problem-with-windows/3d68fc4b-c968-4796-a270-27027a52de3f?page=2
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.

Error while installing SCOM 2012 reporting component.

Hello Experts,
I had to recently tired installing SCOM 2012 reporting server role on one of the SSRS instances and got the below error.
The SQL team created a dedicated SSRS instance for SCOM(SSRS_SCOM2012) on a SQL instance which hostes other SSRS instances for other applications like SCCM 2007, FEP2010 and FIM2010. I understand the SSRS is are individual components and should not have
dependency with other SSRS instance on the same SQL instance.
A few weeks back i successfully installed the reporting service on another SSRS isntance on a SQL isntance which hosts no other SSRS instances on it for creating a dev SCOM for our enviornment.
The SSRS configuration has been done correctly with service accounts, execution account, database created etc configured for production.
No SSL nor any proxy set for the SQL Report server.
One option i am left with now is running resetSRS.exe to reset the SSRS. But before doing this i would like to take advice from you all as i need to run this on production which hosts other prod SSRS instance on the same SQL instance as well :(
Please Advice.
Regards,
Prajul Nambiar

Thanks Gautam for the quick response.
Answers to your questions are as below.
Q1:Is the SQL version same as of what you are using for the Database engine services as well ?
A1: Yes, its SQL 2008 R2.
Q2: Are the SQL URL's Working as expected ?
A2: Yes, both the Report URL and Report Manager URL are working even though there is no content in it as
SCOM Reporting component is yet to be installed successfully.
Q3: Is
the Scale of deployment joined ?
A3 : No, its Native.
Q4 : Also you can Run resetSRS.exe
So it will just reset the Reporting and will not affect any other component.
A4 : For say my SQL cluster name is ABC which is on a
4 node cluster and we have created SSRS(SSRS_SCOM2012) on one of the node(Server1) of that 4 node cluster. SCOM installer discovers SSRS instance name as Server1\SSRS_SCOM2012. so do it have the run the command as "resetsrs.exe Server1\SSRS_SCOM2012"
or "resetsrs.exe ABC"?

Upgrading from SCOM 2012 SP1 to SCOM 2012 R2 what CU do i install? CU5?

Hi,
I just upgraded from SCOM 2012 SP1 to SCOM 2012 R2. What CU version should I install? CU5?
Thanks
K

The most current CU version os SCOM 2012R2 is CU4
You can download it from
https://support.microsoft.com/kb/2906925?wa=wsignin1.0
For detail description of SCOM 2012 R2 CU4, you may refer to
http://support.microsoft.com/kb/2992020
and
http://syscentercldman.blogspot.hk/2014/12/update-of-scom-2012-r2-ur4.html
Roger

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

How SCOM Agent will get degraded which is installed on the monitored server while reverting Back from CU6 to CU3 of SCOM 2012 SP1?

Hi,
I have SCOM 2012 SP1 (CU3) inatalled on base server 2012 Standard which is a VM.
Now I am planning to Go for CU6 and thinking to take snapshot of complete SCOM server instead of taking Data Base Backup. Which should I prefer?
If i am going for the Snapshot for complete SCOM server and run the CU6 complete setup. And some thing went wrong and not able to fix the issue.
And I need to reverted back to CU3 using Snspshot.
Now, how can I revert the Agent Version to CU3 level which is already upgraded to CU6?
Thanks
Amit Raj

Hi,
all agents with CU6 will be work fine with SCOM CU6.
But if you decide back to the CU3 you need to backup your OPsDB and DWH (if CU6 contains sql scripts).
In regard agents you can use repair from OPsMGR console.

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

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.

SCOM 2012 SP1 - PowerShell Script failed to run - 3 alerts appear after every reboot of the SCOM Server

Brand new SCOM 2012 SP1 install with Update Rollup 1 applied
Single server, local SQL install, SQL Server 2012 SP1
Hyper-V VM running on Server 2012. VM has 8GB Ram, single vCPU
Going through initial management pack importing and configuration, at this point I have the Windows Server 2012 and SQL 2012 MP's installed.
See screenshot
http://i.imgur.com/l0Molh1.png
I am getting the following alerts in my SCOM console and cannot find a resolution to fix the issue. I don't want to set an override, as an override will prevent the PowerShell alert in other instances, where I might want to receive an alert.
Looking at the alert description, it states "The Data Access service is either not running or not yet initialized"
The SCOM Console launches and responds fine, and I get no other errors. I check the Data Access service and it is online. I have left the system alone for a couple of hours and no other errors. I then closed those alerts and restarted the
server, and they came right back in, so I know that this is something that is happening at either server startup of during the start of the SCOM services.
Is it possible that SCOM is trying to execute these scripts and the Data Access service has not come online yet?
Has anyone else come across this before?

Please try the method in the following thread:
Note: As there is operations related to Registry, please perform a backup before doing this.
OpsMgr 2012 - Power Shell Script failed to run
http://social.technet.microsoft.com/Forums/de-DE/systemcenterde/thread/4be37f8d-1e7b-450c-8cb9-f1e95f3b2bd0/
Thanks.
Nicholas Li
TechNet Community Support

Bulk URL Monitoring is SCOM 2012 SP1

Hey Team,
i need to setup 100 + url monitors in scom 2012 sp1, i came across a term named BULK URL Monitor which suits my requirement. The issue is i am failing to get it to work when i click Bulkmonitor.exe i am gettign the below error and not sure how to resolve
it.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at Microsoft.EnterpriseManagement.BulkUrlManager.BulkUrlManagerForm..ctor()
at Microsoft.EnterpriseManagement.BulkUrlManager.Program.Main()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Any suggestions will be highly appreciated.
-vrkumar01
RajKumar

It worked.
intially i tried to install in \System Center 2012\Operations Manager\Setup & System Center 2012\Operations Manager\Server both failed but this
System Center 2012\Operations Manager\Console worked.
thanks a lot
-vrkumar01
RajKumar

Installing SCOM 2012 SP1 Error

Similar Messages

Maybe you are looking for