Koen Vosters

There is always a point in sharing.

Distributed Cache Service cannot be started

Today we ran into an interesting problem. The distributed cache service was no longer working. As it was a single server environment, we removed the service instance and reprovisioned it following: http://technet.microsoft.com/en-us/library/jj219613.aspx Strangely, it refused to start and went back to the services page. In the end, the following powershell fixed the distributed cache (after… Read more

AutoSPInstaller: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

During the weekend I started setting up a new dev environment on Windows Server 2012 R2. I used SQL Server 2012 and installed everything in the easy dev box setup mode (meaning all running under one account). I had the local farm is not accessible error message, even though all permissions were granted. After some reseach, I found out… Read more

Sorry, this site hasn’t been shared with you – Host Named Site Collections

So, Host Named Site Collections are the new thing. You’ve created your web application and created a host named site collection through PowerShell. You browse to the site and it renders nicely. Yet when you expect to see the site, you get the standard SharePoint screen which tells you that you don’t have access to… Read more

The Subscription Settings service and corresponding application and proxy needs to be running in order to make changes to these settings.

  This is the nice screen I got when I wanted to finalize the configuration of a blank SharePoint 2013 development environment at the customer that was already “partially prepared”. Even if I was quite sure I checked those to see if they were running. I checked again: Looking in the Manage Services Screen: Going… Read more

Failed to instantiate file "ContentQueryMain.xsl" from module "XSLStyleSheets": The specified list does not exist.

When deploying a custom branding solution to one of our customer’s environments, we ran into “Failed to instantiate file “ContentQueryMain.xsl” from module “XSLStyleSheets”: The specified list does not exist.” when we activated the publishing features on the site collection. After some investigation, it seemed that the ContentQueryMain.xsl should exist in a subfolder XSLStyleSheets within the… Read more

The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

What do you do if you are running powershell on your SharePoint farm and get the “The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.” error. You have someone who has the rights to run powershell add your user as SP Shell Admin. Add-SPShellAdmin -username DOMAIN\YourUser That’s quite the nobrainer, but what happens if… Read more

Cannot generate SSPI context

During our project we ran into the “Cannot generate SSPI context” error message. We were using a WCF service to retreive information from SQL. It took quite a while to figure out where it came from as we were not using Kerberos (which is usually the case when this error pops up, see http://support.microsoft.com/kb/811889 )…. Read more

[Quick Fix] An operations error occurred at System.DirectoryServices.AccountManagement.ADStoreCtx.FindPrincipalByIdentRefHelper

As a reference to people running code that is talking to Active Directory and are getting this cryptical message. In most cases it is a permissions issue. Make sure that your code is running under the application pool account (meaning SPSecurity.RunWithElevatedPrivileges) and that this account has the necessary rights to do so on AD…. Read more

[Quick Tip] Fixing: To enable assembly bind failure logging, set the registry value [HKLMSoftwareMicrosoftFusion!EnableLog] (DWORD) to 1.

When you are experiencing the following issue in your SharePoint 2010 environment (in my case the error was happening when certain feature receivers had to be executed): To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging. do not start going… Read more

Unexpected DLL in a WSP package

When you are building SharePoint projects based on a framework/base approach you’ll find yourself in the situation where you want to use specific modules from one of your base projects. The correct way to do that is to ensure that the required features are activated on the farm / web application / site collection / site that provision you those… Read more