Sitecore Pantar

  An approach to upgrade Sitecore from 8.x or 9.x to 10.x   Introduction   If your current Sitecore website is running on 8.x or 9.x version and you are looking to upgrade this to Sitecore 10.x version, then this a good place to start.   In this blog, I’ll try to explain the various details that needs to be considered while upgrading your Sitecore solution to 10.x version. These are aspects that are generally not covered in a “How-To” Guide which only explains the process of upgrading Vanilla Sitecore. This is an attempt to provide a 360 view on the Sitecore upgrade which will help you in carefully executing a complex upgrade program. High Level Approach The overall upgrade process can be sub divided in to three different stages ·          Assess & Prepare o    Identify the pre-requisites – This may include Microsoft Visual C++ 2015 Redistributable, Files and scripts for upgrading   that can...

  Common Issues and solutions: Sitecore Issues a.        Indexes not building in CD server. Root Cause: Config has Instance name explicitly mentioned. This instance will certainly not match to Instance name in Azure App Service as the instance name are dynamically created. This was found by inspecting EventQueue Table in Core Database The instance name is mentioned in this config on CD server. App_Config\Include\<SomeFolder>\SwitchMasterToWeb.config The solution is to Empty the Instance Name so that it takes the default Azure App Service resolved Name. Now on re-indexing you can see dynamic Instance Name b.       Rebuild index failure due to high CPU usage on AppService High CPU usage (above 70-80%) was observed when trying to rebuild index for core database. So as and when the CPU reached high usage the Sitecore instance itself getting shutdown and failing the index rebuild process. As t...

  Automated Maintenance Heath status check and Auto heal Health Status In order automatically monitor the application’s health status, Health check feature was enabled. Using this feature there will be a ping to the specified health check path on all instances of the webapp every 2 minutes. If any web app instance does not respond within 10 minutes (5 pings), the instance is determined to be  unhealthy  and instance of the webapp will be taken out of the load balancer. The health probe will continue on the instance even though it is out of load balancer. Once the health probe receives a valid response, the instance will be added back into load balancer. Steps to enable the feature, 1.        Open the Resource explorer from the App Service blade in the portal under Development Tools. 2.        The resource explorer will open to the top-level view of your App Service. Expand the config section and c...