Sitecore 10.4.1 is finally here! Everyone's excited about the new release—but with every update, sometimes surprises sneak in. And we’ve got one such story for you. This happened on a Sitecore 10.4.0 instance running in an Azure Kubernetes Service (AKS) cluster. One day, a fellow Sitecorian reached out to me and told that things just… broke. The Problem He said it was supposed to be a normal release. A developer pushed changes, the pipeline ran, and then— boom —errors everywhere. So we started looking into it. For your context, we got the below error - The Analysis Our First Guess: Maybe It’s the Code? We thought maybe the issue was in the new Pull Request (PR). We checked the changes, but everything looked okay. Just to be sure, we reverted the PR and tried the release again. Same error. Then we tried releasing an older build (before the error started). That one worked just fine. So now we knew—this wasn’t caused by code changes. The Solution Soon, w...
If you are restoring a database on your local or if you have forgotten your admin password to Sitecore, you can default it back to admin/b. To do so, copy and run the sql below - UPDATE [aspnet_Membership] SET [Password] = 'qOvF8m8F2IcWMvfOBjJYHmfLABc=' , [PasswordSalt] = 'OM5gu45RQuJ76itRvkSPFw==' , [IsApproved] = '1' , [IsLockedOut] = '0' WHERE UserId IN ( SELECT UserId FROM dbo.aspnet_Users WHERE UserName = 'sitecore\Admin' ) The above query also unlocks your account if it was locked due to wrong password attempts. Now you can log into Sitecore using the credentials username - admin and password - b . This query works on all versions of Sitecore, including 8, 9, 10.1, 10.2, and 10.3.