Our office, like many others, uses SharePoint for a wide variety of uses. To say that our SharePoint is “business critical” is not an over-statement. Recently, we ran our SQL Express instance of the SharePoint database into the SQL Express 4GB database size limit. While moving the database was not a huge issue, what was an issue is that SharePoint, on an internal basis, apparently marked the database as “read-only.”
What is important here is that SQL did not think the database was locked, SharePoint thought it was locked. After we moved the database to full SQL server, and reconnected the database to the SharePoint farm server, we still could not edit, add, or remove items, documents, or perform other action/task except look at database contents.
Running the following command showed that SharePoint had the database marked as “readonly” (command may have wrapped)
stsadm -o getsitelock -url http://servername
This command returned this output, which explained our issue!
<SiteLock Lock="readonly" />
How to fix this? Here’s how: (command may have wrapped)
stsadm -o setsitelock -url http://servername -lock none