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

The Need For Extended Error Information

· 52CE 我爱测

A primary difficulty associated with troubleshooting RPC problems is mapping an RPC error code to the underlying problem.

A primary difficulty associated with troubleshooting RPC problems is mapping an RPC error code to the underlying problem. A configuration error or networking problem can result in one or more workstations receiving RPC_S_* errors, but that workstation can only display the error, paraphrase it, or save it to some log file. Whichever approach is used, the person troubleshooting the problem is deprived of essential information:

  • Where the error occurred. It may have occurred on the local computer, on a remote computer called by the local computer, or on a remote computer called by another remote computer.
  • The original error code that caused the problem. To conform to the OSF standard, MS RPC maps error codes to RPC_S_* codes. RPC_S_* codes are too generic, however, and offer little useful troubleshooting information.
  • Any context information related to the occurrence of the problem. With non-RPC errors, debuggers can stop the process and examine the context in which the error occurred. RPC errors are often generated by a remote process or computer, which continues processing after returning the error, and overwrites any context pertaining to the error.

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)

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

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