SCOM Agent Cache

Hi Guys,
we have SCOM 2012 SP1 in production.
I'm receiving complaints from the customer that SCOM has failed to alert on an event. Example: though the agent service is running and the threshold is breached, logical disk monitor, service monitor (many others) wont generate alerts.
When i check the health explorer, the status of monitor will be "critical" but the time stamp will be very old, say months. i then i manually flush the agent cache and restart the agent service. it works then on.
we are monitoring nearly 600 agents. one or the other agent will be having this issue. it's getting hard for me to identify which agent is having this cache problem. i want to find out such agents, so that i can take some proactive action on it.
i faced this problem in SCOM 2007, 2012 & now in SP1.
has anyone came across this type of problem? Is there any solutoin to this issue? what's the best practice to overcome this issue?
Thanks in advance,
Venu
Best regards, Venu.

Hi,
To examine Agent health with the built in views in OpsMgr:
Under Monitoring, Operations Manager, Agent, Agent Health State, there is a view for all agent, for critical agent, we can flush their cache and restart the agent service.
In addition, we can use powershell script to restart all agents' health service remotely also. By using restart-service command.
Hope the below link be helpful for you:
http://blogs.technet.com/b/kevinholman/archive/2009/10/01/fixing-troubled-agents.aspx
Regards, Yan Li

