Himmat Singh Dulawat (3x Sitecore MVP)

After execution of the Rebuild index on xDB app service I observed that in SOLR Cloud, the data is not reflected in the xdb_internal collection but is being updated in the xdb_rebuild_internal collection. I have checked the Application Insight and found the following exception: In regards to the Errno 50000: Sync token is no longer valid for [Contacts] table error, Rebuilding the xDB index in Solr  should fix it but regrettably, it could not fix my issue. Indeed, when rebuilding the xDB index, the rebuild collection will be updated, and you will need to swap the cores to ensure that the newly rebuilt core is active instead of the prior one. This is mentioned in the " Confirm rebuild " part of the documentation. Therefore, I tried swapping the core mentioned in the Sitecore documentation but unfortunately, it's not working and returning me the error: "Not supported in SolrCloud". I have gone through the SOLR guide documen

Honored to Receive the Sitecore Technology MVP Award for the Third Consecutive Year!. Getting the badge of Sitecore MVP the third time in a row particularly in Technology for me is one of them. My journey for Sitecore MVP begins in the Year 2019. I commenced with Sitecore Technology blogs , and actively participated in the Sitecore Stack Exchange Platform , Sitecore Slack Channel , and SUGCON public speaking. I am honored to be named Sitecore Technology MVP 2024 . I feel fortunate to be participating with a Sitecore Community, Technology, and Product. I am happy that my all efforts and contributions are recognized by Sitecore and the Community. My next focus for this year would be: Exploring more in Sitecore composable including Personalize and CDP, Content Hub, and XM Cloud. Continuing with sharing and helping others in the Sitecore Community. Participating in Sitecore MVP mentorship program. A big thanks to my family, colleagues,

After deploying the Sitecore application on Azure PaaS, I noticed that the physical log files are absent from our PROD CM app service. I can find log files on the day of deployment, but for the subsequent days, the log files are not present on the PROD CM app service. It appears that whenever I perform a deployment, the old worker process (w3wp) retains an exclusive lock on the log file while shutting down, simultaneously, a new w3wp process is created and attempts to access the same log file. Since the file cannot be used by both processes at the same time, the logging appenders for the new w3wp may not initialize correctly, resulting in no further logging. For better visibility and clarity, I have raised the concern to Sitecore over a support ticket. Solution: The behavior I reported was registered as a bug in the Sitecore bug-tracking system. The bug specifically affects the log file appender after an application pool recycle, which happens afte

If you are using the SOLR search provider, to rebuild the request command we need to build the xDB index using the command manually from the xDB app service in Sitecore XP. You can find more details here: Invoke the rebuild request command Upon execution command, you get the following output: The index rebuild process takes time to complete and the request rebuild command does not provide any information about the progress status. However, there are certain ways you can monitor the state of an ongoing rebuild process. To Monitor the Index Rebuild Process: SOLR Interface: You can do so by running the following query by navigating to the original xDB Solr core and go to the Query tab. On the Query tab, insert the above into "q" part and click "Execute Query". Once executed, we should be able to see the result as such. In this example, the rebuild state is at 5 (Ongoing) and it is at 95%.

Recently we have added the Korean language to our multilingual Sitecore website. As we know Sitecore automatically creates dynamic fields in the SOLR schema. But while publishing we found the following issue in our logs: Solution: The error is in sitecore_web_index and it seems we are missing a dynamic field for the Korean language. To solve this issue, we need to add the dynamic field in the SOLR schema file: <dynamicField name="*_t_ko" type=" text_general" indexed="true" stored="true" /> Restart the SOLR But take care that whenever you populate the managed schema from Sitecore, it will overwrite your managed schema, and you will lose all the changes. Another approach is to customize the SOLR schema using backend code. Step 1: Create a custom class and add the following logic: Step 2: Create one more class that inherits from IPopulateHelperFactory implement the

