大网数据广告活动
Windows Server 管理

Microsoft-Windows-RPC-Events event 11 after reboot

· 52CE 我爱测

Resolves the Microsoft-Windows-RPC-Events event 11 that occurs when you run the Server Manager Snap-in (servermanager.msc) for extended periods of time or start the Resource Host Monitor (rhs.exe) hosting FileServer Resource.

This article provides a solution to fix the Microsoft-Windows-RPC-Events event 11 that occurs when you run the Server Manager Snap-in (servermanager.msc) for extended periods of time or start the Resource Host Monitor (rhs.exe) hosting FileServer Resource.

Original KB number:   974814

Symptom

When you run the servermanager.msc for extended periods of time or start the rhs.exe hosting FileServer Resource, the following Application event log warning is written:

  • For DHCP Servers, you may notice the following event description:

    Log Name: Application
    Source: Microsoft-Windows-RPC-Events
    Event ID: 11
    Task Category: None
    Level: Warning
    Keywords:
    User: CONTOSO\Administrator
    Computer: contoso.com
    Description:
    Possible Memory Leak. Application ("C:\WINDOWS\SYSTEM32\MMC.EXE" "C:\WINDOWS\SYSTEM32\SERVERMANAGER.MSC") (PID: 584) 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.

  • For FileServer resource:

    Description:
    Possible Memory Leak. Application (C:\Windows\Cluster\rhs.exe -key SYSTEM\CurrentControlSet\Services\ClusSvc\Parameters\Rhs\<GUID> -parentPid <ParentPid> -initEvent <initEvent> -replyEndpoint <replyEndpoint>) (PID: \<PID>) 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 ({4B324FC8-1670-01D3-1278-5A47BF6EE188}), Method number <Method number>). User Action: Contact your application vendor for an updated version of the application.

Cause

This issue occurs during the portion of the UID calling an internal structure with a parameter not initialized as NULL. This causes a false positive detection for a memory leak.

Resolution

There is no memory leak or functional impact to this specific condition. This warning can be ignored as long as the UUID is {6bffd098-a112-3610-9833-46c3f874532d} or {4B324FC8-1670-01D3-1278-5A47BF6EE188}, and memory is not leaking.

More information

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。