No bean named importRegistry: On prem Jamf Pro not starting after update to 10.37.2

ops-accounts
New Contributor

No bean named 'org.springframework.context.annotation.ConfigurationClassPostProcessor.importRegistry' available.

Resulting in a failed startup showing an error message "No database connection". We have verified that our problem isn't related to the issue with " duplicate computer management Check-In settings".

 

2022-04-04 09:10:08,335 [ERROR] [Thread-3   ] [JssDispatcherServlet     ] - Context initialization failed

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'legacyMdmControllerProcessorImpl' defined in file [/usr/local/jss/tomcat/webapps/ROOT/WEB-INF/classes/com/jamfsoftware/mdm/jss/controller/LegacyMdmControllerProcessorImpl.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportService' defined in file [/usr/local/jss/tomcat/webapps/ROOT/WEB-INF/classes/com/jamfsoftware/jss/objects/report/ReportService.class]: BeanPostProcessor before instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'metaDataSourceAdvisor': Cannot resolve reference to bean 'methodSecurityMetadataSource' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.jamfsoftware.security.core.config.MethodSecurityConfiguration': Initialization of bean failed; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.springframework.context.annotation.ConfigurationClassPostProcessor.importRegistry' available

0 REPLIES 0