Another day, another issue – this time with an on-premises environment with a ridiculously complicated architecture and an absolute ton of pipelines. There are plenty of ways to fix this particular issue (because there are plenty of reasons), and after ferocious googling (and a very brief binging just to see if Microsoft had found something Google hadn’t), the trail ran cold and I felt like nobody had run into the same issue before. This is probably not true – just that the documentation wasn’t there.…Continue reading How to fix a 403.18 in a virtual application?
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
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.
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
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.
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
This post is about a small programmatic workaround to creating new SPFields for SPLists in SharePoint with human-readable internal names. This is mainly a usability improvement for your editors (and doesn’t change your life that much), but at the very least they will probably appreciate it! In short, I’ll show you how to avoid SharePoint’s dirty encoding (like replacing a space with “_x0020_”). This appliesto when you’re using server-side code to generate fields. Problem: non-readable internal names for SharePoint list fields When you create a…Continue reading Programmatically creating readable internal names for new SharePoint fields
This post describes how to fix Windows Authentication on a SharePoint server that is failing on other local addresses other than localhost. Symptoms You get the standard Windows/Basic Authentication prompt when accessing your SharePoint site, but the site won’t accept your credentials when you are accessing the site using an address like http://website. However, using an address like http://localhost works fine (but of course may cause other problems). You also get event log entries like this (most likely in System -category): The program w3wp.exe, with the…Continue reading Windows Authentication fails on SharePoint for all hostnames (other than localhost)