New answers tagged site-collection
For debug purpose, use the broswer console. Identify your REST Call in the console's XHR tab. If red, REST call returned an error: => either query is wrong or SP threw an exception If not red, REST call returned success, even though it has no results: => your query is ok. Right-click to open call in a new tab to see xml results on browser, or ...
You can do that from the UI, from SharePoint Admin Center. Navigate to your Admin center and on the ribbon, you should see the recycle bin where you can find any deleted site collections.
--------EXAMPLE 1-------- Get-SPODeletedSite -Identity http://contoso.sharepoint.com/sites/marketing This example returns the properties for the deleted site collection http://contoso.sharepoint.com/sites/marketing that is in the Recycle Bin. --------EXAMPLE 2-------- Get-SPODeletedSite -IncludePersonalSite This example returns all of the properties ...
You need to write PowerShell in 2 parts. One will create site collection and the other will apply custom template. Start Part 1 Create a SharePoint Site Collection with a custom Template using Powershell Write-Host “Provide the site collection URL e.g. http://intranet/site/custom” $Siteurl = read-host Write-Host “Provide the site collection owner email ...
The reason is when they were created, they were added on the SSA (Search Service Application) level not on the site collection level. I found this article very helpful in explaining the differences and limitations
There are two Publishing features that need to be enabled, one at the site collection level and one at the web (aka site) level. A key concept to understand here is that when you create a site collection, it has what is known as a "Root Web", which is the top site in the site collection. Because it's the top site in the site collection, it has some special ...
Style Library is located on the top level publishing web site. So you need to enable the publishing feature on the root site as well.
I think you are seeing the effect of a known "issue" I asked about here. Basically, when checking for a site existence, SharePoint seem to reference some internal caching mechanism. This seem to be the root cause of a site still begin detected as still "existing". As you can see from the linked discussion, there are actually two different aspects that you ...
I found the reason for the above scenario from the below link, https://technet.microsoft.com/en-us/library/ff607948.aspx Remove-SPSite -Identity "http://sitename" -GradualDelete -Confirm:$False This command actually leaves some mark about the deletion of the Site. But without GradualDelete option, Remove-SPSite completely removes the Site Collection ...
Use Get-SPDeletedSite "/" to get all the deleted site collections from the root site Check this link below https://technet.microsoft.com/en-us/library/hh286316.aspx
Welcome to the site. What happens when you add site columns to a list or content type is that a copy of that column is taken and added to the list or content type. For this reason, if you were to delete the columns from the list or content type, you would only ever be deleting the copy. Are you using content types in your list? If so, go to your list's ...
There might be something wrong with the config so i recommend not to do anything with config but you can follow below steps if there is no risk in it. Delete the web app (and site collection), and all newly created App Pools Re-Create the Web App using the SharePoint Central Administration with new App Pool Re-Create site collection Go into IIS settings ...
Looks like you miss the most important root level site collection. Could you please create the root level site collection on qwe web app. this site should be on "/" path. When you go to Create new site collection, Select "/" in the managed path.
Top 50 recent answers are included