Author: Josh Roark

SharePoint: About the Distributed Cache PowerShell Modules

There are two App Fabric PowerShell Modules that SharePoint (2013+) uses for all Distributed Cache commands. They are located here: C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\DistributedCacheAdministration\DistributedCacheAdministration.psm1 C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\DistributedCacheConfiguration\DistributedCacheConfiguration.psm1     — If there are problems with these modules, certain (or all) Distributed Cache PowerShell commands may fail to run with error:

SharePoint: Common NTLM Authentication Issues, aka: Consider Ditching NTLM

Update 4/1/22: Added Important note to Issues #2 and #6 Update 1/26/21: Added Issue #7 NTLM authentication is not great. It’s not the fastest. In most cases, that honor would go to Kerberos. It’s not the most secure. Again, Kerberos. It’s not all that flexible. For example, it doesn’t work well for extranets or anything cross-firewall.

SharePoint: Another Reason User Profiles are not Imported

This is kind of a “fringe” case, but since it may not be the last time it happens, here’s a post: Consider the following scenario: In SharePoint 2013+ you’re using Active Directory Import to import user profiles as trusted provider-type (SAML) profiles. You find that profiles for some users are not imported. You have already

SharePoint – Distributed Cache – Cache referred to does not exist

Problem: You may find that certain functions within the farm that rely on Distributed Cache are not working. You review the SharePoint ULS logs and find errors like the following: Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage ‘DistributedBouncerCache’ – Exception ‘Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode:SubStatus:Cache referred to does not exist. Contact administrator or use the Cache administration tool to

SharePoint: SAML and FBA authentication fail from Word, Excel, Outlook, etc

Consider the following scenario: You have a SharePoint web application that uses Trusted Provider (SAML) authentication. When trying to open a Microsoft Office (Word, Excel, PowerPoint, etc) document from a SharePoint library, the Office app pops up a dialog with a “Sorry, something went wrong” error: Outlook calendar sync behavior: Users have SharePoint calendars that

SharePoint MIM Profile Sync – Completed No Objects

Consider the following scenario: You’re using SharePoint 2016 or 2019 and using Active Directory Import to import user profiles. You decide to switch to using an external identity manager utilizing Microsoft Identity Manager (MIM). You configure MIM and run a Full Import on the SharePoint Management Agent (SPMA). The Full Import does not import anything

SharePoint: Domain Local groups from Trusted Forest are not valid

  Consider the following scenario: You have a SharePoint 20xx (doesn’t matter) site and have configured People Picker to search a trusted Active Directory Forest or Domain. You have a security group of type “domain local” in the trusted forest that has several users in it. You use People Picker to search for the group,