"Error Code 0x10fe ERROR_FILE_OFFLINE" Error Message When You Redirect the My Documents Folder to a Distributed File System Share (309648)
The information in this article applies to:
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q309648 Windows Bugs:513034
SYMPTOMSWhen you apply a Folder Redirection Group Policy that
redirects the My Documents folder to a Microsoft Distributed File System (DFS)
share, you may receive an error message similar to the following error
message: Error code 0x10fe [ (decimal 4350) ==
ERROR_FILE_OFFLINE] You receive this error message even though the
DFS share is online. CAUSEThis problem may occur if the Mrxsmb.sys component does not
correctly resolve the UNC path of the target shared folder. In this situation,
the Mrxsmb.sys component may incorrectly report the DFS share where the folder
is redirected as offline. This problem may occur if all the following
conditions are true:
- The client has turned on the Offline Files
feature.
- The Folder Redirection Group Policy is configured to
redirect the My Documents folder on the client to a DFS root share, for
example, \\Server1.Lab\DfsRoot
- The DFS root share points to a single DFS replica share.
For example, the DFS root share, \\Server1.Lab\DFSRoot, points to the DFS
replica, \\DC1\DFSRoot Replica1. This is equivalent to
\\DC1.Server1.Lab\DfsRootReplica1
- The caching option is disabled at the shared folder level.
For example, caching is disabled on DFSRoot and DFSRootReplica1.
The Mrxsmb.sys component keeps track of the physical shares
(such as the DFS replica share in this example, DFSRoot Replica1), but does not
keep track of the virtual shares (in this example, the DFSRoot share
). In the scenario that is mentioned in the "Cause" section of this
article, the UNC path (\\Server1.Lab\DfsRoot) is not resolved correctly to
\\DC1.Server1.Lab\DfsRootReplica1. The Mrxsmb.sys component links a server name
(\\DC1.Server1.Lab), to a DFSRootName (Server1.Lab), and then appends the share
name that it is looking for (DFSRoot) to the server name. The resulting path is
\\DC1.Server1.Lab\DFSRoot. However, this path does not exist because the server
named DC1 handles the DfsRootReplica1 share and does not directly handle the
DFSRoot share. The UNC path is incorrectly resolved as
\\DC1.Server1.Lab\DFSRoot instead of
\\DC1.Server1.Lab\DfsRootReplica1. WORKAROUNDTo work around this problem, use the same name for the DFS
root share and the DFS replica share where the DFS root share points.
Note Only use this workaround if the problem that you are experiencing
occurs under the specific conditions that are mentioned in the "Symptoms" and
"Cause" sections of this article.STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 3/27/2006 |
---|
Keywords: | kbnofix kbBug kbnetwork KB309648 kbAudITPRO |
---|
|