Himmat Singh Dulawat (3x Sitecore MVP)

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