I created and installed certificate in my SQL Server 2017 (used CREATE CERTIFICATE MyCertificate FROM BINARY) and signed my assemblies, based on what described here: Impact of CLR Strict Security configuration setting in SQL Server 2017.
Everything worked fine for about 2 years but suddenly I'm getting the 'clr strict security' exception again -
CREATE or ALTER ASSEMBLY for assembly 'MyAssembly' with the SAFE or EXTERNAL_ACCESS option failed because the 'clr strict security' option of sp_configure is set to 1. Microsoft recommends that you sign the assembly with a certificate or asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission. Alternatively, you can trust the assembly using sp_add_trusted_assembly.
My certificates and assembly didn't change (the certificate expiration is set to - "2022-12-20 12:00:00.000"). What could be the cause?