SharePoint2013 Site Locked and stuck in read only mode

Method 1.  By using SharePoint central administration

Follow the Steps

1. Central Administration--> Application management> Configure quotas and locks.

 

 

2. Choose the option Not Locked

 

Method 2. By using PowerShell Script

Sometime Not Locked option disable then you cannot unlock using SharePoint central administration.

Open SharePoint 2013 Management Shell.

From the SharePoint 2013 management Shell, execute the following command:

 $site = Get-SPSite “SharePointSiteURL”

$site.GetType().GetProperty("MaintenanceMode").GetSetMethod($true).Invoke($site, @($false))

 

Thank you very much

          Fahadullah Karimi

         SharePoint Specialist

http://sharepoint-solution-tricks.blogspot.com/

• Previous Post
• Next Post

SharePoint 2013 and W3C Standard validator

Step by Step Backup and Restore Solution in SharePoint 2013

SharePoint 2013 and W3C Standard validator

 Following are case of SharePoint 2013 site does not validate by W3C validator

1. Attribute webpartid not allowed on element div at this point.

2. Attribute haspers not allowed on element div at this point.

3. Attribute width not allowed on element div at this point.

4. Attribute allowdelete not allowed on element div at this point.

5. Attribute allowexport not allowed on element div at this point.

And finally: 

6. Bad value for attribute action on element form: Must be non-empty.

7. Element ie:menuitem not allowed as child of element menu in this context. (Suppressing further errors from this subtree.)

 

So, It means SharePoint 2013 never follow full W3C Specification.

 

Thank you very much

          Fahadullah Karimi

         SharePoint Specialist

http://sharepoint-solution-tricks.blogspot.com/

• Previous Post
• Next Post

SharePoint 2016 Vs SharePoint 2013 Vs SharePoint 2010

SharePoint2013 Site Locked and stuck in read only mode

SharePoint 2016 Vs SharePoint 2013 Vs SharePoint 2010

 SharePoint 2016 Vs SharePoint 2013 Vs SharePoint 2010

Below table showing the high level comparison

 

	SharePoint 2016	SharePoint 2013	SharePoint 2010
Content Database Size	Content database sizing into TB’s	200 GB in general usage scenarios.	200 GB in general usage scenarios.
Site Collections per Content Database	100,000 site collections per content database	2,000 recommended 5,000 maximum	2,000 recommended 5,000 maximum
List Threshold	Increased List Threshold >5,000	5,000 items	5,000 items
Max File Size	Max File Size increases to 10GB and removed character restrictions	Default maximum file size is 250 MB which can increase up to 2GB	Default maximum file size is 250 MB which can increase up to 2GB
Indexed Items	2x increase in Search scale to 500 million items	100 million per search service application. 10 million per index partition	100 million per search service application. 10 million per index partition

New features list in Share Point 2016

1.      Mini Roles

2.      Sensitive Information Types and Data Loss Prevention

3.      Enhanced Software boundaries

4.      Image and Video Preview

5.      UI Changes and App Launcher

6.      Expanded Support for special characters

7.      Enhanced Document Library UI

8.      Improved Threshold limit by providing Auto Indexing

9.      Microsoft Project Server 2016 (PWA) integrated to SharePoint 2016

10.  Fast Site Collection Creation

11.  Zero downtime patching

12.  In-Place Hold Policy Centre site template

13.  Enhanced PowerShell scripts.

14.  SMTP Connection encryption for outgoing email

15.  Cloud Hybrid Search

16.  Hybrid OneDrive and Site Features

17.  Durable Links

18.  Increased number of Timer jobs

19.  SharePoint Logging API (SLAPI)

Deprecated features list from SharePoint Server 2016

1.      SharePoint Foundation

2.      Standalone Install Mode

3.      InfoPath

4.      SharePoint Designer

5.      Forefront Identity Manager Client (FIM)

6.      Excel Services

7.      Tags & Notes

8.      STSADM

9.      Upgrade Considerations

There is no supported upgrade from Share Point 2010 directly to 2016. Existing sites and Content DB should be running under Share Point 2013.

The upgrade process remains the same as in Share Point 2010 – Share Point 2013. Content Databases can be detached from SharePoint 2013 and attached to SharePoint 2016.

 

Thank you very much

          Fahadullah Karimi

         SharePoint Specialist

http://sharepoint-solution-tricks.blogspot.com/

• Previous Post
• Next Post

Step by step Configuration of SharePoint Server 2016

SharePoint 2013 and W3C Standard validator