<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: WBEM Data collection timeout in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728608#M42747</link>
    <description>Hi Greg,&lt;BR /&gt;&lt;BR /&gt;You may run the repair agent task on selected server to repair/install missing/corrupted setting and agents. this will also check the connections.&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;Aftab&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 20 Dec 2010 16:26:22 GMT</pubDate>
    <dc:creator>Ali</dc:creator>
    <dc:date>2010-12-20T16:26:22Z</dc:date>
    <item>
      <title>WBEM Data collection timeout</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728607#M42746</link>
      <description>I have been having trouble with my Data Collection job were it seems like the WBEM\WMI service hangs and SIM starts to timeout collecting the data.&lt;BR /&gt;&lt;BR /&gt;[WBEM] Data collection on this system has exceeded the allowed time.&lt;BR /&gt;&lt;BR /&gt;I can fix it by deleting the nodesecurity.xml file and recycling the SIM and WMI services.  Problem is, it still fails after a day or two and the data collection job runs and overwrites all of our disk stat information.&lt;BR /&gt;&lt;BR /&gt;SIM = 6.0&lt;BR /&gt;WMI Mappper = 2.7.1&lt;BR /&gt;SIM OS = Server 2008 x64 sp2&lt;BR /&gt;&lt;BR /&gt;Are there any tips for troubleshooting the data collection and wmi?  Data collection works when it uses the SNMP protocol, but 50% of our servers are virtual and I need to pull disk information for these as well.  Thank you.</description>
      <pubDate>Mon, 20 Dec 2010 15:15:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728607#M42746</guid>
      <dc:creator>Greg Bates</dc:creator>
      <dc:date>2010-12-20T15:15:20Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM Data collection timeout</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728608#M42747</link>
      <description>Hi Greg,&lt;BR /&gt;&lt;BR /&gt;You may run the repair agent task on selected server to repair/install missing/corrupted setting and agents. this will also check the connections.&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;Aftab&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Dec 2010 16:26:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728608#M42747</guid>
      <dc:creator>Ali</dc:creator>
      <dc:date>2010-12-20T16:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM Data collection timeout</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728609#M42748</link>
      <description>But it's not an agent problem.  It is a SIM server problem.  I can get the data collection to work if the WMI mapper service is working properly.  Something makes it stop working though, then all the WBEM collections time out after that.&lt;BR /&gt;&lt;BR /&gt;It's all or none.</description>
      <pubDate>Mon, 20 Dec 2010 16:30:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728609#M42748</guid>
      <dc:creator>Greg Bates</dc:creator>
      <dc:date>2010-12-20T16:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM Data collection timeout</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728610#M42749</link>
      <description>Hi Greg,&lt;BR /&gt;&lt;BR /&gt;it's just a name of the option.&lt;BR /&gt;&lt;BR /&gt;Please check what all it does in this guide\&lt;BR /&gt;&lt;A href="http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/repairAgents_5.pdf" target="_blank"&gt;http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/repairAgents_5.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;it verifies the target systems their connections, SNMP/WBEM configuration, authentications, SSH, SSl and many other things, actually it helps diagnose the issue.&lt;BR /&gt;&lt;BR /&gt;another option HP Insight Managed System Setup Wizard which is also incrediable.&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;aftab</description>
      <pubDate>Mon, 20 Dec 2010 17:15:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728610#M42749</guid>
      <dc:creator>Ali</dc:creator>
      <dc:date>2010-12-20T17:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM Data collection timeout</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728611#M42750</link>
      <description>FYI, in case anyone runs across this issue again.  I might have solved my issue.&lt;BR /&gt;&lt;BR /&gt;I believe that my SIM server was running out of memory and the WMI process choked.  The SIM server did have 8 GB's of memory, but it was using every bit of it.&lt;BR /&gt;&lt;BR /&gt;I added another 8 GB to the server and now it is consistently using 13 GB's.&lt;BR /&gt;&lt;BR /&gt;I haven't had the reoccurrence of the issue since I added the memory.&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Feb 2011 16:35:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-data-collection-timeout/m-p/4728611#M42750</guid>
      <dc:creator>Greg Bates</dc:creator>
      <dc:date>2011-02-15T16:35:07Z</dc:date>
    </item>
  </channel>
</rss>

