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

The remote procedure call failed error

· 52CE 我爱测

Helps resolve the error - The namespace cannot be queried. The remote procedure call failed.

This article helps resolve the error "The namespace cannot be queried. The remote procedure call failed."

When you access, modify, or create a Distributed File System (DFS) Namespace on a DFS Namespace server, domain member server, or Windows client with File Services tools (included in Remote Server Administration Tools (RSAT)) installed, you might receive the following error message:

The namespace cannot be queried. The remote procedure call failed

The DFS Namespace service stops responding

You use the DFS Management console, on a machine that's a member server or a member client with RSAT File Services tools installed, to view, manage or perform changes in a DFS Namespace. This issue occurs because the DFS Namespace service running on the DFS Namespace server you have (just moments ago) successfully connected to (via Remote Procedure Call (RPC) over Transmission Control Protocol (TCP)), crashes or stops responding.

Note: If the DFS Namespace service doesn't restart or isn't manually started on the DFS Namespace server, subsequent tries to access the namespace via the DFS Management console will result in the error "The Namespace cannot be queried. The RPC Server is unavailable."

Wireshark trace example

The Server Message Block (SMB) Create Request for netdfs is successful. The DFS Namespace service is still started or running:

192.168.0.45    192.168.0.42    SMB2    190    Create Request File: netdfs
192.168.0.42    192.168.0.45    SMB2    210    Create Response File: netdfs

After the DFS Namespace service stops responding, the following error occurs:

192.168.0.45    192.168.0.42    NETDFS    310    dfs_GetInfo request
192.168.0.42    192.168.0.45    SMB2    130    Ioctl Response, Error: STATUS_PIPE_BROKEN

Start the DFS Namespace service

Note: After you apply the solution, remove the DFS Namespace from the DFS Management console and add it back, or close and reopen the console to make the changes take effect.

To resolve the issue, start the DFS Namespace service.

Run the following PowerShell cmdlet to check if the DFS Namespace service is running:

Get-Service -Name Dfs

If the DFS Namespace service isn't started, run the following PowerShell cmdlet to start the DFS Namespace service:

Start-Service -Name Dfs

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)

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

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