tag:blogger.com,1999:blog-14718171.post115884255475613483..comments2024-02-18T09:32:27.373+01:00Comments on Robin's Sharepoint Blog: Sharepoint 2003 : Unlocking longterm checked-out documentsRobin Meuréhttp://www.blogger.com/profile/06878262430984779866noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-14718171.post-8662087213957783902014-12-28T08:36:38.283+01:002014-12-28T08:36:38.283+01:00Very informative post. I sometimes do presentation...Very informative post. I sometimes do presentations on SharePoint and was wondering if I could use your Print List example in my presentations and refer my audience to your website for further info.public key infrastructurehttp://www.arx.com/resources/white-papers/pki-solution-for-electronic-signatures.htmnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-17566536928813347292012-03-23T09:10:46.540+01:002012-03-23T09:10:46.540+01:00I ecountered the same issue on SP2003, and I went ...I ecountered the same issue on SP2003, and I went to the General Setting and uncheck Version control and re-enable the version control again, then the file can be opening again without telling you it was locked by a user.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-57505284461755598612011-05-20T15:25:54.091+02:002011-05-20T15:25:54.091+02:00Stumbled accross this post whilst trying to resolv...Stumbled accross this post whilst trying to resolve an issue I was having with being unable to check out a document that was not checked out or locked locally. I eventually found the cause to be that we had reached SharePoint's inherent limit of 511 minor draft versions and the fix was to publish a major version. Switching off 'Require checkout' on the versioning setttings revealed the underlying problem.Robnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-33995568743636748402011-01-20T18:28:55.197+01:002011-01-20T18:28:55.197+01:00I exported the list with contents as a template, c...I exported the list with contents as a template, created a new list from the template, and everything worked. I then deleted the original list with the bad file.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-59045370364302776112009-12-18T15:20:10.241+01:002009-12-18T15:20:10.241+01:00Hi Robin,
I just found another fix, which seems t...Hi Robin,<br /><br />I just found another fix, which seems to work OK for me in the same situation.<br /><br />Click Site Actions > Site Settings<br />Under Site Administration, select Content and Structure<br />Navigate to the relevant doc library<br />Find your document, hover your mouse over the name field, then select Discard Checkout from the drop down list.<br /><br />The other method of managing checked out files is to go the the list & select Settings, Document Library Settings. Next, click "Manage checked out files" under "Permissions and Management"; I believe that's the method you had been using previously?<br /><br />Hope that helps,<br /><br />JBJohnLBevanhttps://www.blogger.com/profile/08453894127666119527noreply@blogger.comtag:blogger.com,1999:blog-14718171.post-84423514134054169892009-09-10T21:00:51.320+02:002009-09-10T21:00:51.320+02:00See relate post for this in http://social.msdn.mic...See relate post for this in http://social.msdn.microsoft.com/Forums/en-US/tfsgeneral/thread/d1d5a9bd-9f37-418f-8ed6-8bb70a3d120b?prof=required <br /><br />Use SQL Server Management to connect to your WSS_Content database do select your files using this select:<br />(select * from alldocs where dirName like "directory to your file"%' and checkoutuserid = "user")<br /><br />Update the checkoutuserid, checkoutdate, and checkoutexpires to NULL.Thien Tonnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-17691294223001116962009-01-10T05:10:00.000+01:002009-01-10T05:10:00.000+01:00Actually, it's not this complicated. Open the libr...Actually, it's not this complicated. Open the library in SharePoint Designer, right-click on the locked document and select Check-In on the context menu.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-62352230112057974762008-08-18T20:28:00.000+02:002008-08-18T20:28:00.000+02:00What Visual Studio Project Should I use to run thi...What Visual Studio Project Should I use to run this code? How can I implement this in SharePoint 2007?<BR/><BR/>I have Visual Studio 2005, but don't know how to easily run this code snippet to unlock the file.<BR/><BR/>Please help. Thanks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-14718171.post-44948346509400547042007-01-12T12:12:00.000+01:002007-01-12T12:12:00.000+01:00Hi,
sorry about the delay in my reply. But if I'm...Hi,<br /><br />sorry about the delay in my reply. But if I'm not mistaken, a user who has read-only rights who will open a document. The document will be openend in readonly mode and thus not enforcing a short term lock.Robin Meuréhttps://www.blogger.com/profile/06878262430984779866noreply@blogger.comtag:blogger.com,1999:blog-14718171.post-1165510107840450652006-12-07T17:48:00.000+01:002006-12-07T17:48:00.000+01:00Robin,Thanks for the information. I have a similia...Robin,<BR/><BR/>Thanks for the information. I have a similiar issue that I was hoping you might have a solution or suggestion about. I have given certian user's read permision only. I however have noticed that sharepoint 2003 still allows them to open the document residing on the server thus locking it from editing from authorized user with write permision. I was wondering if there is a method that can force that can force a read only user to have to open a copy on the local drive of his or her own machine? I would greatly appreciate any insight you or your colleages may have on this matter.Anonymousnoreply@blogger.com