Hi Mazen, Yes both services are started and running. The broker is set to 1 I could have access to the console as well but the CU5 did not apply. Event Log: 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. Additional information is available in the log file C:\Users\SQLSER~1\AppData\Local\Temp\KB2495674-x64_1.log. Log Name: System Source: Service Control Manager Date: 3/16/2012 10:46:09 PM Event ID: 7009 Task Category: None Level: Error Keywords: Classic User: N/A Computer: OPMGRRMS1.ad.medctr.ucla.edu Description: A timeout was reached (60000 milliseconds) while waiting for the System Center Data Access service to connect. The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the System Center Management Configuration service, but this action failed with the following error: Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager An instance of the service is already running.

Some "failure" from the file KB2495674-x64_ENU_0.log === Verbose logging started: 3/16/2012 22:38:46 Build type: SHIP UNICODE 4.05.6002.00 Calling process: C:\Windows\SysWOW64\msiexec.exe === ... MSI (s) (48!30) [22:38:49:932]: Note: 1: 2711 2: MOMGateway GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMGateway SetHealthServiceConfig: Failed to get Feature State.. Error Code: 0x80070646. MOMGateway ... MSI (s) (48!64) [22:38:52:400]: Note: 1: 2711 2: MOMGateway GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMGateway ... SetErrorReportingAndADIntegrationSettings: Failed to get Feature State.. Error Code: 0x80070646. MOMGateway ... ExecuteSql: Failed to execute SQL script. Error Code: 0x80004005. DECLARE dbnames_cursor CURSOR FOR SELECT name from sysdatabases where (DATABASEPROPERTY(name, 'IsOffline')=0 AND DATABASEPROPERTY(name, 'IsShutDown')=0 AND DATABASEPROPERTY(name, 'IsInLoad')=0); OPEN dbnames_cursor; DECLARE @dbname sysname; FETCH NEXT FROM dbnames_cursor INTO @dbname; WHILE (@@FETCH_STATUS <> -1) BEGIN IF (@@FETCH_STATUS <> -2) BEGIN SELECT @dbname = RTRIM(@dbname); EXEC ('USE ;if EXISTS (select * from sysobjects where name=''__MOMManagementGroupInfo__'') SELECT db_name(), ManagementGroupName, DBVersion from __MOMManagementGroupInfo__'); END; FETCH NEXT FROM dbnames_cursor INTO @dbname; END; CLOSE dbnames_cursor; DEALLOCATE dbnames_cursor;. Additional Error Description : The server principal "AD\SQLServer" is not able to access the database "model" under the current security context. EnumerateMOMDBInstances: Failed to retrive database list from 'master' database. Error Code: 0x80004005. ... DeleteLink: Failed to remove shortcut. ... DeleteLink: Failed to remove shortcut. ... WaitForServiceState: Failed to get service state within time limits. Error Code: 0x80070102. CAStartServices: WaitForServiceState failed for start request. Error Code: 0x80070102. OMCFG ... MSI (c) (48:18) [22:41:21:926]: Note: 1: 2262 2: Binary 3: -2147287038 Warning 25362.Failed to start OMCFG service. Setup will proceed, please examine your eventlog ... WaitForServiceState: Failed to get service state within time limits. Error Code: 0x80070102. ... CAStartServices: WaitForServiceState failed for start request. Error Code: 0x80070102. OMCFG ... MSI (c) (48:18) [22:45:03:671]: Note: 1: 2262 2: Binary 3: -2147287038 Warning 25362.Failed to start OMCFG service. Setup will proceed, please examine your eventlog ... MSI (s) (48!64) [22:46:09:316]: Creating MSIHANDLE (3165) of type 790531 for thread 9828 CAStartServices: StartService failed. Error Code: 0x8007041D. ... StartSDKConfigServiceForUpgrade: CAStartServices failed for . Error Code: 0x8007041D. OMSDK ... Property(S): HEALTH_SERVICE_DESC = Monitors the health of the computer. The service may be configured to monitor the health of other computers in addition to this computer. If this service is stopped, detection of failures may not occur. If this service is disabled, any services that explicitly depend on it will fail to start. ... Property(S): SQLServicesErrDlg_Title = Setup failed to start Microsoft SQL Server services Property(S): SQLServicesErrDlg_Desc = The Operations Manager 2007 R2 setup failed to start the Microsoft SQL server services. To continue setup, go back and choose a different instance or start the SQL Server services for the selected instance. ... Property(S): UserIsNotSysAdminDlg_Title = Could not verify if current user is in sysadmin Role. Property(S): UserIsNotSysAdminDlg_ReportingDBDesc = The user running setup is not in sysadmin role in the Reporting database. Property(S): UserIsNotSysAdminDlg_MOMDBDesc = The user running setup is not in sysadmin role in the Operations Manager database or we are unable to connect to Operations Manager database, please verify if you can connect to Operations Manager database from this computer. Property(S): Check_DNS_Name_Of_MS = Check the DNS name resolution of the Management Server. Property(S): UserExit_TextLine = The wizard was interrupted before System Center Operations Manager 2007 R2 could be installed. Property(S): FatalError_TextLine = The setup wizard was interrupted before System Center Operations Manager 2007 R2 could be installed. ... Property(S): SQLServicesErrDlg_Title.68918168_3885_4F75_BBF8_0CC84213F8D1 = Setup failed to start Microsoft SQL Server services Property(S): SQLServicesErrDlg_Desc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The Operations Manager 2007 R2 setup failed to start the Microsoft SQL server services. To continue setup, go back and choose a different instance or start the SQL Server services for the selected instance. Property(S): SQLServerInstanceDlg_Note.68918168_3885_4F75_BBF8_0CC84213F8D1 = Note: Setup will automatically start the Microsoft SQL Server service if it is not running. Property(S): SQLServerInstanceDlg_SQLServer.68918168_3885_4F75_BBF8_0CC84213F8D1 = SQL &Server database instance Property(S): UserIsNotSysAdminDlg_Title.68918168_3885_4F75_BBF8_0CC84213F8D1 = Could not verify if current user is in sysadmin Role. Property(S): UserIsNotSysAdminDlg_ReportingDBDesc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The user running setup is not in sysadmin role in the Reporting database. Property(S): UserIsNotSysAdminDlg_MOMDBDesc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The user running setup is not in sysadmin role in the Operations Manager database or we are unable to connect to Operations Manager database, please verify if you can connect to Operations Manager database from this computer. ... Property(C): SQLServicesErrDlg_Title = Setup failed to start Microsoft SQL Server services Property(C): SQLServicesErrDlg_Desc = The Operations Manager 2007 R2 setup failed to start the Microsoft SQL server services. To continue setup, go back and choose a different instance or start the SQL Server services for the selected instance. Property(C): SQLServerInstanceDlg_Note = Note: Setup will automatically start the Microsoft SQL Server service if it is not running. Property(C): SQLServerInstanceDlg_SQLServer = SQL &Server database instance Property(C): UserIsNotSysAdminDlg_Title = Could not verify if current user is in sysadmin Role. Property(C): UserIsNotSysAdminDlg_ReportingDBDesc = The user running setup is not in sysadmin role in the Reporting database. Property(C): UserIsNotSysAdminDlg_MOMDBDesc = The user running setup is not in sysadmin role in the Operations Manager database or we are unable to connect to Operations Manager database, please verify if you can connect to Operations Manager database from this computer. Property(C): Check_DNS_Name_Of_MS = Check the DNS name resolution of the Management Server. ... Property(C): HEALTH_SERVICE_DESC.68918168_3885_4F75_BBF8_0CC84213F8D1 = Monitors the health of the computer. The service may be configured to monitor the health of other computers in addition to this computer. If this service is stopped, detection of failures may not occur. If this service is disabled, any services that explicitly depend on it will fail to start. ... Property(C): SQLServerNotFoundDlg_Desc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The Operations Manager 2007 database component requires Microsoft SQL Server 2005 Service Pack 1 or later. The selected instance does not have the correct version. To continue setup, go back and choose custom setup and unselect the database component or select a different instance or upgrade the selected instance to the correct version. Property(C): SQLServicesErrDlg_Title.68918168_3885_4F75_BBF8_0CC84213F8D1 = Setup failed to start Microsoft SQL Server services Property(C): SQLServicesErrDlg_Desc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The Operations Manager 2007 R2 setup failed to start the Microsoft SQL server services. To continue setup, go back and choose a different instance or start the SQL Server services for the selected instance. Property(C): SQLServerInstanceDlg_Note.68918168_3885_4F75_BBF8_0CC84213F8D1 = Note: Setup will automatically start the Microsoft SQL Server service if it is not running. Property(C): SQLServerInstanceDlg_SQLServer.68918168_3885_4F75_BBF8_0CC84213F8D1 = SQL &Server database instance Property(C): UserIsNotSysAdminDlg_Title.68918168_3885_4F75_BBF8_0CC84213F8D1 = Could not verify if current user is in sysadmin Role. Property(C): UserIsNotSysAdminDlg_ReportingDBDesc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The user running setup is not in sysadmin role in the Reporting database. Property(C): UserIsNotSysAdminDlg_MOMDBDesc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The user running setup is not in sysadmin role in the Operations Manager database or we are unable to connect to Operations Manager database, please verify if you can connect to Operations Manager database from this computer. ... MSI (c) (48:20) [22:46:30:492]: Note: 1: 1729 MSI (c) (48:20) [22:46:30:493]: Product: System Center Operations Manager 2007 R2 -- Configuration failed. MSI (c) (48:20) [22:46:30:496]: Attempting to delete file C:\Users\SQLSER~1\AppData\Local\Temp\39959b.msp MSI (c) (48:20) [22:46:30:496]: Unable to delete the file. LastError = 32 .. MSI (c) (48:20) [22:46:30:508]: MainEngineThread is returning 1603 === Verbose logging stopped: 3/16/2012 22:46:30 === System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Dom, Which account are you using to install CU5? DEALLOCATE dbnames_cursor;. Additional Error Description : The server principal "AD\SQLServer" is not able to access the database "model" under the current security context. EnumerateMOMDBInstances: Failed to retrive database list from 'master' database. Error Code: 0x80004005. In 3rd post you mentioned that, you have added sqlserver account to the 3 security group (I'm not sure is it a computer or user account), however, it should be the account you are using for installation (current logged on user account..) OR use an account already has the privilege (Operations Manager Administrator, Local Admin on All RMS/MS/GW/Reporting and the SQL Server, SysAdmin on the SQL Server/Instance).. Dont forget to start the update from cmd Running As Administrator.. Reboot the SQL Server, then the RMS and any MS, and start a new fresh update.. after the privilege check.. Regards, Mazen

Hi Mazen, Which account are you using to install CU5? I am using an account "sqlserver" which is - sysadmin on the SQL Server Cluster where the OperationsManager Database is sharing the MSSQLSERVER instance with other databases. I am very surprised that the account could not access the database as it is the main account used by the DBAs. It is the account I added to the - Local Administrator Group on the RMS (it was already local administrator on the SQL Cluster) and also in the Operations Manager Administartor Role in the SCOM console, the wto entities I am managing. it is a service account kind of super-user account. I don't have any account before having the three privileges as the database is own by another department, I am owning only the Application !!! I always open a command prompt with Run As Administrator and run the msi, is it correct or should I do the Run As on the msi itself. Is it the user logged to the computer which is used to load the msi and run the processes and access the database, or is the process using a background user like the SDK user or the MomAction user to access the DB? I cannot Reboot the SQL Server as it is a SQL Cluster shared by multiple departments. is it possible just to restart the SQL Service for this particular instance MSSQLServer (it will affect less people!! 25 databases) than the full cluster. As this account as alwyas been a Sysadmin do I still need to restart the service(the reboot is something I would have to delay) I have rebooted the RMS and any MS. The infrastructure is as: One SQL Cluster with two nodes hosting OperationsManager Database on the MSSQLSERVER instance One RMS Server for the Application Two management Servers One Datawarehouse server hosting the Datawarehouse database and SSRS. One ACS Server hosting the ACS Database and SSRS Thank you for your huge help! Regards, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Dom, So, the privileges seems ok,, Running the .msi update file should be running from command prompt, Run As Administrator is not available on the .msi itself.. So now, if possible, restart the SQL service or in the cluster take this instance app group offline and get it back online.. After that, lets see what is in the logs.. BTW, do you see any errors on the Operations Manager eventlog on the RMS? Regards, Mazen

Hello, I am trying to install the CU5 on the RMS Server and getting an eroor: 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. Additional information is available in the log file C:\Users\DOMINI~1\AppData\Local\Temp\KB2495674-x64_0.log. Information 1603.The file G:\Program Files\System Center Operations Manager 2007\HealthServiceRuntime.dll is being held in use by the following process: Name: MonitoringHost, Id: 5556, Window Title: '(not determined yet)'. Information 1603.The file G:\Program Files\System Center Operations Manager 2007\MonitoringHost.exe is being held in use by the following process: Name: MonitoringHost, Id: 5556, Window Title: '(not determined yet)'. Information 1603.The file G:\Program Files\System Center Operations Manager 2007\MOMModules.dll is being held in use by the following process: Name: MonitoringHost, Id: 5556, Window Title: '(not determined yet)'. Information 1603.The file G:\Program Files\System Center Operations Manager 2007\MomIISModules.dll is being held in use by the following process: Name: MonitoringHost, Id: 5556, Window Title: '(not determined yet)'. MSI (s) (FC:94) [13:36:18:960]: 1 application(s) had been reported to have files in use. MSI (c) (FC:F8) [13:36:18:960]: File In Use: -MonitoringHost- Window could not be found. Process ID: 5556 MSI (c) (FC:F8) [13:36:18:961]: No window with title could be found for FilesInUse Trying to run with another account the MOMAction I am getting another error: Warning 25362. Failed to start OMCFG service. Setup will proceed, please exemine your eventlog. What to do next? Any idea? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Mazen, It is definetely in progress as now I have three log files after the process: this is the summary of each of them: === Logging stopped: 3/17/2012 14:29:19 === MSI (c) (C4:08) [14:29:19:529]: Note: 1: 1728 MSI (c) (C4:08) [14:29:19:529]: Product: System Center Operations Manager 2007 R2 -- Configuration completed successfully. MSI (c) (C4:08) [14:29:19:531]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Reconfiguration success or error status: 0. MSI (c) (C4:08) [14:29:19:533]: Attempting to delete file C:\Users\SQLSER~1\AppData\Local\Temp\26afa0.msp MSI (c) (C4:08) [14:29:19:545]: Grabbed execution mutex. MSI (c) (C4:08) [14:29:19:545]: Cleaning up uninstalled install packages, if any exist MSI (c) (C4:08) [14:29:19:546]: Attempting to delete file C:\Users\SQLSER~1\AppData\Local\Temp\26afa0.msp MSI (c) (C4:08) [14:29:19:547]: Unable to delete the file outside of the engine. LastError = 2 MSI (c) (C4:08) [14:29:19:547]: MainEngineThread is returning 0 === Verbose logging stopped: 3/17/2012 14:29:19 === ============================================================================================================================== === Logging stopped: 3/17/2012 14:35:27 === MSI (c) (CC:F4) [14:35:27:932]: Note: 1: 1728 MSI (c) (CC:F4) [14:35:27:932]: Product: System Center Operations Manager 2007 R2 -- Configuration completed successfully. MSI (c) (CC:F4) [14:35:27:934]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Reconfiguration success or error status: 0. MSI (c) (CC:F4) [14:35:27:936]: Attempting to delete file C:\Users\SQLSER~1\AppData\Local\Temp\329369.msp MSI (c) (CC:F4) [14:35:27:946]: Grabbed execution mutex. MSI (c) (CC:F4) [14:35:27:946]: Cleaning up uninstalled install packages, if any exist MSI (c) (CC:F4) [14:35:27:949]: Attempting to delete file C:\Users\SQLSER~1\AppData\Local\Temp\329369.msp MSI (c) (CC:F4) [14:35:27:949]: Unable to delete the file outside of the engine. LastError = 2 MSI (c) (CC:F4) [14:35:27:950]: MainEngineThread is returning 0 === Verbose logging stopped: 3/17/2012 14:35:27 === =============================================================================================================================== === Logging stopped: 3/17/2012 14:43:23 === MSI (c) (28:2C) [14:43:23:788]: Product: System Center Operations Manager 2007 R2 - Update 'System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674) - Cross-Platform Components' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\SQLSER~1\AppData\Local\Temp\KB2495674-x64-SCX_0.log. MSI (c) (28:2C) [14:43:23:789]: Windows Installer installed an update. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Update Name: System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674) - Cross-Platform Components. Installation success or error status: 1603. MSI (c) (28:2C) [14:43:23:792]: Note: 1: 1729 MSI (c) (28:2C) [14:43:23:792]: Product: System Center Operations Manager 2007 R2 -- Configuration failed. MSI (c) (28:2C) [14:43:23:794]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Reconfiguration success or error status: 1603. MSI (c) (28:2C) [14:43:23:795]: Attempting to delete file C:\Users\SQLSER~1\AppData\Local\Temp\3830f0.msp MSI (c) (28:2C) [14:43:23:796]: Unable to delete the file. LastError = 32 MSI (c) (28:2C) [14:43:23:801]: Grabbed execution mutex. MSI (c) (28:2C) [14:43:23:802]: Cleaning up uninstalled install packages, if any exist MSI (c) (28:2C) [14:43:23:803]: Attempting to delete file C:\Users\SQLSER~1\AppData\Local\Temp\3830f0.msp MSI (c) (28:2C) [14:43:23:824]: MainEngineThread is returning 1603 === Verbose logging stopped: 3/17/2012 14:43:23 === It seems only the Cross-Platform part is failing now... but the error 05 on the ql statement remains in the three steps !!! Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Dom, Can you try this for more logging details, then check the output open command prompt as administrator >> msiexec.exe /update "C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2495674\KB2495674-x64.msp" REBOOT=ReallySuppress REINSTALL=ALL REINSTALLMODE=omus UPDATE_AGENT=1 /l*vx "D:\KB2495674-x64_today.log" Regards, Mazen

Hello, I am trying with another account andf this is the end of the KB2495674-x64_0.log ... what else I should look for in this file as I could not any more 1603 error as before...? It is strange the server is SQL Server 2008 Clustered 10.0.2531 The RMS is Windows Server 2008 Property(C): SQLServerNotFoundDlg_Desc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The Operations Manager 2007 database component requires Microsoft SQL Server 2005 Service Pack 1 or later. The selected instance does not have the correct version. To continue setup, go back and choose custom setup and unselect the database component or select a different instance or upgrade the selected instance to the correct version. Property(C): SQLServicesErrDlg_Title.68918168_3885_4F75_BBF8_0CC84213F8D1 = Setup failed to start Microsoft SQL Server services Property(C): SQLServicesErrDlg_Desc.68918168_3885_4F75_BBF8_0CC84213F8D1 = The Operations Manager 2007 R2 setup failed to start the Microsoft SQL server services. To continue setup, go back and choose a different instance or start the SQL Server services for the selected instance.... MSI (c) (14:50) [15:31:07:885]: 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. Additional information is available in the log file C:\Users\SQLSER~1\AppData\Local\Temp\KB2495674-x64_0.log. MSI (c) (14:50) [15:31:07:886]: Windows Installer installed an update. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Update Name: System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674). Installation success or error status: 1603. MSI (c) (14:50) [15:31:07:888]: Note: 1: 1729 MSI (c) (14:50) [15:31:07:888]: Product: System Center Operations Manager 2007 R2 -- Configuration failed. Any idea? As the RMS is down due to the CU5 installation failure I could not check all privileges... Local Administrator, SysAdmin on SQL OperationsManager, and Operations Manager Administrators svcMOMACTION is Local Administrator and in Operations Manager Administrators sqlServer is Local Administrator and SysAdmin but not part of the Operations Manager Administrators and as the server id down due to the failing update .... difficult to change??? SVCMOMSDK is Local Administrator and in Operations Manager Administrators.(running System Center Data Access Service and System Management Configuration Service) Which account should be the one to change and the third attributes? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Mazen, Let me try this... The complete logs(15 Mb) exist but I don't want to post too long stuff on this forum as it will be really long... maybe by email my own is dominique_duchemin at hotmail dot com. Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Mazen, I sent the log from the command above and the three files from the previous try from the command pormpt and the msi GUI. Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Mazen, Apparently it has been only an issue with the ServicePipesTimeout... by increasing it to 200000 I finahe three modules fine... let me review the result in the console... Lets see the next steps. The version 6.1.7221.81 is listed for the DLLs. The new agent is avalaible in the Agent management folder KB2495674-x64-ENU-Agent Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, I find this article http://blogs.technet.com/b/kevinholman/archive/2010/03/02/how-to-apply-a-scom-hotfix-to-a-clustered-rms.aspx I have a Cluster for hosting the operation database but a physical server for the RMS application does this apply? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Error 1053 The service System Center Data Access refused to start!!! after the CU5 failure So the console remains unavailable even it says the upgrade was not applied the old version is even not working anymore!! What to do? http://support.microsoft.com/kb/922918 has fixed the issue for the service, I was able to start the console and add the sqlserver account in the Operations Manager Administrator meaning it is in the three groups: SysAdmin on OperationsManager Database, Operations Manager Administrators, Local Administrator Group. but it is still failing: OMCFG: ConfigureSDKConfigService: CAStartServices failed, trying again.... Error Code: 0x8007041D. OMCFG CAStartServices: WaitForServiceState failed for start request. Error Code: 0x80070102. OMCFG System Center Data Access did not start Thanks, Dom

Hi Dom, Which account are you using for SDK and Config services? Check it in OperationsManager database\Security\Roles\Database Roles\sdk_users (Role Members) >> this account should be used for the SDK and Config services runas account. SDK and Config Service Account: http://technet.microsoft.com/en-us/library/bb735419.aspx The SDK and Config Service account is one set of credentials that is used by the System Center Data Access service and System Center Management Configuration service to update and read information in the Operations Manager database. Operations Manager ensures that the credentials used for the SDK and Configuration action account will be assigned to the sdk_user role in the Operations Manager database. The SDK and Config Service account can be configured as either Local System or as a domain account. A Local User account is not supported. If the root management server and the Operations Manager database are on different computers, the SDK and Config Service account will need to be changed to a domain account. For better security, we recommend that you use an account different from the one used for the management server action account. To change these accounts, see the Knowledge Base article How to change the credentials for the OpsMgr SDK Service and for the OpsMgr Config Service in Microsoft System Center Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=112435). Regards, Mazen

Hi Mazen, Apparently it has been only an issue with the ServicePipesTimeout... by increasing it to 200000 I finahe three modules fine... let me review the result in the console... Lets see the next steps. The version 6.1.7221.81 is listed for the DLLs. The new agent is avalaible in the Agent management folder KB2495674-x64-ENU-Agent Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Dom, After applying http://support.microsoft.com/kb/922918 are you able to start the SDK and the Config normal? Would you check if the SQL broker service enabled? SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager' 1 enabled,, 0 disabled Regards, Mazen

Yes in this Role I have svcmomsdk.System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Mazen, For the SDK and Config Services I am using svcMOMSDK it is a Domain Account. Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

is it a member in OperationsManager database\Security\Roles\Database Roles\sdk_users (Role Members)