<?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: memory leak in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908807#M6607</link>
    <description>landesk 8.5 service pack 1 had to be installed</description>
    <pubDate>Fri, 22 Jul 2005 01:17:55 GMT</pubDate>
    <dc:creator>Dorn</dc:creator>
    <dc:date>2005-07-22T01:17:55Z</dc:date>
    <item>
      <title>memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908800#M6600</link>
      <description>hello support, &lt;BR /&gt;we have a compaq dl380 g2 server with windows 2003 reporting memory leaks once a week, becomes unresponsive and has to be hard reset. &lt;BR /&gt;all hardware drivers/bios/firmware has been updated without solving the problem. &lt;BR /&gt;&lt;BR /&gt;the server has the following software installed: &lt;BR /&gt;W2K3 Server Std. (member of an AD) &lt;BR /&gt;HP Utilities &lt;BR /&gt;IBM Tivoli Storage Manager Client &lt;BR /&gt;LanDesk 8.5 &lt;BR /&gt;MSDE &lt;BR /&gt;Symantec Antivirus Client &lt;BR /&gt;&lt;BR /&gt;the server runs for about a week without problems and then becomes unresponsive (no logon possible due to lack of ressources) with the following event entries: &lt;BR /&gt;&lt;BR /&gt;Source: PerfDisc &lt;BR /&gt;Category: None &lt;BR /&gt;EventID: 2001 &lt;BR /&gt;Description:Unable to read the disk performance information from the system. Disk performance counters must be enabled... &lt;BR /&gt;&lt;BR /&gt;Source: Userenv &lt;BR /&gt;Category: None &lt;BR /&gt;EventID: 1053 &lt;BR /&gt;Description:Windows cannot create registry key Software\Microsoft\Windows\CurrentVersion\Group Policy. (Access is denied. ).... &lt;BR /&gt;&lt;BR /&gt;Source: Storage Agents &lt;BR /&gt;Category: Alerter &lt;BR /&gt;EventID: 773 &lt;BR /&gt;Description:The Remote Alerter Agent received an error on WaitForMultipleObjects call. The data contains the error code..... &lt;BR /&gt;&lt;BR /&gt;Source: Application PopUp &lt;BR /&gt;Category: None &lt;BR /&gt;EventID: 333 &lt;BR /&gt;Description:An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry... &lt;BR /&gt;&lt;BR /&gt;Source: Srv &lt;BR /&gt;Category: None &lt;BR /&gt;EventID: 2019 &lt;BR /&gt;Description:The server was unable to allocate from the system nonpaged pool because the pool was empty.... &lt;BR /&gt;&lt;BR /&gt;Source: cpqcissm &lt;BR /&gt;Category: None &lt;BR /&gt;EventID: 56 &lt;BR /&gt;Description:The driver failed to allocate memory. ... &lt;BR /&gt;&lt;BR /&gt;Source: Foundation Agents &lt;BR /&gt;Category: (17) &lt;BR /&gt;EventID: 4402 &lt;BR /&gt;Description:The External Status MIB Agent could not create an SNMP session. The data contains the error code.... &lt;BR /&gt;&lt;BR /&gt;anybody got a hint where to start solving this issue ? i´m kind of stuck as i thought after updating all the bios/drivers it would be solved...&lt;BR /&gt;&lt;BR /&gt;thanks in advance !&lt;BR /&gt;and</description>
      <pubDate>Thu, 23 Jun 2005 05:38:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908800#M6600</guid>
      <dc:creator>Dorn</dc:creator>
      <dc:date>2005-06-23T05:38:59Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908801#M6601</link>
      <description>You sould create performance logs with perfmon, add relevant counters for CPU, MEMORY, DISKS, NETWORK.&lt;BR /&gt;&lt;BR /&gt;You can also create a trace log.&lt;BR /&gt;&lt;BR /&gt;This may be usefull. You can then focus on troublehooting the problematic area.&lt;BR /&gt;&lt;BR /&gt;You can generate a memory dump and send it to support. To do this, use the EMS (bootcfg /ems on) and use the crashdump command.</description>
      <pubDate>Thu, 23 Jun 2005 09:08:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908801#M6601</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-06-23T09:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908802#M6602</link>
      <description>Have you installed all of the current patches (SP1), hotfixes, etc.??&lt;BR /&gt;&lt;BR /&gt;Jon&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 23 Jun 2005 14:29:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908802#M6602</guid>
      <dc:creator>Jon Finley</dc:creator>
      <dc:date>2005-06-23T14:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908803#M6603</link>
      <description>i will monitor ressources with tools provided by MS to get into this and let you know my results</description>
      <pubDate>Thu, 23 Jun 2005 14:49:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908803#M6603</guid>
      <dc:creator>Dorn</dc:creator>
      <dc:date>2005-06-23T14:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908804#M6604</link>
      <description>Assuming that the above was done and you still get the smae problems,&lt;BR /&gt;this sounds like one of the applications you have is not Windows 2003 certified.&lt;BR /&gt;&lt;BR /&gt;I would contact the manufacturers of all the software you have installed (or visit their support websites) to check if the version of the software you have running is for Windows 2003 server.&lt;BR /&gt;&lt;BR /&gt;- Andre</description>
      <pubDate>Fri, 24 Jun 2005 07:56:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908804#M6604</guid>
      <dc:creator>Andre Thompson_1</dc:creator>
      <dc:date>2005-06-24T07:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908805#M6605</link>
      <description>Same problem here, came to this site via "event id 4402 Foundation Agents" and Google. Also a compaq dl380, only a g4 server with windows 2003, Memory leaks and hard reset.&lt;BR /&gt;&lt;BR /&gt;So IÂ´m very interested if you have found an answer or direction to search for a solution?</description>
      <pubDate>Fri, 22 Jul 2005 00:50:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908805#M6605</guid>
      <dc:creator>CWT Diemen</dc:creator>
      <dc:date>2005-07-22T00:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908806#M6606</link>
      <description>thanks all, &lt;BR /&gt;the problem was caused by landesk software and was resolved with landesks service pack 1 for landesk 8.5.&lt;BR /&gt;cheers</description>
      <pubDate>Fri, 22 Jul 2005 01:16:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908806#M6606</guid>
      <dc:creator>Dorn</dc:creator>
      <dc:date>2005-07-22T01:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908807#M6607</link>
      <description>landesk 8.5 service pack 1 had to be installed</description>
      <pubDate>Fri, 22 Jul 2005 01:17:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-leak/m-p/4908807#M6607</guid>
      <dc:creator>Dorn</dc:creator>
      <dc:date>2005-07-22T01:17:55Z</dc:date>
    </item>
  </channel>
</rss>

