Application Error When Access /_admin/createsite.aspx
in the process of upgrading from SharePoint 2010 to SharePoint 2013. One of the problems we faced were the fact that we had some orphaned content databases in our production environments, but the problem didn’t surface in SharePoint 2010 but was given light in 2013. So this short post is talking about how I fixed those issues, which was a bit of a pain to be honest. In the environments we’re working, we’ve set up a scheduled upgrade that takes place once every week on a schedule. The reason for this is to re-iterate the upgrade process as many times we can, with production data, before the actual upgrade which will take place later down the road when all bugs, code tweaks/customizations and other random problems have been taken care of. One of the problems that surfaced recently was that we couldn’t create any new Site Collections, where the ULS spit out the unfortunate message: Application error when access /_admin/createsite.aspx, Error=Object reference not set to an instance of an object. at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.FindBestContentDatabaseForSiteCreation(IEnumerable`1 contentDatabases, Guid siteIdToAvoid, Guid webIdToAvoid, SPContentDatabase database, SPContentDatabase databaseTheSiteWillBeDeletedFrom) While it took some time to boil down the nuts of what was going on, here’s the details in case you end up with the same issues. Cannot create new Site Collections So the problem we faced of not being able to create new Site Collections surfaced itself in the ULS logs, stating this message: Application error when access /admin/createsite.aspx, Error=Object reference not set to an instance of an object. at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.FindBestContentDatabaseForSiteCreation(IEnumerable`1 contentDatabases, Guid siteIdToAvoid, Guid webIdToAvoid, SPContentDatabase database, SPContentDatabase databaseTheSiteWillBeDeletedFrom) at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.FindBestContentDatabaseFo
March CU and SQL 2012 SP1 w/PowerPivot and SSRS for sharepoint installed. I have a problem with creating the root or any site collection on the server using the Business Intelligence Center site template in Central Administration. I am able to create site collection using the BICENTERSITE template in PowerShell https://zimmergren.net/findbestcontentdatabaseforsitecreation-problem-after-upgrading-to-sharepoint-2013-solution/ New-SPSite script no problem. I found in the ULS logs this error when trying to create the site in Central Admin: SharePoint Foundation General 85m6 Medium Applying web template 'BICenterSite#0' on web url 'https://vmscatspbi20/sites/testing' SharePoint Foundation General 85m7 Medium Actual http://www.networksteve.com/enterprise/topic.php/Error_in_SharePoint_2013_creating_site_collections_using_Busines/?TopicId=66730&Posts=0 web template to apply to Url 'https://vmscatspbi20/sites/testing' is 'BICenterSite#0' SharePoint Foundation Monitoring nasq Verbose Entering monitored scope (Applying Named Web Template: BICenterSite#0). Parent Request (POST:http://vmscatspbi20:4678/_admin/createsite.aspx) SharePoint Foundation General 72h7 Medium Applying template "BICenterSite#0" to web at URL "https://vmscatspbi20/sites/testing". SharePoint Foundation General 8E+25 Medium Failed to look up string with key "EXCELSERVICESSAMPLE_XLWEBPART_DESC", keyfile ppsma. SharePoint Foundation General 8l3c Medium Localized resource for token 'EXCELSERVICESSAMPLE_XLWEBPART_DESC' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\SiteTemplates\BICENTERSITE\xml\onet.xml". SharePoint Foundation General 6y13 Verbose VdirIter::globToRE: "^doctemp.*\.xml$" SharePoint Foundation Fields 88xy Verbose Failed to find
. Recently we have seen hell lots of issues in our farm .While troubleshooting those issues I learnt the below points regarding SharePoint search which I feel like to share . SharePoint Search is comprised http://sharepoint693.blogspot.com/2014_02_01_archive.html of three main functional process components: Crawling (Gathering): Collecting content to be processed https://sp2013dev.wordpress.com/page/14/ Indexing: Organizing the processed content into a structured/searchable index Query Processing: Retrieving a relevant result set relative to a given user query How Search Works : A server running a SharePoint Search Crawl Component (e.g. a "Crawl Server") performs the act of crawling by making web requests such as HTTP GET to the applicable application error web front ends (WFEs) hosting the hosting the content. More simplistically, the Crawler makes requests for content and the WFE responds with the requested documents/pages/data. After the content has been gathered by the Crawler, it then gets filtered and processed into the final end product as an index. Regardless of SharePoint Search or FAST Search for SharePoint 2010, the component responsible for crawling (aka "gathering") content-to-be-indexed is the application error when SharePoint Crawl Component. By default, the SharePoint Server 2010 crawler crawls all available Web front-end computers in a SharePoint farm through the network load balancer in that farm. Therefore, when a crawl is occurring, the crawler can cause increased network traffic, increased usage of hard disk and processor resources on Web front-end computers, and increased usage of resources on database servers. Putting this additional load on all Web front-end computers at the same time can decrease performance across the SharePoint farm. This decrease in performance occurs only on the SharePoint farm that is serving user requests, and not on the SharePoint search farm. This decreased performance can cause delayed response times on the Web front-end computers and delayed response times for the overall farm. The decreased performance might not be diagnosed by specific logs, resource counters, or standard monitoring. You can reduce the effect of crawling on SharePoint performance by doing the following: Redirect all crawl traffic to a single SharePoint Web front-end computer in a small environment or a specific group of computers in a large environment. This prevents the crawler from using the same resources that are being used to render and serve Web pages and content
Claims in SharePoint2013 This post is a contribution from Adam Burns, an engineer with the SharePoint Developer Support team.This post repackages examples that are already out there on MSDN, but brings two examples together and provides some implementation details that may not be obvious in the existing articles. I also tried to leave out confusing details that didn’t bear directly on the subject of using custom claims to do Pre-Trimming of search results. In general you should look at the included sample code after reading the description of the different parts and that should be enough to understand the concepts.We will review basic concept of a custom Indexing Connector because we will have to implement a connector in order to demonstrate the capabilities of the new Security Trimmer Framework.We’ll cover how a connector can provide Claims to the Indexer and how the Security Trimmer can use those Claims to provide a very flexibly way to trim and customize search results.We’ll quickly cover the different between a pre- and post- trimmer but we’ll only implement the pre-trimmer. The sample code includes two projects, the Custom Indexing Connector (XmlFileConnector) which sends claims to BCS, and the SearchPreTrimmer project which actually implements the trimming. In addition you’ll find:Products.xml - a sample external data file for crawling.Xmldoc.reg - to set the proper registry value so that the custom protocol is handled by the connector.Datafile.txt – a sample membership data file. This is where the claims for each user are specified. We’ll use the XmlFileConnector. One of the good things about this kind of connector is that you can use it for a database. For instance it can be a product catalog, a navigation source, etc.To install the connector do the belo