SharePoint 2013 – the awesome, if already slightly legacy portal solution by Microsoft. These posts handle the on-premises installations and their issues.
This article applies to a lot of different issues you might be having with your SharePoint-powered site, or even custom functionality like mobile apps using SharePoint’s search index. I’ll list a few of the situations, which could be caused by these issues, below: You’re using Search to show a list of User Profiles with their properties, but it’s showing outdated or missing information Your intranet has the classic “Upcoming Birthdays” -webpart (only weather and lunch lists are more classic than that!) This webpart is not…Continue reading Issues with User Profile Property visibility in Search-powered functionalities
Every now and then, an API or a method call comes along, that you need to be very careful with. “Microsoft.SharePoint.Client.Web.AddSupportedUILanguage()” seems to be one of them. In this post, I’ll try and document my findings and workarounds for said method! Issues and solutions Posts Related to “Problematic behavior of web.AddSupportedUILanguage(int lcid) in SharePoint 2013 and 2016”:SharePoint Localization – a (somewhat) comprehensive how-to!How to resolve Webpart title changes not reflected to some users?5 ways to enable Custom Scripts for a SharePoint site collection
This article explains how to enable custom scripting for any SharePoint site collection. This is functionally equivalent with setting setting “-DenyAddAndCustomizePages 0” or disabling the NoScript feature. Different instructions and solutions apply to SharePoint Online, and on-premises scenarios (SharePoint Server 2013, 2016 and probably 2019) – so see below for all of them. Different solutions are required to resolve the issue for different target sites: Modern SharePoint Team Sites (attached to Office Groups if on SharePoint Online, and without one if On-Premises) Modern SharePoint Communication…Continue reading 5 ways to enable Custom Scripts for a SharePoint site collection
Twitter embed has a stupid, built-in failure condition: if the User Agent contains IE10 or older, the embed script will not load. This causes SharePoint embeds to fail. This post describes how to fix that.
Can’t access a web part page because of a broken web part? Yeah, that’s a classic issue – and it’s nicely ported into Modern world, too! In these cases, web part page maintenance mode comes in handy! There’s a query parameter available for accessing it. For whatever reasons, it’s different for Classic and Modern mode, though. Why make things easy if you can make them difficult, right? :) Posts Related to “Opening a web part page in maintenance mode”:SharePoint Home, Hub, Sites, Start… What?SharePoint Localization…Continue reading Opening a web part page in maintenance mode
Debugging SharePoint On-Premises configuration issues is the best thing since sliced bread, right? This post is about allowing/enabling Anonymous Access to a site collection – a simple configuration, that “simply works” like once every ten times you try it.
A quick heads-up – if you remove the root site (or RootWeb, like it’s called in the code) of your classic SharePoint Site Collection, that’s going to cause you some grey hairs. It might even, in some rare cases, be unrecoverable! The following post describes what kind of issues you might run into, if you remove the root web instead of the whole site collection, and how to remove the site collection instead. Update 13.7.2019:SharePoint Online keeps evolving, and at least on some tenants, removing…Continue reading Don’t remove the root web of your classic SharePoint Site Collection!
If you’re working on SharePoint deployments, and aren’t familiar with SharePoint Search Query Tool, you’re probably doing something wrong. Or you’ve gotten a really troublefree tenant and simple requirements.. :) At least for technical issues, it’s the #1 tool for debugging what’s in the index and what isn’t. This blog post describes how to use it to investigate SharePoint Online Search index issues. This blog post is about using SharePoint Search Query Tool to investigate search index issues in SharePoint Online. First of all, you…Continue reading Using SharePoint Search Query Tool
In this post I instruct a simple way to stop SharePoint (either on-premises installation or SharePoint Online) from redirecting to Delve or MySites (respectively). The normal behavior is, that this happens when users click any name of a user anywhere in SharePoint. This is often not desired, and sometimes just confusing or impractical. Problem If your customers are like mine, a lot of them hate Delve or MySite or both. Or maybe they just are’nt willing to yet adopt Delve. Or perhaps you’ve heard of…Continue reading Disabling Delve/MySite redirection from SharePoint Site Collections
Luckily, SharePoint Add-ins (or App Parts, like they were called earlier) are slowly getting killed and rooted out of all the sites they once were deployed to – and I don’t think anyone’s going to miss them. However, as so often happens with legacy implementations, there will still be thousands of sites, where SharePoint administrators and developers will be responsible for maintaining and developing the solutions further. This will occasionally require updating app parts, which is a process that kind of sucks. Here I’ll try to simplify…Continue reading Updating files in an App Part (SharePoint Add-in)
This post contains a really small, but nifty tweak to search box in SharePoint list views. Applies to 2013, and Office 365 (for now). Pretty basic stuff, but had to figure this out for a customer so can just as well document it here :) Okay – so a customer needed to be able to filter view items in a SharePoint list by values in a keyword-field (managed metadata, with values added by editor users), and wanted to use the SharePoint’s searchbox. The problem was,…Continue reading Tweaking the SharePoint list view search box to filter on managed metadata fields
This blog post describes how set the SharePoint’s ULS level to “Extra Verbose” (VerboseEx) using PowerShell. This is not possible using the browser UI, so some POSH magic is required! Luckily, it’s quite straightforward, but to avoid filling your hard drive(s) with huge log files, you should reset the level when you’re done debugging! Description of the solution By default, ULS logging is somewhat non-detailed. This means that a lot of data that could be used to debug issues is omitted. The UI cannot be…Continue reading Using PowerShell to set ULS logging level to “extra verbose” to catch all the events in the logs
This post is about managing Anonymous Access on a SharePoint site (SPWeb) using PowerShell commandlets. It’s often a lot more feasible and even easier than using the browser interface! In some cases, it’s borderline impossible to avoid it anyway – since accessing the GUI switch might not be possible. Description Assume you have a site collection that you have published to the whole world. You’ll have anonymous access enabled at both web application and site collection levels, and configured permissions at the root web -level.…Continue reading Using PowerShell to modify anonymous access permissions on SharePoint On-Premises
Have you ever run into this, a very non-descriptive and weird SharePoint error message “Cannot uninstall the LanguagePack 0 because it is not deployed”? You could encounter it while running some PowerShell scripts – most typically when trying to update a wsp solution. I have, and luckily often easily solved! Symptoms Assume you’re trying to install, update or uninstall a SharePoint solution (.wsp package) using PowerShell-commands Install-SPSolution, Update-SPSolution, or Uninstall-SPSolution (respectively). The operation fails with the following (or similar) error: Error: Cannot uninstall the LanguagePack 0…Continue reading Powershell Error: Cannot uninstall the LanguagePack 0 because it is not deployed.
This post describes how to resolve a kind of cryptic and oddly misdescriptive error message about Parser Error on your ASP.NET application or (an On-Premises) SharePoint site. I ran into this after deploying wsp-packages to a SharePoint farm, but you can apparently get this on ASP.NET MVC sites, too. The error doesn’t actually tell you what’s wrong, so figuring it out took a while. Hopefully it’ll help you, though! Symptoms: Parser Error from a random-looking location Once you navigate to your web- or SharePoint site, you only…Continue reading “Server Error in ‘/’ Application” or “Parser Error” – it’s actually a malformed web.config killing your ASP.NET-application or SharePoint
Sometimes – pretty often in the good old on-premises world, actually – you’ll need to have a copy of all the packages that are deployed to a certain farm. So – how to download all of the deployed farm solutions (essentially, cabinet files renamed to .wsp) from a farm? Luckily, it’s quite easy! Solution To download all deployed farm solutions (wsp-packages) from a SharePoint farm is pretty simple using PowerShell. No need to download individual packages through cumbersome interfaces! You don’t even have to open…Continue reading Quickest way to download all the wsp-packages in a SharePoint farm
SharePoint Server versions 2013, 2016, and 2019 don’t have that old and familiar “sign in as a different user” option in the site menu, and for the time being, nor does SharePoint Online. However, sometimes it’s very useful functionality to have, so it’s a bit weird Microsoft chose to get rid of the option. This post outlines a method that I’ve found to work quite well for making SharePoint ask for credentials so that you can use another account to then log in! Really nice…Continue reading How to log in to SharePoint as a different user
In this post, I describe how you can figure out if IE11 (Internet Explorer 11) has jumped in the compatibility mode. You run into this requirement every now and then, when trying to figure out some SharePoint browser compatibility mess-up. This is quite frequent, because in compatibility mode IE does its best to screw up your CSS. Compatibility view now and before Microsoft has been pretty keen on introducing new ways to handle browser compatibility and make IE behave in even stranger ways that it…Continue reading Identifying IE11 compatibility mode in SharePoint
This post describes the (probably) easiest and most straightforward way of creating a new Thread in your SharePoint (or any other .NET) server-side/desktop code. Solution Let’s face it – one should not create new Threads lightly when developing SharePoint solutions, but sometimes it’s difficult to avoid. Or sometimes it’s just the simplest way to get around weird framework limitations. Posts Related to “The simplest way to create a thread on SharePoint”:Using Dispatcher to update values in GUI elements from a background threadProgrammatically creating readable internal…Continue reading The simplest way to create a thread on SharePoint