After finishing putting some brand new servers in place with Windows 2008 R2, installing its rolls and leaving a happy client I’m usually very happy about a job well done. That feeling can last for a while when doing the paperwork involved with the project. It can also go away blazingly fast when you get a call that there is an “RPC memory leak or something no right” on the servers. Not good. So you remotely access the server and start looking. Luckily for me this was to be a non issue. The event logged was the following:
Log Name: Application
Source: Microsoft-Windows-RPC-Events
Date: 06/01/2011 22:26:18
Event ID: 11
Task Category: None
Level: Warning
Keywords:
User: BIGBillyTheServerAdmin
Computer: infra01.big.corp
Description:
Possible Memory Leak. Application ("C:Windowssystem32mmc.exe" "C:Windowssystem32dhcpmgmt.msc" ) (PID: 5000) has passed a non-NULL pointer to RPC for an [out] parameter marked [allocate(all_nodes)]. [allocate(all_nodes)] parameters are always reallocated; if the original pointer contained the address of valid memory, that memory will be leaked. The call originated on the interface with UUID ({6bffd098-a112-3610-9833-46c3f874532d}), Method number (2). User Action: Contact your application vendor for an updated version of the application.
If you do a search for this you’ll find several unresolved news group and support site questions but also a Microsoft knowledge base article http://support.microsoft.com/kb/974814. It states that when you run the Server Manager Snap-in (servermanager.msc) for extended periods of time, the application event log warning as seen above is logged. It also says it only happens on DHCP servers, which is exactly a roll these servers have and the warning entry we see in the application even log. As long as the UUID is {6bffd098-a112-3610-9833-46c3f874532d} and you have no other indications of a memory leak you’re good to go. Armed with the link we quickly put the owners mind at easy and all is well again. Back to the paperwork.
Cool beans, just what I needed
Thanks for the tip. very helpful
But what about the same error for the lsass.exe process? This error pops up from time to time and I lost connectivity to SQL server at least once but maybe more times.
That sounds like a completly different issue. Good luck with troubleshooting. For more help check out the Microsoft forums http://social.technet.microsoft.com/Forums/en-us/categories/