The case of the failed SCOM R2 CU2 Update On the 30th of April Microsoft released Cumulative Update 2 for System Center Operations Manager 2007 R2. In this article i will detail my experiences from the installation, which didn't work out in the first place. Before starting the update, i did the following: 1. Downloaded the update 2. Read the corresponding KB article: KB979257 3. Read the blogpost from Kevin Holman detailing his experiences. Well, especially the article from Kevin Holman was a very interesting read, so i decided to follow this article and use this as a guide during my upgrade. I started with the update on the RMS, but the installation failed instead of giving a success as mentioned in Kevin's article. The installation just stated that the update failed, without any additional information. So how did i troubleshoot this issue. I first started looking for a logfile, which couldn't be found. This is bad in my opinion. Second i started searching the eventlog for any messages related to my installation, without succes unfortunately. I then decided to start the installation using the msiexec method and to enable verbose logging, resulting in the following command line: msiexec.exe /p "kb979527-x64.msp" /L*v "%temp%\CU2_Log.txt" The installation failed again, but i could find some information in the logfile now. This is what the logfile partially said. Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.SetRootHealthService 2010-05-06T09:13:44.8095014+02:00 Debug: *** Trace Started *** 2010-05-06T09:13:44.8095014+02:00 Warn: SetRootHealthService: The sql client throws exception Login failed for user '\'. 2010-05-06T09:13:44.8095014+02:00 Error: Exception analysis: Errors are from master.dbo.sysmessages table,Error 208 means object not found, we assume the MT_HealthService table not found 2010-05-06T09:13:44.8251324+02:00 Debug: *** Trace Ended *** The solution So, it looked like the account used to install the update had enough rights within SCOM, because it was an SCOM administrator and even local administrator on the RMS. But the account didn't have the necessary rights within the database. We logged on with an account which had enough rights on the RMS and the DB and the installation succeeded. Keep in mind that this requirement isn't mentioned in the KB article anywhere. So i hope this article will help some people experiencing the same issue, during the upgrade. After solving this issue, i followed the rest of the steps from the article of Kevin Holman, and i was able to complete the installation successfully. Back to main menu