Cameron Fuller
Cameron is an author, speaker, Microsoft MVP (Cloud and Datacenter Management), principal consultant and Corporate Practice Lead for Catapult Systems. Cameron blogs about infrastructure topics including SCOM, the Cloud, virtualization and consulting.

OpsMgr (#SCOM) CU installation extracts but fails to install   

Tags: OpsMgr and MOM
Technorati Tags:

As most everyone knows in the OpsMgr community Kevin Holman has an excellent article on the various CU installations including the one on CU5: http://blogs.technet.com/b/kevinholman/archive/2011/08/03/opsmgr-2007-r2-cu5-rollup-hotfix-ships-and-my-experience-installing-it.aspx 

We ran into an issue which I did not see discussed in his article however – or to be more clear – his article told us what we had to do to succeed in the installation but not how it would fail if we didn’t have the correct pre-requisites in place. What was happening for us is we downloaded CU5, extracted it, and ran it but it failed and rolled back almost immediately. In the applications log we had an error from MSInstaller of event # 1024 with the information below:

“Product: System Center Operations Manager 2007 R2 - Update 'System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674)' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127

Per Kevin’s article:

****Requirement – as a required practice for a major update/hotfix, you should log on to your OpsMgr role servers using a domain user account that meets the following requirements:

  • OpsMgr administrator role
  • Member of the Local Administrators group on all OpsMgr role servers (RMS, MS, GW, Reporting)
  • SA (SysAdmin) privileges on the SQL server instances hosting the Operations DB and the Warehouse DB.”

In our installation, the account we were attempting to install with was an OpsMgr administrator and was a member of the local administrators group on all OpsMgr role servers but it did NOT have SA permission on the OperationsManager or the OperationsManagerDW. Once we added these rights on the SQL server, it installed without issue.

 

Bonus CU installation tip: If you don’t know who has the Operations Manager console installed and you have SMS or Configuration Manager in your environment, you can use the following blog article to identify systems with the OpsMgr console installed on them:

http://blogs.catapultsystems.com/cfuller/archive/2011/04/06/configmgr-query-for-computers-with-the-opsmgr-console-executable.aspx

 

Summary: Make sure that the account that you attempt to install your OpsMgr CU under matches the requirements (OpsMgr administrator, local administrators group, and SA permissions on the OperationsManager and OperatoinsManagerDW.

 
Posted by  Cameron Fuller  on  11/21/2011
3  Comments  |  Trackback Url  | 0  Links to this post | Bookmark this post with:        
 

Links to this post


Pingback from  TechNet Blogs  on  2/26/2013  7:37 AM







Pingback from  Cameron Fuller - Details to resolve an upgraded...  on  12/19/2013  9:05 AM


Pingback from  MSDN Blogs  on  6/2/2014  3:19 PM



Comments


Dominique  commented on  Friday, March 16, 2012  9:20 PM 
Hello,

I have an issue during the installation. it might be due to the service account of SCOM (svcMOMACTION) nit to be Sysadmin on the SQL Server.
But Also the installation is trying to restart the SQL Server Service but as it is on a Shared instance all others Databases will be impacted as welll (: Does SCOM OM DB needs a specific instance?
Thanks,
Dom


Dominique  commented on  Saturday, March 17, 2012  2:03 PM 
Hello,

I have an issue during the installation. it might be due to the service account of SCOM (svcMOMACTION) nit to be Sysadmin on the SQL Server.
But Also the installation is trying to restart the SQL Server Service but as it is on a Shared instance all others Databases will be impacted as welll (: Does SCOM OM DB needs a specific instance?
Thanks,
Dom


Cameron Fuller  commented on  Monday, March 19, 2012  9:27 AM 
The installation account needs to be an administrator on both the SQL server and on the databases. It should NOT however request a restart of the SQL services from what I have seen. And SCOM does not require a seperate instance - it can be shared but you need to consider overall utilization/performance of the SQL server.

Name *:
URL:
Email:
Comment:


CAPTCHA Image Validation