I am trying to create a new site (
SPSite), in a SharePoint 2016 portal environment, using the following code:
SPWebApplication webApplication = SPWebApplication.Lookup(new System.Uri("http://portal.companyname.com")); SPSite newSiteCollection = webApplication.Sites.Add("/products", "Product Portfolio", "", 1033, "STS#0", "DOMAINNAME\SiteAdmin", "Site Admin", "email@example.com"); newSiteCollection.Dispose();
I developed a SharePoint solution that entails a custom master page and CSS to customize the branding of all websites created in the portal. Rather than enabling that feature in the site provisioning code above, I stapled that feature globally to the web application, so all new sites have the feature automatically activated. Somehow, the code fails to create the site and the following exception is thrown.
Exception message: The web being updated was changed by an external process. Exception stack trace: at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) at Microsoft.SharePoint.Library.SPRequest.ApplyWebTemplate(String bstrUrl, String bstrWebTemplateContent, Int32 fWebTemplateContentFromSubweb, Int32 fDeleteGlobalListsWithWebTemplateContent, Int32 fIgnoreMissingFeatures, String& bstrWebTemplate, Int32& plWebTemplateId) at Microsoft.SharePoint.SPWeb.ProvisionWebTemplate(SPWebTemplate webTemplate, String webTemplateToUse, SPFeatureWebTemplate featureWebTemplate, Page page, SPFeatureDependencyErrorBehavior featureDependencyErrorBehavior, ICollection`1& featureDependencyErrors) at Microsoft.SharePoint.SPWeb.ApplyWebTemplate(SPWebTemplate webTemplate, Page page, SPFeatureDependencyErrorBehavior featureDependencyErrorBehavior, ICollection`1& featureDependencyErrors) at Microsoft.SharePoint.Administration.SPSiteCollection.AddInternal(SPSiteCollectionAddParameters param) at Microsoft.SharePoint.Administration.SPSiteCollection.Add(SPSiteCollectionAddParameters param)
If I deactivate the feature stapler, then the code works just fine and the site collection is created.
What really surprised me is that if the feature stapler is activated and I create the same site via PowerShell (see below), the site collection is provisioned and the branding is applied (as expected).
$ template = Get-SPWebTemplate "STS#0" New-SPSite -Url "http://portal.companyname.com/products" -OwnerAlias "DOMAINNAME\siteadmin" -Template $ template
Obviously, the C# code and inner-workings of the
New-SPSite command are not equivalent. Is there anything I can do to work around this problem? Is it a SharePoint bug?
✓ Extra quality
ExtraProxies brings the best proxy quality for you with our private and reliable proxies
✓ Extra anonymity
Top level of anonymity and 100% safe proxies – this is what you get with every proxy package
✓ Extra speed
1,ooo mb/s proxy servers speed – we are way better than others – just enjoy our proxies!
USA proxy location
We offer premium quality USA private proxies – the most essential proxies you can ever want from USA
Our proxies have TOP level of anonymity + Elite quality, so you are always safe and secure with your proxies
Use your proxies as much as you want – we have no limits for data transfer and bandwidth, unlimited usage!
Superb fast proxy servers with 1,000 mb/s speed – sit back and enjoy your lightning fast private proxies!
99,9% servers uptime
Alive and working proxies all the time – we are taking care of our servers so you can use them without any problems
No usage restrictions
You have freedom to use your proxies with every software, browser or website you want without restrictions
Perfect for SEO
We are 100% friendly with all SEO tasks as well as internet marketing – feel the power with our proxies
Buy more proxies and get better price – we offer various proxy packages with great deals and discounts
We are working 24/7 to bring the best proxy experience for you – we are glad to help and assist you!