Web Folder Client (MSDAIPP.DLL) Versions and Issues List


Please report both new issues and existing issues that have been confirmed to be present or fixed in a specific webfolder version to fax@greenbytes.de

How to find out about the DLL version

The webfolder functionality is implemented by means of MSDAIPP.DLL. It usually resides inside "C:\Program Files\Common Files\SYSTEM\OLE DB" or it's language dependant equivalent (such as "C:\Programme\Gemeinsame Dateien\SYSTEM\OLE DB" for German Windows versions). To find the DLL version, select the file in Explorer, choose "Properties" from the right-click context menu, then select the "Version" tab.

If you're running Microsoft Internet Explorer you can also let a script find the currently registered DLL. However, this requires this page to execute some standard ActiveX components from your system (WScript.Shell and Scripting.FileSystemObject). Click the button below if you want to try that:

Related Information

See WebDAV Mini-Redirector (MRXDAV.SYS) Versions and Issues List for a known list of versions and issues in Microsoft's WebDAV "Mini-Redirector" client (a new component introduced with Windows XP).

"User-Agent" request header

The Webfolder client sends a User-Agent request header starting with "Microsoft Data Access Internet Publishing Provider DAV".

Known Versions

Major Build numberProducts
8Windows 2000, Windows ME, Office 2000
10Sharepoint Portal Server 2001, Windows XP
11Sharepoint Portal Server 2003, Office 2003, Windows 2003
DLL versionDB entrycommentsconfirmed issues
8. 102. 1403. 0243635Office 2000
8. 103. 2402. 0240893Windows 2000, Windows 2000 SP1, Windows 2000 SP2, Windows 2000 SP3, Office 2000 SR1
collection-open-non-ASCII-name2, date-format, hashmark-escaping, options-req-against-root, property-display-xml-attr, redirect-on-get, resourcetype-collection, undefined-properties, upper-lower-case
8. 103. 2519. 0191493Windows MEundefined-properties
8. 103. 3521. 0275470Office 2000 SP3
10. 145. 3722. 0collection-open-non-ASCII-name
10. 145. 3812. 0243175Office XP (?)collection-open-non-ASCII-name, folder-mismatch, hashmark-escaping, undefined-properties, upper-lower-case
10. 145. 3914. 3245687Sharepoint 2001undefined-properties
10. 145. 3914. 17275315Office XP SP1, Office XP SP2collection-open-non-ASCII-name, displayname-1, displayname-2, folder-mismatch, hashmark-escaping, undefined-properties, upper-lower-case
10. 145. 3914. 21.NET framework (?), Windows Server 2003 RC2undefined-properties
8. 102. 4004. 0OLE DB Provider for Internet Publishing Update for Windows 95 & 98, NT 4.0, 2000, Windows Me
8. 103. 4004. 0OLE DB Provider for Internet Publishing Update for Windows 95 & 98, NT 4.0, 2000, Windows Me
12. 0. 4407. 1001Microsoft Expression Web Designer (Beta 1)
12. 0. 4518. 1014Software Update for Web Folders
10. 145. 4629. 0246844Sharepoint 2001 SP1undefined-properties
10. 145. 4629. 5Sharepoint 2001 Client Hotfix
10. 145. 4629. 25Sharepoint 2001 Client Hotfix
10. 145. 4629. 40Sharepoint 2001 Client Hotfix
11. 0. 4920. 6Office 2003 Beta 2ampersand-escaping, collection-open-non-ASCII-name, date-format, displayed-href, property-display-xml-attr, resourcetype-collection, undefined-properties
11. 0. 4920. 22Sharepoint Portal Server v2.0 Beta 2
8. 103. 5219. 0256177Windows XP SP1, Windows 2000 SP4redirect-on-propfind, undefined-properties
11. 0. 5321. 11Office 2003 Beta 2 (freshup)ampersand-escaping, hashmark-escaping, displayname-1, displayname-2, options-req-against-root, redirect-on-propfind, upper-lower-case
11. 0. 5321. 19Sharepoint Portal Server v2.0 Beta 2 Technical Refreshdisplayname-1, displayname-2
11. 0. 5510. 0289240Office 2003, Windows 2003, Sharepoint Portal Server 2003connect-parent-coll-escaped, displayed-href, displayname-1, displayname-2, folder-mismatch, lock-loss, lock-timeout, namespace-handling, property-display-xml-attr
10. 145. 6011. 0Sharepoint 2001 SP2, Sharepoint 2001 SP2a Client
10.145.6011.0-client-download-broken, collection-open-non-ASCII-name, connect-parent-coll-3, date-format, displayed-href, folder-mismatch, property-display-xml-attr, resourcetype-collection, undefined-properties
10. 145. 6011. 7Office XP / Sharepoint 2001 Client Hotfix, Office XP SP3
10. 145. 6011. 12Sharepoint 2001 Client Hotfix
10. 145. 6011. 18Sharepoint 2001 Client Hotfix
10. 145. 6011. 25Sharepoint 2001 Client Hotfix
10. 145. 6011. 28Sharepoint 2001 Client Hotfix
10. 145. 6011. 31Sharepoint 2001 Client Hotfix
12. 0. 6211. 1000SharePoint Designer 2007 Service Pack 1
12. 0. 6300. 5000Office 2007 Post-Service Pack 1 Hotfix
12. 0. 6415. 10002007 Microsoft Office System Service Pack 2
11. 0. 6715. 15Software Update for Web Folders
collection-open-non-ASCII-name, date-format, folder-mismatch, property-display-xml-attr, resourcetype-collection
11. 0. 6715. 60Office 2003 post-Service Pack 2 hotfix
10. 145. 7329. 0Office XP Update


