New answers tagged

1

First you test your database by running Test-SPContentDatabase -name WSS_Content_DB -webapplication http://sitename If you get errors, solve them. When you have no errors, continue with Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename This example mounts an existing database to the sitename web ...


0

If the users have sufficient permissions you can use webinfos. But sometimes users do not have access to some of the subsites. Then SharePoint pops up the login prompt and the call does not work (401 error). In this case you have to use /_api/web/Webs and set effectivebasepermissions in the query string. I have written a relevant post here ...


1

You are in the right path. Use the search REST API. The below code from this post should get you started. <button id='btnGetSites'>Get Sites</button> <div id='list'> </div> <script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js" type="text/javascript"></script> <script ...


1

Ultimately it comes down to the amounts of data that your architecture can handle. If you go with 1 site collection and put all the data (400GB) there, then it will all go to one content database (because site collection can have only one database). Microsoft recommends not exceeding 200 GB for an actively used content database. So this is a clear case where ...


0

I had the same symptoms on a SharePoint 2013 On Premise SP1 and October 2015 CU problem was I ensured the user using the windows login name: domain\username e.g: var user = clientContext.Web.EnsureUser("dev\administrator"); with this user, IsSiteAdmin returned False (he was definitely directly added to site collection admins) also with this user I did ...


1

Content Types work in that way and propagating changes is a good way to apply changes to all inheriting objects (List/Libraries). You should not afraid because it requires higher privileges to do so, so only responsible person would be doing that. You should wisely set up permission that will ensure only responsible persons can make necessary changes. ...


1

I've just worked through your scenario in SharePoint online. Did 1. through to 4. Description is hidden in my custom Issue list form. Then I edited the native Issue CT and made the Description field required. clicked "Yes" to update all content types inheriting from this type opened a new issue in my custom Issue list The previously hidden Description ...


0

there are couple of reason for this issue. We have received a report that a customer has a modern group from Outlook Web App which has the same name as a deleted site collection, when recreating a site collection with the same URL, the issue happens and this site collection doesn't exist in Recycle Bin. Based on this situation, we suggest you first check ...


1

Did you try deleting it from the first and second stage recycle bin ? Try appending ?View=2 at the end of your recycle bin URL to go to second stage recycle bin. URl should look like, https:///_layouts/15/AdminRecycleBin.aspx?View=2


1

You have to create the Content Database 1st then you will be able to create new site collection. New-SPContentDatabase -Name "database name" -DatabaseServer "database server name" -WebApplication "web app url" $dbname = Get-SPContentDatabase "databasename" New-SPSite -URL $site -OwnerAlias $owner1 -SecondaryOwnerAlias $owner2 -ContentDatabase $dbname ...


3

You can use: New-SPSite -Url $url –ContentDatabase $ContentDatabase -Name $WebsiteName –Description $WebsiteDesc -Template $Template -OwnerAlias $PrimaryLogin –OwnerEmail $PrimaryEmail see: https://social.technet.microsoft.com/forums/sharepoint/en-US/89c90032-5be1-4fe6-8546-0114eaf018ca/site-collection-in-a-particular-content-database


2

if you have both web application properly configured. Make sure both DNS are properly registered. Create Web Applications on http://one port 80 and http://secondwebapp port 80. once 1st web app created it will ask to create the root level site collection. I think, this is where you created 1st root level. Now once 2nd web app created same message will ...


1

Unfortunately, there is not a simple method available in SharePoint Online to copy an entire site collection in SharePoint online. The only method available in SharePoint Online is to do a manual copy/backup for each site under the site collection using the Save Site as Template including its content feature (Include Content). read the response from the ...


1

there are couple of Methods to remove the orphan site. Method 1 : $site = Get-SPSite http://siteurl $siteId = $site.Id $siteDatabase = $site.ContentDatabase $siteDatabase.ForceDeleteSite($siteId, $false, $false) Method 2, try to use stsadm. Try to use Old Fashioned Stsadm command. stsadm -o deletesite -force -siteid e2a114b8-80c9-41f6-87bf-3feddf2ad9b6 ...


3

things are as simple as you mentioned in your question. Here are the steps. You have to perform the SQL backup of the Content Database from Source Farm Move the back file to destination server(sql) Restore the Database on destination SQL Server now you have two options over here if you overwrite the destination dB while restoring, then no need to attach ...



Top 50 recent answers are included