Onedrive Upload Failed This File Is Locked for Editing by Another User

Problem

The file is currently checked out or locked for editing by another user in SharePoint

About the Problem

How-do-you-do geeks, sometimes it becomes a little catchy to delete a binder in SharePoint library.

In this item commodity, we're going to run into such a scenario in which a user has full rights on the library but is unable to delete the folder in SharePoint 2013 or in SharePoint Online.

Or in modern view, it's something similar:

Let's starting time the journey.

In SharePoint, a user having full permission on the library, even is he/she is site collection admin, is unable to delete items just because that item is checked out by some other user. But, what if he is unable to figure out past whom the detail is checked ou?. So, hither, we come at the problem with a expert solution.

Allow'due south understand it by a scenario here.

A user created a library named Library1 and created a folder named Folder1.

Now, create a binder in Library1 named Folder1.

Now, the user has created a document in a document library.

Note: The tricky part comes into the picture at present. By Default, when a user creates a Library, it comes with versioning enabled. Somehow suppose that versioning is not enabled or manually disabled by the user at the time of creation, and so the versions of the item will non be captured.

Sometimes, what happens is that when a user creates a document, it directly goes into the checked out state without having version enabled in the list. So now, the document is in checked out state and doesn't have a bank check-in version as the version was not enabled. This is chosen "Files with no checked in version".

So, let's dig deeper into the problem and find the solution.

A user uploaded a certificate in Folder1 (created above).

At present, let's check its version history.

And so, nosotros empathize that versioning is enabled on the listing. At present, user checked out the certificate for editing purposes. Another user is still able to see the document in the checked out state just because information technology has a version.

Permit's see some other aspect of this scenario. Suppose versioning is disabled from the setting page of listing/library.

Besides, user enabled one more setting for checking out document.

What is this setting all well-nigh? When a user creates a certificate, information technology direct goes into the checked out land without having any changes which means the user is now authorized to brand changes earlier anyone else makes a modify.

If you wait in ECB card, the option related to versioning is non shown.

At present, user uploaded a new document and that document is directly checked out as required and checked out setting is enabled at the library level.

Now, allow's see when another user looks into the library.

Annotation - The first user who created the certificate checks in ImportTermSet.csv file .

Wow, some other user can't see a newly created document that was checked out at the time of creation past the showtime user (Asha in this case).

So when another user wants to delete Folde1, he/she gets the fault.

Then at present, think how a user identifies which document is checked out by which user so that he tin delete the unused folder.

So here is the solution. There is a setting in setting page  -

Click on the setting above. The user is able to meet how many documents in Libray1 are checked out that have no checked in version. So, in this case, the user can do two things to delete that folder. One, he can ask the person to check out in order to release the document or second, he can accept ownership of that document.

And then in rare cases, suppose a user takes the buying of that document that is checked out by someone else.

Now, the user is able to see both documents.

Now, the user tin discard check out or can check in.

Now if the user wants to delete the folder he can successfully delete that folder.

Note: For security reasons, information technology is not adequate that someone else deletes our file. This is but acceptable when folders accept some garbage files that have no meaning at all.

So here is the terminal output of the problem.

Now the folder has been deleted. This is besides applicable when nosotros try to delete the folder using custom lawmaking (JSOM, CSOM, SSOM, REST API, PowerShell).

Thanks for reading.

Please comment for a salubrious knowledgeable chat.

huffwourry.blogspot.com

Source: https://www.c-sharpcorner.com/article/resolving-file-checked-out-or-locked-for-editing-issue-in-sharepoint/

Share this post