Cannot Edit Documents in SharePoint
We have MOSS 2007 installed. From this implementation, I run a site that has all that SharePoint has to offer and another site trimmed down to just Windows SharePoint Services functionality. Recently my users have reported and problem to me that they find irritating. It happens on both my sites where I run SharePoint Server and Windows SharePoint Services. The odd thing is that it does not happen on all the sub sites created under these two top-level sites. Users that have reported the problem have contribute and full control permissions on the sites in question. "This document could not be checked out to your local drafts folder. The document may have already been checked out, or the local drafts folder could not be written to." My users are using MS Office 2007 and run Windows XP SP and Windows Vista SP1. If anyone could be so kind to help me I sure would appreciate it. I have search all available resources that I am aware of and have yet to find anything that points me to a solution. Thanks,
April 19th, 2008 5:28pm
Any luck resolving this?
April 28th, 2008 11:07pm
Nasty! Here's a few things to check: What zone is Internet Explorer detecting the web site as (bottom right of your web browser window). Ensure that it is in the Intranet or Trusted Sites zone Do these users have the SharePoint Drafts folder in their My Documents folder? If so, can they copy a file into it? They are using Internet Explorer - right? Do you have automatic check-out enabled? Does it make a difference if you disable this option? Ivan
April 29th, 2008 12:55am
Any luck resolving this? I have the same issue.
May 7th, 2008 9:06pm
I have the same issue with two users. No reported issues from anyone else. This is a big problem.I've seen some tech notes that proxy configuration may also cause some trouble like this but we do not have this configured. We also have the MOSS server in the "trusted sites" zone.
July 23rd, 2008 4:53am
What is this"where I run SharePoint Server and Windows SharePoint Services."supposed to mean.You already said you have MOSS 2007 - so why do you say that some sites run "SharePoint Server and Windows SharePoint Services" ?You can't run both products on the same server.
July 23rd, 2008 6:53pm
I've resolved the problem on one of the laptops by doing a repair on the MS Office 2007 install.
July 23rd, 2008 7:02pm
I have the same issue. I have the site in my trusted sites list.Actually I have a test environment and production. No problem checking out on the Test but Production I get this error. I'm using the same PC and browser. The production environment is behind a different firewal which is doing NAT though .... but I'm clutching at straws here :-)
August 26th, 2008 4:18pm
Has anyone been able to correct this issue? I've come across it recently as well, but with an interesting twist.The following error occurs, This document could not be checked out to your local drafts folder. The document may have already been checked out, or the local drafts folder could not be written to.when I click OK, the following error then immediately occurs, The document could not be opened for editing. A Windows SharePoint Services compatible application could not be found to edit the document.We are running MOSS with Project Server 2007.These errors only occur in certain Folders within certain SharePoint Document Libraries. It isn't consistent.A workaround was discovered. We check out the file manually, then open the folder and the Desktop in Windows explorer, make our changes and save them on the Desktop, then copy them back into SharePoint. On Checkin, it gives us the ability to add a new version with comments.This is really annoying and time consuming. Any assistance would be greatly appreciated.
June 26th, 2009 12:58am
Did you check the location of the local drafts folder on the local client, and if the users have access to it? You can do this e.g. in Word: click the Office button, click on Word Options, go to the Save category and check the Server drafts location...
July 3rd, 2009 4:28pm
Is client integration turned off for the web application that contains the site that you're attempting to access documents? Just throwing it out there...More than likely it is not since it sounds like things are working for one of the client machines properly post fixing your 2007 installation.http://www.spdan.com
July 4th, 2009 6:08am
We had the same problem and discovered that it was because we had exceeded the 260 character UTF-16 limitation for SharePoint paths (see http://support.microsoft.com/kb/894630). After we shortened the length of some of our subfolders, this resolved the problem.Hope this helps,Eric Barkerhttp://www.barkerzone.net
July 21st, 2009 10:47pm
This issue has flummoxed me for close to a month. Our original nine month (MOSS 2007 Enterprise) test site and the proposed MOSS 2007 (Standard) production site have been affected with the same inability to edit and save documents that have the Forced Check Out feature turned on. Many of the original sites from the original (Enterprise) test site collection are fine, and are still fine after migrating to the (Standard) production site via SP Designer. This issue only occurs to new subsites and their (forced Check Out) document libraries. There are no content types that have required columns (neither Item nor Document). Weve set up a third site for further testing, but have not been able to replicate the issue. Strangely, now when I open a document from one of the affected sites a subfolder structure that corresponds to the SharePoint structure is created within SharePoint Drafts folder. Example: C:\My Documents\SharePoint Drafts\huddle\departments\is\sysadmins\Server Documentation\filename.docx When forced Checked Out files are opened from the non-affected (third) site, their local copy is stored in the root of C:\My Documents\SharePoint Drafts\ This folder structure creation seems to onlyhappen to me, yet everything else seems to be consistent with all others. (I did do an Office Repair, might be the cause) All of this has to be a site issue because our successful third site environment is built on the same server as one of the affected sites. And yes to all the other items listed in this thread (Trusted Intranet Zone, no proxies, and I do have permissions to my local folder), and an example of URL length is in the area of 96 characters. I understand exceeding 260 can cause problems.
August 4th, 2009 5:21pm
Workaround, ask admin to reload the document, or check it out and resave it, or undo check out. Then try again by checking out and check in.Sara
January 28th, 2010 10:52pm
If you are running URLScan with IIS try this http://support.microsoft.com/kb/825538 I had the same issue and this fixed it.
March 12th, 2010 10:57pm
Hi i have similar issue but with windows 7 installed with Office 2007 trying edit any document on WSS 3.0 it gives erorr "a problem occurred while connecting to the server. If problem continues, contact your administrator"
May 6th, 2010 4:45pm
We are having the same problem with Sharepoint once we upgraded to Windows 7. We can connect to the Server, some machines can only download in a "Read Only" mode although the users have permission to edit and save, and other machines will download but will only save files to the local computer's Libarary. We are wasting lots of time on this. Very frustrating that you cannot save directly to the site. I have tried mapping the drive to the website and everything else on this thread and many more. Obviously Microsoft needs to come up with a "Fix" for Windows 7. We also cannot open files in Windows Explorer. Hopefully Microsoft will hear and come to our rescue.
May 6th, 2010 10:26pm
I was having the same problem and tried all the things that everyone had suggested about office, IE security settings, Fake Proxy, and so forth. I was having problems with a particular document list and I tried created another document center and move the documents and see if that worked. IT DIDN"T. Anyways long story short I uploaded some new files and they weren't having the same issue. Then I took one of the documents that where having the same problem moved it to my desktop and it still couldn't edit it. I did this using the explorer view and checked the properties of the file and for some reason it was set to READ ONLY. I uncheck the box and the problem solved. I did this to all the files in the document center and now I can edit them again. Hope this helps.
May 12th, 2010 9:40pm
i had the same issue but was able to resolve by freeing up some space on the servers. We kinda ran out of disk space on our Front End servers that was causing the whole situation. Have you checked to mkae sure your Front End Server has enough resources ?Jawad
May 12th, 2010 10:38pm
This is one reason I tend to suggest not using the option for Local Drafts Folder. This is a client side application setting and not a Sharepoint one. I have seen, many times, issues of corruption, file locks etc, revolving around this function. most folks don't need this ability as they use SharePoint while connected to the network. You can use Group policy to turn it off, or your users can through the Word Options (for 2007) as mentioned earlier in this thread.Imagine what we could be...If we could just imagine. Daniel A. Galant
May 13th, 2010 9:09pm
Daniel, Can you expand on the "client side application" idea? We're having a Very Strange issue with doc libraries. MOSS 2007, but we use Office 2003. After working fine for months, a site began acting strangely. Files only open as Read-Only. The ONLY way to get a file to open in Edit mode is to click the link, select 'Check Out and Edit' and then check the 'Use Local Drafts Folder'. The ONLY way. If we first Check Out the document, then in the next step select 'Edit if Office program', it opens in Read-Only. We have to manually ensure that Local Drafts is checked in order to be able to edit. Even if we edit a document, and save it, then leave it checked out, we can't return to it and edit it a second time. We have to check it in, then go through the process which allows us to manually check 'Use Local Drafts Folder'. Our problem is that not everyone gets this option, to use Local. Am looking for clues as to what might have changed, or what I can do to fix this. Thanks! Keith
July 8th, 2010 5:53pm
I have same problem with WSS3. From few systems, not able to checkout or open most of the files. I did, reinstallation of office 2007, changed word file drafts folder path(although it is happening for excel, notepad and pdf file also). Reinstalled IE8 but not worked. My observations are: 1. Same user able to open from other system in IE6.(So not a permission issue) 2. Using Mozila Firefox, it is working fine. So looks like problem with IE8 only. Please share if there is any trick for this. Thanks/ Ibnul
July 10th, 2010 2:25pm
me having the same issue like Ibnul. IE 8 is not able to check out. i get a "Permission denied", but in Firefox i can checkout! Any suggestions? Pat
July 30th, 2010 1:44pm
Another observation: If I install Office 2003 version instead, It works fine with any version of IE. So looks like something to do with MS Office. Please help. Thanks/ Ibnul
August 5th, 2010 6:06pm
you need to install office in your sharepoint server.Sara
October 7th, 2010 8:36pm
you need to install office in your sharepoint server. Sara What's the reason for doing that?
April 5th, 2011 12:35am
Office repair sorted it for me but we've seen many problems with more than one version of office installed, Office 2003 with say Access or Project 2007 causes problems
July 5th, 2011 5:33pm
You probably have multiple versions of Office on the workstation. Like Office 2010 Professional and Office 2007 Project or Visio or SharePoint Desinger. To correct this you should disable SharePoint Support Services in the smalerl Office applications (Project and Visio), and run a repair of the full Office Client. Simiplay running a repair will only fix the problem until an update is released for one of the smaller products. Example ===== Windows XP machine with Office 2003 Professional, Office 2007 Project, and Office 2007 Visio. You would do a change in add remove programs on Project and Visio and disable SharePoint Support. Then run a repair of Office 2003. -AseemThis posting is provided "AS IS" with no warranties, and confers no rights
July 5th, 2011 9:05pm
This is incorrect you should not install Office on your SharePoint Server. This posting is provided "AS IS" with no warranties, and confers no rights
July 5th, 2011 9:06pm