Himmat Singh Dulawat (3x Sitecore MVP)

After Login on Sitecore CMS does not redirect to Content Editor and throws error 500 - The request timed out. The web server failed to respond within the specified time error. I have deployed our Application on PROD CM and CD instance on the Azure PAAS and the instance is working fine. When I try to log in to the CM instance, I can log in, but instead of redirecting me to the Sitecore Content Editor it's throwing me an error 500 - The request timed out. The web server failed to respond within the specified time. After logging into the CM site, the following error is displayed: 500 - The request timed out. The web server failed to respond within the specified time After login into the CM instance: I have verified the AllowedCorsOrigins and Redirect URL in the identity server and CM instance in both Sitecore.IdentityServer.Host.xml and Sitecore.Owin.Authentication.IdentityServer.config respective files and all are correct. The same code and depl...

While rebuilding the index on your Sitecore CMS you may face scenarios where indexing data not populating in website search functionality, search stopped working, or slowdown. After completion of indexing again search functionality returns the results. Here Sitecore introduces the very nice concept of SwitchOnRebuild. To understand it assume you have two cores for your Sitecore index active and passive. It means when you rebuild the Active index Sitecore will return the result using the Passive index and after rebuilding Sitecore will switch the Active index to serve the results. It’s a concept of switching of Sitecore index during the rebuild of the particular index to avoid downtime and search unavailability. Recently when I was working on one migration project, when I deployed an application on the Azure Paas environment. I faced a similar type of issue while rebuilding the index it was throwing me the below error: Job started: Index_Update_IndexNa...