Skip Ribbon Commands
Skip to main content

Markus' Blog

Dec 10
Microsoft.Exchange.PswsClient.PswsException when trying to AutoApply a retention label with KQL

​If you try to AutoApply a retention label using the Office 365 Security & Compliance Center you might get an error message if you use KQL (Keyword Query Language):


This is because a KQL query for AutoApply only allows you to use certain "Queryable" Managed Properties. Some of them are listed here:

But the Managed Properties in the article listed above are not the only ones. Although you cannot use custom Manged Properties (that are queryable), you can use the predefined ones like RefinableString00 etc. Make sure that you don't use the alias name in the query. This is valid KQL but doesn't work in the AutoApply policy.

You can associate crawled properties to managed properties in the SharePoint Admin Center | More Features | Search | Manage Search Schema.

Dec 03
ESPC 2019 Prague - Slides

The slides of my presentation at ESPC 2019 in Prague about "What's new in Microsoft Search" can be found here. Thank's everyone for coming to the session!

Dec 02
SharePoint Saturday Munich 2019 – What’s new in Microsoft Search

The slides for my Session at SPS Munich about "What's new in Microsoft Search" can be found here.

Dec 03
Why you should use a really old SQL Compatibility Level for your SP2016 databases

You might know, that the support policy for SharePoint and SQL Server has always been

N, N-1, N+1

That means that for SharePoint 2016 the supported versions of SQL Server are SQL 2016 (N), SQL 2014 (N-1) and SQL 2017 (N+1) – which means a database compatibility level of 12 or higher. But when reading this knowledgebase article and Stefan Gossner's blog, it turns out, that selecting a database compatibility level of 11 (SQL Server 2012) is beneficial for the performance of the SharePoint farm. Compatibility Level 11 it is!


Apr 04
SPRequestDuration is back in SharePoint Online – kind of…

When troubleshooting SharePoint (Online) performance issues, the SPIISLatency and SPRequestDuration headers are a very important part of the puzzle. Unfortunately, Microsoft removed those headers from SPO - honi soit qui mal y pense.

Despite a few reappearances for a short time – I missed those headers every time when dealing with MS Support in SharePoint Online Performance Cases (

But now, it looks like the performance figures are back – but depending on the UI you chose, in different flavors:

Modern UI

Look for the perf-JSON-Object in the Source Code of the page:

Classic UI

Search for g_duration in the Source Code:


SPO Performance Troubleshooting just got easier again!

Mar 23
Document Libraries not listed in dropdown when creating a Flow for SharePoint

Microsoft took a big step forward when integrating Flow into SharePoint-Lists by allowing us to execute a flow on an existing SharePoint ListItem or Document.

However, if you try to create a flow on a document by executing the following steps, the dropdown only shows Lists and no Libraries:


So this dropdown is missing all the existing libraries and shows only Lists. Does this mean, that we can create a Flow on an existing ListItem only? No! There is one thing you need to do – and it's not "enter custom value" with the Library Title – this doesn't work, the Flow doesn't get bound to the Library in this case.

Solution: you need to enter the ID of the Library as custom value.


How do you find out the ID of your Document Library? Just go to "Library Settings" and you'll see the ID – without %7B and %7D:


Now you should be able to work with your Document in the Flow – and the Flow gets bound to the Library:





Jul 20
Indexing .rtf files in SharePoint 2016

Although Windows Server 2012 R2/2016 comes with an IFilter for .rtf-Files, SharePoint does not crawl/index .rtf files out of the box.

The following article lists .rtf as a crawled filename, but it also states, that .rtf is not in the Managed File Types page by default:

What happens when you add .rtf to the Managed File Type in the SharePoint Enterprise Search Service Application and Restart OSearch16? The file gets crawled, but with an error saying the file is "in a wrong format".

Resolution: you need to tell SharePoint to use the rtffilt.dll (which is the .rtf IFilter) for .rtf-Files by adding two Registry Keys:

new-item -Path "HKLM:\software\microsoft\Shared Tools\Web Server Extensions\16.0\search\setup\ContentIndexCommon\Filters\clsid\{e2403e98-663b-4df6-b234-687789db8560}"

Set-ItemProperty -Path "HKLM:\software\microsoft\Shared Tools\Web Server Extensions\16.0\search\setup\ContentIndexCommon\Filters\clsid\{e2403e98-663b-4df6-b234-687789db8560}" -Name "(default)" -type MultiString -Value "{e2403e98-663b-4df6-b234-687789db8560}"

new-item -Path "HKLM:\software\microsoft\Shared Tools\Web Server Extensions\16.0\search\setup\ContentIndexCommon\Filters\extension\.rtf"

Set-ItemProperty -Path "HKLM:\software\microsoft\Shared Tools\Web Server Extensions\16.0\search\setup\ContentIndexCommon\Filters\extension\.rtf" -Name "(default)" -type MultiString -Value "{e2403e98-663b-4df6-b234-687789db8560}"


After restarting OSearch16 (restart-service osearch16), .rtf files should be crawled and indexed in SharePoint 2016 just fine.


May 16
SharePoint Virtual Summit – a summary

Here's a short summary of today's SharePoint Virtual Summit:


Extend Lists and Libraries with SPFx

Modern Pages did not allow any customizations with JavaScript (eg. things we could do with jslink). With the new SharePoint Framework it will be possible


SPFx – included in FP2 (fall)

The SharePoint Framework will we included in Feature Pack 2 for SharePoint 2016, which is scheduled for fall 2017.


Webhooks across sites and lists

Until now, Webhooks in SharePoint Online are only available in Document libraries, now they will be extended to sites and lists.


New SharePoint Admin center

The SharePoint Admin Center gets a nice makeover (still no Managed Paths though).



PowerApps forms inside of SharePoint Lists

Finally, we can talk of PowerApps as the legal successor of InfoPath. We will be able to use PowerApps forms inside of SharePoint lists and thus provide users with a rich and customizable UI.


Approval of Documents with Flow

Document Libraries will get the ability to easily submit documents for approval with Flow.


Additional details of today's announcements can be found at

Sep 27
Yes, there will be a new major version of SharePoint

Today at Microsoft Ignite in Atlanta there were some interesting announcements during Bill Baer's and Troy Starr's session:

  • There will be a new major version of SharePoint on-premises, MS is already working on it
  • No more Service Packs: Updates are only delivered through Public Updates (PU, formerly called Uber-Cumulative-Updates), there will be no Service Pack for SharePoint 2016
  • Feature Packs will bring new functionality, the first one is scheduled for November, the second one for Q2 2017.

More Info on the new Feature Pack can be found at

Jun 16
PSConfig error: The upgraded database schema doesn't match the TargetSchema

When applying a Cumulative Update to your SharePoint 2016 Farm, you might run into troubles when executing PSConfig/PSConfigUI after installing the Binaries. The error that is logged in the Windows Event Log looks as follows:

The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID ..) threw an exception. More information is included below.

The upgraded database schema doesn't match the TargetSchema. (Correlation=..)

You can avoid this issue if you either

  • dismount all the Content Databases before executing PSConfig/PSConfigUI (which is a good idea in larger environments anyway) and upgrade them later in a second step or
  • upgrade all the Content Databases before executing PSConfig/PSConfigUI with something like Get-SPContentDatabase | Upgrade-SPContentDatabase. You could speed up this process by using multiple PowerShell Sessions or even multiple SharePoint Servers.

With detached or already upgraded Content Databases PSConfig/PSConfigUI should run successfully.

1 - 10Next
About this blog

My thoughts and findings about Azure, Office 365, SharePoint and SQL Server.


Markus Hintner