SCOM 2012 Agent Install Failed with Error Code: 80070645

We are trying to deploy SCOM 2012 agent to a Windows server 2008 R2 SP1 server, but we got the following error message:

The Operations Manager Server failed to perform specified operation on computer XXXXX 
Operation: Agent Install 
Install account: XXXX
Error Code: 80070645 
Error Description: This action is only valid for products that are currently installed.

Here is the agent mgmt log:

10:09:52 AM : CServiceModule::Init : m_bService is set to true. HResult: 0
10:09:52 AM : CServiceModule::Start : Service flag is set
10:09:52 AM : CServiceModule::SetServiceStatus : State: 2, Error: 0
10:09:52 AM : CServiceModule::SetServiceStatus : State: 2, Error: 0
10:09:52 AM : IsCurrentMOMServerInstalled : MOM Setup key could not be queried.
10:09:52 AM : CServiceModule::_RegisterFile : Before LoadLibrary
10:09:52 AM : CServiceModule::_RegisterFile : After LoadLibrary
10:09:52 AM : CServiceModule::_RegisterFile : Before GetProcAddress
10:09:52 AM : CServiceModule::_RegisterFile : After GetProcAddress
10:09:52 AM : CServiceModule::_RegisterFile : After FreeLibrary
10:09:52 AM : CServiceModule::RegisterFile : Success return
10:09:52 AM : CServiceModule::RegisterFile : WaitForSingleObject return  HResult: 0
10:09:52 AM : CServiceModule::SetServiceStatus : State: 4, Error: 0
10:09:53 AM : OmAgentFunctions::GetPatches : Entering
10:09:53 AM : OmAgentFunctions::GetPatches : MsiEnumPatches failed HResult: 80070645
10:09:53 AM : OmAgentFunctions::GetPatches : Leaving
10:09:53 AM : CServiceModule::SetServiceStatus : State: 3, Error: 0
10:09:53 AM : CServiceModule::SetServiceStatus : State: 3, Error: 0
10:09:53 AM : IsCurrentMOMServerInstalled : MOM Setup key could not be queried.
10:09:53 AM : CServiceModule::_RegisterFile : Before LoadLibrary
10:09:53 AM : CServiceModule::_RegisterFile : After LoadLibrary
10:09:53 AM : CServiceModule::_RegisterFile : Before GetProcAddress
10:09:53 AM : CServiceModule::_RegisterFile : After GetProcAddress
10:09:53 AM : CServiceModule::_RegisterFile : After FreeLibrary
10:09:53 AM : CServiceModule::RegisterFile : Success return
10:09:53 AM : CServiceModule::RegisterFile : WaitForSingleObject return  HResult: 0
10:09:53 AM : CServiceModule::SetServiceStatus : State: 1, Error: 0

We saw some article suggest installing the agent manually, but we don't want this workaround, because if we install agent manually for this one particular server, in the future, we will always have to update it manually. We have deployed the same agent to a lot of other serves without any problem. Can anyone help?

Thanks.


  • Edited by IBM236 Tuesday, September 23, 2014 2:36 PM
September 23rd, 2014 2:35pm

Makes sure that
1)The following ports must be open between the Management Server and the target computer:
RPC endpoint mapper Port number: 135 Protocol: TCP/UDP
RPC/DCOM High ports (2000/2003 OS) Ports 1024-5000 Protocol: TCP/UDP
RPC/DCOM High ports (2008 OS) Ports 49152-65535 Protocol: TCP/UDP
NetBIOS name service Port number: 137 Protocol: TCP/UDP
NetBIOS session service Port number: 139 Protocol: TCP/UDP
SMB over IP Port number: 445 Protocol: TCP
MOM Channel Port number: 5723 Protocol: TCP/UDP
2)The following services must be enabled and running on the target computer:
Netlogon
Remote Registry
Windows Installer
Automatic Updates
3)  account previously specified to perform the agent installation in the discovery wizard will has local administrator permissions
4) Group Policy Objects in Active Directory does not prevent the Management Server computer account, or the user account used by the Discovery Wizard, from remotely accessing the Windows folder, the registry, WMI or administrative shares on the target computer


Roger

Free Windows Admin Tool Kit Click here and download it now
September 24th, 2014 3:23am

Hi,

Check if you have one of these registry keys on the server:

HKLM:\SOFTWARE\Microsoft\Microsoft Operations Manager

HKLM:\SYSTEM\CurrentControlSet\services\HealthService

HKLM:\SYSTEM\CurrentControlSet\services\AdtAgent

September 24th, 2014 6:47am

You can check Bob's blog here for this issue

http://www.bictt.com/blogs/bictt.php/2010/05/07/scom-agent-error-microsoft-esent-keys-are-required

Free Windows Admin Tool Kit Click here and download it now
September 28th, 2014 2:14pm

also make sure the agent is not already deployed to that machine. SCOM throws an error at you when that is done from the console as well.

September 29th, 2014 3:15am

Hi!

Had the same problem. 

Solution: removed all the Operations Manager registry entries (2007/2012) and did again the discover of the Windows Server 2003 R2 SP2 (x64).

Install agent OpsMgr 2012 R2 successful!

Best regards

Free Windows Admin Tool Kit Click here and download it now
May 11th, 2015 1:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics