When you try to open a Microsoft Office document from a Web site hyperlink in a 2007 Microsoft Office application, you may experience the following symptoms:
Performance is slow, or the 2007 Office application may stop responding for several minutes.
You are repeatedly prompted for authentication even when correct credentials are supplied. This can occur for users who have ReadOnly permissions to a document on a Microsoft SharePoint 2003 server.
You lose session state. Then, you are redirected to a logon page or to an error page on the Web site.
The document is downloaded two times. When the files are large, the download process consumes more network bandwidth.
Note These problems do not occur when you try to open the document on a Windows XP-based computer or on a Windows Server 2003-based computer. These problems occur on Windows operating systems beginning with Windows Vista.
This article helps you fix the problem.
To resolve this problem apply hotfix 954573.
For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
954573 Description of the 2007 Office system hotfix package: June 26, 2008
Note you must install the hotfix discussed in the Resolution section above before continuing.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To fix this problem, follow these steps.
Enable the hotfix by configuring the UseWinINETCopy registry entry. To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
On the Edit menu, point to New, and then click DWORD Value.
Type UseWinINETCopy, and then press ENTER.
Right-click UseWinINETCopy, and then click Modify.
In the Value data box, type 1, and then click OK.
Exit Registry Editor.
Restart the computer.
Note Applying this registry setting implies that read-only files open from a URL address will remain read-only as long as the file is open. This can negatively impact some features with Microsoft SharePoint Server. This setting prevents the client from being able to edit and save directly back to the server once while it was opened as Read-Only. For example, Office 2007 has a feature that allows a user to open a file read-only and switch to read-write access at a later time by using the [Edit] button on the Information bar at the top of the document. This kind of feature will not work with the registry setting that is applied here. In order to edit and save directly back to SharePoint you must choose to open the document in Edit mode by choosing the [Edit in <application>] selection in the dropdown (where <application> is the registered editor associated with the document file type).
This problem occurs because, on client computer running Windows Vista or newer operating system, 2007 Office applications use the Windows WebDAV Mini-Redirector Client component to open URL-based files. This component provides read/write permissions to DAV-based Web servers that support Web authoring.
When you try to open a document from a hyperlink, 2007 Office applications may request that the Windows WebDAV Client try to author the document at the URL location. However, if the authoring attempt is not expected on certain Web servers or in certain situations, the symptoms that are mentioned in the "Problem description" section may occur.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Did this fix the problem?
Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support.