Limitations of SharePoint Foundation 2013

Some of the Limitations of SharePoint Foundation 2013 Are :

1. Do not have any publishing features.

2. Don't Support Search Box in Page.

3. It Doesn't Support Page Layout as it doesn't support publishing features so we can't create templates.

4. It doesn’t support Workflows.

5. It Doesn't Managed Metadata.

6. It doesn't have Yes App Catalog (SharePoint).

7. It doesn't support Cloud-Hosted Apps, SharePoint-Hosted Apps, Auto hosted Apps.

8. It doesn't Support:App Management Services: This feature allows you to install apps from the Internal      Catalog or the Public SharePoint Store.

9. It doesn't Support:Auditing: Auditing – Site collection administrators can use the audit feature to track        which users have taken what actions on the sites, content types, lists, libraries, list items, and library        files of site collections.

10. It doesn't Support: Business Intelligence: Business intelligence (BI) in SharePoint 2013 provides                comprehensive BI tools that integrate across Microsoft Office applications and other Microsoft            technologies. These BI tools are: Excel 2013, Excel Services in SharePoint 2013, 

Performance Point Services in SharePoint Server 2013, Visio Services

11. It doesn't Support:

Community: Community – In SharePoint 2013, a Community Site is a new site template that provides a forum experience in the SharePoint environment. Use communities to categorize and cultivate discussions among a broad group of people across organizations in a company. Communities promote open communication and information exchange by enabling people to share their expertise and seek help from others who have knowledge in specific areas of interest. You can deploy a Community Portal to promote communities to users within your enterprise.

12. It doesn't Support:

Content Search Web Part: Content Search Web Part – The Content Search Web Part (CSWP) is a new feature in SharePoint 2013. It can be most accurately compared to the Content Query Web Part.

13. It doesn't support: News feed: News feed – Use the SharePoint News feed app to interact with your organization’s SharePoint social network.

Plan customizations, solutions, and apps for SharePoint Online

Customizations solutions & Apps for SharePoint Online

Get Started with SharePoint Online

https://dev.office.com/sharepoint

Find and remove SharePoint orphan database and unable to create site collection

• Cannot create new site collections
• SharePoint 2013 : Orphaned Content Database Removal
• Cannot create site collection error object reference not set
• SHAREPOINT ORPHANED CONTENT DATABASE
• SharePoint 2013: Deleting Orphaned SharePoint Databases
• SharePoint 2010: Cleaning Up Deleted Databases

Get Site URL, Site Title, Web Id etc

Get-SPWebApplication http://site | Get-SPSite -Limit All | Get-SPWeb -Limit All | Select Title, URL, ID, ParentWebID | Export-CSV C:\WebAppInventory.csv -NoTypeInformation

Unable to remove web application from SharePoint 2013

I have tried delete web application facing below error, my scenario is there is no database, and IIS site. 

An object in the SharePoint administrative framework, “SPWebApplication Name=ulabtechnologies:1234’ Site Parent=SPWebService”, could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation. The dependant objects are as follows: SPSolutionDeploymentJobDefinition Name=solution-deployment-


In SQL Management Studio:

SELECT * FROM Objects (NoLock) where Name like '%%'

Note the "Id" GUID.
SELECT * FROM SiteMap (nolock) where ApplicationId = ''

Note the 'DatabaseId' GUID.



Next step is to be done on a SharePoint server in the farm:

STSADM -O DeleteConfigurationObject -id {DatabaseId GUID from step above}

Repeat this for each row returned in the first step and then you will be able to successfully delete the web application from the farm.

Now try to delete web application 

Remove-SPWebApplication -Identity "" -Confirm

Rename Web Application name

$WebApp = SPWebApplication | where {$_.Name -match "OldWebAppName"}

$WebApp.Name ="NewWebAppName" 

$WebApp.Update() 

Get-SPWebApplication | where {$_.Name -match "NewWebAppName"}

Upgrading a multi-server SharePoint farm from Standard to Enterprise

1. Stop the Timer Service on all machines in the farm except for 1, in my case I left it running on the APP server.
2. Add the new product key and hit OK to start the SKU upgrade process in the Central Admin GUI.
3. Watch the event log of the APP server and wait for an entry with a source of “SharePoint 2010 Products Configuration Wizard” which will inform you that it was Successful.
4. Start the Timer Service on the next machine in the farm.
5. Watch the event log and wait again for the successful entry…
6. Continue with steps 4-5 on all additional servers in the farm.
7. Once you’ve received all successful entries in your event logs, a minute or so later you should get a successful notification in the GUI for the SKU upgrade.