Console based Agent Deployment Troubleshooting table


This post is a list of common agent push deployment errors… and some possible remediation options.

 

 

Most common errors while pushing an agent:

 

Error Error Code(s) Remediation Steps

The MOM Server could not execute WMI Query "Select * from Win32_Environment where
NAME=’PROCESSOR_ARCHITECTURE’" on computer server.domain.com

Operation: Agent Install
Install account: domain\account
Error Code: 80004005
Error Description: Unspecified error

80004005

1.  Check the PATH environment variable.  If the PATH statement is very long, due to lots of installed third party software – this can fail.  Reduce the path by converting any long filename destinations to 8.3, and remove any path statements that are not necessary.  Or apply hotfix:  http://support.microsoft.com/?id=969572

2.  The cause could be corrupted Performance Counters on the target Agent.

To rebuild all Performance counters including extensible and third party counters in Windows Server 2003, type the following commands at a command prompt. Press ENTER after each command.
cd \windows\system32
lodctr /R
Note /R is uppercase.
Windows Server 2003 rebuilds all the counters because it reads all the .ini files in the C:\Windows\inf\009 folder for the English operating system.

How to manually rebuild Performance Counter Library values
http://support.microsoft.com/kb/300956

3.  Manual agent install. 

The MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.

The MOM Server could not execute WMI Query "(null)” on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.

8004100A

800706BA

1.  Ensure agent push account has local admin rights

2.  Firewall is blocking NetBIOS access.  If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed.  We need port 135 (RPC) and the DCOM port range opened for console push through a firewall. 

3.  Inspect WMI service, health, and rebuild repository if necessary

4.  Firewall is blocking ICMP  (Live OneCare)

5.  DNS incorrect

The MOM Server failed to open service control manager on computer "servername.domain.com". Access is Denied
Operation: Agent Install
Install account: DomainName\User Account
Error Code: 80070005
Error Description: Access is denied.

80070005

80041002

1.  Verify SCOM agent push account is in Local Administrators group on target computer.

2.  On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin.

3.  Disable McAfee antivirus during push

The MOM Server failed to open service control manager on computer "servername.domain.com".
Therefore, the MOM Server cannot complete configuration of agent on the computer.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.

800706BA 1.  Firewall blocking NetBIOS ports

2.  DNS resolution issue.  Make sure the agent can ping the MS by NetBIOS and FQDN.  Make sure the MS can ping the agent by NetBIOS and FQDN

3.  Firewall blocking ICMP

4.  RPC services stopped.

The MOM Server failed to acquire lock to remote computer servername.domain.com. This means there is already an agent management operation proceeding on this computer, please retry the Push Agent operation after some time.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 80072971
Error description: Unknown error 0x80072971

80072971

This problem occurs if the LockFileTime.txt file is located in the following folder on the remote computer:
%windir%\422C3AB1-32E0-4411-BF66-A84FEEFCC8E2
When you install or remove a management agent, the Operations Manager 2007 management server copies temporary files to the remote computer. One of these files is named LockFileTime.txt. This lock file is intended to prevent another management server from performing a management agent installation at the same time as the current installation. If the management agent installation is unsuccessful and if the management server loses connectivity with the remote computer, the temporary files may not be removed. Therefore, the LockFileTime.txt may remain in the folder on the remote computer. When the management server next tries to perform an agent installation, the management server detects the lock file. Therefore, the management agent installation is unsuccessful.

http://support.microsoft.com/kb/934760/en-us

The MOM Server detected that the following services on computer "(null);NetLogon" are not running. These services are required for push agent installation. To complete this operation, either start the required services on the computer or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Remote Computer Name: servername.domain.com Install account: DOMAIN\account
Error Code: C000296E
Error Description: Unknown error 0xC000296E

C000296E

1.  Netlogon service is not running.  It must be set to auto/started

The MOM Server detected that the following services on computer
"winmgmt;(null)" are not running

C000296E 1.  WMI services not running or WMI corrupt

The MOM Server detected that the Windows Installer service (MSIServer) is disabled on computer "servername.domain.com". This service is required for push agent installation. To complete this operation on the computer, either set the MSIServer startup type to "Manual" or "Automatic", or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: C0002976
Error Description: Unknown error 0xC0002976

C0002976

1.  Windows Installer service is not running or set to disabled – set this to manual or auto and start it.

