Skip to main content
SharePoint

Return to Question

added explanations how to reproduce the steps.
Source Link
Francois Verbeeck
Francois Verbeeck
  • 3.4k
  • 2
  • 18
  • 29

I do have a SharePoint (2013) site collection that is stuck in read only mode due to a backup that was either interrupted or didn't terminated properly.

I'm unable to unlock from :

  • Site Quotas and Lock in Central Administration (option is greyed-out)
  • Stsadm : operation completes successfully but no change
  • Using PowerShell : same behavior as stsadm

I reviewed the associated content database to ensure it was not in single user mode neither in read-only which was not the case. Disk space is not an issue neither.

Anyone knows how SharePoint is persisting that information in the content database so that I could have a sneak peek ? Any other way to unlock this state ?

If anyone wants to reproduce this, you can break a backup operation (stsadm / powershell CTRL+C) while the site is being backed up. The ReadOnlyMode Property (and the associated MaintenanceMode property) will be left to "True" preventing any update.

I do have a SharePoint (2013) site collection that is stuck in read only mode.

I'm unable to unlock from :

  • Site Quotas and Lock in Central Administration (option is greyed-out)
  • Stsadm : operation completes successfully but no change
  • Using PowerShell : same behavior as stsadm

I reviewed the associated content database to ensure it was not in single user mode neither in read-only which was not the case. Disk space is not an issue neither.

Anyone knows how SharePoint is persisting that information in the content database so that I could have a sneak peek ? Any other way to unlock this state ?

I do have a SharePoint (2013) site collection that is stuck in read only mode due to a backup that was either interrupted or didn't terminated properly.

I'm unable to unlock from :

  • Site Quotas and Lock in Central Administration (option is greyed-out)
  • Stsadm : operation completes successfully but no change
  • Using PowerShell : same behavior as stsadm

I reviewed the associated content database to ensure it was not in single user mode neither in read-only which was not the case. Disk space is not an issue neither.

Anyone knows how SharePoint is persisting that information in the content database so that I could have a sneak peek ? Any other way to unlock this state ?

If anyone wants to reproduce this, you can break a backup operation (stsadm / powershell CTRL+C) while the site is being backed up. The ReadOnlyMode Property (and the associated MaintenanceMode property) will be left to "True" preventing any update.

added 36 characters in body
Source Link
Francois Verbeeck
Francois Verbeeck
  • 3.4k
  • 2
  • 18
  • 29

I do have a SharePoint (2013) site collection that is stuck in read only mode.

I'm unable to unlock from :

  • Site Quotas and Lock in Central Administration (option is greyed-out)
  • Stsadm : operation completes successfully but no change
  • Using PowerShell : same behavior as stsadm

I reviewed the associated content database to ensure it was not in single user mode neither in read-only which was not the case. Disk space is not an issue neither.

Anyone knows how SharePoint is persisting that information in the content database so that I could have a sneak peek ? Any other way to unlock this state ?

I do have a SharePoint (2013) site collection that is stuck in read only mode.

I'm unable to unlock from :

  • Site Quotas and Lock in Central Administration (option is greyed-out)
  • Stsadm : operation completes successfully but no change
  • Using PowerShell : same behavior as stsadm

I reviewed the associated content database to ensure it was not in single user mode neither in read-only which was not the case.

Anyone knows how SharePoint is persisting that information in the content database so that I could have a sneak peek ? Any other way to unlock this state ?

I do have a SharePoint (2013) site collection that is stuck in read only mode.

I'm unable to unlock from :

  • Site Quotas and Lock in Central Administration (option is greyed-out)
  • Stsadm : operation completes successfully but no change
  • Using PowerShell : same behavior as stsadm

I reviewed the associated content database to ensure it was not in single user mode neither in read-only which was not the case. Disk space is not an issue neither.

Anyone knows how SharePoint is persisting that information in the content database so that I could have a sneak peek ? Any other way to unlock this state ?

Tweeted twitter.com/#!/StackSharePoint/status/319402632731033600
Source Link
Francois Verbeeck
Francois Verbeeck
  • 3.4k
  • 2
  • 18
  • 29

Site collection locked & stucked in read only mode

I do have a SharePoint (2013) site collection that is stuck in read only mode.

I'm unable to unlock from :

  • Site Quotas and Lock in Central Administration (option is greyed-out)
  • Stsadm : operation completes successfully but no change
  • Using PowerShell : same behavior as stsadm

I reviewed the associated content database to ensure it was not in single user mode neither in read-only which was not the case.

Anyone knows how SharePoint is persisting that information in the content database so that I could have a sneak peek ? Any other way to unlock this state ?