Quick-fix Orphan Site Blocks Patch

Quick-fix Orphan Site Blocks Patch


After applying Cummulative Updates to SharePoint, it can happen that you are facing an issue with orphan sites in one or more content dbs.

As these are flagged as errors, the configuration wizzard that needs to be run after the bits have been applied to all servers, cannot complete the job and will fail.


06/29/2016 07:17:54.93 OWSTIMER (0x4D38) 0x4F84 SharePoint Foundation Upgrade SPContentDatabaseSequence ajxkz ERROR Database [SP_DVT_INSIGHT_ContentInsightDB_01] contains a site (Id = [54916e1a-54f3-43d0-ae74-d2915ab4e55f], Url = [/Workspaces/WS_002250]) that is not found in the site map. Consider detach and reattach the database. 39cc8a9d-a8ae-a04a-f205-a18cb49efb20


The solution is to detach the content db where the orphan site has been detected and then mont the database back in. After the database is back in its place, you can locate the orphan site and delete it. (If you are curious, you should be able to browse to that orphan site, just to double check there is no critical content in it).

high level steps

  • Detach mentioned content db
  • Mount mentioned content db back in
  • Delete orphan site
  • Restart configuration wizzard


Get-SPContentDatabase [DB] | Dismount-SPContentDatabase
Mount-SPContentDatabase [DB] -DatabaseServer “SP-SQL-FARM” -WebApplication [DEFAULT ZONE URL OF THE WEB APP]



Fresh Search Results with SharePoint

Fresh Search Results with SharePoint

How fresh do you want your search results?

Introduced with SharePoint 2013 we have got a new feature for Search in order to support better content freshness. Its called continious crawling. The name suggests SharePoint is crawling and processing content continiously. The truth is – by default – it is a type of incremental crawling in 15 minutes intervalls with a few extras.

Once we know something, we find it hard to imagine what it was like not to know it.

Chip & Dan Heath, Authors of Made to Stick, Switch

Continious crawling

…is a type of crawl with the purpose to maintain the index as current as possible by fixing the shortcommings the incremental crawling has.

Incremental crawling

…is sort a of crawling where existing content in the index is being crawled again – e.g. picking up changes.

Full crawling

…kicks off content discovery of the entire content source.


30 Minutes

15 Minutes

Every Sunday

Use continious crawling for SharePoint content – it is not availible for indexing external content e.g. BCS, File Share and Websites. With continious crawling enabled you will benifit from parallel indexing of content.

Imagine some major changes are happening on the content and the crawling needs more time than usual to process them. With continious crawling the next crawl wont wait for complition – he will kick off as scheduled and will process the latest changes – crawling is running in paralel.


Simon is a project manager and is introducing a lot of changes to large documents in a short time. During the changes the SharePoint crawling is kicking in and while this happens, Anita, who is working in finance is uploading her calculation and expects it to be aggregated and displayed in the finance portal by search driven webparts.

Without continious crawling

Anita has to wait for the current crawling to be finished, so that the next crawling can start and processing her calculation sheet. On some environments even incremental crawls can take up to 60 minutes. So in worst case Anita has to wait [60 Minutes + Time for the current crawl]. This behaviour will irritate the users – depending on how heavily the portal relys on search – it will likely cause some headaces to the management as users will complain if your portal is completely search driven.

With continious crawling

While a crawl is running to process the “deep” change, another crawl kicks in after 15 Minutes in parallel and is eventually processing Anitas excel sheet. Even if one crawling needs longer due to processing of “deep” changes, another crawl will begin its work as per schedule, without being bothered by any other crawls.

Use continious crawling on all SharePoint content sources and if your farm has the power .e.g. is fast responding to user requests during crawls and you want users to have super fresh search results – change the continious crawling schedule. It is 15 Minutes per default.


$IntervalMinutes = 10;
Write-Host "Changing Continuous Crawl Interval to $($IntervalMinutes) minutes"
$ssa = Get-SPEnterpriseSearchServiceApplication
$interval = (Get-SPEnterpriseSearchServiceApplication).GetProperty("ContinuousCrawlInterval") 
Write-Host "New continuous crawl interval set to $interval"
Changing continuous crawl interval

Zweiter Platz und ein Intra.NET Award für uns

Zweiter Platz und ein Intra.NET Award für uns

Zweiter Platz für das neue Intranet der PwC

Intra.NET RELOADED Berlin 2016

April 27 – 28, 2017

Park Inn Hotel Berlin | KOSMOS Cinema Berlin, Germany

Die nicht selten gewordenen 18 Stunden Tage in diesem Projekt haben sich “ausgezahlt”. Es macht wirklich spass mit einem so starken Team zusammen arbeiten zu dürfen.


Ganz knapp am ersten Platz - Royal DSM - vorbei

Royal DSM räumte mit 40% der Stimmen den ersten Platz ab.

Wir sind ganz knapp mit 38% der Stimmen vorbei geschrammt – aber mit viel Abstand nach hinten zu Swisscom mit 22%.

Der zweite Platz bei den Intra.NET Awards in Berlin in der Kategorie “Innovative Technology Integration” ist jetzt unser 🙂


Royal DSM





Ich glaube wir sind deshalb so erfolgreich mit unserem Intranet, weil wir nicht versuchen das Rad neu zu erfinden.

Wir setzen auf Match Point Snow von der Colygon AG und bauen mit ihnen und einem Partner Unternehmen, der Elca ein Digital Workplace für die PwC Schweiz auf.

Das bedeutet, dass wir künftig alle Informationsflüsse und Kollaborativen Prozesse auf eine neue Ebene heben.

Client Collaboration

Kunden und andere Firmen in unserem Netzwerk gelangen mittels Zwei Wege Authentifizierung auf das Client Portal, welches nahtlos innerhalb der Insight integriert ist.


Wissens Management

Mit der Integration von Starmind als das Digital Brain werden Know How Träger mit den Fragenden vernetzt.

Ganz egal wo man sich im Intranet aufhält, man kann jederzeit eine Frage absetzen und man erhält automatisch via Push Integration eine Meldung im Portal, sobald jemand geantwortet hat.


Alles setzt auf Starmind, MatchPoint Snow und SharePoint 2013 auf. Wir schauen aber schon neugierig auf SharePoint 2016

Microsoft SharePoint Server 2013 Service Pack 1

Microsoft SharePoint Server 2013 Service Pack 1

Good news for everyone planning to build a farm with  Windows Server 2012 R2.

The Server Pack 1 for SharePoint Server 2013 has just been released and is now supporting  Windows Server 2012 R2 !!!

Download the Server Pack

List of adressed issues. (Excel)



  • Added support for  Windows Server 2012 R2
  • Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and security.
  • All the monthly security updates that were released through January 2014, and all the Cumulative Updates that were released through December 2013.



%d bloggers like this: