Skip to main content

Posts

Sitecore Solr Error - KeeperErrorCode = Session expired for /aliases.json

 The Problem We use SOLRcloud for SOLR with Zookeeper. While performing my routine development activities, I encountered that my local SOLR instance is giving a weird error as shown in snapshot below -  The Solution We checked SOLR logs and could see error like below repeating continuously -  2024-11-10 22:31:31.216 ERROR (zkConnectionManagerCallback-7-thread-1-EventThread) [   ] o.a.s.c.LeaderElector node exists => org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /overseer_elect/leader at org.apache.zookeeper.KeeperException.create(KeeperException.java:126) org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /overseer_elect/leader at org.apache.zookeeper.KeeperException.create(KeeperException.java:126) ~[zookeeper-3.5.5.jar:3.5.5] at org.apache.zookeeper.KeeperException.create(KeeperException.java:54) ~[zookeeper-3.5.5.jar:3.5.5] at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1538) ~[z
Recent posts

Cannot find options for the 'SitecoreIdentityJwtBearer' authentication type

The Problem We needed to disable identity server in Sitecore 10.4 instance. We followed the instructions mentioned on Sitecore portal here When we activated the \App_Config\Include\Examples\Sitecore.Owin.Authentication.IdentityServer.Disabler.config.example, we got  this error:  Cannot find options for the 'SitecoreIdentityJwtBearer' authentication type. The Solution We found that we also need to set the  authentication type  as  empty  for  GraphQL , through below configuration, when you disable the  identity server  in Sitecore. <?xml version="1.0" encoding="utf-8" ?> <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:role="http://www.sitecore.net/xmlconfig/role/"> <sitecore role:require="Standalone or ContentManagement"> <authoring> <graphql> <tokenValidator> <param desc="authenticationType"> <patch:delete/>

Links DB in Sitecore not consistent

  The Problem The Links DB, found by going to Content Editor - Navigate - Links menu, in our environments was rarely up-to-date even after full site publishes and deploys. Content authors worked on an archival project and removed many links to the page item and republished those pages but the links still kept showing up under the Links menu. The Links menu was consistently found to be unreliable when it comes to identifying where a page is linked. It made it very difficult to know when a page can be archived.  The Research - The process for accessing items under the 'Links' icon.  There are two sections in Links menu - 'Items that the selected item refer to' and 'Items that refer to the selected item' Each of these operate differently. 'Items that the selected item refer to' - retrieves data from the fields of the item in the 'Items' table of the Master database using the Sitecore.Shell.Applications.ContentManager.Galleries.Links.GalleryLinksForm

XM cloud instance on Sitecore Demo portal

 Hello, Welcome to Our Sitecore XM Cloud Instance Walkthrough! Are you ready to explore the powerful capabilities of Sitecore XM Cloud? In this video, we’ll take you on an in-depth tour of the Sitecore Demo Portal, showcasing how to set up and navigate a Sitecore XM Cloud instance. Whether you’re a seasoned developer or just starting out, this walkthrough will provide valuable insights and tips to help you make the most of Sitecore’s robust features. Join us as we dive into the world of Sitecore XM Cloud and discover how it can transform your digital experience management! Happy coding! 😊

Sitecore Exception: Input string was not in a correct format.

The Problem While working on Sitecore on my local, I started getting an exception like this -    [FormatException: Input string was not in a correct format.] Here is the snapshot of the exception -  The Solution I found that I was publishing the debug and release versions of a config by mistake. They had placeholder text which needed to be replaced during transformation step in release pipelines. Since no transformation was occurring at my local instance, the config xml was broken and hence erroring out. Hope it helps you guys!