After we began rolling out Windows 7 at the day job, we found our first issue–when people checked out documents from SharePoint 2007, the documents were opened as "Read Only", and the users could not save the edited document back to the portal. The work-around was to save the document locally and re-upload.
After four months of working with Microsoft, we were able to find the solution. The problem was in URLScan, and Windows 7's use of the OPTIONS verb. By default, this verb is blocked. If you look in the URLScan logs (by default, %WINDIR%\system32\inetsrv\urlscan\logs), you'll see an entry like the following (important parts are in bold):
2010-03-19 02:12:15 127.0.0.1 778810668 OPTIONS /<document library path>/ Rejected verb+not+allowed HTTP+method – –
All we need to do to fix this problem is edit urlscan.ini by default, (%WINDIR%\system32\inetsrv\urlscan), find the [AllowVerbs] section and add OPTIONS. Then scroll down a little to the [DenyVerbs] section, and remove OPTIONS from that list. Do an IISRESET and all is well.
For reference, our server platform is Windows Server 2008/IIS 7/SharePoint 2007, and clients are Windows 7 Professional using IE8. This issue does not seem to affect Windows XP users with IE 8.
Questions/comments? Please use the contact form. Because of jackass comment spammers, I've had to turn off comments for a while.
5 thoughts on “Windows 7 Cannot Save Documents to SharePoint 2007/Windows Server 2008”
I am having the same issue, however we are using Windows 7 with Office 2010 and a Sharepoint 2003 server on Server 2003. We cannot upload documents directly to SP. Save works, save as does not. We need to save to local and then re-upload.
I cannot find urlscan file in SP 2003 or on my Windows 7 machine. Can you provide any info on this? Any help is welcome!!!
Mark, did you ever find a solution to this? I’m having the exact same issue you are.
I no longer have an environment to test this, but you both might want to look at using Fiddler for some debugging. It might be a similar incompatiblity with protocols on the Win7/Office 10 and SPS 2003. If that’s the case, I’m not sure what can be done to resolve the issue.
Just thought I’d chime in and say I’m having this exact same and very annoying issue as well. Platform: Win7 client w/ Office 2007 & 2010, Sharepoint Foundation 2010 server on windows 2008 R2
Very same issue here. Very annoying indeed. Users are complaining my head off…
Comments are closed.