Similar Messages

  • Scom agent errors from dmz computer

    hello everybody.
    i have installed scom agent on dmz computer. there is connection with scom rms server and after approving it listed in my agent managed computer list.
    but i have some erros in agent computer event log .
    hear is.
    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          03/10/2014 09:17:13
    Event ID:      11903
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      srv-ns1
    Description:
    The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
    Property Expression: Property[@Name='QueriesResponded']
    Property Value: Property[@Name='QueriesResponded']
    Conversion Type: DataItemElementTypeInteger(5)
    Original Error: 0x80FF005A
    One or more workflows were affected by this.  
    Workflow name: Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries
    Instance name: ameriaam.am on srv-ns1
    Instance ID: {CA3BB4AA-6AD9-B0CD-D35E-CF17BAC9BCE2}
    Management group: AmeriabankMG
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">11903</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-03T05:17:13.000000000Z" />
        <EventRecordID>1051</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>srv-ns1</Computer>
        <Security />
      </System>
      <EventData>
        <Data>AmeriabankMG</Data>
        <Data>Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries</Data>
        <Data>ameriaam.am on srv-ns1</Data>
        <Data>{CA3BB4AA-6AD9-B0CD-D35E-CF17BAC9BCE2}</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>DataItemElementTypeInteger(5)</Data>
        <Data>0x80FF005A</Data>
      </EventData>
    </Event>
    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          03/10/2014 09:17:13
    Event ID:      11903
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      srv-ns1
    Description:
    The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
    Property Expression: Property[@Name='QueriesResponded']
    Property Value: Property[@Name='QueriesResponded']
    Conversion Type: DataItemElementTypeInteger(5)
    Original Error: 0x80FF005A
    One or more workflows were affected by this.  
    Workflow name: Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries
    Instance name: esazatem.am on srv-ns1
    Instance ID: {8A7B8118-E730-492F-30BD-E754979CF884}
    Management group: AmeriabankMG
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">11903</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-03T05:17:13.000000000Z" />
        <EventRecordID>1049</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>srv-ns1</Computer>
        <Security />
      </System>
      <EventData>
        <Data>AmeriabankMG</Data>
        <Data>Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries</Data>
        <Data>esazatem.am on srv-ns1</Data>
        <Data>{8A7B8118-E730-492F-30BD-E754979CF884}</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>DataItemElementTypeInteger(5)</Data>
        <Data>0x80FF005A</Data>
      </EventData>
    </Event>
    Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          03/10/2014 09:17:12
    Event ID:      11903
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      srv-ns1
    Description:
    The Microsoft Operations Manager Expression Filter Module could not convert the received value to the requested type.
    Property Expression: Property[@Name='QueriesResponded']
    Property Value: Property[@Name='QueriesResponded']
    Conversion Type: DataItemElementTypeInteger(5)
    Original Error: 0x80FF005A
    One or more workflows were affected by this.  
    Workflow name: Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries
    Instance name: ameriagroup.am on srv-ns1
    Instance ID: {C57A482A-A0B6-CC89-0855-FD43B75FCE26}
    Management group: AmeriabankMG
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Modules" />
        <EventID Qualifiers="49152">11903</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-03T05:17:12.000000000Z" />
        <EventRecordID>1047</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>srv-ns1</Computer>
        <Security />
      </System>
      <EventData>
        <Data>AmeriabankMG</Data>
        <Data>Microsoft.Windows.Server.DNS.2012R2.Monitor.DNSSEC.NameResolutionQueries</Data>
        <Data>ameriagroup.am on srv-ns1</Data>
        <Data>{C57A482A-A0B6-CC89-0855-FD43B75FCE26}</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>Property[@Name='QueriesResponded']</Data>
        <Data>DataItemElementTypeInteger(5)</Data>
        <Data>0x80FF005A</Data>
      </EventData>
    </Event>

    These errors are coming from the DNS 2012 R2 MP. Is this server in your DMZ a DNS 2012 R2 Server? if not, it should go away once the discovery for this mp runs or re-runs, and the SCOM agent stops running those monitors on that agent. If it does not go away,
    stop the SCOM Agent, and clear the agent cache then start up the agent again.
    Hope this helps!
    Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
    Please remember to click “Mark as Answer” on the post that helps you!
    my new blog om2012.wordpress.com

  • Dynamic Creation of Physical Data Server / Agent cache Refresh

    Scenario:
    I have a requirement to load data from xml source to oracle DB, and the xml source will change at run time,but the xsd of the xml would remain same ( so I don't have to change the Logical data Server, models, mappings, interfaces and scenarios - only the Physical Data Server will change at runtime).I have created all the ODI artifacts using ODI studio in my Work Repo and then I'm using odi sdk to create the physical dataserver for the changed xml data source and then invoking the agent programmatically.
    Problem:
    The data is being loaded from the xml source to oracle DB for the first time, but it is not working fine from the second time onwards. If I restart the agent, it is again working fine for one more time. on the first run, I think the agent maintains some sort of cache for the physical data server details and so when ever I change the data server, something is going wrong and that is leading to the following exception. So I want to know, if there is any mechanism to handle dynamic data servers or if there is any way of clearing the agent cache, if any.
    Caused By: org.apache.bsf.BSFException: exception from Jython:
    Traceback (most recent call last):
    File "<string>", line 41, in <module>
    AttributeError: 'NoneType' object has no attribute 'createStatement'
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:346)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2458)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:48)
         at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
         at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:540)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1596)
         at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:582)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
         at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
         at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1070)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:50)
         at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
         at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:93)
         at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
         at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:68)
         at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:445)
         at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:394)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:503)
         at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
         at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
         at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
         at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
         at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
         at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
         at org.mortbay.jetty.Server.handle(Server.java:326)
         at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
         at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
         at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
         at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
         at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
         at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
         at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

    Hi ,
    If you want to load multiple files ( same structure) through one connection then in topology create M.XSD for M.XML file
    Create three directories
    RAW -- It will contain file with original name
    PRO- Processing area where file will be moved one by one & renamed it as M.XML.
    OUT- Once file data will be loaded into tables move the file M.XML from PRO to OUT.
    Go to odiexperts to create loop,
    Use odifilemove ( to move & rename/masking) to move A.XML from RAW to PRO & rename to M.XML
    use ODIfilemove to move M.XML to OUT folder & then rename back to A.XML
    Use variables to store file names & refresh
    NoneType' object has no attribute 'createStatement' : It seems that structure of your file is different & your trying to load different files in same schema. If stucture is same then use Procedure "SYNCHRONIZE ALL" after every load...
    Edited by: neeraj_singh on Feb 16, 2012 4:47 AM

  • SCOM agent install fails Error 80070035 - the network path was not found

    I have deployed SCOM 2012 agents to most servers (2008, 2008 R2, 2012, 2012R2) in our estate but some either fail to install or are not monitored. I assume the two problems are related, but for now I am concentrating on the servers that fail completely.
    Installation is from the Discovery Wizard and I have about 20 servers that fail of various server versions.
    So looking at one specific server that is failing to install the agent - a 2008 standard service pack 2
    The firewall in on and file and printer sharing is enabled for domain, remote administration is enabled for domain
    I added a specific rule to allow TCP 5723 and 5724
    DCOM is enabled
    I can Ping the target server from the SCOM server by both name and FQDN - both return the same IP and our DNS server has only one entry for this server
    I can browse to the admin share \\server\C$ from the SCOM Server, using the same account that I specify for the agent install that is a domain admin with rights on this server (and on the other servers the agent
    did install to) and the server has plenty of disk space available
    I am not sure what else to look at so would welcome any ideas
    Thanks

    Hi Petro,
    I have a Agent installation failure cheat sheet, For your error 80070035 it is said to perform a manual installation.
    So i would like to understand which version of SCOM is this ? 2007 R2 or 2012 or 2012 r2 ?
    Also check if your agents have the WMI service started and enabled ?
    Also if yours is a SCOM 2007 R2 do you have a RMS & MS in your management group ? If yes then Pushing the agent installation from MS may cause such issue. So would suggest you push the installation from RMS.
    Also check if your Network connectivity meets the minimum requirement as recommended by SCOM. Below is applicable for Both SCOM 2007 R2 & SCOM 2012 & 2012 R2.
    Component A
    Component B
    Minimum Requirement
    Root management server or management server
    Agent
    64 Kbps
    Root management server or management server
    Agentless
    1024 Kbps
    Root management server or management server
    Database
    256 Kbps
    Also check if you have any Anti virus / Firewall which is blocking the install / communication. If yes disabe or add the "Monitoringhost.exe to the safe list or what your feature is.
    Check if you have another IP assigned to the NIC card and remove it tempraurly andchecl.
    Also post the event logs of the Agents which are in not monitored state for analysis.
    SCOM Agent installation failure error codes
    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.
    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.
    8004100A
    800706BA
    1.  Ensure agent push account has local admin rights
    2.  Firewall is blocking NetBIOS access
    3.  Inspect WMI 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.
    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.
    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
    Gautam.75801

  • Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

    I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
    We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
    installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
    I have to remove the management installation first. And that's not gonna happen.
    I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
    In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
    Control Panel. And this can NOT be the most healthy way of getting through the setup.
    I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
    Any of you have tips as to how I can get rid of the agents more gracefully?

    Hi
    Thanks for the replay guys!
    None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
    I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
    days.
    Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
    agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
    So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
    but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

  • Reporting doesn't show the newly installed SCOM Agents

    Hello,
    I am running SCOM 2012 SP1 on Win2008 R2.
    I recently deployed scom agent to couple of machines the agents are showing up healthy and i can see the performance and health data from Monitoring tab but when i try to run report i can't find these new agents in the objects to add to report.
    Report
    it doesn't even query the agents.
    and on the SCOM manamgent server i see this error in event viewer not sure if it is related.
    Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.
    Exception 'SqlException': Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 368, Message: Violation of UNIQUE KEY constraint 'UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime'. Cannot insert duplicate key in object
    'dbo.ManagedEntityProperty'. The duplicate key value is (528, Aug 25 2013  8:52AM). 
    One or more workflows were affected by this.  
    Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.ManagedEntity 
    Instance name: 08eb00a2-e227-4472-a368-a6e42a2bc502 
    Instance ID: {EEFCB078-6517-97CD-FA4F-8FCAB54E4930} 
    Management group: OPSMGR
    Regards,
    Maqsood
    Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

    Ok, so at this point, without enabling logging and going to the extremes, I would attempt an uninstall and reinstall of the agents.  One at a time.  So remove the agents.  Reinstall one, and monitor what is happening on that server, and investagate
    it in the ops console.
    If you know what applications are on the box, and being discovered, look for the server in discovered inventory for those classes, etc.
    Before you do that, you can try to run this against the DW to see if there are any alerts associated with these two servers, that is if they ever raised alerts:
    USE OperationsManagerDW
    SELECT Alerts.AlertName, SUM(1) AS 'Alert Instances', SUM(Alerts.RepeatCount + 1) AS 'Alert + Repeat Count',
    CASE Alerts.MonitorAlertInd WHEN 1 THEN vMonitor.MonitorDefaultName WHEN 0 THEN vRule.RuleDefaultName ELSE 'Not found' END AS 'Rule or Monitor Name',
    CASE Alerts.MonitorAlertInd WHEN 1 THEN 'Monitor' WHEN 0 THEN 'Rule' ELSE 'Not Found' END AS 'Rule or Monitor', vManagedEntity.Path,
    vManagedEntity.DisplayName
    FROM Alert.vAlert AS Alerts INNER JOIN
    vManagedEntity ON Alerts.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId LEFT OUTER JOIN
    vRule AS vRule ON Alerts.WorkflowRowId = vRule.RuleRowId LEFT OUTER JOIN
    vMonitor AS vMonitor ON Alerts.WorkflowRowId = vMonitor.MonitorRowId
    WHERE (Alerts.RaisedDateTime BETWEEN DATEADD(day, - 180, GETDATE()) AND GETDATE()) AND
    (Alerts.AlertName like '%Hub Servers In Retry Error%') and path like '%servername%'
    GROUP BY Alerts.AlertName, Alerts.MonitorAlertInd, vMonitor.MonitorDefaultName, vRule.RuleDefaultName, vManagedEntity.Path, vManagedEntity.DisplayName
    ORDER BY 'Alert Instances' DESC
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

  • Identify where to install SCOM Agent on SCCM Site hierarchy.

    Hello..
    We have a SCCM Site environment where there is one CAS site, other 5 Primary site servers and one DB server .All are in different machines (7 VMs).i need to monitor complete SCCM site hierarchy.Next on which machines i need to install SCOM Agent on both CAS
    and all Primary Site Server.
    Thanks
    RICHA KM
     

    Hi RICHA,
    Hope it helps:
    http://blogs.technet.com/b/kevinholman/archive/2012/12/11/monitoring-configmgr-2012-with-opsmgr.aspx
    http://blogs.catapultsystems.com/cfuller/archive/2012/01/26/opsmgr-2012-scom-and-configmgr-2012-sccm-q-a.aspx
    http://msandbu.wordpress.com/2012/04/23/monitoring-sccm-2012-via-scom-2012/
    Natalya

  • Need to place the SCOM agents in Maintenance Mode automatically during Patching activity

    Hi,
    I have a requirement to place the SCOM agent servers in MM automatically during shceduled patching every month. I have gone through few blogs but could not find an apt solution for SCOM 2012 R2 environment.
    I think the process should be..
     1. Create a management pack to monitor all servers for event 1074 (or/and 22), which gets triggere during the patching
     2. Write some powershell to put a machine into maintenance mode.
     3. Trigger the powershell script to run when needed.
    Any suggestions please?
    Thanks

    Where doing this in our environment. We have a SCOM monitor looking for Reboot events (ID 1074) where the event contains Shutdown Type: Reboot. the monitor creates an Informational alert which Orchestrator picks up and then sets the machine in MM for 30
    minutes. So its any time the machine is intentionally rebooted. You can have it look for CcmExec in the Event description (assuming you're using SCCM) if you only want it to work when being patched. 
    - Slow is smooth and smooth is fast.

  • WmiPrvSE.exe Consuming A Lot of RAM on 2012R2 DCs with SCOM Agent

    Good afternoon,
    I have three Windows Server 2012 R2 Domain controllers (AD DS, DNS, and DFS roles) and I'm running SCOM 2012 R2 Update Rollup 1 with all the latest management packs for Server 2012 R2, Active Directory, DNS, and DFS.
    When I install SCOM agents on these DCs, a WmiPrvSE process starts consuming a lot of memory until it reaches around 512MB.  At that point no one can RDP to the DCs, but we can enter-possession to get-process | sort ws and kill the offending WmiPrvSE.exe
    process.  When I uninstall the SCOM agent the server returns to normal.
    Other Windows Server 2012 R2 servers in our environment don't have this problem.  And when we had Windows Server 2012 (no R2) domain controllers this wasn't an issue.  My assumption is one of the management packs are an issue.
    I've seen other posts, but they are either related to older versions of Windows Server or not domain controllers.
    These are all the features I have installed on the DCs:
    Active Directory Domain Services                                                                                                                                                             
    DNS Server                                                                                                                                                                                   
    File and Storage Services                                                                                                                                                                    
    File and iSCSI Services                                                                                                                                                                      
    File Server                                                                                                                                                                                  
    DFS Namespaces                                                                                                                                                                               
    DFS Replication                                                                                                                                                                              
    File Server Resource Manager                                                                                                                                                                 
    Storage Services                                                                                                                                                                             
    .NET Framework 3.5 Features                                                                                                                                                                  
    .NET Framework 3.5 (includes .NET 2.0 and 3.0)                                                                                                                                               
    .NET Framework 4.5 Features                                                                                                                                                                  
    .NET Framework 4.5                                                                                                                                                                           
    WCF Services                                                                                                                                                                                 
    TCP Port Sharing                                                                                                                                                                             
    Group Policy Management                                                                                                                                                                      
    Remote Differential Compression                                                                                                                                                              
    Remote Server Administration Tools                                                                                                                                                           
    Role Administration Tools                                                                                                                                                                    
    AD DS and AD LDS Tools                                                                                                                                                                       
    Active Directory module for Windows PowerShell                                                                                                                                               
    AD DS Tools                                                                                                                                                                                  
    Active Directory Administrative Center                                                                                                                                                       
    AD DS Snap-Ins and Command-Line Tools                                                                                                                                                        
    DNS Server Tools                                                                                                                                                                             
    File Services Tools                                                                                                                                                                          
    DFS Management Tools                                                                                                                                                                         
    File Server Resource Manager Tools                                                                                                                                                           
    SMB 1.0/CIFS File Sharing Support                                                                                                                                                            
    User Interfaces and Infrastructure                                                                                                                                                           
    Graphical Management Tools and Infrastructure                                                                                                                                                
    Server Graphical Shell                                                                                                                                                                       
    Windows PowerShell                                                                                                                                                                           
    Windows PowerShell 4.0                                                                                                                                                                       
    Windows PowerShell 2.0 Engine                                                                                                                                                                
    Windows PowerShell ISE                                                                                                                                                                       
    Windows Server Backup                                                                                                                                                                        
    WoW64 Support       

    I have ever seen somebody has similar problem when import DNS MP to DC. Check whether it is this situation.
    Otherwise, Open Event Viewer to see if there are any useful info there.
    Last, apply the Hotfix below.
    http://support.microsoft.com/kb/2919355
    Juke Chou
    TechNet Community Support

  • Connector sync scom agent (microsoft.systemcenter.agent)

    we are trying to sync the microsoft.systemcenter.agent class from scom to scsm with a SCSM connector. we need this to track on which server there's a SCOM agent. but it doesn't seem to work here.
    i enabled the Microsoft.SystemCenter.Library as the MP to sync in the connector and added the class to the AllowList. I can see the class and use it for views in scsm but no class instance is being synchronized.
    is there still something i could check? or is this class blocked somehow in the connector?

    Hi,
    It could be the CI's you want to synchronize are not on the "Allowed List" and you simply need to add them. Sometimes you need to do this even after importing the proper MP's into SCSM. Here is a detailed blog on the "Allowed List" :
    http://blogs.technet.com/b/servicemanager/archive/2010/02/26/managing-the-allowed-list-for-the-operations-manager-ci-connector-with-powershell.aspx
    My Blog | www.buchatech.com | www.systemcenterportal.com
    If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion
    in a test environment before implementing!

  • Need to Automate the installation of SCOM agent through Script on workgroup machine in my Environment

    Hi Guys,
    Please advise me as i need to install SCOM agent on all workgroup machine automatically and not through Copying certificate and all which is quite hectic process, your help will be Appreciated,
    Thanks
    Amit Singh

    More info:
    How to deploying SCOM Agents to the Workgroup clients
    http://blogs.technet.com/b/csstwplatform/archive/2012/05/28/how-to-deploying-scom-agents-to-the-workgroup-clients.aspx
    Installing SCOM 2012 agent on a non-domain workgroup Windows Server
    http://himmetyildiz.blogspot.com/2013/11/installing-scom-2012-agent-on-non.html
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Running SCOM Powershell cmdlets on SCOM Agent Server

    Hello,
    I have to run some SCOM cmdlets on SCOM Agent Server. But I am getting the below error.
    "Get-SCOMClass : The Data Access service is either not running or not yet initilized. Check the event log for more information."
    In the Agent Server, there is no "Data Access service".
    Please help me in running the SCOM cmdlets on SCOM Agent Server.
    Thanks in advance.
    Regards,
    Mahadevan.G

    Hi Mahadevan:
    On a SCOM management server, the SDK service name is "System Center Data Access Service". If you don't see that service listed then you are not on a SCOM management server.
    Not sure what you mean "SCOM Agent Server"? The SCOM cmdlets won't run on a computer with just the SCOM agent installed unless you also install the SCOM console/powershell features from the SCOM install media.
    The Get-SCOMClass cmdlet (or Get-SCClass) should run on a management server with no problems. Recommend check again that you are really logged into a SCOM management server.
    John Joyner MVP-SC-CDM

  • ConfigMgr 2012 MP – suspending SCOM agent/health service

    Hi,
    I use SCOM agent/health for our SLA reporting. I found a handful of servers last month with something like 99.9% uptime even though I knew they had been up all of the time. Looking in the Operations Manager event log I have found the following events related
    to ConfigMgr 2012 -
    The System Center 2012 - Operations Manager agent running on computer "XXXXXXXXXXXXX" is suspended for the following reason:
    "ConfigMgr 5.00.7804.1000 - SMS_MaintenanceTaskRequests –
    I am trying to understand what and why it is doing this. Presumably something in the ConfigMgr MP is trying to “fix” something with a task? However if I checked open/closed alerts for the servers involved I can’t see any type of alert getting created.
    I have opened the ConfigMgr MP with “Management Pack Viewer” but can’t find any Diagnostics, Recoveries or Tasks listed. Just wondered if anyone had any idea what this was or perhaps it’s a task related to a SCOM internal MP itself? I can’t find any other examples
    of the agent getting suspended whilst something gets “fixed”

    Hi,
    This event is telling you that the SCOM Agent is being paused for an SCCM Maintenance task (often a backup).
    For more information, please refer to the link below:
    Use of Disable Operations Manager alerts option in ConfigMgr
    http://blog.tyang.org/2014/04/24/use-disable-operations-manager-alerts-option-configmgr/
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Find out what servers have a SCOM agent installed

    Hello, 
    With a list of approx 1400 servers, I am after a quick way to see which ones have SCOM agent installed on them? 
    This is over one domain . 
    Thanks in advance
    Tubble with Microsoft

    You can get all servers with SCOM agents and export to a CSV fileGet-Agent | select-object PrincipalName,ComputerName,Domain | export-csv c:\allServerlist.csv
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical

  • SCOM Agent install \ deployment query?

    Hi All
    I have a query regards best practices.  Within our environment we will have a number of Build Environments (all within the same domain), which will involve servers being built, decommissioned and rebuilt for application testing teams.
    Query is how best to handle the install\life-cycle of the SCOM Agent with regards to this scenario?
    Just looking to see if others have had experience of this type of scenario and best practices \ experiences etc
    Any thoughts much appreciated.
    Kind Regards
    Andrew

    Just have a couple of questions/suggestions:
    Do the different servers have some sort of naming convention ie:
    Prod servers have: PRD in the name
    dev servers have: DEV in the name
    ect.... If so then my suggestion is to create a number of groups ie Prod Servers, Dev Servers, Test Servers ect. and have these groups auto populate. You can then configure overrides for these groups for alerts
    to manage alert volume/escalations.
    As for install are these servers windows server/ unix servers or a mix?
    Number of ways you could try managing installs is to script the install (Google SCCM SCOM agent deployment script for some hints)
    Consider if you want to auto approve agents or manually approve them so you know when servers are being added or removed.
    If servers are being removed you could look at scripting a removal of the server from SCOM (have a look at http://social.technet.microsoft.com/Forums/en-US/c4dcfce6-b241-4435-8f8b-1276814c455e/scom-2012-powershell-command-to-remove-agent)
    If you could detail what your setup is or what you would like to be able to do we could make more suggestions.
    Cheers,
    Martin
    Blog:
    http://sustaslog.wordpress.com 
    LinkedIn:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Maybe you are looking for