We had a Windows 7 workstation that was exhibiting “wonky” behavior when opening SharePoint folders in Office 2010 Word (and explorer in general). When it was supposed to open the save-as dialog to a SharePoint folder, it would instead show the default “My Document” folder. You could still enter a SharePoint url, and it would load correctly, but the initial dialog refused to open SharePoint.
Using Fiddler2 I was able see that the problem computer was using a different WebDAV client than the working workstations from the User-Agent in the requests. The first request is identical:
|
OPTIONS http://sharepointserver/doclib/ HTTP/1.1 |
But the second request is all kinds of different.
Normal Workstation:
|
OPTIONS http://sharepointserver/ HTTP/1.1 |
Problem Workstation:
|
OPTIONS http://sharepointserver/ HTTP/1.1 |
The next request gets even weirder:
|
GET http://sharepointserver/_vti_inf.html HTTP/1.1 |
Followed by “MSFrontPage/4.0”.
FrontPage 4.0? Mozilla 2.0? It looks like we’ve travelled into the year 2000! And to some extent, we had. Microsoft Data Access Internet Publishing Provider (MSDIAPP) is the Ole DB provider used by Windows Explorer to access WebDAV since They first started doing it. The feature is also sometimes called “Web Folders” (remember dealing with this in Windows XP?)
In Windows Vista, they replaced the old “Web Folders” with a WebDAV Mini-redirector. This new library caused problems for many people, and Microsoft repackaged the “old” web folders for Windows Vista in a software update. With the release of Windows 7, the MSDIAPP Web Folders are now deprecated, and installing them on Windows 7 is unsupported.
So this Windows 7 PC had somehow gotten the old MSDIAPP WebDAV extension installed, and it had taken over. Not only that, but according to this page:
Web Folder Client (MSDAIPP.DLL) Versions and Issues List
This workstation had the second oldest version of msdiapp.dll – 8.103.2402.0 – installed in C:\Program Files (x86)\Common Files\System\Ole DB. The version that came with Windows 2000, and Office 2000 SR1. The file date is in 1999.
So now that I had identified the problem, how to fix? Finding this proved much more difficult than I would have expected. Cutting to the chase, the necessary steps to remove this component are chronicled here in a microsoft forum post WinXP clients with Office 2007 won’t communicate with WebDAV server, in Chris Ni’s reply. (Don’t worry if the link is broken, I’m including what you need below)
Without further adieu,
Steps to uninstall MSDIAPP Web Folders from a Windows 7 machine
These instructions were modified from a post by a Microsoft support tech here. I followed them myself with good success, but your results may vary.
Proceed at your own risk – I am not responsible for any damage this may cause to your computer. I highly recommend making a backup first, or at the very least ensure you have a good System Recovery snapshot.
Make sure you have all Office applications closed (you probably should just close everything) before proceeding.
Also be warned – if the user has any files checked-out in sharepoint, this check-out will be broken. Check them in before doing this, or you will have to discard the checkout later.
First, paste the following into a batch file, and run it from an elevated command prompt – Do not paste directly into a command prompt, it will not work right.
REM Removing MSDAIPP (Rosebud) files
MSIEXEC /x {90120000-0010-0409-0000-0000000FF1CE} /q
MSIEXEC /x {90140000-0010-0409-0000-0000000FF1CE} /q
del "%ALLUSERSPROFILE%\Application Data\Microsoft\MSDAIPP\OFFLINE" /f /q
del "%ALLUSERSPROFILE%\Microsoft\MSDAIPP\OFFLINE" /f /q
SET ROSEBUDBASE=%CommonProgramFiles(x86)%
IF "%ROSEBUDBASE%"=="" SET ROSEBUDBASE=%CommonProgramFiles%
del "%ROSEBUDBASE%\System\OLE DB\MSDAIPP.DLL" /f /q
del "%ROSEBUDBASE%\System\OLE DB\MSDAPML.DLL" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\Web Folders\MSONSEXT.DLL" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\Web Folders\1033\NSEXTINT.DLL" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\Web Server Extensions\40\bin\FP4AWEC.DLL" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\Web Server Extensions\40\bin\FP4AUTL.DLL" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\Web Server Extensions\40\bin\1033\FPEXT.MSG" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\OFFICE12\Office Setup Controller\Rosebud.en-us\RosebudMUI.XML" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\OFFICE12\Office Setup Controller\Rosebud.en-us\SETUP.XML" /f /q
REM WebFldrsXP files
del "%ROSEBUDBASE%\Microsoft Shared\Web Folders\MSOWS409.DLL" /f /q
del "%ROSEBUDBASE%\Microsoft Shared\Web Folders\PUBPLACE.HTT" /f /q
REM Clear Web Server Extension cache
del "%USERPROFILE%\Application Data\Microsoft\Web Server Extensions\Cache" /f /q
del "%USERPROFILE%\AppData\Roaming\Microsoft\Web Server Extensions\Cache" /f /q
Don’t worry if you get warnings that folders are missing – some of them may not exist, it is ok.
Next, create a .reg file and paste in the following – make sure you save it as unicode!, and that the last line is blank.
This will remove all the registry entries associated with MSDIAPP. I did a double-check on a good workstation, and none of these entries should exist, so they should be safe to delete.
That being said, you do this at your own risk – as with all things registry related it may cause your computer to explode.
Windows Registry Editor Version 5.00
[-HKEY_CLASSES_ROOT\CLSID\{11480D94-C3A5-11D3-BA7C-00C04F7948B3}]
[-HKEY_CLASSES_ROOT\CLSID\{AF320921-9381-11D1-9C3C-0000F875AC61}]
[-HKEY_CLASSES_ROOT\CLSID\{BDEADF00-C265-11D0-BCED-00A0C90AB50F}]
[-HKEY_CLASSES_ROOT\CLSID\{D9D5678A-76CE-4804-AAFC-1DA2502DB0BC}]
[-HKEY_CLASSES_ROOT\CLSID\{E1D2BF40-A96B-11D1-9C6B-0000F875AC61}]
[-HKEY_CLASSES_ROOT\CLSID\{E1D2BF42-A96B-11D1-9C6B-0000F875AC61}]
[-HKEY_CLASSES_ROOT\CLSID\{F6FD0A00-43F0-11D1-BE58-00A0C90A4335}]
[-HKEY_CLASSES_ROOT\CLSID\{F6FD0A01-43F0-11D1-BE58-00A0C90A4335}]
[-HKEY_CLASSES_ROOT\CLSID\{F6FD0A0E-43F0-11D1-BE58-00A0C90A4335}]
[-HKEY_CLASSES_ROOT\CLSID\{F6FD0A0F-43F0-11D1-BE58-00A0C90A4335}]
[-HKEY_CLASSES_ROOT\CLSID\{F6FD0A11-43F0-11D1-BE58-00A0C90A4335}]
[-HKEY_CLASSES_ROOT\CLSID\{F6FD0A13-43F0-11D1-BE58-00A0C90A4335}]
[-HKEY_CLASSES_ROOT\MSDAIPP.BINDER]
[-HKEY_CLASSES_ROOT\MSDAIPP.BINDER.1]
[-HKEY_CLASSES_ROOT\MSDAIPP.DSO]
[-HKEY_CLASSES_ROOT\MSDAIPP.DSO.1]
[-HKEY_CLASSES_ROOT\MSDAIPP.WEBFOLDERFORMS]
[-HKEY_CLASSES_ROOT\MSDAIPP.WEBFOLDERFORMS.1]
[-HKEY_CLASSES_ROOT\MSDAMAGG.Binder]
[-HKEY_CLASSES_ROOT\MSDAMAGG.Binder.1]
[-HKEY_CLASSES_ROOT\MSDAMON.BINDER]
[-HKEY_CLASSES_ROOT\MSDAMON.BINDER.1]
[-HKEY_CLASSES_ROOT\PROTOCOLS\Handler\http\0x00000001]
[-HKEY_CLASSES_ROOT\PROTOCOLS\Handler\http\oledb]
[-HKEY_CLASSES_ROOT\PROTOCOLS\Handler\https\0x00000001]
[-HKEY_CLASSES_ROOT\PROTOCOLS\Handler\https\oledb]
[-HKEY_CLASSES_ROOT\PROTOCOLS\Handler\msdaipp\0x00000001]
[-HKEY_CLASSES_ROOT\PROTOCOLS\Handler\msdaipp\oledb]
[-HKEY_CLASSES_ROOT\Publishing Folder]
[-HKEY_CLASSES_ROOT\SOFTWARE\Microsoft\MasterAggregatorForIPP]
[-HKEY_CLASSES_ROOT\TypeLib\{ED222A11-E1C6-11D0-B1E1-00AA006DCDF4}\1.0]
[-HKEY_CLASSES_ROOT\TYPELIB\{F6FD0A0C-43F0-11D1-BE58-00A0C90A4335}\2.0]
[-HKEY_CLASSES_ROOT\WECAPI2.FpFile]
[-HKEY_CLASSES_ROOT\WECAPI2.FpFile.1]
[-HKEY_CLASSES_ROOT\WECAPI2.FpFolder]
[-HKEY_CLASSES_ROOT\WECAPI2.FpFolder.1]
[-HKEY_CLASSES_ROOT\WECAPI2.FpMetaInfo]
[-HKEY_CLASSES_ROOT\WECAPI2.FpMetaInfo.1]
[-HKEY_CLASSES_ROOT\WECAPI2.FpStructureElement]
[-HKEY_CLASSES_ROOT\WECAPI2.FpStructureElement.1]
[-HKEY_CLASSES_ROOT\WECAPI2.FpStructureModification]
[-HKEY_CLASSES_ROOT\WECAPI2.FpStructureModification.1]
[-HKEY_CLASSES_ROOT\WECAPI2.WebExtenderClient]
[-HKEY_CLASSES_ROOT\WECAPI2.WebExtenderClient.1]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{73fa19d0-2d75-11d2-995d-00c04f98bbc9}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\RootBinder\http]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\RootBinder\https]
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Advanced\Folder\Thickets]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{BDEADF00-C265-11D0-BCED-00A0C90AB50F}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\WebFolders]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved]
"{BDEADF00-C265-11D0-BCED-00A0C90AB50F}"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked]
"{BDEADF00-C265-11D0-BCED-00A0C90AB50F}"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached]
"{BDEADF00-C265-11D0-BCED-00A0C90AB50F}"=-
[-HKEY_CLASSES_ROOT\CLSID\{BDEADF04-C265-11D0-BCED-00A0C90AB50F}]
[-HKEY_CLASSES_ROOT\PROTOCOLS\HANDLER\IPP\0X00000001]
[-HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\DATAACCESS\ROOTBINDER\MSDAIPP]
[-HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSDAIPP\PROVIDERS\{9FECD570-B9D4-11D1-9C78-0000F875AC61}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSDAIPP\PROVIDERS\{9FECD571-B9D4-11D1-9C78-0000F875AC61}]
[-HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\SHELL EXTENSIONS\APPROVED\{BDEADF00-C265-11D0-BCED-00A0C90AB50F}]
[-HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\SHELL EXTENSIONS\BLOCKED\{BDEADF00-C265-11D0-BCED-00A0C90AB50F}]
[-HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\SHELL EXTENSIONS\CACHED\{BDEADF00-C265-11D0-BCED-00A0C90AB50F}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Web Extender Client]
"WecCtlFlags"=-
That’s it. You probably don’t even need to reboot – Windows will fall back to using the built-in WebDAV client.
Pingback: WebDAV and Windows 7 Adventure | Armedia Blog