Microsoft Knowledge Base Email Alertz

BUG: Error message when you try to upload a file from a Windows Vista client to a server that is running IIS 6.0: Cannot read from source file or disk

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 942858 - Last Review: February 4, 2010 - Revision: 2.0

BUG: Error message when you try to upload a file from a Windows Vista client to a server that is running IIS 6.0: "Cannot read from source file or disk"

SYMPTOMS

When you try to upload a document to a server that is running Internet Information Services (IIS) 6.0, you may receive an error message that resembles the following:
Cannot read from source file or disk
If you click Try Again when you receive the error message, you receive the same error message again. If you click Cancel, the file that you uploaded is deleted from the server.

CAUSE

This issue occurs when the following conditions are true:
  • You try to upload the file from a client computer that is running Windows Vista.
  • The document was created in Microsoft Office 2003 or in an earlier version of Office.
  • You try to upload the file by using the World Wide Web Distributed Authoring and Versioning (WebDAV) extension to the HTTP protocol.
  • IIS content is stored on a remote UNC share.
Note The problem may be more likely to occur if Server Message Block (SMB) opportunistic locking is disabled on the server that is running IIS. Also, note that this problem does not occur in Microsoft Office SharePoint or in other programs that do not depend on the IIS server-side implementation of WebDAV.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

The Windows Vista WebDAV client sends an "If: (<opaquelocktoken:GUID>)" header together with a PROPPATCH request. The PROPPATCH request is sent after the PUT request to upload the file. This behavior causes IIS to try to use OLE structured storage to write properties to the file while the file is being committed to disk on another thread. A network trace shows the PUT request succeeds with status code 207. However, the PROPPATCH request may fail with error code 500. The PROPPATCH request may also fail with error code 405 because an extra check is performed on the file system type on the remote computer on which IIS content is stored.

If the user on the Windows Vista client clicks Cancel in the error message dialog box, a DELETE request is sent to the computer that is running IIS.

Note A Windows XP WebDAV client does not send the lock token. Therefore, you do not experience this issue when you upload files from a computer that is running Windows XP.

REFERENCES

For more information about opportunistic locks, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/aa365433.aspx (http://msdn2.microsoft.com/en-us/library/aa365433.aspx)
For more information about how to configure opportunistic locking in Windows, click the following article number to view the article in the Microsoft Knowledge Base:
296264  (http://kbalertz.com/Feedback.aspx?kbNumber=296264/ ) Configuring opportunistic locking in Windows

APPLIES TO
  • Microsoft Internet Information Services 6.0
Keywords: 
kbupload kbtshoot kbprb KB942858
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate