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.

When activating TDM Portal for PLA telemetry fails and we are stuck in a loop.


Article ID: 237494


Updated On:


CA Test Data Manager (Data Finder / Grid Tools)


We just did a clean install of TDM Portal 4.10 on a windows 2019 server using SQL Server 2016.
When we try to log into the portal for the first time we are being asked to activate the PLA information.
When we provide the PLA information the telemetry fails to configure and it starts the process over again.

How can we correct this?


There is a problem with the event services service


TDM Portal 4.10
test data manager


1) stop the TDM Portal service
2) Go to the webapps directory 
default location:
 C:\Program Files\CA\CA Test Data Manager Portal\tomcat\webapps
3) delete all folders except ROOT
4) Start the TDM Portal service and test again.

Additional Information

From the startup logs:
FINEST|5888/0|22-03-22 09:18:35|WARNING: Error of type 404 occurred while sending queue event
FINEST|5888/0|22-03-22 09:18:35| Failed to post event, returned response code was 404 and reason 
FINEST|5888/0|22-03-22 09:18:35|        at
FINEST|5888/0|22-03-22 09:18:35|        at
FINEST|5888/0|22-03-22 09:18:35|        at$
FINEST|5888/0|22-03-22 09:18:35|        at java.util.TimerThread.mainLoop(
FINEST|5888/0|22-03-22 09:18:35|        at

from the event service logs

Wrapped by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usage_flyway' defined in class path resource [com/ca/tdm/usage/config/UsageFlywayConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.flywaydb.core.Flyway]: Factory method 'usageFlyway' threw exception; nested exception is org.flywaydb.core.internal.dbsupport.FlywaySqlException: 
Unable to check whether table [dbo].[schema_version_usage] exists
SQL State  : 40001
Error Code : 1205
Message    : Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.