Microsoft Data Access Internet Publishing Provider configuration repair script

Applies to: Microsoft Windows XP ProfessionalMicrosoft Windows XP Professional x64 EditionMicrosoft Windows Server 2003 Enterprise x64 Edition More


Many problems can arise from corruption in the configuration of the Microsoft Data Access Internet Publishing Provider (MSDAIPP). MSDAIPP provides client workstations Web Folder connectivity to web servers that support either Web Distributed Authoring and Versioning (WebDAV) or FrontPage Server Extensions (FPSE). While native with Windows XP, MSDAIPP is also installed by Microsoft Office 2003. Microsoft Office 2007 and Microsoft Office 2010 only install MSDAIPP components on operating systems prior to Windows Vista. Note: MSDAIPP should not be installed on newer operating systems beginning with Windows Vista unless connectivity is needed to a server via FPSE as WebDAV is now fully supported by the native WebClient service.

Common Issues Seen:
  • Office documents opening up as Read Only from a SharePoint site
  • Unable to Edit Documents from SharePoint
  • Windows Explorer View not functioning
  • Unable to Check-in documents from the Office Client

Common Error messages:

This file could not be checked in because the original version of the file on the server was moved or deleted. A new version of this file has been saved to the server, but your check-in comments were not saved.

To save comments with the new version of this file on the server, you must delete the local copy of this file, check out the file from the server again, and then check in the file with any comments you want to add.

This document was checked out to your local drafts folder but the local copy could not be checked in to the site. Close any application that is editing the document and try to check in again, or discard the checkout.

There has been a network or file permission error. The network connection may be lost

This modification is not allowed because the selection is locked"

"Server Document: A newer version is available. To modify this document, open the latest version or save a copy."


There are many components involved in a properly functioning installation of MSDAIPP and occasionaly the components become unregister or corrupted.


This resolution is a collection of the most common modifications used to clear corruption and re-register MSDAIPP.

To have us fix this problem for you, go to the "Fix it for me" section. If you prefer to fix this problem yourself, go to the "Let me fix it myself" section.

Fix it for me

To fix this problem automatically, click the Fix it button or link. In the File Download dialog box, click Run, and then follow the steps in the Fix it Wizard.

  • Please run the Fix it solution on the client with local administrator privileges.
  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Then, go to the "Did this fix the problem?" section.

Let me fix it myself

These steps are written as a batch file and need to be run on the client with local administrator privileges.

REM Remove any keys that may reside under here; self-reg will add it back
REG DELETE HKCR\Software\Microsoft\MasterAggregatorForIPP\OleDbHandlers /f

REM (Repair WebFldrs XP)
MSIEXEC /fmoc {350C97B0-3D7C-4EE8-BAA9-00BCB3D54227} /q

REM (Repair Office 2007 Web Folders update - Microsoft Software Update for Web Folders [English] 12)
MSIEXEC /fmoc {90120000-0010-0409-0000-0000000FF1CE} /q

REM (Repair Office 2010 Web Folders update - Microsoft Software Update for Web Folders [English] 14)
MSIEXEC /fmoc {90140000-0010-0409-0000-0000000FF1CE} /q

REM Go into the web server extensions cache and delete everything.
REM -----------------------------------------------------------------------------------------
REM WinXP/Server2003: %USERPROFILE%\Application Data\Microsoft\Web Server Extensions\Cache
IF EXIST "%USERPROFILE%\Application Data\Microsoft\Web Server Extensions\Cache" DEL "%USERPROFILE%\Application Data\Microsoft\Web Server Extensions\Cache" /f /q

REM Vista/Server2008: %USERPROFILE%\AppData\Roaming\Microsoft\Web Server Extensions\Cache
IF EXIST "%USERPROFILE%\AppData\Roaming\Microsoft\Web Server Extensions\Cache" DEL "%USERPROFILE%\AppData\Roaming\Microsoft\Web Server Extensions\Cache" /f /q

REM Manually register the OLEDB files that are used with Web folders:
REM -----------------------------------------------------------------------------------------
RegSvr32 "%CommonProgramFiles%\System\Ole DB\oledb32.dll"
RegSvr32 "%CommonProgramFiles%\System\Ole DB\msdaurl.dll"
RegSvr32 "%CommonProgramFiles%\System\Ole DB\msdaipp.dll"

REM Manually register the URLMON file:
REM -----------------------------------------------------------------------------------------
RegSvr32 "%windir%\System32\urlmon.dll"

REM Manually register the HLINK file:
REM -----------------------------------------------------------------------------------------
RegSvr32 "%windir%\System32\hlink.dll"

REM 64-bit
REM ---------
REM Manually register the OLEDB files that are used with Web folders:
REM -----------------------------------------------------------------------------------------
IF EXIST "%CommonProgramFiles(x86)%\System\Ole DB\oledb32r.dll" RegSvr32 "%CommonProgramFiles(x86)%\System\Ole DB\oledb32r.dll"
IF EXIST "%CommonProgramFiles(x86)%\System\Ole DB\msdaurl.dll" RegSvr32 "%CommonProgramFiles(x86)%\System\Ole DB\msdaurl.dll"

Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.
  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email.