issue: confirmed to be present in this release

issue: confirmed to be fixed in this release

Known DLL versions by product

.NET framework (?)10.145.3914.21
2007 Microsoft Office System Service Pack 212.0.6415.1000
Microsoft Expression Web Designer (Beta 1)12.0.4407.1001
Office 20008.102.1403.0
Office 2000 SP38.103.3521.0
Office 2000 SR18.103.2402.0
Office 200311.0.5510.0
Office 2003 Beta 211.0.4920.6
Office 2003 Beta 2 (freshup)11.0.5321.11
Office 2003 post-Service Pack 2 hotfix11.0.6715.60
Office 2007 Post-Service Pack 1 Hotfix12.0.6300.5000
Office XP (?)10.145.3812.0
Office XP / Sharepoint 2001 Client Hotfix10.145.6011.7
Office XP SP110.145.3914.17
Office XP SP210.145.3914.17
Office XP SP310.145.6011.7
Office XP Update10.145.7329.0
OLE DB Provider for Internet Publishing Update for Windows 95 & 98, NT 4.0, 2000, Windows Me8.102.4004.0
OLE DB Provider for Internet Publishing Update for Windows 95 & 98, NT 4.0, 2000, Windows Me8.103.4004.0
Sharepoint 200110.145.3914.3
Sharepoint 2001 Client Hotfix10.145.4629.5
Sharepoint 2001 Client Hotfix10.145.4629.25
Sharepoint 2001 Client Hotfix10.145.4629.40
Sharepoint 2001 Client Hotfix10.145.6011.12
Sharepoint 2001 Client Hotfix10.145.6011.18
Sharepoint 2001 Client Hotfix10.145.6011.25
Sharepoint 2001 Client Hotfix10.145.6011.28
Sharepoint 2001 Client Hotfix10.145.6011.31
Sharepoint 2001 SP110.145.4629.0
Sharepoint 2001 SP210.145.6011.0
Sharepoint 2001 SP2a Client10.145.6011.0
SharePoint Designer 2007 Service Pack 112.0.6211.1000
Sharepoint Portal Server 200311.0.5510.0
Sharepoint Portal Server v2.0 Beta 211.0.4920.22
Sharepoint Portal Server v2.0 Beta 2 Technical Refresh11.0.5321.19
Software Update for Web Folders11.0.6715.15
Software Update for Web Folders12.0.4518.1014
Windows 20008.103.2402.0
Windows 2000 SP18.103.2402.0
Windows 2000 SP28.103.2402.0
Windows 2000 SP38.103.2402.0
Windows 2000 SP48.103.5219.0
Windows 200311.0.5510.0
Windows ME8.103.2519.0
Windows Server 2003 RC210.145.3914.21
Windows XP SP18.103.5219.0

Known issues

