Following on from yesterday’s post about the difference between Check-Out and Locking in SharePoint, I found myself wondering what happens if you violate a lock? Or a Check Out? Let’s look at locks first… Continue reading
I had been asked to look at a SharePoint event receiver that wasn’t behaving as it should. After a document had been checked in, it would set a property and update the item. However, we were getting an error:
SPException: The file “[File Name]” is locked for exclusive use by [User]
This was unfortunate – the user was the user who’d just been making changes, and the code was running after the document had been checked in – so what gives? Well, it turns out that the message is right – the file is locked, not checked out, and a lock is not the same as a check-out.