After updating to SAS Viya 2024.02 or later, sas-microanalytic-score pods might fail to start successfully. Additional symptoms of this issue include the following:

• A Kubernetes command line tool (kubectl) might report the sas-microanalytic-score pods as being in the CrashLoopBackOff state.
• The log from sas-microanalytic-score pods might contain the following warning:

WARN 7 — [ main] ConfigServletWebServerApplicationContext : service Exception encountered during context initialization - cancelling refresh attempt: 
org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'cacheSynchronizer': Unsatisfied dependency expressed through field 'synchronizationHelper'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'synchronizationHelper': Unsatisfied dependency expressed through field 'masCRUDOperationsService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'MASCRUDOperationsService': Unsatisfied dependency expressed through field 'delegate'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'MASCRUDOperationsImpl': Unsatisfied dependency expressed through field 'moduleManager'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'moduleManager': Unsatisfied dependency expressed through field 'masNativeService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'MASNativeService': Unsatisfied dependency expressed through field 'masCoreFactory'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'MASCoreFactory': Unsatisfied dependency expressed through field 'masHistoryTaskScheduler'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'MASHistoryTaskScheduler': Unsatisfied dependency expressed through field 'publisher'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'MASHistoryPublisher': Unsatisfied dependency expressed through field 'masEventPublisher'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: 
Error creating bean with name 'MASEventPublisher': Unsatisfied dependency expressed through field 'publisher'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'com.sas.event.api.producer.EventPublisher' available: expected at least 1 bean which qualifies as autowire candidate. 

SAS^® Micro Analytic Service released in SAS Viya 2024.02 and later is not compatible with the sas.event.enabled=false system property. sas.event.enabled=false is not a default system property, but it is a system property that is often manually set in earlier versions of SAS Micro Analytic Service. If the system property is set for an earlier version, and then you update the environment to 2024.02 or later, this issue occurs.

Workaround

To work around this issue, using SAS^® Environment Manager, navigate to Configuration ► Definitions ► JVM ► Micro Analytic Score service. Then, remove the sas.event.enabled=false system property. You can also set the system property to true (sas.event.enabled=true) as an alternative to removing the sas.event.enabled=false system property.

A fix for this issue is planned for a future software release.