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 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. |
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? 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 |
30 Eylül 2010 Perşembe
Agent kurulumlarında çıkan hatalar ve nedenleri, yararlı bir tablo....
OpsMgr Script hatalarını gidermek
Alper bey'den yararlı bilgiler....
Operations Manager, agentlarda Health Service’i memory’de “healthservice.exe” olarak çalıştırır. Internal olmayan işlemler için (Management Pack’lerden gelen workflow’ları çalıştırmak, performans datası toplamak vb) HealthService.exe MonitoringHost.exe isimli instance’lar oluşturur. MonitoringHost.exe performans datası toplayabilir veya Cscript.exe vasıtası ile agent kurulu bilgisayar üzerinde script çalıştırarak birçok monitoring işlemi gerçekleştirebilir.
Bu script’ler bazı durumlarda çalışamaz ve hata verir ve Operations Manager Console’unda script hataları görmeye başlarsınız.
Management Pack Güncellemeleri veya Yapılandırılması
Öncelikl Operations Manager Management Group’unuza import ettiğiniz Management Pack’lerin son versiyonlarını kurmalı ve beraberinde gelen dokümana göre detaylı olarak yapılandırmalısınz. Bununla birlike arama motorlarından genel bir arama yapıp Mangement Pack ile ilgili olası bug’ları temizlmelisiniz. Yapılandırılmamış, import edildiği şekilde bırakılmış Management Pack’lerdeki birçok script hata verebilir.
Öncelikl Operations Manager Management Group’unuza import ettiğiniz Management Pack’lerin son versiyonlarını kurmalı ve beraberinde gelen dokümana göre detaylı olarak yapılandırmalısınz. Bununla birlike arama motorlarından genel bir arama yapıp Mangement Pack ile ilgili olası bug’ları temizlmelisiniz. Yapılandırılmamış, import edildiği şekilde bırakılmış Management Pack’lerdeki birçok script hata verebilir.
Antivirüs
Bu hataların birçoğunu, agent kurulu makinelerde Operations Manager script’lernin bulunduğu klasörü (Örn: “C:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store) antivirüs veya uygulama seviyesi güvenlik sağlayan yazılımınızdan exclude ederek giderebilirsiniz.
Bu hataların birçoğunu, agent kurulu makinelerde Operations Manager script’lernin bulunduğu klasörü (Örn: “C:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store) antivirüs veya uygulama seviyesi güvenlik sağlayan yazılımınızdan exclude ederek giderebilirsiniz.
Windows Server 2003 WMI Güncellemesi
Bununla birlikte http://support.microsoft.com/kb/933061 maklesinde bulunan güncellemeyi x86 veya x64 Windows Server 2003 SP1 veya Sp2′lerinize yüklerseniz Windows Server 2003 üzerinde WMI’ın çalışması ile ilgili birçok hatayı giderecektir.
Bununla birlikte http://support.microsoft.com/kb/933061 maklesinde bulunan güncellemeyi x86 veya x64 Windows Server 2003 SP1 veya Sp2′lerinize yüklerseniz Windows Server 2003 üzerinde WMI’ın çalışması ile ilgili birçok hatayı giderecektir.
WMI Buffer’ının Arttırılması
WMI servisinin belirli bir buffer boyutu vardır.Çalıştırılan WMI Script’leri bu buffer’ı doldurursa WMI, servisine “sleep delay” inject ederek yeni objeleri kabul etmemeye başlayabilir. Operations Manger ajanı kurulacak bilgisayarlarda bu buffer’ın registry’den arttırılması önerilir:
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\Low Threshold On Events (B)” değerini 35000000 yapın (default olarak 10000000)
”HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\High Threshold On Events (B)” değerini 70000000 yapın (default olarak 20000000)
WMI servisinin belirli bir buffer boyutu vardır.Çalıştırılan WMI Script’leri bu buffer’ı doldurursa WMI, servisine “sleep delay” inject ederek yeni objeleri kabul etmemeye başlayabilir. Operations Manger ajanı kurulacak bilgisayarlarda bu buffer’ın registry’den arttırılması önerilir:
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\Low Threshold On Events (B)” değerini 35000000 yapın (default olarak 10000000)
”HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\High Threshold On Events (B)” değerini 70000000 yapın (default olarak 20000000)
Windows Scripting Host (CScript) versiyonunun yükseltilmesi
http://support.microsoft.com/kb/955360 adresindeki güncellemeyi yükleyerek CScript’in versiyonunu 5.7′ye yükseltin. Bu güncelleme script’lerin çalışırken çok fazla CPU harcaması, script timeout ve eşzamanlı çalışan scriptlerin sebep olduğu hataları gidermektedir. Windows Server 2003 SP1 ve SP2′ye (x86, x64) uygulanır. DNS, DHCP ve Domain Controller’lar için çok faydalı bir hotfix’tir. Aynı zamanda doğası gereği fazla işlemci gücü kullanan VBScript’lerin kaynak kullanımını da azaltır.
http://support.microsoft.com/kb/955360 adresindeki güncellemeyi yükleyerek CScript’in versiyonunu 5.7′ye yükseltin. Bu güncelleme script’lerin çalışırken çok fazla CPU harcaması, script timeout ve eşzamanlı çalışan scriptlerin sebep olduğu hataları gidermektedir. Windows Server 2003 SP1 ve SP2′ye (x86, x64) uygulanır. DNS, DHCP ve Domain Controller’lar için çok faydalı bir hotfix’tir. Aynı zamanda doğası gereği fazla işlemci gücü kullanan VBScript’lerin kaynak kullanımını da azaltır.
Kaydol:
Kayıtlar (Atom)