ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Application not working - problems with ED

book

Article ID: 240084

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Hi team,


Service virtualization is inactive.
The "Log" service does not start and reports issues with Enterprise Dashboard.

The enterprise dashboard log has the following errors:
In the ED logs we are seeing the following:
2022-04-21 21:59:39,343Z (18:59) [main] INFO  dradis.DradisInitBean          - Database Driver Version: 4.0.2206.100
2022-04-21 21:59:40,627Z (18:59) [main] INFO  com.ca.dradis.db.FlywayDbMigration - Schema Version: 17
2022-04-21 21:59:42,961Z (18:59) [main] WARN  org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'beanProcessor': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ca.dradis.BeanProcessor]: Constructor threw exception; nested exception is org.mapdb.DBException$GetVoid: Record does not exist, recid=145592
2022-04-21 21:59:43,148Z (18:59) [main] ERROR org.springframework.boot.SpringApplication - Application startup failed

Please, we need support ASAP.

 

Cause

a file in the lisa_temp Directory has become corrupted.

Environment

Devetst 10.6.X 10.7.x
 DevTest Enterprise Dashboard

Service virtualization

Resolution

It looks like there is a corrupt local file on your ED server.
We can not explain how it became corrupted but below is the solution:

Stop ED
Delete the file <\DevTest?\lisatmp_10.X.0\messageStore\objstore.dat
Start ED

Example location:
E:\CA\DevTest\lisatmp_10.6.0\messageStore\objstore.dat

Or you can just STOP ED and then delete the entire temp directory and start it again and this should resolve the issue.