UMP not loading correctly

Document ID : KB000074776
Last Modified Date : 31/05/2018
Show Technical Document Details
Issue:
From wasp.log:

Mar 21 00:56:24:518 ERROR [localhost-startStop-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] listenerStart() Exception sending context initialized event to listener instance of class com.liferay.portal.spring.context.PortalContextLoaderListener

Mar 21 00:56:24:518 ERROR [localhost-startStop-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.spring.aop.ServiceBeanAutoProxyCreator#0' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve reference to bean 'counterTransactionAdvice' while setting bean property 'methodInterceptor';

nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'counterTransactionAdvice' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve reference to bean 'counterTransactionManager' while setting bean property 'platformTransactionManager';

nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'counterTransactionManager' defined in class path resource [META-INF/hibernate-spring.xml]: Cannot resolve reference to bean 'counterHibernateSessionFactory' while setting constructor argument;

nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'counterHibernateSessionFactory' defined in class path resource [META-INF/hibernate-spring.xml]: Invocation of init method failed;
Environment:
UMP 8.51 and SQL Server enabled Windows authentication.
Cause:
Wasp probe does not have access to SQL Server using Windows authentication
Resolution:
Change Nimsoft Robot Watcher service account in UMP server to a domain account with proper permissions on UIM database (CA_UIM) and UR database(unifiedreporter).

Restart nimsoft service in UMP server.

 
Additional Information:
This could also be a password change issue or any issue that causes wasp probe not connecting to db.