The Agent Management Operation Agent Install failed for remote computer servername.domain.com.
Install account: DOMAIN\account
Error Code: 80070643
Error Description: Fatal error during installation.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameAgentInstall.LOG
C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameMOMAgentMgmt.log" on the Management Server.

80070643

1.  Enable the automatic Updates service…. Install the agent – then disable the auto-updates service if desired.
Call was canceled by the message filter 80010002 Install latest SP and retry. One server that failed did not have Service pack installed
The MOM Server could not find directory \\I.P.\C$\WINDOWS\. Agent will not be installed on computer "name". Please verify the required share exists. 80070006

1.  Manual agent install

Possible locking on registry?

http://www.sysadmintales.com/category/operations-manager/

Try manual install.

Verified share does not exist.

The network path was not found. 80070035 1.  Manual agent install
The Agent Management Operation Agent Install failed for remote computer "name". There is not enough space on the disk. 80070070 1.  Free space on install disk
The MOM Server failed to perform specified operation on computer "name". The semaphore timeout period has expired. 80070079

NSlookup failed on server. Possible DNS resolution issue.

Try adding dnsname to dnssuffix search list.

The MOM Server could not start the MOMAgentInstaller service on computer "name" in the time. 8007041D

80070102

NSlookup failed on server. Possible DNS resolution issue.

Verify domain is in suffix search list on management servers.

Sometimes – the Windows Firewall service – even if disabled – will have a stuck rule.  Run:  (netsh advfirewall firewall delete rule name=”MOM Agent Installer Service”)

The Agent Management Operation Agent Install failed for remote computer "name" 80070643 1.  Ensure automatic updates service is started
2.  Rebuild WMI repository
3.  DNS resolution issue
The Agent Management Operation Agent Install failed for remote computer "name". Another installation is already in progress. 80070652

Verify not in pending management. If yes, remove and then attempt installation again.

The MOM Server detected that computer "name" has an unsupported operating system or service pack version 80072977 Install latest SP and verify you are installing to Windows system.
Not discovered   Agent machine is not a member of domain
Ping fails   1.  Server is down
2.  Server is blocked by firewall
3.  DNS resolving to wrong IP.
Fail to resolve machine   1.  DNS issue
The MOM Server failed to perform specified operation on computer "name". Not enough server storage… 8007046A 1.  This is typically a memory error caused by the remote OS that the agent is being installed on.
There are currently no logon servers available to service the logon request. 8007051F 1.  Possible DNS issue
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. 8007064D 1.  Install Windows Installer 3.1
The network address is invalid 800706AB

Possible DNS name resolution issue.

Tried nslookup on server name and did not get response.

Verify domain is in suffix search list on management servers.

The MOM Server failed to perform specified operation on computer servername.domain.com 80070040 1.  Ensure agent push account has local admin rights
The MOM Server detected that the actual NetBIOS name SERVERNAME is not same as the given NetBIOS name provide for remote computer SERVERNAME.domain.com. 80072979 1.  Correct DNS/WINS issue.
2.  Try pushing to NetBIOS name
The Operations Manager Server cannot process the install/uninstall request for computer xxxxxxx due to failure of operating system version verification 80070035 When Error Code: 80070035 appears with a Console based installation of the OpsMgr Agent and the targeted systems are Windows Server 2008 based systems which have their security hardened by using the Security Configuration Wizard, check to see whether the Server service is running
     
