大网数据广告活动
网络与域名解析

Independence From Other Components

· 52CE 我爱测

Extended error data is useful even when the server or application through which the chain passed does not recognize extended error data, or does not take advantage of it. Recommended approaches for such situations are provided at the end of this section.

Extended error data is useful even when the server or application through which the chain passed does not recognize extended error data, or does not take advantage of it. Recommended approaches for such situations are provided at the end of this section.

Extended error data is most useful when applications or servers using RPC take advantage of extended error information. When investigating an RPC_S_* error code and the servers or applications involved do not make extended error data available, consider the following approaches:

  • Take a sniff.

    Reproduce the scenario while taking the sniff. The sniff of the wire will contain the extended error data.

  • Examine it from the debugger.

    If taking a sniff of the problem does not work, because the call is local or because the error originates locally, attach a debugger to the process returning the error and put a breakpoint immediately after the RPC call generating the error. RPC often indicates errors by throwing exceptions, so if you are looking for error 1825 (RPC_S_SEC_PKG_ERROR), enable exception 1825 and when the debugger breaks on that exception, examine the extended error information for the thread.

Source: Microsoft Learn / Windows Win32 documentation 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 / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

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

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