Console based Agent Deployment Troubleshooting table


<!--[if lt IE 9]>

<![endif]-->

Comments (36)

  1. Anonymous says:

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

  2. Kevin Holman says:

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

  3. Kevin Holman says:

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

  4. Dominique 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. Kevin Holman 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”)

    1. John Bradshaw says:

      Lifesaver!

  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.

  33. Georg says:

    Addition for 80070005:

    If install account is a member of Protected Users AD Group installation failed with error.

    I think problem caused by CredSSP that disabled for accounts in this group

  34. Atif Aman says:

    Hi Kevin,
    My scom is showing 60 gray agents out of 370 .
    I tried your all given troubleshooting instructions and confirmed the results but no luck
    Here is small brief:

    1. I can discover the machines and install/reinstall the agent. and It shows up healthy in SCOM MS (Green with check sign) but after a couple of heartbeats become Gray.
    2. I am getting Error message ” System Center Management Health Service Unloaded System Rules(s)

    Alert Description :
    The System Center Management Health Service FFE470E1-5F55-CF44-FC7C-1ABC9C5A340F running on host PMANDCTW01.westfrasertimber.ca and serving management group with id {95B7ADE0-427C-B1DE-0B59-EBF5F3612BC9} is not healthy. Some system rules failed to load.

    Checklist / Troubleshooting Steps:
    DNS name resolution (Agent to MS, and MS to Agent) – good
    DNS domain membership (disjointed)
    DNS suffix search order
    Kerberos connectivity
    Kerberos SPN’s accessible
    Firewalls blocking 5723
    Firewalls blocking access to AD for authentication
    Packet loss
    Invalid or old registry entries
    Missing registry entries
    Corrupt registry
    Default agent action accounts locked down/out (HSLockdown)
    HealthService Certificate configuration issues.
    Hotfixes required for OS Compatibility
    Management Server rejecting the agent

    1. Kevin Holman says:

      Your best friend is the agent’s OpsMgr event log.

      If it is unloading system rules and going grey – this is usually bad management packs, or a supported configuration mismatch.

      What version of SCOM? What SCOM version of agent? What OS version are the troublemakers? Is SCOM and agent patched to a recent UR? Is you SCOM environment connected to OMS and downloading the intelligence packs? There is a known issue of OMS causing some issues on older agent OS versions.

Skip to main content