While working on Sitecore PaaS you have a Redis issue. This time we have a Redis timeout issue but with a different message: Solution: After conducting research and using Google, I have discovered that there are 2 links from the above exception: https://stackexchange.github.io/StackExchange.Redis/Timeouts https://stackexchange.github.io/StackExchange.Redis/ThreadTheft I am experiencing the "thread theft" of the reader. The parameter "rs" in the error message tells me the state of the reader. If this is frequently reporting CompletePendingMessage , it is possible that the reader loop has been hijacked when trying to set results. It's further elaborated in the Thread Theft. To address this issue try adding the following early on in your application startup: ConnectionMultiplexer.SetFeatureFlag("preventthreadtheft", true); The issue is more related to the StackExchange.Redis commun

I was encountering frequent time-out issues with Redis and my application deployed on Azure PaaS. Following are the sample exceptions from logs: Solutions: I have reviewed config files from our CD server according to Sitecore's recommendation in this KB article here  Excessive load on ASP.NET Session State store , and checked some of the points. In the Web.config and Sitecore.Analytics.Tracking.config files, increase the pollingInterval attribute value on both Private and Shared session state provider definitions from 2 to 60 seconds. => For my case, the pollingInterval value is in the Sitecore.Analytics.Tracking.Azure.config file and the value is still 30. I have considered increasing the value further. In the Sitecore.Analytics.Tracking.config file, find the timeoutBetweenLockAttempts parameter. Increase its value from 10 to 200 milliseconds. => The value should be defined in the

If you are on Sitecore Managed Cloud and your SOLR is with Managed Cloud Server Searchstax then it is not easy to manage it. In today’s blog, I am going to discuss how to manage Managed Cloud SOLR Server, especially Restart SOLR. After successfully setting up Sitecore and SOLR instance by Sitecore, Sitecore provides you the URL of SOLR Server and the following details: Solr server connection string Solr server URL Zookeeper Ensemble API key Solr server user Solr server password To access the SOLR admin UI: Open the https://<server_name>-azure.searchstax.com/solr/ URL and enter the Username and Password. Get a List of Nodes: Before doing this exercise, you need to find the number of nodes in your SOLR server (a standard server consists of 3 nodes). For example, if your server_name provided by Sitecore is "ss123456" then ideally your nodes will be ss123456-1, ss123456-2, ss123456-3. By using the below URL, you can

In continuation of the cache tunning, if your website is multilingual then you may need to tune the isLanguageFallbackValid field cache value. The initial thought was it could be tuned using the Small Cache Size as <setting name="Caching.SmallCacheSize" set:value="200MB" />  But "Caching.SmallCacheSize" no longer controls isLanguageFallbackValid due to a Feature Request with reference number 221831.  Starting with Sitecore 9.2, the cache size now depends on setting Caching.IsFallbackValid.DefaultCacheSize To find out about how to tune cache in Sitecore,  See the blog post- Cache Tunning in Sitecore To find out more about monitoring and tuning cache on CD Server, see the blog post- Monitor and Tune Cache on CD Server Happy Sitecoreing  😊

While Installing the Sitecore 10.3 on my local machine (Windows 11), I encountered with the following error: The root cause of the issue is that a connection to the SqlServer is established without the "TrustServerCertificate" parameter. Solution: Go to the xconnect-xp0.json  in your Sitecore download setup files, open it in any editor tool, and search the following parameters: CreateShardApplicationDatabaseServerLoginInvokeSqlCmd CreateShardManagerApplicationDatabaseUserInvokeSqlCmd CreateShard0ApplicationDatabaseUserInvokeSqlCmd CreateShard1ApplicationDatabaseUserInvokeSqlCmd Add the "TrustServerCertificate": true , to all parameters. For example: Reference:  https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB1003015 Happy Sitecoreing  😊

Instead of redirecting to the "Item Not Found" page, Sitecore may generate the following error messages when it receives a request containing Illegal characters in the path: Solution: I saw a similar issue and it could depend on the "requestPathInvalidCharacters" settings in <httpRuntime> in Web.config . Go to the web.config and search for httpRuntime node. Check if the requestValidationMode is there, if it is not then add the attribute requestValidationMode="2.0"   Make sure validateRequest attribute in the page node is set to false. <pages validateRequest="false"> If you want to add these characters to the path, add the requestPathInvalidCharacters attribute to the httpRuntime node. <httpRuntime targetFramework="4.8" ...... requestPathInvalidCharacters="&lt;,&gt;,*,%,&amp;,:,\,?"/> Reference: