SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Every site in the collection is now read-only. I can still change settings in the central admin site but am unsure what has changed.

This affects everyone, users with write permission, even site administrators.

I've checked non of the service accounts have expired passwords, the SQL permissions are OK, even adding new users to Windows and assigning them to the SharePoint users group does not allow access when it should.

We have a single server running one site collection with about 8 sites and the central admin site.

I'm not sure if this is down to the cock up with the August CU and SP1 install thats just happened. I've now got SP1 on and the

I'm not a full time SharePoint admin either, its defiantly part time.

EDIT: Sorry, yes the databases were not set to read only, what I should have said is that the correct service accounts are allocated to the correct databases & content databases

share|improve this question
Checked 'SQL permissions' means the databases are not set to read only, right? Can you be a bit more descriptive about what error(s) you get? – Regmi Sep 23 '11 at 22:21
up vote 5 down vote accepted

You can set the site collection to Read-Only from CA, so it is possible that someone did this:

CA > Application Management > Site Collections section > Configure Quotas and Locks > Select site collection > check if it is set to Read Only

I think its default that site collections are set to read only during backup, so maybe you have a failed backup that didnt get to set the site collection back to normal?

More here

share|improve this answer
Would you mind adding info about database status (RO or data file / transaction log full, not enough space on disk?) to make the answer more universal? – Alexey Krasheninnikov Jan 14 '15 at 10:09

Check Disk Space. If it runs too low, the farm will go read-only

share|improve this answer
That's true, and disk space on SQL server too, transaction logs sometimes consume all available space. First you can't change anything, second images missing and than portal is unacessible at all... – Molik Sep 24 '11 at 16:44

Sometimes, a DBA might switch the database to Read-Only. It would have the same effect.

share|improve this answer

Check this link

  1. Central Administration -> Site Collection Quotas and Locks.
  2. Select your site collection

One of the following might be enforced: Adding content prevented, Read-only or No access. If not, this answer doesn't apply. Check the content database status in SQL Server Management Studio, as it could be switched to Read-only as well.

  1. Change the Site Lock Information radio button from “Read-only” to “Not locked”
  2. OK the changes
share|improve this answer
This site's policy encourages content in answers rather than links. Please include at least some content from the blog post in your answer to avoid your posts being downvoted. – Alexey Krasheninnikov Jan 14 '15 at 10:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.