(Ref: http://www.microsoft.com/downloads/details.aspx?FamilyID=9652a8e1-2d6e-4d0f-812e-759b0ccbd370)
The separate client download for Sharepoint 2001 SP2a doesn't install (the MSI information seems to be incomplete). This has been confirmed both for English and German versions. UPDATE: as of March 2004, this problem seems to be fixed.
(Ref: http://issues.apache.org/bugzilla/show_bug.cgi?id=15825)
PROPFIND response processing of URLs containing ampersands that are not URL-escaped (marshalled in XML as "&") is broken. When displaying the collection contents, the webfolder client removes all characters starting with the ampersand. See http://issues.apache.org/bugzilla/show_bug.cgi?id=15825 for more details.
(Ref: http://support.microsoft.com/?kbid=325355)
When using Internet Explorer's "AnchorClick" behavior to link to WebDAV collections, there seems to be a fixed limit for the maximum URL length of around 100 characters (note that this is indeed an Internet Explorer problem rather than a webfolder client issue).
collection-open-non-ASCII-name Opening a folder which contains non-ASCII characters in it's name (such as German umlauts) causes the webfolder client to display an error message ("Documents in this folder are not available. The folder may have been moved or deleted, or network problems may be preventing a connection to the server.") if the server is running on a port other than the default port (80). A server trace however shows that the client actually does not attempt any request at all.
collection-open-non-ASCII-name2 Opening a folder which contains non-ASCII characters in it's name (such as German umlauts) works, but causes the webfolder client to wrongly re-encode the characters in the URI (server sends URL-escaped UTF8, client displays URL-escaped ISO-8859-1).
connect-parent-coll-escaped Connecting through "network places" fails if an ancestor of the target collection contains an URL-escaped character, such as "%20" for a blank. Unescaping (replacing "%20" by a simple space character, thereby creating an invalid URL) seems to workaround this issue. Note: this applies also to other characters such as "@", escaped as "%40".
connect-parent-coll-with-blanks See connect-parent-coll-escaped.
date-format When displaying resources, the WebDAV properties DAV:getlastmodified and DAV:creationdate are only recognized if they are sent with datatype properties in the obsolete XDR namespace (this is what Microsoft II 5.0 does).
displayed-href The URI displayed in the "internet adress" column is constructed from the base URI of the collection and the resource's DAV:displayname property (when present). This is wrong - the column should display the DAV:href returned in the PROPFIND response body.
displayname-1 The Webfolder client displays the DAV:displayname only if it doesn't contain some characters that happen to be reserved in filenames (such as "/"). However, the displayname is just a textual description, so it should be displayable no matter what kind of text it contains (basically this is caused by the Webfolder mistaking the displayname to be some kind of replacement resource name).
displayname-2 If the client decides to use the DAV:displayname instead of the last path segment for display, it seems to internally confuse both. A rename operation on a resource where the displayname and the last path segment differ fails because the client submits the MOVE request to a broken request URI (collection href and displayname concatenated). Note that in addition, the client extracts file type information from the extension in the displayname (!).
folder-mismatch When specifying port 80 explicitly in the URL (rather than letting the default apply), the webfolder fails to detect the entry for the parent collection from the PROPFIND/Depth:1 response body, displaying it as additional child collection.
hashmark-escaping When the last path segment of a URI starts with a hash mark ("#"), it doesn't get escaped in the HTTP request, so that a RFC2396-conformant parser would assume the last part is the fragment identifier. Some HTTP servers ignore fragment identifiers, thus apply the request to the parent collection, which may result in data loss (for instance, for DELETE).
lock-loss Bad handling when a WebDAV lock is lost: client just continues to use the old (invalid) lock token, instead of just re-locking the resource (possibly after consulting with the user). Old versions even seem to go into a "panic" mode where the failing LOCK refresh is repeated once a second, causing a high server load.
lock-timeout When locking a resource, Office attempts to specify a 180s timeout. WebDAV servers are allowed to ignore this preference, though. When this occurs (for instance, when the server only supports infinite timeouts), Office opens the document "read only" and never unlocks the resource (thus potentially requires administator intervention to get rid of the lock).
namespace-handling DAV: namespaced elements in a PROPFIND responses can not use a default namespace; each element must be explicitly prefixed with a namespace prefix defined in itself or a parent. If a default namespace is used the client will give no errors, but will not display any resources.
property-display-xml-attr The properties dialogue fails to display if a dead (custom) property carries an attribute in the XML namespace, such as xml:lang. The error message is "Unable to display properties".
(Ref: http://support.microsoft.com/?kbid=288440)
If the server replies to a GET request with 3xx (redirect) status, copying that file to local storage may result in an empty file an no error message (instead of the redirect being followed).
redirect-on-propfind If the server replies to a PROPFIND request with 3xx (redirect) status, the client doesn't automatically follow the link; instead it displays an error message.
(Ref: http://support.microsoft.com/?kbid=830255)
When the DAV:resourcetype property is non-empty, the client assumes it's a collection. This should only happen when it contains the DAV:collection child.
options-req-against-root When using the Internet Explorer "open" dialog and checking the "open as webfolder" checkbox, Explorer first accesses the root of the server instead of the specified URI. Therefore, opening a webfolder will fail unless the root of the namespace indeed is WebDAV-enabled.
undefined-properties When PROPFINDing collections, the webfolder client tries to retrieve values for a set of properties in the "DAV:" namespace, although they aren't defined in any WebDAV related specification (DAV:contentclass, DAV:defaultdocument, DAV:href, DAV:iscollection, DAV:ishidden, DAV:isreadonly, DAV:isroot, DAV:isstructureddocument, DAV:lastaccessed, DAV:name and DAV:parentname). Except one (DAV:hidden), none of these properties seems to be actually used by the client. Note that proprietary properties (vendor extensions) MUST NOT use the "DAV:" namespace.
upper-lower-case Client doesn't support servers where collections contain resources that only differ in upper/lowercase, such as "Test" and "test". It will only show one of the two.
(Ref: http://support.microsoft.com/?kbid=298637)
Windows XP Home seems to come with a version of the library, but IE6 seems to lack the ability to talk to it, so IE's "open as webfolder" option doesn't work, nor the HTML "AnchorClick" behaviour. Opening through "Network Places" however does seem to work. This problem does not seem to be present in Windows XP Professional nor in Windows 2003 Server. Note that Microsoft claims in it's Knowledge Base article that this is a known limitation, not a bug.