This article was previously published under Q304133
This article has been archived. It is offered "as is" and will no longer be updated.
If you try to use a Microsoft Office XP program such as Microsoft Word 2002 to save your content to a FrontPage Web or Web site based on SharePoint Team Services from Microsoft, you may experience one of the following symptoms:
A message appears that indicates that the document will open as read only.
A network or file permission error appears, and you cannot save the file.
An error message appears that indicates that you cannot save the file.
When you open a Web folder on a Web server running Microsoft Internet Information Services (IIS), you do not see any files listed in a SharePoint Team Services document library, or the following error message appears:
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.
In every case, you can temporarily resolve this problem by restarting IIS.
This problem may occur if IIS returns an incorrect MS-Author-Via HTTP header. This header notifies a client computer using Web folders about which Web publishing protocols are supported by the Web server.
To work around this problem, follow these steps in the order shown.
Step 1: Add a Custom HTTP Header
You can enable a custom HTTP header that forces IIS to always inform the client that it is a server based on FrontPage or SharePoint Team Services. To do this, follow these steps:
Start the IIS Internet Service Manager.
Right-click the computer name, and then click Properties.
In the Master Properties section, click WWW Service, and then click Edit.
Click the HTTP Headers tab.
In the Custom Header Name box, type MS-Author-Via.
In the Custom Header Value box, type MS-FP/4.0,DAV, and then click OK.
In the Custom Header Name box, type MicrosoftOfficeWebServer.
In the Custom Header Value box, type 5.0_Collab.
Note If the Inheritance Overrides dialog box appears, select the appropriate option for your situation:
Note which servers have unique settings applied to them and manually add the MS-Author-Via and MicrosoftOfficeWebServer headers to each virtual server later.
Click Select All to apply the settings you just made to all your virtual servers.
Note You will lose any custom headers that you added to your virtual servers.
From a command prompt, type IISRESET, and press ENTER.
If you are still experiencing the problem, go to step 2.
Step 2: Clear the Cache on the Client
Some Windows 2000 clients may still have a problem saving to the server. This can occur if the client is caching the Web folder settings. To correct the problem, clear the cache on the client computer. To do this, follow these steps:
Double-click the My Network Places icon on the desktop.
Delete the Web folder that points to the Web where the problem is occurring.
From a command prompt, type the following
cd /d %USERPROFILE%\Application Data\Microsoft
and then press ENTER.
Leave the command prompt window open.
Right-click the taskbar, and then click Task Manager.
Click the Processes tab.
In the list of processes, right-click Explorer.exe, and then click End Process.
If you are prompted to confirm if you want to end this task, click Yes.
Switch to the command prompt.
Type the following
rd /q /s MSDAIPP
and then press ENTER.
Switch to Task Manager.
On theFile menu, click New Task (Run).
In the Open box, type explorer, and then click OK.
If you are still experiencing the problem, go to step 3.
Step 3: Disable WebDAV on the Web Server
Disable WebDav on the IIS Web server. For additional information about how to do this, click the article number below to view the article in the Microsoft Knowledge Base: