Himmat Singh Dulawat (4x Sitecore MVP)

You are all aware of the installation of Sitecore Connect for Content Hub on the premise environment. In this blog post, I am going to describe how to install Sitecore Connect for Content Hub in Sitecore Azure Cloud Service PaaS 2.0 environment. In PaaS1.0, you can install it using by Sitecore Azure Toolkit and SXP ARM templates, but in PaaS2.0, you cannot directly access the App Service as it provides an extra security layer using Bastian. Azure Bastion is a fully managed service that is provisioned in the PaaS 2.0 Hub environment to securely connect virtual machines via a private IP address. You can find more information here:  Azure Bastion for PaaS 2.0   What is Azure Bastion? Step 1: Log in to the Sitecore Content Hub and collect the following details: Need to create an OAuth Client ID and secret. (click Manage > OAuth Clients >) Need to create an Action to get the Hub in and Hub out value.  (click M...

Problem Statement: I was following the article Download options for Azure AppService deployments to install Sitecore PowerShell and SXA modules on Sitecore Managed Cloud Service PaaS 2.0 instead of my local dev instance. Sitecore Version: Sitecore 10.4 XP Managed Cloud Service: PaaS 2.0 I have successfully installed both the PowerShell and SXA modules, and they appear correctly in the CM instance.  But after restarting the CM Web App, both modules disappear from the CM instance, their config file is missing from the App_Service folder, and require reinstallation to complete the setup again. Here, I have used Sitecore CM instance Development Tools -> Installation Wizard to install the modules. Solution:  To investigate this issue further, I have checked the logs generated in Application Insights to confirm the installation. Additionally checked the traces and verified that the module is installed in the correct path: However...

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...

We had encounter the following error frequently in our application. Problem Id: System.NullReferenceException at Sitecore.SessionProvider.Redis.StackExchangeClientConnectionAsync+<EvalAsync>d__22.MoveNext Message: Object reference not set to an instance of an object. Exception type: System.NullReferenceException Failed method: Sitecore.SessionProvider.Redis.StackExchangeClientConnectionAsync+<EvalAsync>d__22.MoveNext Call Stack: StackExchange.Redis DLL version: 2.1.58 The application is deployed on Sitecore Managed Cloud Service Azure PaaS and uses Redis app service . I have applied the below fixes as well as the following articles but the issue is not resolved: Increased the min worker thread pool to 100 Increased polling Interval to 60 Tuned Redis Configuration as described here: Tuning Redis Configuration Settings Added sslprotocols=tls12 to Redis connection string Sitecore PAAS Redis Exce...