When you try to mount a directory to a WebDAV server by
using the Web DAV client in Windows Vista, the attempt may fail if do not have
Read permission on the parent folders of the WebDAV directory. The mount
succeeds in Windows Vista if the user who is trying to access the WebDAV
resource has Read permission on the root of the drive where the WebDAV share is
located. This behavior does not occur if you are using Windows XP with Office
2003 is installed. This is also a problem if the WebDAV share is
SSL-based.
For example, you try to use the Add Network
Location option in Network Places to access a WebDAV
server such as http://server/Root/Share/SubShare. You will not be able to
access a WebDAV directory that is located several levels deep if you do not
have Read permission to any of the parent directories. These directories may
include one of the following:
/
/Root
/Root/Share
Additionally, the WebDAV share might point to a virtual
directory that is not located on the root of the server from which the WebDAV
share is shared from.
This problem occurs because the functionality that is
provided by the Office 2003 component, Web Client service, is not included in
Windows Vista. Like Windows XP, Windows Vista only includes a WebDAV client.
Based on how the Explorer shell and the WebDav client work when Windows Vista
accesses a WebDAV directory, Windows Vista makes OPTIONS and PROPFIND requests
to the root of the WebDAV directory. If the root of the directory does not
support the WebDAV protocol or the user does not have Read permission to any of
the shares in the path to the root, the attempt to access to the WebDAV
directory will fail and this issue occurs. The same problem can be duplicated
on Windows XP-based computers on which the Web Client service is
stopped.
To resolve this problem, obtain the latest
service pack for Windows Vista. For more information, click the following
article number to view the article in the Microsoft Knowledge Base:
935791
(http://support.microsoft.com/kb/935791/
)
How to obtain the latest Windows Vista service pack
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
No prerequisites are required.
Restart requirement
You have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other previously released
hotfixes.
File information
The English version of this hotfix has the file
attributes (or later file attributes) that are listed in the following table.
The dates and times for these files are listed in Coordinated Universal Time
(UTC). When you view the file information, it is converted to local time. To
find the difference between UTC and local time, use the Time
Zone tab in the Date and Time item in Control
Panel.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. This
problem was first corrected in Windows Vista Service Pack
1.
Back to the top
