It has gone rather worryingly quiet. We have discovered that the problem does not exist in Windows7 beta either, so that would suggest it's a Vista thing. Is there any way we can trace the process to see if we can capture where the problem lies. Regards Robert. Thursday, February 12, AM. Thursday, February 19, PM. Hi YM I feel your pain. I would have hoped for a solution before now, but it appears no-one knows whats going on. We have had to resort to the good old method of emailing documents and then managing the changes from different departments manually.
We're looking at raising an incident report with Microsoft to see if we can get this thing moving along. If I get an answer that works , then I'll post it here. Monday, February 23, AM. Thanks for the info Dave. I will try this out today and let you know how successful it is.
Fingers crossed it solves the issue. Monday, March 2, AM. Did the solution ever work? Friday, April 3, PM. It has definitely worked for us. I am not sure if the registry key alone will do it and therefore not do steps 1 - 3 but we will be testing this shortly - will let you know outcome. Cheers Dave. Sunday, April 5, PM. These settings worked for me, but only after the last bit of the compatibility mode. I am running this on Windows server OK, almost Vista.
On the other hand, I can imagine that the solution is somewhat embarrasing to Microsoft. And also Mm, interesting setup, bravo for those who manage to sell this. Friday, July 24, AM. We were having the same trouble and then, lo and behold, I found your post. Works a treat. We didn't need to perform step 2 as we had disabled that early on. Or, you can ask the person to close the file, check it in , or give you edit permissions.
If you want to work on the file at the same time as other people, then make sure everyone uses a version of Excel that supports co-authoring. When you co-author, more than one person can open the file, and you can see each other's changes quickly — in a matter of seconds.
If just one person uses a version of Excel that doesn't support co-authoring, then everyone else will get the "locked" error — even if everyone else is using a version of Excel that does support co-authoring. Libraries on SharePoint On-Premises sites. If you have an on-premises site and Excel for Microsoft , try using Excel Online to co-author instead. For Windows : If you are trying to co-author , check the file name of the file and make sure it is in either.
For Mac : If you are trying to co-author , check the file name of the file and make sure it is in either. If you are using the OneDrive sync app for Windows, make sure you are using the latest version. Also, make sure the sync app is not paused. Ask the person who has the file open to do one or more of the following. The first thing to try is to turn off the Shared Workbook feature.
Also, if you are opening a snapshot from SharePoint, open the workbook itself instead. If those two solutions don't work, try one or more of the following.
Help please. Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google.
Sign up using Facebook. If so, as this happens on your browser, I'd suggest that you may change the settings of your browser by the following steps to fix this error:. Please add the SharePoint site as a trusted site on your browser. Please click "Edit in Excel" to edit this workbook with your Excel desktop application to see if it would work;.
In order to check if this is related to the settings on the SharePoint site, please check if you could encounter the same issue with opening the other workbooks in this SharePoint sites, and whether your colleagues encounter the same issue. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. You are correct about the workbook however my colleague and I are still experiencing the issue after following your steps.
Thank you for your feedback. To better understand the issue and further assist you, I'd appreciate it if you should share with us the results after you tried the trouble shooting steps above.
0コメント