I've got a memory leak error on my windows 2003 std edt server. the strange thing is, it ONLY happens if i rename the server, and change its ip address to that of an old server on our domain. I'm trying to upgrade our fileserver, so i've got a brand new dl380, with windows 2003 std edt. It's been running for a month now(on the domain) all ok, no errors at all. On the weekend, i planned to put it live. I took the old fileserver (called fileserver, Win2k) off the domain, and into a workgroup, changed its ip address and re-booted, all ok. I then started work on the new fileserver (called temp2), i dropped it into a workgroup, changed its name to "fileserver" (left in workgroup) and re-booted. I then changed it IP address to reflect the original fileserver's address, re-booted. I then joined the new fileserver, to the domain. Everything looked good all the mapped drives worked fine. BUT, about an hour later, i could't access the new fileserver, tried pinging, but that failed as well. Went to site, checked out the event logs, and there were lots of error messages stating: "the server was unable to allocate from the system nonpaged pool because the pool was empty". I restarted the server this fixed it, but it then died about 2 hours later. I reversed the process of naming it, as stated above, and now its back to Temp2, and there are no problems? How can the change of name and ip address cause these problems?
I've found an article on the hp website which has all the error messages and symptoms that i'm having, but, this error is constant, and was resolved by updating Landesk software, i've attached the errors:
we have a compaq dl380 g2 server with windows 2003 reporting memory leaks once a week, becomes unresponsive and has to be hard reset.
all hardware drivers/bios/firmware has been updated without solving the problem.
the server has the following software installed:
W2K3 Server Std. (member of an AD)
IBM Tivoli Storage Manager Client
Symantec Antivirus Client
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:
Description:Unable to read the disk performance information from the system. Disk performance counters must be enabled...
Description:Windows cannot create registry key Software\Microsoft\Windows\CurrentVersion\Group Policy. (Access is denied. )....
Source: Storage Agents
Description:The Remote Alerter Agent received an error on WaitForMultipleObjects call. The data contains the error code.....
Source: Application PopUp
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...
Description:The server was unable to allocate from the system nonpaged pool because the pool was empty....
Description:The driver failed to allocate memory. ...
Source: Foundation Agents
Description:The External Status MIB Agent could not create an SNMP session. The data contains the error code....