Comments (32)

  1. Anonymous says:

    Thanks to Kevin Holman: Console based Agent Deployment Troubleshooting table and Which hotfixes should

  2. Anonymous says:

    Are you saying that "domainSCOMsvcacct" is a DOMAIN ADMIN on the domain controller for the WAN site?

  3. Anonymous says:

    Thats odd…. because I have a $ sign in my password – and it works just fine.  

  4. Anonymous says:

    Hi Kevin,

    I think this code is not in the list above …

    The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time,

    or established connection failed because connected host has failed to respond.).  

    Please verify there is network connectivity, the server is running and has registered it’s listening port,

    and there are no firewalls blocking traffic to the destination.

    Thanks,

    Dom

  5. Anonymous says:

    Peter – without the text that was shown with the error number, I cant help.

  6. Anonymous says:

    Your table shows c000296E error with a service name but as I push/repair to the SP1 agent for R2 upgrade, I get:

    The Operations Manager Server detected that the following services on computer "(null)" are not running. These services are required for push agent installation. To complete this operation, either start the required services on the computer or install the Operations Manager agent manually by using MOMAgent.msi located on the product CD. Operation: Agent Install Remote Computer Name: <server.domain.com> Install account: <Agent Action Account> Error Code: C000296E Error Description: Unknown error 0xC000296

    Any thoughts on what service to check?

  7. Anonymous says:

    Kevin,

    "The Agent Management Operation Agent Install failed for remote computer XXXXXX.

    Install account: XXXXXXX

    Error Code: 80070652

    Error Description: Another installation is already in progress. Complete that installation before proceeding with this install."

    I am getting above error when I try to push the agent from console. I have checked that Server is not listed in Pending Management. Please spread some light on this issue.

    Thanks,

    Suresh

  8. chicken_neck says:

    I received "The network path was not found. Result code: 80070035" when attempting to modify/create a custom data provider / NT performance counter by browsing a remote computer.  Turns out, you need remote registry service on, at least to add it and see the detatils of the parameter on the remote server.

  9. jb says:

    For the first one, I found running wbemtest that processor_architecture was completely missing from the win32_environment class. By doing this: creat a new REG_SZ value PROCESSOR_ARCHITECTURE under HKCUEnvironment identical with the one under HKLMSYSTEMCurrentControlSetControlSession ManagerEnvironment.

    I found it was created! Then the remote installs worked.

  10. will says:

    I received 80070643 when trying to push out agents from the console. 80070643 is a generic error. The cause was due to the fact that I had  dollar sign "$" in my password. (Example = Pa$$word)  It’s crazy, I know. It was recreated in a test environment, and the dollar sign in the password was definitely the cause. I hope this helps.

  11. Zarif says:

    i am gettin and error stating 80070040. the Specified network name is no longer available.

    based on the resolutions above will verifying that the agent push account has local admin rights fix this problem as well?

  12. Lyons Pope says:

    I am getting a C000296E error on my R2 agent push, but it does not show what is not running like your examples.  It just says,"The Operations Manager Server detected that the following services on computer "(null)" are not running"

    Any Ideas?

  13. I actually had lots of agent install errors, and it turned out TEMP was hardcoded to a partition that wasn't present. If the agent got installed, it simply refused to start. Once we rewrote the TEMP (written somewhere in registry, cant remember exactly where) to %SYSTEMROOT%Temp the agent started fine.

  14. justin says:

    Thank you for the information provided,

    But sadly my incident matched none of above:

    I'm trying to push to windows 2008 x64 which is domain controller for WAN site, which fails with below error:

    The Operations Manager Server failed to open service control manager on computer computername.domain.

    Therefore, the Server cannot complete configuration of agent on the computer.

    Operation: Agent Install

    Install account: domainSCOMsvcacct

    Error Code: 80070005

    Error Description: (null)

    —–

    I tried manual install also, but System Center OM service does not start.

    there are many more Windows 2008 servers that agent install not successful.

    Windows 2008 OS reinstalled recently so cannot be issues with OS, firewall disabled and there are other servers in the same subnet/site so cannot be firewall issue.

    User domain admin acct for all operations, so cannot be permissions issue.

    Appreciate your advice in this matter.

    Thanks.

  15. Vitthal N says:

    I am facing an issue that while installing scom agent from console. it is not discovered if i point any member server for installation, however if i point RMS then it getting discovered successfully.

  16. Deepak K says:

    I am facing an issue that while installing scom agent from console. it is not discovered if i point any member server for installation, however if i point RMS then it getting discovered successfully.

    Can you help on this.

  17. tingleau says:

    I was facing an issue and this blog helped.

    thanks.

  18. Ravi HR says:

    The Operations Manager Server could not start the MONAgentInstaller service on computer

    This service is user to perform configuration operations on the computer before the system center operations mangaer agent can be configured.

    Opertation: Agent Install

    Install Account: Domainaccount

    Error code:- 80070102

    Error Description: (null)

  19. Dominique says:

    Hello Kevin,

    I have this error on machine wehere the agent was installed before and as it went grayed out it has been uninstalled after other tries. Now trying to reinstall the agent is giving the following error:

    The Operations Manager Server failed to open service control manager on computer Server name

    Therefore, the Server cannot complete configuration of agent on the computer.

    Operation: Agent Install

    Install account: ADSVCMOMAction

    Error Code: 80070005

    Error Description: (null)

    The account svcMOMAction is a local Administrators

    The account used to push is in the Administrators Group on the local machine.

    It is not domain controller

    These machines were having the agent before but got grayed out since…

    There is no firewall

    Any idea?

    Thanks,

    Dom

  20. Dillon B says:

    I'm seeing error two from above for all agents push-out attempts from all scom management servers. can no longer roll out agents. question is how do you perform remedy 3 from the list? "3.  Inspect WMI service, health, and rebuild repository if necessary" I've ruled out all remedy's 1,2,4 and 5 as the cause.

    inspect wmi service where?

    health? health of what? where?

    rebuild what repository? how?

    thanks

  21. Peter says:

    Kevin,

    Have you seen error: 80070654? If yes to you know any resolution?

    Thanks!

  22. Code unknown? says:

    Hello Kevin,

    I am getting a code which is not listed:

    800706BE

    any idea?

    Thanks,

    Dominique

  23. John Bradshaw says:

    Saved my bacon again!! Thx Kevin.

  24. Dominique says:

    Hello,

    The MOM Server failed to perform specified operation on computer servername.domain.com 80070040 1.  Ensure agent push account has local admin rights

    The Installed By is correct but the Action Account is wrong, how to corect it?

    Thanks,

    DOm

  25. Manjun Wang says:

    please add 'Error Code 80070641', 'Remediation Steps' = 'turn User Access Control off'

  26. Schliam says:

    I saw some info on error code 800706BA but im not sure what to do with it??  I got it when i was installing MS updates.  Ive also been getting a blue screen with STOP:0x0000007E so not sure if these two are somehow tied together. Any recommendations would be great?

  27. markd says:

    Hi Kevin,

    We moving from SCOM 2007 to SCOM 2012 (100% new SCOM environment – nothing was upgraded).  On a few servers that I want to report to a gateway server, I get the following:

    The Operations Manager Server failed to open service control manager on computer DUDESTAGING20DB.prod.sd.local.

    Therefore, the Server cannot complete configuration of agent on the computer.

    Operation: Agent Install

    Install account: NT AUTHORITYSYSTEM

    Error Code: 80070005

    Error Description: Access is denied.

    I verified the following:

    – "Verify SCOM agent push account is in Local Administrators group on target computer."  Done – domainSCOM12SvcAct is a local admin.

    -"On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin."  The servers with the error on the installation are not domain controllers.  They can ping and telnet to the gateway server which is on the same subnet.

    -"Disable McAfee antivirus during push".  Done, but installation still fails.

    A manual install of the agent works after uninstalling the agent from SCOM 2007.  I attempted a push of the agent after uninstalling SCOM 2007 agent and it still fails.  Any ideas?

  28. Gwenael says:

    Wiil is right, I have the same error issue 80070643, $ in my password, and I confirm it works with an other account with no $ in password !!!!!!

    Juste save my day 🙂 Thank Will !!

    Precision, two account have the exact same rigtht, domain adminiwstrator 😉

    Remove your dollars..

  29. Deltawp says:

    Thanks awesome   ! ! !  -> 80070102 Sometimes – the Windows Firewall service – even if disabled – will have a stuck rule.  Run:  (netsh advfirewall firewall delete rule name=”MOM Agent Installer Service”)

  30. JSee says:

    I am trying to install SCOM agent manually using MomAgent.msi. I do get the error " A 32 bit version of the agent must be uninstalled before upgrade to 64 bit" (used AMD64). However, i don’t see any agent already installed on the server. I cant i386 files
    as my processor is AMD64 and OS is x64. i am not sure if we have to tweek any Reg Keys for this. Please suggest.

  31. Justen H says:

    I received error 80070643 during my SCOM 2012 R2 agent rollout. I ran lodctr /R to rebuild the perfmon counter library, and it works just fine now.

  32. Graham C says:

    I was getting the Access Denied error, tried everything to resolve it. Turns out the SCOM server required access to the internet to push the agent to another server on the same subnet and same domain. Blocking Access at the network gateway firewall caused
    the Access denied, enabling it again and the agent was installed with no issues.